[rancid] Re: Issues with rancid not collecting configs

john heasley heas at shrubbery.net
Tue Jan 12 21:07:08 UTC 2010 

Tue, Jan 12, 2010 at 07:53:56AM -0500, Gallardo, Winfred C:
> read(4, "Image           Size(Bytes)   Da"..., 4096) = 190
> read(4, "Boot Rom Version: K.12.20\r\r\nDefa"..., 4096) = 82
> read(4, " show system-information\r\r\n", 4096) = 27
> read(4, "Invalid input: system-informatio"..., 4096) = 59
> lseek(4, 771, SEEK_SET)                 = -1 ESPIPE (Illegal seek)
> close(4)                                = 0
> rt_sigaction(SIGHUP, {0x1, [], SA_RESTORER, 0x330b40e7c0}, {SIG_DFL, [], 0}, 8) = 0
> rt_sigaction(SIGINT, {0x1, [], SA_RESTORER, 0x330b40e7c0}, {SIG_DFL, [], 0}, 8) = 0
> rt_sigaction(SIGQUIT, {0x1, [], SA_RESTORER, 0x330b40e7c0}, {SIG_DFL, [], 0}, 8) = 0
> wait4(24119, [{WIFEXITED(s) && WEXITSTATUS(s) == 1}], 0, NULL) = 24119
> --- SIGCHLD (Child exited) @ 0 (0) ---

the clues are there.  if you had used the option to follow children, you'd
get more clues.

