Ntpd[5644]: %WAAS-UNKNOWN-5-899999: time reset

Gentlemen,
I need your good help in helping resolve a issue that I am facing with the WAE-574 device for a client.
This device alarmed in the CM as offline, twice. Necessary reset the device to regain access (the device is remote and I'm not have access to the console).
I realize several occurrences of syslog.txt the message below:
2013 Mar 4 11:18:16 SPO-EVE-WAAS-34828 ntpd[5858]: %WAAS-UNKNOWN-5-899999: time reset +0.190850 s
2013 Mar 4 11:51:58 SPO-EVE-WAAS-34828 Nodemgr: %WAAS-NODEMGR-5-330084: [CLI_CLOCK_SET] requests restart service crond
2013 Mar 4 11:51:58 SPO-EVE-WAAS-34828 Nodemgr: %WAAS-NODEMGR-5-330032: Stopping service: 'crond'.
2013 Mar 4 11:51:58 SPO-EVE-WAAS-34828 Nodemgr: %WAAS-NODEMGR-5-330027: Process with pid 15291 exits
2013 Mar 4 11:51:58 SPO-EVE-WAAS-34828 Nodemgr: %WAAS-NODEMGR-5-330048: DEBUG: respawn_count = 1, period: 2024.430000
2013 Mar 4 11:51:59 SPO-EVE-WAAS-34828 Nodemgr: %WAAS-NODEMGR-5-330040: Start service 'crond' using: '/ruby/bin/cron.start' with pid: 23724
Does anyone know let me know if there is a correlation between this post and the device error?
Cisco Wide Area Application Services Software (WAAS)
Copyright (c) 1999-2011 by Cisco Systems, Inc.
Cisco Wide Area Application Services (universal-k9) Software Release 4.4.3 (build b4 Aug 22 2011)
Version: oe574-4.4.3.4
Compiled 09:59:49 Aug 22 2011 by damaster

Response Cisco support team (in Portuguese Brazil):
Nosso time de escalation teve a oportunidade de revisar as informações disponíveis, e eles confirmaram o match em dois bugs que causam esgotamento de memória, e consequentemente o congelamento (hang) inesperado no equipamento:
- CSCtr94024 (Printer installation failing between Win2k8 SP1 64 bit and Win7 64bit) - este bug está fixado na versão 4.4.5 e posteriores;
- CSCtx83789 (CIFS statistics collection may not time out on clock change) - este bug está fixado na versão 4.4.7 e posteriores;;
Informações adicionais - Cisco Bug Toolkit
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtr94024
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtx83789
Diante do exposto, a recomendação é de que seja realizado o upgrade de software para uma versão contendo o fix para os dois bugs mencionados acima (4.4.7 ou posteriores). Segue abaixo o link para os documentos de Release Notes, onde podem ser obtidas maiores informações:
Cisco Wide Area Application Services (WAAS) Software - Release Notes
http://www.cisco.com/en/US/products/ps6870/prod_release_notes_list.html

Similar Messages

WAAS syslog error: nscd: %WAAS-UNKNOWN-5-899999: 5317: Handled cache clean up for SIGHUP

Hi All,
Can anyone tell me what this syslog message relates to? I'm seeing it on a whole lot of WAEs. Is it something I need to worry about or not?
nscd: %WAAS-UNKNOWN-5-899999: 5317: Handled cache clean up for SIGHUP
Thanks
Claire

Hi Claire,
Getting this message can be normal.
Since it is generated by the nscd process that takes care of the dns caching (and that is it generated when the cache is flushed), I would maybe verify the DNS config on those devices and if it is properly configured, I wouldn't worry about it.
If you want, the test self-diagnostic basic should test your DNS settings for you.
Regards,
Nicolas

%WAAS-UNKNOWN-6-899999

Hi
In WAE log we found below messages
config: %WAAS-UNKNOWN-6-899999: ReportCommandsAccounting: Report accounting after command is executed (logging host 10.11.4.20 priority information)
07-17-2011          16:15:08          User.Info          10.10.170.71          2011 Jul 17 16: config: %WAAS-UNKNOWN-6-899999: SendReport: Unknown Remote Host address due to console login.
07-17-2011          16:15:08          User.Info          10.10.170.71          2011 Jul 17 16: config: %WAAS-UNKNOWN-6-899999: ReportCommandsAccounting: Report accounting before command is executed (exit)
07-17-2011          16:15:08          User.Info          10.10.170.71          2011 Jul 17 16: config: %WAAS-UNKNOWN-6-899999: SendReport: Unknown Remote Host address due to console login.
07-17-2011          16:15:09          User.Info          10.10.170.71          2011 Jul 17 16: config: %WAAS-UNKNOWN-6-899999: ReportCommandsAccounting: Reported an accounting to a remote server
07-17-2011          16:15:09          User.Info          10.10.170.71          2011 Jul 17 16: config: %WAAS-PARSER-6-350232: CLI_LOG log_cli_command: exit
07-17-2011          16:15:09          User.Info          10.10.170.71          2011 Jul 17 16: config: %WAAS-UNKNOWN-6-899999: ReportCommandsAccounting: Report accounting after command is executed (exit)
07-17-2011          16:15:09          User.Info          10.10.170.71          2011 Jul 17 16: config: %WAAS-UNKNOWN-6-899999: SendReport: Unknown Remote Host address due to console login.
07-17-2011          16:15:09          User.Info          10.10.170.71          2011 Jul 17 16: -exec: %WAAS-UNKNOWN-6-899999: ReportCommandsAccounting: Report accounting after command is executed (conf t)
07-17-2011          16:15:09          User.Info          10.10.170.71          2011 Jul 17 16: -exec: %WAAS-UNKNOWN-6-899999: SendReport: Unknown Remote Host address due to console login.
07-17-2011          16:15:10          User.Info          10.10.170.71          2011 Jul 17 16: -exec: %WAAS-UNKNOWN-6-899999: ReportCommandsAccounting: Report accounting before command is executed (wr)
07-17-2011          16:15:10          User.Info          10.10.170.71          2011 Jul 17 16: -exec: %WAAS-UNKNOWN-6-899999: SendReport: Unknown Remote Host address due to console login.
07-17-2011          16:15:10          User.Info          10.10.170.71          2011 Jul 17 16: -exec: %WAAS-UNKNOWN-6-899999: ReportCommandsAccounting: Reported an accounting to a remote server
07-17-2011          16:15:10          User.Info          10.10.170.71          2011 Jul 17 16: -exec: %WAAS-PARSER-6-350232: CLI_LOG log_cli_command: wr
07-17-2011          16:15:10          User.Info          10.10.170.71          2011 Jul 17 16: sshd: %WAAS-UNKNOWN-6-899999: ReportExecAccounting
07-17-2011          16:15:10          User.Info          10.10.170.71          2011 Jul 17 16: sshd: %WAAS-UNKNOWN-6-899999: Report exec shell accounting after command is executed
What these means?
Is there any unknown user trying to execute some commands? The same is reflecting as security warning in TACACS reports.
Regards
Sameer Shah

Hi Sameer,
What is this ip address in logs: 10.10.170.71?
Further, can you also post the sh ver output from WAAS?
Regards.

NTP Error Logs on Nexus 5K [ ntpd[4746]: ntp:time reset +0.279670 s]

Hi Team,
We are using almost 10 Nexus 5k in our DC currently we are getting same error logs in all Nexus 5k.
" ntpd[4746]: ntp:time reset +0.279670 s "
Is it major error or just for reset time?........
Please check and let me know if you need any other logs from our switches.
Thanks....
Regards,
Senthil

Hi Senthilkumar
it is just an informational message stating that the NTP timer has been reset which would have been originated from the NTP server and communicated to all the devices connecting to this server
It's an informational message.
HTH,
Alex

Reason: watchdog timer reset.

Just recently, like the last 2 weeks I have had my AIR-LAP1042N-A-K9 and AIR-LAP1142N-A-K9 AP's suddenly reboot. Primary Software Version 7.4.100.0. I am using a 2504 controller,AIR-CT2504-K9. Looking in the traps I see:
106
Tue Mar 17 10:53:00 2015
AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:18:33:9d:b6:f5:10 Cause=Radio interface reset. Status:NA
107
Tue Mar 17 10:53:00 2015
AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:18:33:9d:b6:f5:10 Cause=Radio interface reset. Status:NA
108
Tue Mar 17 10:53:00 2015
AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:18:33:9d:b6:f5:10 Cause=Radio interface reset. Status:NA
109
Tue Mar 17 10:52:58 2015
AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:b4:e9:b0:d4:59:90 Cause=Radio interface reset. Status:NA
110
Tue Mar 17 10:52:58 2015
AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:b4:e9:b0:d4:59:90 Cause=Radio interface reset. Status:NA
111
Tue Mar 17 10:52:58 2015
AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:b4:e9:b0:d4:59:90 Cause=Radio interface reset. Status:NA
112
Tue Mar 17 10:52:58 2015
AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:b4:e9:b0:d4:59:90 Cause=Radio interface reset. Status:NA
113
Tue Mar 17 10:52:56 2015
AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:18:33:9d:b6:f5:10 Cause=Radio interface reset. Status:NA
114
Tue Mar 17 10:52:56 2015
AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:18:33:9d:b6:f5:10 Cause=Radio interface reset. Status:NA
115
Tue Mar 17 10:52:55 2015
AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:b4:e9:b0:d4:59:90 Cause=Unknown Reset Status:NA
116
Tue Mar 17 10:52:55 2015
AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:b4:e9:b0:d4:59:90 Cause=Unknown Reset Status:NA
117
Tue Mar 17 10:52:55 2015
AP 'ESU13_DL_Room', MAC: b4:e9:b0:d4:59:90 disassociated previously due to AP Reset. Uptime: 0 days, 00 h 01 m 40 s . Reason: watchdog timer reset.
118
Tue Mar 17 10:52:53 2015
AP 'ESU13_Conf_rooms_BC', MAC: 18:33:9d:b6:f5:10 disassociated previously due to AP Reset. Uptime: 0 days, 00 h 01 m 42 s . Reason: watchdog timer reset.
And
167
Tue Mar 17 10:49:29 2015
AP 'ESU13_Administration', MAC: 18:33:9d:b7:09:c0 disassociated previously due to Link Failure. Uptime: 0 days, 20 h 18 m 52 s . Reason: Capwap Echo request.
168
Tue Mar 17 10:49:29 2015
AP 'ESU13_Basement', MAC: 18:33:9d:b7:28:a0 disassociated previously due to Link Failure. Uptime: 7 days, 23 h 19 m 29 s . Reason: Capwap WTP Event request.
169
Tue Mar 17 10:49:29 2015
AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:18:33:9d:d2:4a:00 Cause=Unknown Reset Status:NA
170
Tue Mar 17 10:49:28 2015
AP 'ESU13_Meridian', MAC: 18:33:9d:d2:4a:00 disassociated previously due to Link Failure. Uptime: 14 days, 13 h 38 m 32 s . Reason: Capwap Echo request.
171
Tue Mar 17 10:49:28 2015
AP 'ESU13_Soar', MAC: 18:33:9d:d2:37:20 disassociated previously due to Link Failure. Uptime: 137 days, 20 h 30 m 58 s . Reason: Capwap WTP Event request.
I have read that the watchdog issue is related to version 7.4. Do I need to go back to 7.3 or is there a newer version that addresses this?
TIA,
Eric

Hi Eric,
Upgrade to 7.6.130.0 as 7.4.100.0 is initial release of 7.4.x & had lots of bugs.
http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/crn76mr03.html
HTH
Rasika
*** Pls rate all useful responses ****

When I try to log on to icloud it says "Apple ID is valid but not an icloud account? Changed my Apple password a few times reset my system still no luck Please help!t

When I try to log on to icloud it says "Apple ID is valid but not an icloud account? Changed my Apple password a few times reset my system still no luck Please help!t

Welcome to the Apple community.
These types of messages often indicate a problem with the devices serial number, have you had your phone repaired at any stage or did you buy it second-hand.

No sleep mode at low battery - data loss and time reset

I'm having this issue for about a year now:
When I run my macbook pros Battery down, there comes the low battery warning. After a while the system just goes down without suspending anything to my harddisk. When I restart my computer it does a normal start and after logging in I'm experiencing a lot messages due to the reset time. I correct my system-time and restart my mac and the system is back to normal.
Usually I'd say: Replace your CMOS-Battery (I know I have an EFI-Firmware), but where is it?. Or in other words: Is there a "System"-Battery, that would prevent my mac from forgetting the time?
Since I'm not running down my battery to 0 very often I only experience this issue from time to time and never took time to do anything about it.
I would also appreciate a workaround so that my mac immediately starts shutting down, after the low battery warning. That would be great.
iStats battery-Status says: Health:83%, Cycles:333, charge 50%...

Well, the problem, seem's to have reoccured: Battery ran out (even the indicator leds on the side didn't show any life), Time reset to 1.1.2001, again some rebooting and setting the time again...
Is this a sign of a degrading battery health status?
It looks like reseting the SMC didn't help after all.

