syslog entries

[aconticisco]

Hello,

I am getting repetitive entries please see below :

08-26-2011    07:40:44    Local7.Critical    192.168.1.2    37905: -Traceback= 0x80695558 0x8014A084 0x8014B5E0 0x807E3160 0x80693A74 0x80695F14 0x8069616C 0x80C13A58 0x80C153A8 0x80C15A88 0x80C17748 0x8008B2F0 0x8005A0D4 0x80061F58 0x80068C58 0x8005EBDC

08-26-2011    07:40:44    Local7.Critical    192.168.1.2    37904: -Process= "<interrupt level>", ipl= 6

08-26-2011    07:40:44    Local7.Critical    192.168.1.2    37903: *Mar  1 17:50:11.515: %SYS-2-GETBUFFFAIL: Small buffer allocation (3 bytes) failed from 0x807E315C

what are these ?

Thanks!

[raga.fusionet]

Hi,

If you have a CCO user try uploading this into the Output interpreter tool preceeded with a show ver.

Traceback= 0x80695558 0x8014A084 0x8014B5E0 0x807E3160 0x80693A74  0x80695F14 0x8069616C 0x80C13A58 0x80C153A8 0x80C15A88 0x80C17748  0x8008B2F0 0x8005A0D4 0x80061F58 0x80068C58 0x8005EBDC

https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl

In some case the output interpreter would give you an idea of what's wrong. You can also try looking at the log messages right before and after the traceback and see if it gives you any hints.

I none of that works you might need to open a TAC case.

HTH.

Raga

[Richard Burts]

I can not say specifically what these messages are about, but in general a traceback is a sign of a software problem.

As Raga points out you might find information from the Output Interpreter, and a case with the TAC is a good approach (assuming that you are able to open TAC cases). Another approach could be to plan to try a different version of code and see if the messages go away.

HTH

Rick