OK, that is solved too, I think, but still getting a series of errors:
94.229.14.250 clogin error: Error: TIMEOUT reached
94.229.14.250: missed cmd(s): show stack,show module,show flash,show version,show system-information,write term,show system information
94.229.14.250: End of run not found
;
94.229.11.218: missed cmd(s): show configuration
94.229.11.218: End of run not found
;
;
;
Getting missed routers: round 4.
Received signal - ending run (1).
/usr/lib/rancid/bin/control_rancid: 461: /usr/lib/rancid/bin/control_rancid: cannot create /tmp/tmp.EACqI3Q2IP/rancid.MVSNetwork.14801.diff: Directory nonexistent
cvs diff: Diffing .
cvs diff: Diffing configs
cvs commit: Examining .
cvs commit: Examining configs
Regards,
Ryan Milton
MVS Network Manager
o: 201-447-1505 x124
c: 862-249-5230
www.mvsusa.com<http://www.mvsusa.com/>
[MVS final logo GOOD very small]
From: Hinote, Scotty (MSFC-IS40)[NICS] [mailto:***@nasa.gov]
Sent: Friday, September 13, 2013 10:44 AM
To: Ryan Milton; Aaron Dudek
Cc: rancid-***@shrubbery.net
Subject: RE: [rancid] Permissions errors
You can set autoenable X.X.X.X 1 in your cloginrc stanzas. Or you can specify your enable password on the same line as your password as password X.X.X.X {password} {enable_password}.
From: Ryan Milton [mailto:***@mvsusa.com]
Sent: Friday, September 13, 2013 9:41 AM
To: Hinote, Scotty (MSFC-IS40)[NICS]; Aaron Dudek
Cc: rancid-***@shrubbery.net<mailto:rancid-***@shrubbery.net>
Subject: RE: [rancid] Permissions errors
I'm wondering, if the issue may have to do with the login procedure. Typically we login directly into enable mode, not into operator mode. If the script is looking to do it the traditional way, would that cause the error too?
Because, I can login via ssh to the HP switch in question from the rancid sever.
When I run this script (vs an ssh -v login that works):
/usr/lib/rancid/bin/hlogin -f /var/lib/rancid/.cloginrc 94.2
94.229.11.92
Error: no enable password for 94.229.11.92 in /var/lib/rancid/.cloginrc.
Regards,
Ryan Milton
MVS Network Manager
o: 201-447-1505 x124
c: 862-249-5230
www.mvsusa.com<http://www.mvsusa.com/>
[MVS final logo GOOD very small]
From: Hinote, Scotty (MSFC-IS40)[NICS] [mailto:***@nasa.gov]
Sent: Friday, September 13, 2013 10:31 AM
To: Ryan Milton; Aaron Dudek
Cc: rancid-***@shrubbery.net<mailto:rancid-***@shrubbery.net>
Subject: RE: [rancid] Permissions errors
Timeout reached usually indicates that the server is not able to establish a connection to the device due to routing, firewall, etc. Try SSHing from the rancid server to the device eg. ssh ***@device. Do not use the login scripts. You can also increase the verbose output of SSH by specifying the -v flag. If you cannot SSH to the device then the rancid scripts will not work either but it rules out rancid as the issue.
From: Ryan Milton [mailto:***@mvsusa.com]
Sent: Friday, September 13, 2013 9:24 AM
To: Aaron Dudek; Hinote, Scotty (MSFC-IS40)[NICS]
Cc: rancid-***@shrubbery.net<mailto:rancid-***@shrubbery.net>
Subject: RE: [rancid] Permissions errors
Ok, I attempted this a few times:
Trying to get all of the configs.
94.229.11.92 clogin error: Error: TIMEOUT reached
94.229.11.92: missed cmd(s): show stack,show module,show flash,show version,show system-information,write term,show system information
94.229.11.92: End of run not found
And then the /.MVSNetwork.run.lock happens again
Regards,
Ryan Milton
MVS Network Manager
o: 201-447-1505 x124
c: 862-249-5230
www.mvsusa.com<http://www.mvsusa.com/>
[MVS final logo GOOD very small]
From: Aaron Dudek [mailto:***@gmail.com]
Sent: Friday, September 13, 2013 9:57 AM
To: Hinote, Scotty (MSFC-IS40)[NICS]
Cc: Ryan Milton; rancid-***@shrubbery.net<mailto:rancid-***@shrubbery.net>
Subject: Re: [rancid] Permissions errors
+1
On Fri, Sep 13, 2013 at 9:51 AM, Hinote, Scotty (MSFC-IS40)[NICS] <***@nasa.gov<mailto:***@nasa.gov>> wrote:
[cid:***@01CEB077.B4D8B1A0]
I would try removing the lock file and execute rancid-run again.
From: rancid-discuss-***@shrubbery.net<mailto:rancid-discuss-***@shrubbery.net> [mailto:rancid-discuss-***@shrubbery.net<mailto:rancid-discuss-***@shrubbery.net>] On Behalf Of Ryan Milton
Sent: Friday, September 13, 2013 8:46 AM
To: rancid-***@shrubbery.net<mailto:rancid-***@shrubbery.net>
Subject: [rancid] Permissions errors
What is the possible solution to this:
Is this yet another permissions issue?
hourly config diffs failed: /tmp/.MVSNetwork.run.lock exists
-rw-r----- 1 rancid rancid 0 Sep 12 17:08 /tmp/.MVSNetwork.run.lock
Regards,
Ryan Milton
MVS Network Manager
o: 201-447-1505 x124
c: 862-249-5230
www.mvsusa.com<http://www.mvsusa.com/>
[MVS final logo GOOD very small]