Answer the question
In order to leave comments, you need to log in
There is a need to identify the cause of the server shutdown, can anyone help?
The first solution is to implement an online hard disk status monitor, using perfmon is not very convenient.
Answer the question
In order to leave comments, you need to log in
What do you want to get as a result? Deal with the reason for the sudden shutdown? Or testify to the very fact of shutting down / inoperability of the server?
If the first sin on the software / driver / gasket between the monitor and keyboard, then:
1. In windows, read the event log. Determine the approximate shutdown time and wool in search of the appropriate event.
2. On nix, look at the logs in the /var/log directory. Pay attention to /var/log/kern.log, /var/log/cron.
Well, if you need to monitor the current status, then there are a lot of different systems for monitoring and pinging the end device.
Depending on what you want to monitor -
Little information.
First of all, look in the Windows log.
Disk errors will definitely be there. But most likely the reason is not in the disks.
Typically:
Power supply.
Fans, primarily on the processor.
Much less often - the motherboard and the problems of the operating system itself.
One of the new servers was experiencing a reboot every few hours, a service visit and a BIOS update fixed the problem. You can do it yourself, but if you have little experience, it’s better to have a service. Maybe look in this direction? Although in the first place - carefully read the logs.
There is a need to identify the cause of the server shutdownAs said above, read the logs.
The first solution is to implement an online hard disk status monitor.And after that, 2 options come to mind:
perfmonit will show you the performance status for example: "length of the disk queue"
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question