My Orion server (oh and all my other servers...!) experienced a power outage last week. Once power was restored and the boxes where rebooted all seemed well. However I checked the status of the Orion services today to find that they hadn't been running since the outage. In the System event log I have various Service Control Manager messages (Event id 7035) saying the Solarwinds Alerting Engine, trap service, syslog service were succesfully sent a Stop control. These messages appear about a minute after the Orion server rebooted. All 3 services are set to restart the service on failure.
Can anyone explain this behavour? And can I stop it? For preference I want the Orion services to restart after a reboot/catastrophic failure etc.
I suspect it has something to do with the services dependency on SQL server (also running locally on the box).
I'll also note here that the Orion server is a virtual server running on ESX 3.0.2. I'm reasonably sure this isn't the cause if my issue because I've had problems with the engines not starting after a reboot before I virtualised Orion.
Thanks
Andrew
