1. Home
  2. Cisco Systems
  3. Help! Cisco 857 reloads when switched DNS server on :(

Help! Cisco 857 reloads when switched DNS server on :(

Can you shed some light on this?

My router reloads after activating the IOS DNS server. :(

Version 12.4T(15) T7

This is what I get:

01-06-2009 19:45:17 Local7.Error 192.168.1.1 127: 000105: Jan 6 19:45:13.636 GMT: %ALIGN-3-TRACE: -Traceback= 0x814BE558 0x8062EE48 0x8128B8B8 0x8010476C 0x801078B0 0x0 0x0 0x0 01-06-2009 19:45:17 Local7.Error 192.168.1.1 126: 000104: Jan 6 19:45:13.636 GMT: %ALIGN-3-TRACE: -Traceback= 0x814BF138 0x809B04DC 0x8062EE20 0x8128B8B8 0x8010476C 0x801078B0 0x0 0x0 01-06-2009 19:45:17 Local7.Error 192.168.1.1 125: 000103: Jan 6 19:45:13.636 GMT: %ALIGN-3-TRACE: -Traceback= 0x814BF138 0x8062ED70 0x8128B8B8 0x8010476C 0x801078B0 0x0 0x0 0x0 01-06-2009 19:45:17 Local7.Error 192.168.1.1 124: 000102: Jan 6 19:45:13.636 GMT: %ALIGN-3-TRACE: -Traceback= 0x814BE564 0x8062EE48 0x8128B8B8 0x8010476C 0x801078B0 0x0 0x0 0x0 01-06-2009 19:45:17 Local7.Error 192.168.1.1 123: 000101: Jan 6 19:45:13.636 GMT: %ALIGN-3-TRACE: -Traceback= 0x8062EC7C 0x8062F060 0x81289D90 0x8010476C 0x801078B0 0x0 0x0 0x0 01-06-2009 19:45:17 Local7.Error 192.168.1.1 122: 000100: Jan 6 19:45:13.636 GMT: %ALIGN-3-TRACE: -Traceback= 0x8062EC60 0x8062F060 0x81289D90 0x8010476C 0x801078B0 0x0 0x0 0x0 01-06-2009 19:45:17 Local7.Error 192.168.1.1 121: 000099: Jan 6 19:45:13.636 GMT: %ALIGN-3-TRACE: -Traceback= 0x8062EC7C 0x8062F060 0x812862E8 0x81289D90 0x8010476C 0x801078B0 0x0 0x0 01-06-2009 19:45:17 Local7.Error 192.168.1.1 120: 000098: Jan 6 19:45:13.636 GMT: %ALIGN-3-TRACE: -Traceback= 0x8062EC60 0x8062F060 0x812862E8 0x81289D90 0x8010476C 0x801078B0 0x0 0x0 01-06-2009 19:45:17 Local7.Error 192.168.1.1 119: 000097: Jan 6 19:45:13.636 GMT: %ALIGN-3-TRACE: -Traceback= 0x8062EC7C 0x8062F048 0x81289D90 0x8010476C 0x801078B0 0x0 0x0 0x0 01-06-2009 19:45:17 Local7.Error 192.168.1.1 118: 000096: Jan 6 19:45:13.636 GMT: %ALIGN-3-TRACE: -Traceback= 0x8062EC60 0x8062F048 0x81289D90 0x8010476C 0x801078B0 0x0 0x0 0x0 01-06-2009 19:45:17 Local7.Error 192.168.1.1 117: 000095: Jan 6 19:45:13.632 GMT: %ALIGN-3-TRACE: -Traceback= 0x8062EC7C 0x8062F048 0x812862E8 0x81289D90 0x8010476C 0x801078B0 0x0 0x0 01-06-2009 19:45:17 Local7.Error 192.168.1.1 116: 000094: Jan 6 19:45:13.632 GMT: %ALIGN-3-TRACE: -Traceback= 0x8062EC60 0x8062F048 0x812862E8 0x81289D90 0x8010476C 0x801078B0 0x0 0x0 01-06-2009 19:45:17 Local7.Error 192.168.1.1 115: 000093: Jan 6 19:45:13.632 GMT: %ALIGN-3-SPURIOUS: Spurious memory access made at 0x8062EC60 reading 0x0 01-06-2009 19:45:17 Local7.Error 192.168.1.1 114:

-Traceback= 0x814BF13C 0x809B04DC 0x8062EE20 0x8128B8B8 0x8010476C

0x801078B0 01-06-2009 19:45:17 Local7.Error 192.168.1.1 113: 000092: Jan 6 19:45:13.564 GMT: %SYS-3-CPUHOG: Task is running for (85000)msecs, more than (5000)msecs (214/4),process = DNS Server. 01-06-2009 19:45:17 Local7.Error 192.168.1.1 112:

-Traceback= 0x814BF13C 0x809B04DC 0x8062EE20 0x8128B8B8 0x8010476C

0x801078B0 01-06-2009 19:45:17 Local7.Error 192.168.1.1 111: 000091: Jan 6 19:45:08.500 GMT: %SYS-3-CPUHOG: Task is running for (80000)msecs, more than (5000)msecs (198/4),process = DNS Server. 01-06-2009 19:45:17 Local7.Error 192.168.1.1 110:

-Traceback= 0x814BF13C 0x8062ED70 0x8128B8B8 0x8010476C 0x801078B0

01-06-2009 19:45:17 Local7.Error 192.168.1.1 109: 000090: Jan 6 19:45:03.440 GMT: %SYS-3-CPUHOG: Task is running for (75000)msecs, more than (5000)msecs (183/4),process = DNS Server. 01-06-2009 19:45:17 Local7.Error 192.168.1.1 108:

-Traceback= 0x814BF13C 0x809B04DC 0x8062EE20 0x8128B8B8 0x8010476C

0x801078B0 01-06-2009 19:45:17 Local7.Error 192.168.1.1 107: 000089: Jan 6 19:44:58.352 GMT: %SYS-3-CPUHOG: Task is running for (70000)msecs, more than (5000)msecs (161/4),process = DNS Server. 01-06-2009 19:45:17 Local7.Error 192.168.1.1 106:

-Traceback= 0x814BF13C 0x8062ED70 0x8128B8B8 0x8010476C 0x801078B0

01-06-2009 19:45:17 Local7.Error 192.168.1.1 105: 000088: Jan 6 19:44:53.308 GMT: %SYS-3-CPUHOG: Task is running for (65000)msecs, more than (5000)msecs (150/4),process = DNS Server. 01-06-2009 19:45:17 Local7.Error 192.168.1.1 104:

-Traceback= 0x814BE55C 0x8062EE48 0x8128B8B8 0x8010476C 0x801078B0

01-06-2009 19:45:17 Local7.Error 192.168.1.1 103: 000087: Jan 6 19:44:48.252 GMT: %SYS-3-CPUHOG: Task is running for (60000)msecs, more than (5000)msecs (136/4),process = DNS Server. 01-06-2009 19:45:17 Local7.Error 192.168.1.1 102:

-Traceback= 0x814BE55C 0x8062EE48 0x8128B8B8 0x8010476C 0x801078B0

01-06-2009 19:45:17 Local7.Error 192.168.1.1 101: 000086: Jan 6 19:44:43.196 GMT: %SYS-3-CPUHOG: Task is running for (55000)msecs, more than (5000)msecs (122/4),process = DNS Server. 01-06-2009 19:45:17 Local7.Error 192.168.1.1 100:

-Traceback= 0x814BF13C 0x8062ED70 0x8128B8B8 0x8010476C 0x801078B0

01-06-2009 19:45:17 Local7.Error 192.168.1.1 99: 000085: Jan 6 19:44:38.164 GMT: %SYS-3-CPUHOG: Task is running for (50000)msecs, more than (5000)msecs (114/4),process = DNS Server. 01-06-2009 19:45:17 Local7.Error 192.168.1.1 98:

-Traceback= 0x814BF13C 0x809B04DC 0x8062EE20 0x8128B8B8 0x8010476C

0x801078B0 01-06-2009 19:45:17 Local7.Error 192.168.1.1 97: 000084: Jan 6 19:44:33.096 GMT: %SYS-3-CPUHOG: Task is running for (45000)msecs, more than (5000)msecs (97/4),process = DNS Server. 01-06-2009 19:45:17 Local7.Error 192.168.1.1 96:

-Traceback= 0x814BF13C 0x8062ED70 0x8128B8B8 0x8010476C 0x801078B0

01-06-2009 19:45:17 Local7.Error 192.168.1.1 95: 000083: Jan 6 19:44:28.016 GMT: %SYS-3-CPUHOG: Task is running for (40000)msecs, more than (5000)msecs (77/4),process = DNS Server. 01-06-2009 19:45:17 Local7.Error 192.168.1.1 94:

-Traceback= 0x814BF13C 0x809B04DC 0x8062EE20 0x8128B8B8 0x8010476C

0x801078B0
Reply to
Goldrider
Loading thread data ...

.1.1 =A0 =A0 127:

.1.1 =A0 =A0 126:

.1.1 =A0 =A0 125:

.1.1 =A0 =A0 124:

.1.1 =A0 =A0 123:

.1.1 =A0 =A0 122:

.1.1 =A0 =A0 121:

.1.1 =A0 =A0 120:

.1.1 =A0 =A0 119:

.1.1 =A0 =A0 118:

.1.1 =A0 =A0 117:

.1.1 =A0 =A0 116:

.1.1 =A0 =A0 115:

.1.1 =A0 =A0 114:

.1.1 =A0 =A0 113:

.1.1 =A0 =A0 112:

.1.1 =A0 =A0 111:

.1.1 =A0 =A0 110:

.1.1 =A0 =A0 109:

.1.1 =A0 =A0 108:

.1.1 =A0 =A0 107:

.1.1 =A0 =A0 106:

.1.1 =A0 =A0 105:

.1.1 =A0 =A0 104:

.1.1 =A0 =A0 103:

.1.1 =A0 =A0 102:

.1.1 =A0 =A0 101:

.1.1 =A0 =A0 100:

.1.1 =A0 =A0 99:

.1.1 =A0 =A0 98:

.1.1 =A0 =A0 97:

.1.1 =A0 =A0 96:

.1.1 =A0 =A0 95:

.1.1 =A0 =A0 94:

T train is generally nowhere near as reliable as GD code, have you looked up this behavior on Cisco?

Reply to
Trendkill

I'll have look. I have added de the dns servers from opendns, it has not reloaded so far. I'll keep you posted.

Greetings.

Reply to
Goldrider

or =3DA0 =3DA0192.168=3D

Here is the link, hopefully you have a CCO account:

formatting link
I pasted in the %align error but it said it references a previous error. I plugged in the CPU error and here is what it says: The specified process ran for too long without relinquishing the processor. Each process should run for only a small amount of time before relinquishing the processor so that other processes can run. This problem can be caused by many conditions such as traffic, system load, hardware, operational configuration, a configuration change, initialization of many interfaces, a high momentary error rate, or a sustained abnormal condition.

Recommendations are that you probably want to toss it into the bug toolkit and provide your IOS. Either way plenty of info on there for you to dig through.

Reply to
Trendkill

Well this is a bug (or two.) One aspect is that the DNS server was not very CPU efficient till CSCsg64586 (in 12.4(20)T). However, that won't help you on the 850 whose final resting branch is 12.4(15)T. (Btw, the 12.4(15)T throttle *is* the current equivalent of mainline IOS.)

So I would recommend that you open a TAC case and get the TAC engineer to decode your ALIGN and CPUHOG tracebacks and see what bug(s) apply and to get the fixes patched into 12.4(15)T.

Cheers,

Aaron

Reply to
Aaron Leonard

What are you doing with the dns server?

If you dont *need* it turn it off, I would sugest:)

You might care to look at the memory use, if you have a lot of diffrent internet targets perhaps it is using up a lot or memory.

It would not be so surprising if this router failed to deal with a very large table of DNS entries.

If you are desperate to keep it on and while you wait on TAC you might care to check for a lot of buffer failures or misses and manually increase buffers 'til they more or less go away - or of course untill you think you are using too much memory. *Warning* that is my own idea - I think it may avoid potential race conditions in the code and has worked for me at least once. Just increase them slowly and dont run out of memory.

Also look at scheduler allocate to give the CPU more access to do what it needs.

"ip dns server queue limit..."

I looked this up and could not find anything in a few minutes. Perhaps it will control the resources that the DNS server is using?

OOPS - Once again I have looked more closely after writing a load of stuff.

Align errors are I understand benign. They are not expected however they are fixed up in software and so do not cause a crash.

If you wish please post

sh ip dns st sh proc mem sh buff

when the problem is occuring.

Reply to
bod43

I've had various crashiness that turned out to be from running a DNS server on anything beyond 12.4(15)T1 on both an 1841 and a 2801. I haven't tried 12.4(15)T8 yet, but I seem to remember that T7 didn't help.

12.4(15)T1's been deferred, but you can still click through the warning page to download it if you really want to, I think.
Reply to
Andrew J Cosgriff

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.