L
L
le1872017-08-24 11:52:45
System administration
le187, 2017-08-24 11:52:45

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

6 answer(s)
R
Roman Kulakovich, 2017-08-24
@Wernisag

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.

A
Artem @Jump, 2017-08-24
Tag

Depending on what you want to monitor -

  • If load monitoring is needed, these are performance counters in administrative equipment. Or Russinovich's utilities
  • If you need state monitoring, you just need to read SMART,
    take any console utility like smartmontools and put the batch file that launches it into the scheduler.
    If you are not looking for easy ways, and like to work exclusively with standard tools, you can pull out SMART attributes in PS through WinAPI.

R
res2001, 2017-08-24
@res2001

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.

K
kmg4e, 2017-08-24
@kmg4e

Typically:
Power supply.
Fans, primarily on the processor.
Much less often - the motherboard and the problems of the operating system itself.

M
Maxim Yaroshevich, 2017-08-24
@YMax

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.

M
Maxim, 2017-08-24
@cross_01

There is a need to identify the cause of the server shutdown
As 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:
1. Do you already suspect the disk that the server is shutting down?
As a rule, there are testing and monitoring utilities from the manufacturer, use them.
2. Do you just need condition monitoring? Monitoring what: a disk, a server as a whole?
perfmon
it will show you the performance status for example: "length of the disk queue"
If you need to monitor the server for whether it is enabled or not, then look here for a solution .
If you need some kind of monitoring of server components (hardware, software) for further analysis, then you can look towards zabbix (I recommend it because there are a lot of documentation and articles for this product).

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question