Date and time reset when batery is empty

the date and time reset to initial state when the battery is empty, what should i do, thanx

Moy666 wrote:
Hi TJK, Thanx for answering,
My MBP have already a three months bought, what i should do, call to apple or to dealer?
I supposed its in warranty yet. THX
Your MBP has a one year hardware warranty on it.
As Trey suggested, it wouldn't hurt to try an SMC reset. If that doesn't work, you definitely want to contact AppleCare so you get it taken care of under warranty.

IPad shuts down unexpectedly and does a time reset

Hey,
I have an iPad2 iOS 5.0.1 and I have this problem:
When I ever try to just use my iPad normaly like playing or listening to music for somereason it shuts down everytime. after powering the iPad up and it does a time reset to 01.01.1970 4:00 AM , hard reset doesnt work with me I have to plug it to the charger when plugging it an empty battery picture shows up even though it's at 100% full battery I don't know if it's a hardware problem or a software problem. Does any one have the same problem as I do?
I'm hoping that I can find an answer or a solution here

Khalloof-
If the empty battery picture shows up, you do NOT have a 100% full battery unless there is a loose connection inside the iPad. The time reset makes me think that is the problem.
If you can show it to an Apple Store Genius, you may get a new iPad on the spot. If there is no Apple Store near you, search for an Apple Authorized Repair Center near you. There may be one in your city.
Fred

