Topic: [SOLVED] server crashed on Friday night

[didwedo]

Hello everyone,

it's been 3 weeks since the agency's server crashed on Friday night.

Oct 28 00:40:37 sme-hp init: tty (/dev/tty1) main process (3232) killed by TERM signal
Oct 28 00:40:37 sme-hp init: tty (/dev/tty2) main process (3234) killed by TERM signal
Oct 28 00:40:37 sme-hp init: tty (/dev/tty3) main process (3236) killed by TERM signal
Oct 28 00:40:37 sme-hp init: tty (/dev/tty4) main process (3240) killed by TERM signal
Oct 28 00:40:37 sme-hp init: tty (/dev/tty5) main process (3242) killed by TERM signal
Oct 28 00:40:37 sme-hp init: tty (/dev/tty6) main process (3244) killed by TERM signal
Oct 28 00:40:39 sme-hp acpid: exiting
Oct 28 00:40:39 sme-hp init: Disconnected from system bus
Oct 28 00:40:39 sme-hp console-kit-daemon[13829]: WARNING: no sender
Oct 28 00:40:39 sme-hp kernel: Kernel logging (proc) stopped.
Oct 28 00:40:39 sme-hp rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="1157" x-info="http://www.rsyslog.com"] exiting on signal 15.
Oct 30 08:39:57 sme-hp kernel: imklog 5.8.10, log source = /proc/kmsg started.
Oct 30 08:39:58 sme-hp rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="1007" x-info="http://www.rsyslog.com"] start

thx for all.

best regards chris

PS: server and installation are totally new:
- HPE ProLiant MicroServer Gen10/ProLiant MicroServer Gen10, BIOS 5.12
- 8 Go de ram
- sme 9.2

[CharlieBrady]

Your server didn't crash. Somebody shut it down (or somebody rebooted it, and the system's CMOS clock is wrong).

[didwedo]

hello,

thx, i change the day of full backup from friday to saturday and now all is ok.

see u