> On Jan 6, 2010, at 12:41 PM, john heasley wrote:
> 
> > Wed, Jan 06, 2010 at 10:50:34AM -0500, Gallardo, Winfred C:
> >> i'm having trouble diagnosing why rancid is having trouble collecting configs on HP procurve 5412.
> >>
> >>
> >> I get the expected out put when running
> >>
> >> hlogin -c 'show config' xx.xx.xx.xx
> >>
> >>
> >> i checked my rancid log files and i'm not sure
> >> what all the lines mean for the errors.
> >>
> >> here is a sample.
> >>
> >> Trying to get all of the configs.
> >> write(spawn_id=1): broken pipe
> >>    while executing
> >> "send_user -- "$expect_out(buffer)""
> >
> > its an expect/tcl trace.  the relevant parts are 'broken pipe' and
> > send_user, which seem indicate that hrancid or hpuifilter exited
> > prematurely.  are they getting killed?  dumping core?  tried runing
> > hrancid manually?  ktrace/truss/strace it?
> >
> >>    invoked from within
> >> "expect -nobrace -re {^[^
> >> *]*BL579-DC-Ent-R6-AJ32-1#} { send_user -- "$expect_out(buffer)"
> >>                                              } -re {^[^
> >> ]*BL579-DC-Ent-R6-AJ32-1#.} { send_user ..."
> >>    invoked from within
> >> "expect {
> >>              -re "^\[^\n\r *]*$reprompt"     { send_user -- "$expect_out(buffer)"
> >>                                              }
> >>              -re "^\[^\n\r]*$reprompt."      { send_user -- "$expect_out(buffer)"
> >> ..."
> >>    invoked from within
> >> "if [ string match "*\;*" "$command" ] {
> >>      set commands [split $command \;]
> >>      set num_commands [llength $commands]
> >>      # the pager can not be turned off on ..."
> >>    (procedure "run_commands" line 17)
> >>    invoked from within
> >> "run_commands $prompt $command"
> >>    ("foreach" body line 136)
> >>
> >>
> >>
> >> Please let me know what other commands i can try to see where the errors are coming from.
> >>
> >> Thanks in advance,
> >>
> >>
> >> Chris Gallardo
> >> Network Services
> >> 278-9067
> >> wcgallar at iupui.edu
> >>
> >>
> >>
> >> On Dec 23, 2009, at 12:04 PM, Chris Gauthier wrote:
> >>
> >>> While I should be able to follow that path, the only result available is "8.2(1)" and it does not get more specific than that.  Here is an excerpt from the site:
> >>>
> >>> asa821-k8.bin
> >>> Release Date: 06/May/2009
> >>> Cisco Adaptive Security Appliance Software version 8.2(1) for the ASA 5505, 5510, 5520, 5540, and ASA5550. Please read the Release Note prior to downloading this release.
> >>> Size: 15894.00 KB  (16275456 bytes)
> >>>
> >>>
> >>> However, Cisco also has, in a different spot (now that I notice it differently), an 8.2.1.ED and then 8.2.1.11.  ugh....  Sometimes Cisco really frustrates me.
> >>>
> >>> I'll be changing to 8.2.1.11 vs the 8.2.1.4 given me by the TAC.
> >>>
> >>> Chris
> >>>
> >>>
> >>>
> >>> From: P C [mailto:pc50000 at gmail.com]
> >>> Sent: Wednesday, December 23, 2009 8:50 AM
> >>> To: Chris Gauthier
> >>> Cc: rancid-discuss at shrubbery.net
> >>> Subject: Re: [rancid] Re: Cisco ASA Coredump bug--fixed yet?
> >>>
> >>> You should also be able to go to suppport  > download software > security > firweall > firewall appliances > cisco asa 55x0 > cisco asa software > drill down to 8.2, and 8.2.1.11 is posted and downloadable as a more TAC-posted and more thoroughly tested interim build.  It's been fixed since 8.2.1.2
> >>>
> >>>
> >>> On Tue, Dec 22, 2009 at 1:34 PM, Chris Gauthier <cgauthier at mapscu.com> wrote:
> >>> I went to Cisco.com and looked for the fixed versions and they were not
> >>> there.  So, even after my attempts to just "fix it", I still had to
> >>> contact the TAC for the files.  They set me up with version 8.2.1.4
> >>> (Interim).
> >>>
> >>> Thanks for pointing out the Bug ID, that made the case SUPER easy for me
> >>> to describe to TAC and for TAC to just give me what I needed.
> >>>
> >>> Chris
> >>>
> >>> -----Original Message-----
> >>> From: Ron Whitney [mailto:ron.whitney at doitbest.com]
> >>> Sent: Monday, December 21, 2009 3:37 PM
> >>> To: Chris Gauthier; rancid-discuss at shrubbery.net
> >>> Subject: RE: [rancid] Cisco ASA Coredump bug--fixed yet?
> >>>
> >>>
> >>>> Did anyone ever find a solution to the coredump bug on the
> >>>> Cisco ASA? Did TAC ever come back with anything?
> >>>
> >>> Here's the last status I received (about a week ago) on that bug:
> >>>
> >>> The following bug(s) you have subscribed to have been updated as
> >>> follows:
> >>>
> >>> ------------------------------------------------------------------------
> >>> ----------
> >>>
> >>> BugID: CSCsz85597
> >>> What Changed: Fixed in version
> >>> Title: coredump.cfg file gets rewritten every time show run is executed
> >>> Technology: nav
> >>> Version: 8.2(1)
> >>> Fixed-in: 8.2(1.2), 8.3(0.0), 100.3(0.3)M
> >>> Severity: 2
> >>> State: Verified
> >>> Bug Details:
> >>> http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method
> >>> =fetchBugDetails&bugId=CSCsz85597
> >>> _______________________________________________
> >>> Rancid-discuss mailing list
> >>> Rancid-discuss at shrubbery.net
> >>> http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss
> >>>
> >>> _______________________________________________
> >>> Rancid-discuss mailing list
> >>> Rancid-discuss at shrubbery.net
> >>> http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss
> >>
> >> _______________________________________________
> >> Rancid-discuss mailing list
> >> Rancid-discuss at shrubbery.net
> >> http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss

More information about the Rancid-discuss mailing list