Time reset

The following VI generates a random number and the time starts when the value generated is between two specified values. How could I modify this Vi to have the elapsed time reset to zero every time the random number is between those two values instead of continuing counting?
Thanks in advance
Valls
Attachments:
time reset.vi ‏38 KB

If I understood you correctly, all you need to do is wire a TRUE to the "Reset" input, and then use a shift register to pass out the "Present (s)" output to use as the value to pass into the "Set Start Time (s)" input. See attached.
Attachments:
time reset (mod).vi ‏42 KB

Date/time resets when battery runs out on E51

Any ideeas how to solve the problem?

There is a little auxilliary in the phone. This is the battery that keeps the clock going when the main battery is removed or flat.
Usually the date/time resets when there is a fault with this auxilliary battery. You can get it replaced at your nearest Nokia Care Point.
You can find your nearest Nokia Care Point at:
For UK
http://www.nokia.co.uk/A4228006
For Europe:
http://europe.nokia.com/A4388379
For Asia-Pacific
http://www.nokia-asia.com/A4416070
Elsewhere:
http://www.nokia.com select your country, go to the support section, then select repair.

Time Resets after restart

I recently installed 10.6.5 on a Mac Pro DESKTOP. After I restart, the time (clock) resets to an earlier time, just the hour not the date etc. I just changed the pram battery - same result (time changes).

