This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Flood of Node Reboot Alerts after 10.1 upgrade

cdh over 13 years ago

I just completed the upgrade of my NPM deployment to 10.1 this morning. Had a couple little snags:

1) When I upgraded my additional polling engine, it told me that I needed to make sure that both polling engines were completely shut down. When I went through the configuration wizard on the additional poller, it complained that the Information Service wasn't running on the primary poller. I went back and manually restarted both Information Service services, waited for a minute, and then the install completed successfully on the 2nd polling engine.

2) This is the bigger issue I saw - I (and my whole NOC team) got flooded with alert emails for devices rebooting. The alert shows the correct date and time of last reboot, I'm just wondering why we were notified of all of these after the upgrade.

Other than that, things seem to be great so far.

0 Donald_Francis over 13 years ago

I too had a flood of old alerts (months old) after the upgrade as if they were just stuck.
Cancel
Vote Up 0 Vote Down

Cancel
0 jtimes over 13 years ago

Did you read the release notes?

http://www.solarwinds.com/support/Orion/docs/ReleaseNotes/releaseNotes.htm#FalseRebootAlertsAfterUpgrade
I haven't done the 10.1 upgrade yet, but I will be turning off ALL Alerts that have any action prior to doing the upgrade. I know that doesn't help with your situation, but us that haven't done it yet thank you ;)
Cancel
Vote Up 0 Vote Down

Cancel
0 netlogix over 13 years ago in reply to jtimes

I was getting this too, sometimes. I think I have fixed it by changing the start-up type of "SolarWindsAlertingEngine" to "Automatic (Delayed Start)".
I have no proof, but I think it's because the the Alerting Engine queries it once while it's set to "Unknown" then when it changes to the real date/time of last boot, it reports the reboot. (This is purely me shooting from the hip and I could be completely wrong).
Cancel
Vote Up 0 Vote Down

Cancel
0 cdh over 13 years ago in reply to jtimes

No, I missed that buried in there. Thanks for pointing that out!
Cancel
Vote Up 0 Vote Down

Cancel
0 aplatt over 13 years ago

I saw the same issue after rebooting the NPM server. I received a flood of node rebooted alerts.
Cancel
Vote Up 0 Vote Down

Cancel
0 drburge over 13 years ago

I too keep getting these fauls alarms whenever i reboot the server. Going far back as September 2010. Anyone find a solution to this. Management gets kind of worried when they see their emails with equipment being down.
Cancel
Vote Up 0 Vote Down

Cancel
0 netlogix over 13 years ago in reply to drburge

I still get some too:
check out the last post here:
/
Basically it says:
------------------------------------------
There should be only two possible sources of false reboot alerts in Orion:
1.   Upgrade from 10.0 to 10.1
2.   sysUptime counter rollover on the device + restart of NPM services
3.   device with faster clocks

If device runs for more then 497 days, it's sysUptime counter can rollover

If non of the "known conditions" for false reboot alerts described above matches your case, please open a support ticket.
------------------------------------------
PS I did not make the errors ("three" not "two", and "none" not "non")
Cancel
Vote Up 0 Vote Down

Cancel
0 MarieB over 13 years ago in reply to netlogix

Hi All--
I checked w the PM and this should only happen the first time after an upgrade and then it goes away.
If you can turn off your alerts, as suggested earlier in the post, that would be most helpful.
Sorry, wish I could be of more help.
Also, NPM 10.1.1 now has two hot fixes available for download in your customer portal.
M
Cancel
Vote Up 0 Vote Down

Cancel