Why is this happening?

Unanswered Question
Mar 12th, 2007
User Badges:

Mar 12 21:20:08.872 SAST: %SYS-2-NOTQ: unqueue didn't find 821F4068 in queue 821F3FA4

e Timer Process", ipl= 0, pid= 59

-Traceback= 0x80134D74 0x8027CD6C 0x80395590 0x80396E5C 0x8026EEB8 0x802724F4

Mar 12 21:20:09.684 SAST: %SYS-2-NOTQ: unqueue didn't find 821F4068 in queue 821F3FA4

-Process= "Dynamic DNS Update Timer Process", ipl= 0, pid= 59

-Traceback= 0x80134D74 0x8027CD6C 0x80395590 0x80396E5C 0x8026EEB8 0x802724F4

Mar 12 21:20:09.688 SAST: %SYS-2-NOTQ: unqueue didn't find 821F4068 in queue 821F3FA4

-Process= "Dynamic DNS Update Timer Process", ipl= 0, pid= 59

-Traceback= 0x80134D74 0x8027CD6C 0x80395590 0x80396E5C 0x8026EEB8 0x802724F4

Mar 12 21:20:09.688 SAST: %SYS-2-NOTQ: unqueue didn't find 821F4068 in queue 821F3FA4

-Process= "Dynamic DNS Update Timer Process", ipl= 0, pid= 59

-Traceback= 0x80134D74 0x8027CD6C 0x80395590 0x80396E5C 0x8026EEB8 0x802724F4

Mar 12 21:20:09.688 SAST: %SYS-2-NOTQ: unqueue didn't find 821F4068 in queue 821F3FA4

-Process= "Dynamic DNS Update Timer Process", ipl= 0, pid= 59

-Traceback= 0x80134D74 0x8027CD6C 0x80395590 0x80396E5C 0x8026EEB8 0x802724F4

Mar 12 21:20:09.896 SAST: %


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
bradlesliect Mon, 03/12/2007 - 12:35
User Badges:

how do i stop this............


#sh proc cpu

CPU utilization for five seconds: 99%/4%; one minute: 99%; five minutes: 99%

PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process

59 3039280 112094 27113 87.55% 88.97% 88.09% 0 Dynamic DNS Upda


b-ulrich Mon, 03/12/2007 - 14:03
User Badges:
  • Bronze, 100 points or more

Hi, you may be running into this.


CSCef89364: Traceback at Dynamic DNS Update Timer Process


Symptoms: A Cisco router may show the following line while scrolling down the log:


Process= "Dynamic DNS Update Timer Process," ipl= 0, pid= 40 -Traceback= 0x412044F0 0x4009B7B0 0x412CAC40 0x412CC3BC 0x422B5C2C 0x422B5C10.


The router needs to be rebooted to recover.


Conditions: This error is observed when removing a ip ddns update from an interface, and after entering shutdown followed by no shutdown on the interface, on a Cisco router running IOS version 12.4(1a).


Workaround: Do not configure the using following sequence:


shutdown followed by no shutdown after removing ip ddns update from the interface.



Actions

This Discussion