I have since discovered that the TIME RESET happens ONLY AFTER rebooting from WINDOWS.
OSX assumes the hardware clock is set to UTC (GMT). Windows sets the hardware clock to local time, so, in most places, OSX will then boot with the wrong time. It is possible to set Windows to use UTC, but some applications may have problems with this.

Difference between Timer.stop() and Timer.reset()?

Hello,
What is the difference between Timer.stop() and Timer.reset()
functions because it seems that the 2 functions do the same thing?
I image Timer.stop() to stop the timer and when Timer.start() is
called the timer starts from where it stopped. For example, if I
have a 3 sec. timer (3000 ms). If I stop the timer after 2.5 sec.
and start the timer again, I would expect the timer to expire/trip
within .5 sec. Is this a correct assumption?
Thanks,
Nilang

Hello,
Here is a better description of what I am trying to do and
the problem I encountered.
I am developing an application that plays multiple sound
files at different time offsets. For example, snd1 starts at time
offset 0 and snd2 starts at time offset 5000 ms (5 sec). I have
created a timer for each sound file and enabled the handlers via
addEventListener() function. I encounter a problem after the timer
has been stopped (Stop button pressed) before the timer expires.
When the user presses the Play Button, the timer seems to be reset
because the onTimerComplete() function is triggered after an
additional 5000 ms (5 sec). Is this normal behavior? If this is not
the correct behavior, is there a workaround Any help would be
appreciated.
I have created a small application in Flash CS3 that depicts
the problem with just a single sound file. I have Flash Player
9.0.124.0 installed. Sample code is above.
Thanks,
Nilang

Creative Zen Touch Time reseting problem.

When my player is off for more then 24 hours the time resets back to jan 200. i realize the player has a hard shutdown after 24 hours but everything else stays the same well except the songs that were in the playlist and the time. i have tried reloading the firmware and other such methods. has anyone else had this problem and able to correct it's

If you've tried everything from rescue mode it unfortunately sounds like the player is faulty.

Timed Trigger timer resets when text is eneterd in TEXTEDIT

Forum,
I have a java WD applcation, where the requirement is to Auto Save the contents of a view with several Text Edits automatically after 10 minutes, so that the data gets saved while the user is writing (and it is saved if he forgets to save the content and logs out or power goes off).
For the same, i have used a Timed Trigger Element which calles a method to save the contents in the textedits. But the problem is, it is not behaving as espected.
The Timed Trigger element's timer resets even when text is entered in the textedit, though i was under an impresseion that the Timed Triggers timer resets only when there is a request from clent to sever.
pls tell me how to rectify this issue.
Edited by: rana brata de on Sep 9, 2010 5:27 AM

Hi,
Ensure that you do not have any events which are triggered by changes in the TextEdit control.
Walter

Ntpd[5644]: %WAAS-UNKNOWN-5-899999: time reset

Similar Messages

Maybe you are looking for