Komischer Reboot

Status
Not open for further replies.
S

sportY

New Member
Hallo zusammen,

zur Info: Debian "etch", Plesk 8.4.0, xinet, qmail ...

habe Logcheck am laufen und lasse mir stündlich die Logs zu schicken. Heute ist mir aufgefallen, das 4 E-Mails im Betreff zuerst "Reboot" stehen haben. Da wurde ich etwas stuztig.

Das hier steht im syslog:

Code: 
Oct 29 07:04:27 vs189065 shutdown[8040]: shutting down for system halt
Oct 29 07:04:27 vs189065 init: Switching to runlevel: 0
Oct 29 07:04:28 vs189065 qmail: 1288328668.041815 status: exiting
Oct 29 07:04:28 vs189065 xinetd[17780]: Exiting...
Oct 29 07:04:28 vs189065 mysqld[15890]: 101029  7:04:28 [Note] /usr/sbin/mysqld: Normal shutdown
Oct 29 07:04:28 vs189065 mysqld[15890]:
Oct 29 07:04:28 vs189065 mysqld[15890]: 101029  7:04:28 [Note] /usr/sbin/mysqld: Shutdown complete
Oct 29 07:04:28 vs189065 mysqld[15890]:
Oct 29 07:04:28 vs189065 mysqld_safe[9455]: ended
Oct 29 07:04:29 vs189065 named[14253]: shutting down: flushing changes
Oct 29 07:04:29 vs189065 named[14253]: stopping command channel on 127.0.0.1#953
Oct 29 07:04:29 vs189065 named[14253]: no longer listening on 127.0.0.1#53
Oct 29 07:04:29 vs189065 named[14253]: no longer listening on xx.xx.xx.xx#53
Oct 29 07:04:29 vs189065 named[14253]: exiting
Oct 29 07:04:29 vs189065 exiting on signal 15
Oct 29 07:05:17 vs189065 syslogd 1.4.1#18: restart.
Oct 29 07:05:17 vs189065 named[25901]: starting BIND 9.3.4-P1.2 -t /var/named/run-root -c /etc/named.conf -u bind
Oct 29 07:05:17 vs189065 named[25901]: found 1 CPU, using 1 worker thread
Oct 29 07:05:17 vs189065 named[25901]: loading configuration from '/etc/named.conf'
Oct 29 07:05:17 vs189065 named[25901]: no IPv6 interfaces found
Oct 29 07:05:17 vs189065 named[25901]: listening on IPv4 interface lo, 127.0.0.1#53
Oct 29 07:05:17 vs189065 named[25901]: listening on IPv4 interface venet0:0, xx.xx.xx.xx#53
Oct 29 07:05:17 vs189065 named[25901]: command channel listening on 127.0.0.1#953
Oct 29 07:05:17 vs189065 named[25901]: zone 0.0.127.IN-ADDR.ARPA/IN: loaded serial 20010622
Oct 29 07:05:17 vs189065 named[25901]: zone 189.75.62.in-addr.arpa/IN: loaded serial 1288187708
Oct 29 07:05:17 vs189065 named[25901]: zone Kundendomain.de/IN: loaded serial 1288187708
Oct 29 07:05:17 vs189065 named[25901]: zone Kundendomain.de/IN: loaded serial 1288187708
Oct 29 07:05:17 vs189065 named[25901]: zone Kundendomain.de/IN: loaded serial 1288187708
Oct 29 07:05:17 vs189065 named[25901]: zone Kundendomain.de/IN: loaded serial 1288187708
Oct 29 07:05:17 vs189065 named[25901]: zone Kundendomain.de/IN: loaded serial 1288187708
Oct 29 07:05:17 vs189065 named[25901]: zone Kundendomain.de/IN: loaded serial 1288187708
Oct 29 07:05:17 vs189065 named[25901]: zone Kundendomain.de/IN: loaded serial 1288187708
Oct 29 07:05:17 vs189065 named[25901]: running
Oct 29 07:05:18 vs189065 mysqld_safe[26146]: started
Oct 29 07:05:18 vs189065 mysqld[26152]: 101029  7:05:18 [Note] /usr/sbin/mysqld: ready for connections.
Oct 29 07:05:18 vs189065 mysqld[26152]: Version: '5.0.32-Debian_7etch12-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Debian etch distribution
Oct 29 07:05:19 vs189065 /etc/mysql/debian-start[27660]: Upgrading MySQL tables if necessary.
Oct 29 07:05:19 vs189065 xinetd[27928]: Reading included configuration file: /etc/xinetd.d/chargen [file=/etc/xinetd.conf] [line=38]
Oct 29 07:05:19 vs189065 xinetd[27928]: Reading included configuration file: /etc/xinetd.d/daytime [file=/etc/xinetd.d/daytime] [line=28]
Oct 29 07:05:19 vs189065 xinetd[27928]: Reading included configuration file: /etc/xinetd.d/discard [file=/etc/xinetd.d/discard] [line=26]
Oct 29 07:05:19 vs189065 xinetd[27928]: Reading included configuration file: /etc/xinetd.d/echo [file=/etc/xinetd.d/echo] [line=25]
Oct 29 07:05:19 vs189065 xinetd[27928]: Reading included configuration file: /etc/xinetd.d/ftp_psa [file=/etc/xinetd.d/ftp_psa] [line=26]
Oct 29 07:05:19 vs189065 xinetd[27928]: Reading included configuration file: /etc/xinetd.d/poppassd_psa [file=/etc/xinetd.d/poppassd_psa] [line=20]
Oct 29 07:05:19 vs189065 xinetd[27928]: Reading included configuration file: /etc/xinetd.d/smtp_psa [file=/etc/xinetd.d/smtp_psa] [line=8]
Oct 29 07:05:19 vs189065 xinetd[27928]: Reading included configuration file: /etc/xinetd.d/smtps_psa [file=/etc/xinetd.d/smtps_psa] [line=24]
Oct 29 07:05:19 vs189065 xinetd[27928]: Reading included configuration file: /etc/xinetd.d/time [file=/etc/xinetd.d/time] [line=23]
Oct 29 07:05:19 vs189065 xinetd[27928]: removing chargen
Oct 29 07:05:19 vs189065 xinetd[27928]: removing chargen
Oct 29 07:05:19 vs189065 xinetd[27928]: removing daytime
Oct 29 07:05:19 vs189065 xinetd[27928]: removing daytime
Oct 29 07:05:19 vs189065 xinetd[27928]: removing discard
Oct 29 07:05:19 vs189065 xinetd[27928]: removing discard
Oct 29 07:05:19 vs189065 xinetd[27928]: removing echo
Oct 29 07:05:19 vs189065 xinetd[27928]: removing echo
Oct 29 07:05:19 vs189065 xinetd[27928]: removing time
Oct 29 07:05:19 vs189065 xinetd[27928]: removing time
Oct 29 07:05:19 vs189065 xinetd[27928]: xinetd Version 2.3.14 started with libwrap loadavg options compiled in.
Oct 29 07:05:19 vs189065 xinetd[27928]: Started working: 4 available services
Oct 29 07:05:20 vs189065 /etc/mysql/debian-start[28137]: Checking for crashed MySQL tables.
Oct 29 07:05:20 vs189065 qmail: 1288328720.186936 status: local 0/10 remote 0/20
Oct 29 07:05:27 vs189065 ntpdate[24548]: step-systime: Operation not permitted
Oct 29 07:05:28 vs189065 ntpdate[24489]: step-systime: Operation not permitted
Oct 29 07:05:28 vs189065 /usr/sbin/cron[3479]: (CRON) INFO (pidfile fd = 3)
Oct 29 07:05:28 vs189065 /usr/sbin/cron[3481]: (CRON) STARTUP (fork ok)
Oct 29 07:05:28 vs189065 /usr/sbin/cron[3481]: (CRON) INFO (Running @reboot jobs)
Oct 29 07:05:28 vs189065 /USR/SBIN/CRON[3504]: (logcheck) CMD (   if [ -x /usr/sbin/logcheck ]; then nice -n10 /usr/sbin/logcheck -R; fi)

Warum macht der Server das? Hat er noch nie gemacht. Das ist heute um 06:19, 06:36 und um 07:05 passiert. Außerdem noch einmal am 27.10. um 05:09.

Auch interessant: Als das am 27.10. passiert ist, gibt es im Authlog ziwschen 23 Uhr und dem Reboot um 05:09 keine Logs. Wieso war der Server 6 h offline???

Code: 
Oct 26 23:06:44 vs189065 sshd[25686]: Received signal 15; terminating.
Oct 27 05:09:43 vs189065 sshd[30270]: Server listening on 0.0.0.0 port 22.

Fummelt da einer rum?

Gruß,
SportY
 
Last edited by a moderator:
Status
Not open for further replies.
Back
Top