Currently Being ModeratedFeb 12, 2014 3:27 PM (in response to roarkh)
I just installed a program called "Hardware Monitor" (from bresink.com) and the sensors themselves must be functioning because it is able to report all of the temperatures, it appears that it is only the Server Monitor software that is unable to read these items.
Currently Being ModeratedFeb 12, 2014 5:34 PM (in response to roarkh)
I've seen that happen once or twice, when the Xserve LOM got confused and/or the daemon became confused.
In the immortal words of the IT Crowd — "Have You Tried Turning It Off And On Again?" I've cleared that by shutting down Xserve entirely, removing grid power for 30+ seconds — it's that power removal which triggers the complete LOM reset, the physical disconnection of Xserve from the grid power — and then re-connecting and re-powering and rebooting the Xserve. If Xserve isn't physically disconnected from grid power, the LOM retains power.
You may alread be aware of this, but if you're using Server Monitor directly from the local Xserve system, you must use the local connection path and not the network path, too.
Currently Being ModeratedFeb 12, 2014 6:44 PM (in response to MrHoffman)
Thanks for your help. So I should power it off, unplug the power cords for a minute or so then boot it back up to get the server monitor working again. Since drive monitoring is working and I can use the hardware monitor to watch temperatures I guess it should be ok to leave it running like this for a few days. If for some reason you think that is a bad idea, please let me know.
Currently Being ModeratedFeb 18, 2014 2:52 PM (in response to MrHoffman)
I was able to find a good time to power off the Xserve today so I powered it off, unplugged it for about 30 seconds, fired it back up and everythign is back to normal. Thanks for your help.
More Like This
- Retrieving data ...
- This solved my question - 10 points
- This helped me - 5 points