871w locked/attack?

Unanswered Question
Feb 21st, 2009
User Badges:

Hi,


after 3-4 days running my new config I got this serious error which locked up the Cisco completely; sounds to me like a loop in the DNS Resolver... maybe an attack?


2009-02-21 13:46:22 Syslog.Critical 192.168.1.1 72: 000067: Feb 21 13:46:20.960 UST: %SYS-2-NOTQ: unqueue didn't find 844B1D2C in queue 8268FDD0 -Process= "DNS Resolver", ipl= 0, pid= 3, -Traceback= 0x807D8E04 0x8003BAA4 0x807F7358 0x80C60470 0x80C606AC 0x80C60BEC 0x800225CC 0x80025710

2009-02-21 13:47:04 Syslog.Error 192.168.1.1 73: 000068: Feb 21 13:47:03.744 UST: %ALIGN-3-SPURIOUS: Spurious memory access made at 0x807F82C8 reading 0x0

2009-02-21 13:47:04 Syslog.Error 192.168.1.1 74: 000069: Feb 21 13:47:03.744 UST: %ALIGN-3-TRACE: -Traceback= 0x807F82C8 0x807F8860 0x81A2CED4 0x807FA440 0x812EED64 0x803BAD58 0x800225CC 0x80025710

2009-02-21 13:47:04 Syslog.Error 192.168.1.1 75: 000070: Feb 21 13:47:03.744 UST: %ALIGN-3-TRACE: -Traceback= 0x807F82D0 0x807F8860 0x81A2CED4 0x807FA440 0x812EED64 0x803BAD58 0x800225CC 0x80025710

2009-02-21 13:47:04 Syslog.Error 192.168.1.1 76: 000071: Feb 21 13:47:03.744 UST: %ALIGN-3-TRACE: -Traceback= 0x812BEBA8 0x807F82E0 0x807F8860 0x81A2CED4 0x807FA440 0x812EED64 0x803BAD58 0x800225CC

2009-02-21 13:47:05 Syslog.Error 192.168.1.1 77: 000072: Feb 21 13:47:03.744 UST: %ALIGN-3-TRACE: -Traceback= 0x812BEBAC 0x807F82E0 0x807F8860 0x81A2CED4 0x807FA440 0x812EED64 0x803BAD58 0x800225CC

2009-02-21 13:47:05 Syslog.Error 192.168.1.1 78: 000073: Feb 21 13:47:03.744 UST: %ALIGN-3-TRACE: -Traceback= 0x812BEBB0 0x807F82E0 0x807F8860 0x81A2CED4 0x807FA440 0x812EED64 0x803BAD58 0x800225CC

2009-02-21 13:47:05 Syslog.Error 192.168.1.1 79: 000074: Feb 21 13:47:03.748 UST: %ALIGN-3-TRACE: -Traceback= 0x812BE0E4 0x807F8348 0x807F8860 0x81A2CED4 0x807FA440 0x812EED64 0x803BAD58 0x800225CC

2009-02-21 13:47:05 Syslog.Error 192.168.1.1 80: 000075: Feb 21 13:47:03.748 UST: %ALIGN-3-TRACE: -Traceback= 0x812BE0E8 0x807F8348 0x807F8860 0x81A2CED4 0x807FA440 0x812EED64 0x803BAD58 0x800225CC

2009-02-21 13:49:15 Syslog.Error 192.168.1.1 81: 000076: Feb 21 13:47:10.250 UST: %SYS-3-CPUHOG: Task is running for (5000)msecs, more than (5000)msecs (118/101),process = Appfw IM DNS Resolver.

2009-02-21 13:49:15 Syslog.Error 192.168.1.1 82: -Traceback= 0x812CA09C 0x807F85F8 0x80C5EDA4 0x8175FF60 0x81760634 0x800225CC 0x80025710

2009-02-21 13:49:15 Syslog.Error 192.168.1.1 83: 000077: Feb 21 13:47:15.264 UST: %SYS-3-CPUHOG: Task is running for (10000)msecs, more than (5000)msecs (122/101),process = Appfw IM DNS Resolver.

2009-02-21 13:49:15 Syslog.Error 192.168.1.1 84: -Traceback= 0x81A55B50 0x807F8608 0x80C5EDA4 0x8175FF60 0x81760634 0x800225CC 0x80025710

2009-02-21 13:49:15 Syslog.Error 192.168.1.1 85: 000078: Feb 21 13:47:20.287 UST: %SYS-3-CPUHOG: Task is running for (15000)msecs, more than (5000)msecs (128/101),process = Appfw IM DNS Resolver.

2009-02-21 13:49:15 Syslog.Error 192.168.1.1 86: -Traceback= 0x81A55B3C 0x807F8608 0x80C5EDA4 0x8175FF60 0x81760634 0x800225CC 0x80025710

2009-02-21 13:49:15 Syslog.Error 192.168.1.1 87: 000079: Feb 21 13:47:25.350 UST: %SYS-3-CPUHOG: Task is running for (20000)msecs, more than (5000)msecs (144/101),process = Appfw IM DNS Resolver.

2009-02-21 13:49:15 Syslog.Error 192.168.1.1 88: -Traceback= 0x81A5671C 0x807F8530 0x80C5EDA4 0x8175FF60 0x81760634 0x800225CC 0x80025710

