Como encontrar o motivo da reinicialização do sistema ou desligamento no sistema 16.04 do Ubuntu?

Question

my ubuntu 16.04 server occassionaly reinicia a si mesmo e eu não tenho idéia do porquê? abaixo está o conteúdo do arquivo syslog que tem uma palavra-chave chamada Shutdown

Nov 21 13:51:42 AB-active-server systemd[1]: Created slice User Slice of support.
Nov 21 13:51:42 AB-active-server systemd[1]: Starting User Manager for UID 1000...
Nov 21 13:51:42 AB-active-server systemd[1]: Started Session 1196 of user support.
Nov 21 13:51:42 AB-active-server systemd[18340]: Reached target Sockets.
Nov 21 13:51:42 AB-active-server systemd[18340]: Reached target Paths.
Nov 21 13:51:42 AB-active-server systemd[18340]: Reached target Timers.
Nov 21 13:51:42 AB-active-server systemd[18340]: Reached target Basic System.
Nov 21 13:51:42 AB-active-server systemd[18340]: Reached target Default.
Nov 21 13:51:42 AB-active-server systemd[18340]: Startup finished in 15ms.
Nov 21 13:51:42 AB-active-server systemd[1]: Started User Manager for UID 1000.
Nov 21 13:51:42 AB-active-server console-kit-daemon[21735]: (process:18348): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
Nov 21 13:51:42 AB-active-server console-kit-daemon[21735]: missing action
Nov 21 13:51:44 AB-active-server systemd[1]: Stopping User Manager for UID 1000...
Nov 21 13:51:44 AB-active-server systemd[18340]: Stopped target Default.
Nov 21 13:51:44 AB-active-server systemd[18340]: Reached target Shutdown.
Nov 21 13:51:44 AB-active-server console-kit-daemon[21735]: (process:18386): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
Nov 21 13:51:44 AB-active-server console-kit-daemon[21735]: missing action
Nov 21 13:51:44 AB-active-server console-kit-daemon[21735]: console-kit-daemon[21735]: GLib-CRITICAL: Source ID 739 was not found when attempting to remove it
Nov 21 13:51:44 AB-active-server systemd[18340]: Starting Exit the Session...
Nov 21 13:51:44 AB-active-server console-kit-daemon[21735]: GLib-CRITICAL: Source ID 739 was not found when attempting to remove it
Nov 21 13:51:44 AB-active-server systemd[18340]: Stopped target Basic System.
Nov 21 13:51:44 AB-active-server systemd[18340]: Stopped target Timers.
Nov 21 13:51:44 AB-active-server systemd[18340]: Stopped target Sockets.
Nov 21 13:51:44 AB-active-server systemd[18340]: Stopped target Paths.
Nov 21 13:51:44 AB-active-server systemd[18340]: Received SIGRTMIN+24 from PID 18387 (kill).
Nov 21 13:51:44 AB-active-server systemd[1]: Stopped User Manager for UID 1000.
Nov 21 13:51:44 AB-active-server systemd[1]: Removed slice User Slice of support.

as partições de disco do servidor têm 60% + armazenamento livre e os inodes são usados apenas 1%

A memória é de 60G e CPU Intel Intel® Xeon® E5-2620 v4 @ 2.10GHz

    

Answer 1

Se eu tiver um desligamento inexplicável, eu vou procurar nos meus registros, todos eles, eles provavelmente são a única chance que você tem de descobrir o que aconteceu. Eu olho no log do sistema e descubro onde ele começou a inicializar e, em seguida, examine as entradas anteriores.

Às vezes não há arma fumegante, então você pode perguntar ao seu DC se eles tiveram um evento de energia e para verificar o seu equipamento. Recentemente, um servidor ficou offline inesperadamente algumas vezes e acabou sendo uma PDU de rack defeituosa.