2009-02-21 13:49:15 Syslog.Error 192.168.1.1 89: 000080: Feb 21 13:47:30.376 UST: %SYS-3-CPUHOG: Task is running for (25000)msecs, more than (5000)msecs (151/101),process = Appfw IM DNS Resolver.

2009-02-21 13:49:15 Syslog.Error 192.168.1.1 90: -Traceback= 0x81A55B3C 0x807F8608 0x80C5EDA4 0x8175FF60 0x81760634 0x800225CC 0x80025710

2009-02-21 13:49:15 Syslog.Error 192.168.1.1 91: 000081: Feb 21

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Haris P Sat, 02/21/2009 - 05:45
User Badges:
  • Bronze, 100 points or more

Hi ,



most of the Issues will be related with IOS ,try changing to different bug free IOS



Also please post the full config .


Regards

Haris

berndkunrath Sat, 02/21/2009 - 06:04
User Badges:

Hi Haris,


the IOS is really new i think:


CiscoKunr#show version

Cisco IOS Software, C870 Software (C870-ADVSECURITYK9-M), Version 12.4(15)T7, RE

LEASE SOFTWARE (fc3)

Technical Support: http://www.cisco.com/techsupport

Copyright (c) 1986-2008 by Cisco Systems, Inc.

Compiled Thu 14-Aug-08 07:43 by prod_rel_team


ROM: System Bootstrap, Version 12.3(8r)YI4, RELEASE SOFTWARE


CiscoKunr uptime is 54 minutes

System returned to ROM by power-on

System restarted at 14:02:10 UST Sat Feb 21 2009

System image file is "flash:c870-advsecurityk9-mz.124-15.T7.bin"


And attached you'll find the config.


Ciao, Bernd



berndkunrath Sat, 02/21/2009 - 06:40
User Badges:

Hi,


happened again, seems to be even more serious than I thought!


2009-02-21 15:20:02 Cron.Notice ESXi crond[1287]: USER root pid 20281098 cmd /sbin/decodeSel.sh #Every 10 minutes, translate the latest IPMI SEL data

2009-02-21 15:23:06 Syslog.Critical 192.168.1.1 62: 000058: Feb 21 15:23:05.279 UST: %SYS-2-NOTQ: unqueue didn't find 83DABDDC in queue 8268FDD0 -Process= "DNS Resolver", ipl= 0, pid= 3, -Traceback= 0x807D8E04 0x8003BAA4 0x807F7358 0x80C60470 0x80C606AC 0x80C60BEC 0x800225CC 0x80025710

2009-02-21 15:23:12 Syslog.Error 192.168.1.1 63: 000059: Feb 21 15:23:11.850 UST: %ALIGN-3-SPURIOUS: Spurious memory access made at 0x807F82C8 reading 0x0

2009-02-21 15:23:12 Syslog.Error 192.168.1.1 64: 000060: Feb 21 15:23:11.854 UST: %ALIGN-3-TRACE: -Traceback= 0x807F82C8 0x807F8860 0x81A2CED4 0x807FA440 0x812EED64 0x803BAD58 0x800225CC 0x80025710

2009-02-21 15:23:12 Syslog.Error 192.168.1.1 65: 000061: Feb 21 15:23:11.854 UST: %ALIGN-3-TRACE: -Traceback= 0x807F82D0 0x807F8860 0x81A2CED4 0x807FA440 0x812EED64 0x803BAD58 0x800225CC 0x80025710

2009-02-21 15:23:12 Syslog.Error 192.168.1.1 66: 000062: Feb 21 15:23:11.854 UST: %ALIGN-3-TRACE: -Traceback= 0x812BEBA8 0x807F82E0 0x807F8860 0x81A2CED4 0x807FA440 0x812EED64 0x803BAD58 0x800225CC

2009-02-21 15:23:13 Syslog.Error 192.168.1.1 67: 000063: Feb 21 15:23:11.854 UST: %ALIGN-3-TRACE: -Traceback= 0x812BEBAC 0x807F82E0 0x807F8860 0x81A2CED4 0x807FA440 0x812EED64 0x803BAD58 0x800225CC

2009-02-21 15:23:13 Syslog.Error 192.168.1.1 68: 000064: Feb 21 15:23:11.854 UST: %ALIGN-3-TRACE: -Traceback= 0x812BEBB0 0x807F82E0 0x807F8860 0x81A2CED4 0x807FA440 0x812EED64 0x803BAD58 0x800225CC

2009-02-21 15:23:13 Syslog.Error 192.168.1.1 69: 000065: Feb 21 15:23:11.854 UST: %ALIGN-3-TRACE: -Traceback= 0x812BE0E4 0x807F8348 0x807F8860 0x81A2CED4 0x807FA440 0x812EED64 0x803BAD58 0x800225CC

2009-02-21 15:23:13 Syslog.Error 192.168.1.1 70: 000066: Feb 21 15:23:11.854 UST: %ALIGN-3-TRACE: -Traceback= 0x812BE0E8 0x807F8348 0x807F8860 0x81A2CED4 0x807FA440 0x812EED64 0x803BAD58 0x800225CC

2009-02-21 15:25:18 Local7.Warning SRW2016 %LINK-W-Down: g9


Leo Laohoo Sat, 02/21/2009 - 16:49
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 LAN, Wireless

If you're getting a Traceback error, it can only mean either an IOS bug or a possible hardware failure.


Try to use the previous version you are currently using now.

Actions

This Discussion