1&1 Rootserver L64 bootet nicht mehr

FreeBSD, Gentoo, openSUSE, CentOS, Ubuntu, Debian
skyscrap
Posts: 18
Joined: 2006-11-02 00:22

1&1 Rootserver L64 bootet nicht mehr

Post by skyscrap »

Hallo,

ich fürchte ich bin der tausendste der mit dem Problem ankommt, aber ich hab mit der Sufu bei einer kurzen Recherche nichts entdecken können.

Wie also der Titel schon sagt, mein rootserver bei 1&1 bootet nicht mehr. Gibt's für den Fall irgendwo ein HowTo was man wie alles kontrollieren kann? Laut support haben die pro Tag hunderte dieser Fälle, das muss doch mal jemand dokumentiert haben.

Per Rescue system lassen sich alle partitionen mounten und die daten scheinen auch soweit intakt zu sein. Ein Plattencheck (fsck.3ext und xfs_repair) hat nichts gebracht, rootkit finder (rootkit hunter, chkrootkit) haben auch keine ergebnisse gebracht. Das schlimmste ist aber das in den logfiles (/var/log/boot.msg; /var/log/messages) beim Booten kein enziges Byte geschrieben wird.

Ich hab keine große Lust den Server wieder komplett zu initialisieren, was könnte ich noch checken, was auf dem Server kaputt ist?

Danke für eure Hilfe!
Top
captaincrunch
Userprojekt
Userprojekt
Posts: 7066
Joined: 2002-10-09 14:30
Location: Dorsten

Re: 1&1 Rootserver L64 bootet nicht mehr

Post by captaincrunch »

Gegenfrage: was hast du vor dem Reboot gemacht?
DebianHowTo
echo "[q]sa[ln0=aln256%Pln256/snlbx]sb729901041524823122snlbxq"|dc
Top
skyscrap
Posts: 18
Joined: 2006-11-02 00:22

Re: 1&1 Rootserver L64 bootet nicht mehr

Post by skyscrap »

Jedenfalls nichts an der konfiguration geändert. Der server ist unser build server und in letzter Zeit zeigte der ein recht merkwürdiges verhalten. Ich wollte es dann mit der Windows-methode versuchen (das an sich sagt ja schon einiges über mich), und den server neu starten, da der monatelang lief und ... naja, ende von lied ist, dass jetzt gar nichts mehr läuft.

Auf dem server läuft (oder lief):
  • der apache, mit ein paar subdomains und einem perl basiertem wiki
  • J2EE application server, der aber von aussen per firewall nicht zugänglich war
  • cruisecontrol, das bei änderungen in unserem source code repository automatische builds getriggert hat.
Top
blattlaus
Posts: 52
Joined: 2007-03-08 13:45

Re: 1&1 Rootserver L64 bootet nicht mehr

Post by blattlaus »

Was sagen die Logfiles wenn du sie dir vom Rescuemodus anschaust?
Top
User avatar
Joe User
Project Manager
Project Manager
Posts: 11165
Joined: 2003-02-27 01:00
Location: Hamburg

Re: 1&1 Rootserver L64 bootet nicht mehr

Post by Joe User »

Boote mal per Remote-Console, wo bleibt er hängen? Festplatte(n) voll?
PayPal.Me/JoeUser ● FreeBSD Remote Installation
Wings for Life ● Wings for Life World Run

„If there’s more than one possible outcome of a job or task, and one
of those outcomes will result in disaster or an undesirable consequence,
then somebody will do it that way.“ -- Edward Aloysius Murphy Jr.
Top
skyscrap
Posts: 18
Joined: 2006-11-02 00:22

Re: 1&1 Rootserver L64 bootet nicht mehr

Post by skyscrap »

Die logfiles haben alle einen timestamp von letzten Freitag. Da hatte ich den Server runtergefahren. Danach ist wie gesagt kein einziges Byte mehr geloggt worden.

Code: Select all

rescue:/mnt/var/log# find . -type f -mtime -5 -not -name 'lastlog' -not -name 'wtmp' -exec ls -l {} ;
-rw-r--r--  1 root root 2870286 Jun  1 16:25 ./apache2/access_log
-rw-r--r--  1 root root 404782 Jun  1 17:58 ./apache2/error_log
-rw-r--r--  1 root root 25693 Jun  1 17:58 ./boot.msg
-rw-r--r--  1 root root 902820 Jun  1 17:30 ./xinetd.log
-rw-r-----  1 root root 311070 Jun  1 17:30 ./warn
-rw-r-----  1 root root 236138 Jun  1 17:30 ./mail.warn
-rw-r-----  1 root root 690239 Jun  1 17:58 ./mail.info
-rw-r-----  1 root root 609345 Jun  1 17:58 ./messages
Und jetzt der Inhalt (wenigstens die letzten 50 zeilen, mehr bei bedarf)

Code: Select all

rescue:/mnt/var/log# find . -type f -mtime -5 -not -name 'lastlog' -not -name 'wtmp' -print -exec tail -n 50 {} ; 

./apache2/access_log
195.138.231.2 - - [29/May/2007:20:59:59 +0200] "GET /community/xmlrpc.php HTTP/1.0" 404 1036 "-" "-"
195.138.231.2 - - [29/May/2007:20:59:59 +0200] "GET /blogs/xmlrpc.php HTTP/1.0" 404 1036 "-" "-"
195.138.231.2 - - [29/May/2007:20:59:59 +0200] "GET /blogs/xmlsrv/xmlrpc.php HTTP/1.0" 404 1036 "-" "-"
195.138.231.2 - - [29/May/2007:20:59:59 +0200] "GET /blog/xmlsrv/xmlrpc.php HTTP/1.0" 404 1036 "-" "-"
195.138.231.2 - - [29/May/2007:20:59:59 +0200] "GET /blogtest/xmlsrv/xmlrpc.php HTTP/1.0" 404 1036 "-" "-"
195.138.231.2 - - [29/May/2007:20:59:59 +0200] "GET /b2/xmlsrv/xmlrpc.php HTTP/1.0" 404 1036 "-" "-"
195.138.231.2 - - [29/May/2007:20:59:59 +0200] "GET /b2evo/xmlsrv/xmlrpc.php HTTP/1.0" 404 1036 "-" "-"
195.138.231.2 - - [29/May/2007:20:59:59 +0200] "GET /wordpress/xmlrpc.php HTTP/1.0" 404 1036 "-" "-"
195.138.231.2 - - [29/May/2007:20:59:59 +0200] "GET /phpgroupware/xmlrpc.php HTTP/1.0" 404 1036 "-" "-"
66.194.6.77 - - [30/May/2007:00:02:45 +0200] "GET / HTTP/1.1" 200 266 "-" "Mozilla/5.0 (compatible; Konqueror/3.0-rc5; i686 Linux; 20020321)"
87.118.114.229 - - [30/May/2007:02:21:32 +0200] "GET / HTTP/1.0" 200 266 "-" "-"
212.95.252.16 - - [30/May/2007:14:30:05 +0200] "HEAD /spicons/apache_pb.gif HTTP/1.0" 404 - "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)"
62.103.164.201 - - [30/May/2007:15:44:04 +0200] "GET /phpmyadmin/main.php HTTP/1.0" 404 1041 "-" "pmafind"
62.103.164.201 - - [30/May/2007:15:44:04 +0200] "GET /PMA/main.php HTTP/1.0" 404 1041 "-" "pmafind"
62.103.164.201 - - [30/May/2007:15:44:04 +0200] "GET /mysql/main.php HTTP/1.0" 404 1041 "-" "pmafind"
62.103.164.201 - - [30/May/2007:15:44:04 +0200] "GET /admin/main.php HTTP/1.0" 404 1041 "-" "pmafind"
62.103.164.201 - - [30/May/2007:15:44:05 +0200] "GET /db/main.php HTTP/1.0" 404 1041 "-" "pmafind"
62.103.164.201 - - [30/May/2007:15:44:05 +0200] "GET /dbadmin/main.php HTTP/1.0" 404 1041 "-" "pmafind"
62.103.164.201 - - [30/May/2007:15:44:05 +0200] "GET /web/phpMyAdmin/main.php HTTP/1.0" 404 1041 "-" "pmafind"
62.103.164.201 - - [30/May/2007:15:44:05 +0200] "GET /admin/pma/main.php HTTP/1.0" 404 1041 "-" "pmafind"
62.103.164.201 - - [30/May/2007:15:44:05 +0200] "GET /admin/phpmyadmin/main.php HTTP/1.0" 404 1041 "-" "pmafind"
62.103.164.201 - - [30/May/2007:15:44:05 +0200] "GET /admin/mysql/main.php HTTP/1.0" 404 1041 "-" "pmafind"
62.103.164.201 - - [30/May/2007:15:44:05 +0200] "GET /mysql-admin/main.php HTTP/1.0" 404 1041 "-" "pmafind"
62.103.164.201 - - [30/May/2007:15:44:05 +0200] "GET /phpmyadmin2/main.php HTTP/1.0" 404 1041 "-" "pmafind"
62.103.164.201 - - [30/May/2007:15:44:05 +0200] "GET /mysqladmin/main.php HTTP/1.0" 404 1041 "-" "pmafind"
218.150.111.16 - - [30/May/2007:15:51:00 +0200] "GET http://p2.mumu.pp.ru/index.htm HTTP/1.0" 404 1042 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)"
212.241.207.2 - - [30/May/2007:15:58:06 +0200] "GET /w00tw00t.at.ISC.SANS.Pwn!t:) HTTP/1.1" 400 303 "-" "-"
82.200.143.50 - - [30/May/2007:19:17:01 +0200] "GET /w00tw00t.at.ISC.SANS.DFind:) HTTP/1.1" 400 303 "-" "-"
212.241.207.2 - - [30/May/2007:20:43:58 +0200] "GET /w00tw00t.at.ISC.SANS.Pwn!t:) HTTP/1.1" 400 303 "-" "-"
65.164.250.65 - - [30/May/2007:22:48:40 +0200] "GET /w00tw00t.at.ISC.SANS.DFind:) HTTP/1.1" 400 303 "-" "-"
212.241.207.2 - - [30/May/2007:23:28:38 +0200] "GET /w00tw00t.at.ISC.SANS.Pwn!t:) HTTP/1.1" 400 303 "-" "-"
66.98.148.24 - - [31/May/2007:02:24:28 +0200] "GET /robots.txt HTTP/1.1" 404 1168 "www.agile-ossj.org" "Pingdom GIGRIB (http://www.pingdom.com)"
66.98.148.24 - - [31/May/2007:02:27:35 +0200] "GET // HTTP/1.1" 200 266 "http://www.pingdom.com/tools/fpt/index.htm?url=www.agile-ossj.org" "Pingdom GIGRIB (http://www.pingdom.com)"
62.49.74.246 - - [31/May/2007:02:55:27 +0200] "GET /w00tw00t.at.ISC.SANS.DFind:) HTTP/1.1" 400 303 "-" "-"
62.49.74.246 - - [31/May/2007:02:55:28 +0200] "GET /" 400 982 "-" "-"
87.118.114.229 - - [31/May/2007:03:10:12 +0200] "GET / HTTP/1.0" 200 266 "-" "-"
87.118.115.204 - - [31/May/2007:03:19:10 +0200] "GET / HTTP/1.0" 200 266 "-" "-"
66.194.6.67 - - [31/May/2007:05:33:34 +0200] "GET / HTTP/1.1" 200 266 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Q312464)"
87.118.112.230 - - [31/May/2007:05:47:58 +0200] "GET / HTTP/1.0" 200 266 "-" "-"
74.6.75.13 - - [31/May/2007:13:15:22 +0200] "GET /robots.txt HTTP/1.0" 404 1047 "-" "Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)"
74.6.67.172 - - [31/May/2007:13:15:22 +0200] "GET / HTTP/1.0" 304 - "-" "Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)"
74.96.150.114 - - [31/May/2007:14:35:51 +0200] "GET /favicon.ico HTTP/1.1" 404 1047 "-" "Mozilla/5.0 (compatible; Google Desktop)"
212.241.207.2 - - [31/May/2007:18:10:30 +0200] "GET /w00tw00t.at.ISC.SANS.Pwn!t:) HTTP/1.1" 400 303 "-" "-"
74.208.71.159 - - [01/Jun/2007:04:42:27 +0200] "GET / HTTP/1.0" 200 266 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)"
24.207.52.74 - - [01/Jun/2007:06:52:28 +0200] "GET / HTTP/1.0" 200 266 "-" "-"
68.142.212.198 - - [01/Jun/2007:06:53:09 +0200] "GET /robots.txt HTTP/1.0" 404 1047 "-" "Yahoo-MMCrawler/3.x (mms dash mmcrawler dash support at yahoo dash inc dot com)"
68.142.212.198 - - [01/Jun/2007:06:53:30 +0200] "GET /images/construction.gif HTTP/1.0" 304 - "-" "Yahoo-MMCrawler/3.x (mms dash mmcrawler dash support at yahoo dash inc dot com)"
213.164.110.66 - - [01/Jun/2007:11:55:55 +0200] "GET / HTTP/1.0" 200 266 "-" "-"
87.118.112.230 - - [01/Jun/2007:15:26:01 +0200] "GET / HTTP/1.0" 200 266 "-" "-"
213.164.110.108 - - [01/Jun/2007:16:25:02 +0200] "GET / HTTP/1.0" 200 266 "-" "-"
./apache2/error_log
[Wed May 30 15:44:05 2007] [error] [client 62.103.164.201] File does not exist: /srv/www/vhosts/default/htdocs/dbadmin
[Wed May 30 15:44:05 2007] [error] [client 62.103.164.201] File does not exist: /srv/www/vhosts/default/htdocs/web
[Wed May 30 15:44:05 2007] [error] [client 62.103.164.201] File does not exist: /srv/www/vhosts/default/htdocs/admin
[Wed May 30 15:44:05 2007] [error] [client 62.103.164.201] File does not exist: /srv/www/vhosts/default/htdocs/admin
[Wed May 30 15:44:05 2007] [error] [client 62.103.164.201] File does not exist: /srv/www/vhosts/default/htdocs/admin
[Wed May 30 15:44:05 2007] [error] [client 62.103.164.201] File does not exist: /srv/www/vhosts/default/htdocs/mysql-admin
[Wed May 30 15:44:05 2007] [error] [client 62.103.164.201] File does not exist: /srv/www/vhosts/default/htdocs/phpmyadmin2
[Wed May 30 15:44:05 2007] [error] [client 62.103.164.201] File does not exist: /srv/www/vhosts/default/htdocs/mysqladmin
[Wed May 30 15:51:00 2007] [error] [client 218.150.111.16] File does not exist: /srv/www/vhosts/default/htdocs/index.htm
[Wed May 30 15:58:06 2007] [error] [client 212.241.207.2] client sent HTTP/1.1 request without hostname (see RFC2616 section 14.23): /w00tw00t.at.ISC.SANS.Pwn!t:)
[Wed May 30 19:17:01 2007] [error] [client 82.200.143.50] client sent HTTP/1.1 request without hostname (see RFC2616 section 14.23): /w00tw00t.at.ISC.SANS.DFind:)
[Wed May 30 20:43:58 2007] [error] [client 212.241.207.2] client sent HTTP/1.1 request without hostname (see RFC2616 section 14.23): /w00tw00t.at.ISC.SANS.Pwn!t:)
[Wed May 30 22:48:40 2007] [error] [client 65.164.250.65] client sent HTTP/1.1 request without hostname (see RFC2616 section 14.23): /w00tw00t.at.ISC.SANS.DFind:)
[Wed May 30 23:28:38 2007] [error] [client 212.241.207.2] client sent HTTP/1.1 request without hostname (see RFC2616 section 14.23): /w00tw00t.at.ISC.SANS.Pwn!t:)
[Thu May 31 02:24:28 2007] [error] [client 66.98.148.24] File does not exist: /srv/www/vhosts/default/htdocs/robots.txt, referer: www.agile-ossj.org
[Thu May 31 02:55:27 2007] [error] [client 62.49.74.246] client sent HTTP/1.1 request without hostname (see RFC2616 section 14.23): /w00tw00t.at.ISC.SANS.DFind:)
[Thu May 31 13:15:22 2007] [error] [client 74.6.75.13] File does not exist: /srv/www/vhosts/default/htdocs/robots.txt
[Thu May 31 14:35:51 2007] [error] [client 74.96.150.114] File does not exist: /srv/www/vhosts/default/htdocs/favicon.ico
[Thu May 31 18:10:30 2007] [error] [client 212.241.207.2] client sent HTTP/1.1 request without hostname (see RFC2616 section 14.23): /w00tw00t.at.ISC.SANS.Pwn!t:)
[Fri Jun 01 06:53:09 2007] [error] [client 68.142.212.198] File does not exist: /srv/www/vhosts/default/htdocs/robots.txt
[Fri Jun 01 17:58:21 2007] [warn] child process 12618 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:21 2007] [warn] child process 18035 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:21 2007] [warn] child process 12976 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:21 2007] [warn] child process 13205 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:21 2007] [warn] child process 15018 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:21 2007] [warn] child process 15986 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:21 2007] [warn] child process 13148 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:21 2007] [warn] child process 17969 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:21 2007] [warn] child process 18037 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:21 2007] [warn] child process 18038 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:22 2007] [warn] child process 12618 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:22 2007] [warn] child process 18035 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:22 2007] [warn] child process 12976 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:22 2007] [warn] child process 13205 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:22 2007] [warn] child process 15018 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:22 2007] [warn] child process 15986 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:22 2007] [warn] child process 13148 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:22 2007] [warn] child process 17969 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:22 2007] [warn] child process 18037 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:22 2007] [warn] child process 18038 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:23 2007] [warn] child process 12618 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:23 2007] [warn] child process 18035 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:23 2007] [warn] child process 12976 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:23 2007] [warn] child process 13205 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:23 2007] [warn] child process 15018 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:23 2007] [warn] child process 15986 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:23 2007] [warn] child process 13148 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:23 2007] [warn] child process 17969 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:23 2007] [warn] child process 18037 still did not exit, sending a SIGTERM
[Fri Jun 01 17:58:23 2007] [warn] child process 18038 still did not exit, sending a SIGTERM
./boot.msg
done
mysql  off
Starting service MySQLdone
psa-spamassassin  off
Starting psa-spamassassin service: done
apache2  off
<notice>startproc: execve (/usr/sbin/httpd2-prefork) [ /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf ], [ CONSOLE=/dev/console SHELL=/bin/sh TERM=vt102 PERL5LIB=/usr/local/psa/lib/perl5/site_perl/5.8.6:/usr/local/psa/lib/perl5/site_perl/5.8.6/x86_64-linux-thread-multi get_module_list_done=true INIT_VERSION=sysvinit-2.85 REDIRECT=/dev/ttyS0 COLUMNS=80 AUTOBOOT=YES get_includes_done=true PATH=/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin RUNLEVEL=3 SPLASHCFG= PWD=/etc/init.d LANG=C PREVLEVEL=N LINES=24 SHLVL=3 HOME=/ BOOT_IMAGE=lxser OPENSSL_CONF=/usr/local/psa/admin/conf/openssl.cnf SPLASH=no _=/sbin/startproc DAEMON=/usr/sbin/httpd2-prefork ]
Processing config directory: /usr/local/psa/admin/conf/httpsd.*.include
/usr/local/psa/admin/bin/httpsdctl start: httpd started
Starting Plesk: done
Master Resource Control: runlevel 3 has been reached
<notice>killproc: kill(1421,3)

Boot logging started on /dev/ttyS0(/dev/console) at Fri Jun  1 17:58:10 2007

Master Resource Control: previous runlevel: 3, switching to runlevel: 6
<notice>killproc: kill(2366,15)
Shutting down RPC portmap daemondone
<notice>killproc: kill(2529,15)
Shutting down Name Service Cache Daemondone
Stopping Courier-IMAP server:
   Stopping imapdone
   Stopping imap-ssldone
   Stopping pop3done
   Stopping pop3-ssldone

/usr/local/psa/admin/bin/httpsdctl stop: httpd stopped
<notice>killproc: kill(2398,15)
Stopping : <notice>killproc: kill(2529,9)
Saving random seeddone
Shutting down mailmandone
<notice>killproc: kill(1975,15)
Shutting down resource managerdone
<notice>killproc: kill(1978,15)
Shutting down CRON daemondone
<notice>killproc: kill(1954,15)
Shutting down SSH daemondone
<notice>killproc: kill(2470,15)
Stopping Plesk: done
<notice>killproc: kill(1951,15)
Shutting down syslog servicesdone
Stopping 3ware DiskSwitch daemon: done
Shutting down network interfaces:
    eth0      device: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)
    eth0      configuration: eth-id-00:30:05:bb:97:ab
doneShutting down service network  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .done
Running /etc/init.d/halt.local
done<notice>killproc: kill(27360,3)
Sending all processes the TERM signal...
done
./xinetd.log
07/5/31@22:31:50: START: smtp from=127.0.0.1
07/5/31@22:31:52: EXIT: smtp status=0 duration=2(sec)
07/5/31@22:33:25: START: ftp from=87.106.55.66
07/5/31@22:33:26: EXIT: ftp status=0 duration=1(sec)
07/5/31@22:33:26: START: ftp from=87.106.55.66
07/5/31@22:33:26: START: ftp from=87.106.55.66
07/5/31@22:33:26: EXIT: ftp status=0 duration=0(sec)
07/5/31@22:33:27: EXIT: ftp status=0 duration=1(sec)
07/5/31@22:33:27: START: ftp from=87.106.55.66
07/5/31@22:33:27: START: ftp from=87.106.55.66
07/5/31@22:33:27: EXIT: ftp status=0 duration=0(sec)
07/5/31@22:33:28: EXIT: ftp status=0 duration=1(sec)
07/5/31@22:33:28: START: ftp from=87.106.55.66
07/5/31@22:33:28: START: ftp from=87.106.55.66
07/5/31@22:33:28: EXIT: ftp status=0 duration=0(sec)
07/5/31@22:33:28: START: ftp from=87.106.55.66
07/5/31@22:33:28: EXIT: ftp status=0 duration=0(sec)
07/5/31@22:33:28: EXIT: ftp status=0 duration=0(sec)
07/5/31@22:33:29: START: smtp from=127.0.0.1
07/5/31@22:33:29: EXIT: smtp status=0 duration=0(sec)
07/5/31@22:46:04: START: smtp from=127.0.0.1
07/5/31@22:46:06: EXIT: smtp status=0 duration=2(sec)
07/5/31@23:00:16: START: smtp from=127.0.0.1
07/5/31@23:00:17: EXIT: smtp status=0 duration=1(sec)
07/5/31@23:43:14: START: smtp from=127.0.0.1
07/5/31@23:43:16: EXIT: smtp status=0 duration=2(sec)
07/6/1@08:00:03: START: smtp from=127.0.0.1
07/6/1@08:00:03: EXIT: smtp status=0 duration=0(sec)
07/6/1@08:00:03: START: smtp from=127.0.0.1
07/6/1@08:00:03: EXIT: smtp status=0 duration=0(sec)
07/6/1@17:22:22: START: ftp from=87.106.55.66
07/6/1@17:22:23: EXIT: ftp status=0 duration=1(sec)
07/6/1@17:22:23: START: ftp from=87.106.55.66
07/6/1@17:22:23: START: ftp from=87.106.55.66
07/6/1@17:22:23: EXIT: ftp status=0 duration=0(sec)
07/6/1@17:22:24: EXIT: ftp status=0 duration=1(sec)
07/6/1@17:22:24: START: ftp from=87.106.55.66
07/6/1@17:22:24: START: ftp from=87.106.55.66
07/6/1@17:22:24: EXIT: ftp status=0 duration=0(sec)
07/6/1@17:22:24: EXIT: ftp status=0 duration=0(sec)
07/6/1@17:22:24: START: ftp from=87.106.55.66
07/6/1@17:22:25: START: ftp from=87.106.55.66
07/6/1@17:22:25: EXIT: ftp status=0 duration=1(sec)
07/6/1@17:22:25: START: ftp from=87.106.55.66
07/6/1@17:22:25: EXIT: ftp status=0 duration=0(sec)
07/6/1@17:22:25: EXIT: ftp status=0 duration=0(sec)
07/6/1@17:22:26: START: smtp from=127.0.0.1
07/6/1@17:22:27: EXIT: smtp status=0 duration=1(sec)
07/6/1@17:30:21: START: smtp from=127.0.0.1
07/6/1@17:30:21: EXIT: smtp status=0 duration=0(sec)
./warn
May 30 17:52:52 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:43653 (localhost)
May 30 18:06:58 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:56238 (localhost)
May 30 18:08:47 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:45167 (localhost)
May 30 18:09:57 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:59258 (localhost)
May 30 18:12:05 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:39569 (localhost)
May 30 18:26:17 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:47466 (localhost)
May 30 18:42:30 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:55642 (localhost)
May 30 18:58:39 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:47964 (localhost)
May 30 19:14:49 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:37962 (localhost)
May 30 19:31:03 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:44019 (localhost)
May 30 19:47:16 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:49910 (localhost)
May 30 20:03:30 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:43928 (localhost)
May 30 20:20:02 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:57518 (localhost)
May 30 20:36:29 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:56269 (localhost)
May 30 20:52:59 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:47349 (localhost)
May 30 21:09:28 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:38064 (localhost)
May 30 21:11:48 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:39671 (localhost)
May 30 22:16:09 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:34345 (localhost)
May 30 22:17:58 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:55720 (localhost)
May 30 22:31:52 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:42880 (localhost)
May 30 22:33:59 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:39454 (localhost)
May 30 22:35:49 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:56147 (localhost)
May 30 22:52:16 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:52785 (localhost)
May 30 23:08:41 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:50021 (localhost)
May 30 23:18:02 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:51014 (localhost)
May 30 23:25:06 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:58874 (localhost)
May 30 23:25:56 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:35277 (localhost)
May 30 23:42:48 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:56481 (localhost)
May 31 04:07:10 s15229400 syslog-ng[1951]: Changing permissions on special file /dev/xconsole
May 31 04:07:10 s15229400 syslog-ng[1951]: Changing permissions on special file /dev/tty10
May 31 04:07:10 s15229400 statistics: Unable to execute logrotate.
May 31 08:00:07 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:45104 (localhost)
May 31 08:00:07 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:45105 (localhost)
May 31 09:32:32 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:47295 (localhost)
May 31 15:06:57 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:42804 (localhost)
May 31 16:54:03 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:39321 (localhost)
May 31 22:27:28 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:47963 (localhost)
May 31 22:31:51 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:35540 (localhost)
May 31 22:33:29 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:36469 (localhost)
May 31 22:46:06 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:58499 (localhost)
May 31 23:00:17 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:35276 (localhost)
May 31 23:43:16 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:59121 (localhost)
Jun  1 04:07:08 s15229400 syslog-ng[1951]: Changing permissions on special file /dev/xconsole
Jun  1 04:07:08 s15229400 syslog-ng[1951]: Changing permissions on special file /dev/tty10
Jun  1 04:07:08 s15229400 statistics: Unable to execute logrotate.
Jun  1 08:00:03 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:49911 (localhost)
Jun  1 08:00:03 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:49912 (localhost)
Jun  1 16:09:12 s15229400 sshd[25278]: fatal: Timeout before authentication for 147.243.155.42
Jun  1 17:22:27 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:36803 (localhost)
Jun  1 17:30:21 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:54571 (localhost)
./mail.warn
May 29 13:46:23 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:41916 (localhost)
May 29 14:03:18 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:37081 (localhost)
May 29 14:14:42 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:38982 (localhost)
May 30 08:00:04 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:49892 (localhost)
May 30 08:00:05 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:49893 (localhost)
May 30 11:49:09 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:35894 (localhost)
May 30 17:36:39 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:58720 (localhost)
May 30 17:52:52 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:43653 (localhost)
May 30 18:06:58 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:56238 (localhost)
May 30 18:08:47 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:45167 (localhost)
May 30 18:09:57 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:59258 (localhost)
May 30 18:12:05 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:39569 (localhost)
May 30 18:26:17 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:47466 (localhost)
May 30 18:42:30 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:55642 (localhost)
May 30 18:58:39 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:47964 (localhost)
May 30 19:14:49 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:37962 (localhost)
May 30 19:31:03 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:44019 (localhost)
May 30 19:47:16 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:49910 (localhost)
May 30 20:03:30 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:43928 (localhost)
May 30 20:20:02 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:57518 (localhost)
May 30 20:36:29 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:56269 (localhost)
May 30 20:52:59 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:47349 (localhost)
May 30 21:09:28 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:38064 (localhost)
May 30 21:11:48 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:39671 (localhost)
May 30 22:16:09 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:34345 (localhost)
May 30 22:17:58 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:55720 (localhost)
May 30 22:31:52 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:42880 (localhost)
May 30 22:33:59 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:39454 (localhost)
May 30 22:35:49 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:56147 (localhost)
May 30 22:52:16 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:52785 (localhost)
May 30 23:08:41 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:50021 (localhost)
May 30 23:18:02 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:51014 (localhost)
May 30 23:25:06 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:58874 (localhost)
May 30 23:25:56 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:35277 (localhost)
May 30 23:42:48 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:56481 (localhost)
May 31 08:00:07 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:45104 (localhost)
May 31 08:00:07 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:45105 (localhost)
May 31 09:32:32 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:47295 (localhost)
May 31 15:06:57 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:42804 (localhost)
May 31 16:54:03 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:39321 (localhost)
May 31 22:27:28 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:47963 (localhost)
May 31 22:31:51 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:35540 (localhost)
May 31 22:33:29 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:36469 (localhost)
May 31 22:46:06 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:58499 (localhost)
May 31 23:00:17 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:35276 (localhost)
May 31 23:43:16 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:59121 (localhost)
Jun  1 08:00:03 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:49911 (localhost)
Jun  1 08:00:03 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:49912 (localhost)
Jun  1 17:22:27 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:36803 (localhost)
Jun  1 17:30:21 s15229400 relaylock: /var/qmail/bin/relaylock: mail from 127.0.0.1:54571 (localhost)
./mail.info
Jun  1 17:30:06 s15229400 qmail: 1180711806.802659 bounce msg 181501 qp 26662
Jun  1 17:30:06 s15229400 qmail: 1180711806.802819 end msg 181501
Jun  1 17:30:06 s15229400 qmail: 1180711806.803361 new msg 181502
Jun  1 17:30:06 s15229400 qmail: 1180711806.803465 info msg 181502: bytes 1394 from <> qp 26662 uid 2522
Jun  1 17:30:07 s15229400 qmail: 1180711807.803791 starting delivery 38238: msg 181502 to remote anonymous@s15229400.onlinehome-server.info
Jun  1 17:30:07 s15229400 qmail: 1180711807.803955 status: local 0/10 remote 1/20
Jun  1 17:30:07 s15229400 qmail: 1180711807.808274 delivery 38238: failure: Sorry._Although_I'm_listed_as_a_best-preference_MX_or_A_for_that_host,/it_isn't_in_my_control/locals_file,_so_I_don't_treat_it_as_local._(#5.4.6)/
Jun  1 17:30:07 s15229400 qmail: 1180711807.808541 status: local 0/10 remote 0/20
Jun  1 17:30:08 s15229400 qmail: 1180711808.588366 bounce msg 181502 qp 26664
Jun  1 17:30:08 s15229400 qmail: 1180711808.588544 end msg 181502
Jun  1 17:30:08 s15229400 qmail: 1180711808.589036 new msg 181501
Jun  1 17:30:08 s15229400 qmail: 1180711808.589132 info msg 181501: bytes 2026 from <#@[]> qp 26664 uid 2522
Jun  1 17:30:08 s15229400 qmail: 1180711808.820502 starting delivery 38239: msg 181501 to remote postmaster@s15229400.onlinehome-server.info
Jun  1 17:30:08 s15229400 qmail: 1180711808.820661 status: local 0/10 remote 1/20
Jun  1 17:30:08 s15229400 qmail: 1180711808.824223 delivery 38239: failure: Sorry._Although_I'm_listed_as_a_best-preference_MX_or_A_for_that_host,/it_isn't_in_my_control/locals_file,_so_I_don't_treat_it_as_local._(#5.4.6)/
Jun  1 17:30:08 s15229400 qmail: 1180711808.824379 status: local 0/10 remote 0/20
Jun  1 17:30:08 s15229400 qmail: 1180711808.824460 triple bounce: discarding bounce/181501
Jun  1 17:30:08 s15229400 qmail: 1180711808.824537 end msg 181501
Jun  1 17:30:21 s15229400 qmail: 1180711821.700227 new msg 181501
Jun  1 17:30:21 s15229400 qmail: 1180711821.700387 info msg 181501: bytes 26532 from <dev@jsr264-private.dev.java.net> qp 26669 uid 2020
Jun  1 17:30:21 s15229400 qmail: 1180711821.744229 starting delivery 38240: msg 181501 to remote gerovermaas@dev.java.net
Jun  1 17:30:21 s15229400 qmail: 1180711821.744410 status: local 0/10 remote 1/20
Jun  1 17:30:24 s15229400 qmail: 1180711824.202253 delivery 38240: success: 204.16.104.10_accepted_message./Remote_host_said:_250_ok:__Message_73409501_accepted/
Jun  1 17:30:24 s15229400 qmail: 1180711824.202426 status: local 0/10 remote 0/20
Jun  1 17:30:24 s15229400 qmail: 1180711824.202506 end msg 181501
Jun  1 17:45:01 s15229400 qmail: 1180712701.890010 new msg 181501
Jun  1 17:45:01 s15229400 qmail: 1180712701.890169 info msg 181501: bytes 656 from <anonymous@s15229400.onlinehome-server.info> qp 27202 uid 0
Jun  1 17:45:01 s15229400 qmail: 1180712701.904009 starting delivery 38241: msg 181501 to remote root@s15229400.onlinehome-server.info
Jun  1 17:45:01 s15229400 qmail: 1180712701.904183 status: local 0/10 remote 1/20
Jun  1 17:45:02 s15229400 qmail: 1180712702.120820 delivery 38241: failure: Sorry._Although_I'm_listed_as_a_best-preference_MX_or_A_for_that_host,/it_isn't_in_my_control/locals_file,_so_I_don't_treat_it_as_local._(#5.4.6)/
Jun  1 17:45:02 s15229400 qmail: 1180712702.121074 status: local 0/10 remote 0/20
Jun  1 17:45:02 s15229400 qmail: 1180712702.133910 bounce msg 181501 qp 27204
Jun  1 17:45:02 s15229400 qmail: 1180712702.134050 end msg 181501
Jun  1 17:45:02 s15229400 qmail: 1180712702.134560 new msg 181502
Jun  1 17:45:02 s15229400 qmail: 1180712702.134660 info msg 181502: bytes 1394 from <> qp 27204 uid 2522
Jun  1 17:45:02 s15229400 qmail: 1180712702.147560 starting delivery 38242: msg 181502 to remote anonymous@s15229400.onlinehome-server.info
Jun  1 17:45:02 s15229400 qmail: 1180712702.147724 status: local 0/10 remote 1/20
Jun  1 17:45:02 s15229400 qmail: 1180712702.151490 delivery 38242: failure: Sorry._Although_I'm_listed_as_a_best-preference_MX_or_A_for_that_host,/it_isn't_in_my_control/locals_file,_so_I_don't_treat_it_as_local._(#5.4.6)/
Jun  1 17:45:02 s15229400 qmail: 1180712702.151650 status: local 0/10 remote 0/20
Jun  1 17:45:02 s15229400 qmail: 1180712702.165895 bounce msg 181502 qp 27206
Jun  1 17:45:02 s15229400 qmail: 1180712702.166027 end msg 181502
Jun  1 17:45:02 s15229400 qmail: 1180712702.166497 new msg 181501
Jun  1 17:45:02 s15229400 qmail: 1180712702.166591 info msg 181501: bytes 2026 from <#@[]> qp 27206 uid 2522
Jun  1 17:45:02 s15229400 qmail: 1180712702.183611 starting delivery 38243: msg 181501 to remote postmaster@s15229400.onlinehome-server.info
Jun  1 17:45:02 s15229400 qmail: 1180712702.183772 status: local 0/10 remote 1/20
Jun  1 17:45:02 s15229400 qmail: 1180712702.186583 delivery 38243: failure: Sorry._Although_I'm_listed_as_a_best-preference_MX_or_A_for_that_host,/it_isn't_in_my_control/locals_file,_so_I_don't_treat_it_as_local._(#5.4.6)/
Jun  1 17:45:02 s15229400 qmail: 1180712702.186731 status: local 0/10 remote 0/20
Jun  1 17:45:02 s15229400 qmail: 1180712702.186811 triple bounce: discarding bounce/181501
Jun  1 17:45:02 s15229400 qmail: 1180712702.186889 end msg 181501
Jun  1 17:58:13 s15229400 qmail: 1180713493.669837 status: exiting
./messages
Jun  1 17:30:21 s15229400 qmail: 1180711821.700387 info msg 181501: bytes 26532 from <dev@jsr264-private.dev.java.net> qp 26669 uid 2020
Jun  1 17:30:21 s15229400 qmail: 1180711821.744229 starting delivery 38240: msg 181501 to remote gerovermaas@dev.java.net
Jun  1 17:30:21 s15229400 qmail: 1180711821.744410 status: local 0/10 remote 1/20
Jun  1 17:30:24 s15229400 qmail: 1180711824.202253 delivery 38240: success: 204.16.104.10_accepted_message./Remote_host_said:_250_ok:__Message_73409501_accepted/
Jun  1 17:30:24 s15229400 qmail: 1180711824.202426 status: local 0/10 remote 0/20
Jun  1 17:30:24 s15229400 qmail: 1180711824.202506 end msg 181501
Jun  1 17:35:01 s15229400 /usr/sbin/cron[27112]: (mailman) CMD (/usr/bin/python -S /usr/lib/mailman/cron/gate_news)
Jun  1 17:35:01 s15229400 /usr/sbin/cron[27114]: (mailman) CMD (/usr/bin/python -S /usr/lib/mailman/cron/gate_news)
Jun  1 17:38:00 s15229400 sshd[27117]: Did not receive identification string from 143.89.29.110
Jun  1 17:40:01 s15229400 /usr/sbin/cron[27139]: (mailman) CMD (/usr/bin/python -S /usr/lib/mailman/cron/gate_news)
Jun  1 17:40:01 s15229400 /usr/sbin/cron[27141]: (mailman) CMD (/usr/bin/python -S /usr/lib/mailman/cron/gate_news)
Jun  1 17:45:01 s15229400 /usr/sbin/cron[27155]: (root) CMD ( test -x /usr/lib/cron/run-crons && /usr/lib/cron/run-crons >/dev/null 2>&1)
Jun  1 17:45:01 s15229400 /usr/sbin/cron[27157]: (mailman) CMD (/usr/bin/python -S /usr/lib/mailman/cron/gate_news)
Jun  1 17:45:01 s15229400 /usr/sbin/cron[27161]: (root) CMD (test -x /usr/lib/cron/run-crons && /usr/lib/cron/run-crons >/dev/null 2>&1)
Jun  1 17:45:01 s15229400 /usr/sbin/cron[27168]: (mailman) CMD (/usr/bin/python -S /usr/lib/mailman/cron/gate_news)
Jun  1 17:45:01 s15229400 /usr/sbin/cron[27159]: (root) CMD (ps -C "cvs" -o pid=,etime= | grep -e '..:..:..' | awk '{print $1}' | xargs -x kill)
Jun  1 17:45:01 s15229400 qmail: 1180712701.890010 new msg 181501
Jun  1 17:45:01 s15229400 qmail: 1180712701.890169 info msg 181501: bytes 656 from <anonymous@s15229400.onlinehome-server.info> qp 27202 uid 0
Jun  1 17:45:01 s15229400 qmail: 1180712701.904009 starting delivery 38241: msg 181501 to remote root@s15229400.onlinehome-server.info
Jun  1 17:45:01 s15229400 qmail: 1180712701.904183 status: local 0/10 remote 1/20
Jun  1 17:45:02 s15229400 qmail: 1180712702.120820 delivery 38241: failure: Sorry._Although_I'm_listed_as_a_best-preference_MX_or_A_for_that_host,/it_isn't_in_my_control/locals_file,_so_I_don't_treat_it_as_local._(#5.4.6)/
Jun  1 17:45:02 s15229400 qmail: 1180712702.121074 status: local 0/10 remote 0/20
Jun  1 17:45:02 s15229400 qmail: 1180712702.133910 bounce msg 181501 qp 27204
Jun  1 17:45:02 s15229400 qmail: 1180712702.134050 end msg 181501
Jun  1 17:45:02 s15229400 qmail: 1180712702.134560 new msg 181502
Jun  1 17:45:02 s15229400 qmail: 1180712702.134660 info msg 181502: bytes 1394 from <> qp 27204 uid 2522
Jun  1 17:45:02 s15229400 qmail: 1180712702.147560 starting delivery 38242: msg 181502 to remote anonymous@s15229400.onlinehome-server.info
Jun  1 17:45:02 s15229400 qmail: 1180712702.147724 status: local 0/10 remote 1/20
Jun  1 17:45:02 s15229400 qmail: 1180712702.151490 delivery 38242: failure: Sorry._Although_I'm_listed_as_a_best-preference_MX_or_A_for_that_host,/it_isn't_in_my_control/locals_file,_so_I_don't_treat_it_as_local._(#5.4.6)/
Jun  1 17:45:02 s15229400 qmail: 1180712702.151650 status: local 0/10 remote 0/20
Jun  1 17:45:02 s15229400 qmail: 1180712702.165895 bounce msg 181502 qp 27206
Jun  1 17:45:02 s15229400 qmail: 1180712702.166027 end msg 181502
Jun  1 17:45:02 s15229400 qmail: 1180712702.166497 new msg 181501
Jun  1 17:45:02 s15229400 qmail: 1180712702.166591 info msg 181501: bytes 2026 from <#@[]> qp 27206 uid 2522
Jun  1 17:45:02 s15229400 qmail: 1180712702.183611 starting delivery 38243: msg 181501 to remote postmaster@s15229400.onlinehome-server.info
Jun  1 17:45:02 s15229400 qmail: 1180712702.183772 status: local 0/10 remote 1/20
Jun  1 17:45:02 s15229400 qmail: 1180712702.186583 delivery 38243: failure: Sorry._Although_I'm_listed_as_a_best-preference_MX_or_A_for_that_host,/it_isn't_in_my_control/locals_file,_so_I_don't_treat_it_as_local._(#5.4.6)/
Jun  1 17:45:02 s15229400 qmail: 1180712702.186731 status: local 0/10 remote 0/20
Jun  1 17:45:02 s15229400 qmail: 1180712702.186811 triple bounce: discarding bounce/181501
Jun  1 17:45:02 s15229400 qmail: 1180712702.186889 end msg 181501
Jun  1 17:50:01 s15229400 /usr/sbin/cron[27245]: (mailman) CMD (/usr/bin/python -S /usr/lib/mailman/cron/gate_news)
Jun  1 17:50:01 s15229400 /usr/sbin/cron[27247]: (mailman) CMD (/usr/bin/python -S /usr/lib/mailman/cron/gate_news)
Jun  1 17:55:01 s15229400 /usr/sbin/cron[27252]: (mailman) CMD (/usr/bin/python -S /usr/lib/mailman/cron/gate_news)
Jun  1 17:55:01 s15229400 /usr/sbin/cron[27254]: (mailman) CMD (/usr/bin/python -S /usr/lib/mailman/cron/gate_news)
Jun  1 17:58:09 s15229400 init: Switching to runlevel: 6
Jun  1 17:58:13 s15229400 qmail: 1180713493.669837 status: exiting
Jun  1 17:58:16 s15229400 sshd[1975]: Received signal 15; terminating.
Jun  1 17:58:17 s15229400 kernel: Kernel logging (proc) stopped.
Jun  1 17:58:17 s15229400 kernel: Kernel log daemon terminating.
Jun  1 17:58:18 s15229400 syslog-ng[1951]: syslog-ng version 1.6.5 going down
Top
skyscrap
Posts: 18
Joined: 2006-11-02 00:22

Re: 1&1 Rootserver L64 bootet nicht mehr

Post by skyscrap »

Joe User wrote:Boote mal per Remote-Console, wo bleibt er hängen? Festplatte(n) voll?
was meinst du genau? von der seriellen konsole?
Top
User avatar
Joe User
Project Manager
Project Manager
Posts: 11165
Joined: 2003-02-27 01:00
Location: Hamburg

Re: 1&1 Rootserver L64 bootet nicht mehr

Post by Joe User »

SkyScrap wrote:von der seriellen konsole?
Ja.
PayPal.Me/JoeUser ● FreeBSD Remote Installation
Wings for Life ● Wings for Life World Run

„If there’s more than one possible outcome of a job or task, and one
of those outcomes will result in disaster or an undesirable consequence,
then somebody will do it that way.“ -- Edward Aloysius Murphy Jr.
Top
skyscrap
Posts: 18
Joined: 2006-11-02 00:22

Re: 1&1 Rootserver L64 bootet nicht mehr

Post by skyscrap »

Joe User wrote:
SkyScrap wrote:von der seriellen konsole?
Ja.
Ok, du meinst also erst im 1&1 control center vom recovery tool auf das normale system umschalten, den reboot dann aber manuell von der seriellen konsole triggern. (shutdown -r now ?)

Werde ich mal probieren, irgendwas worauf ich achten sollte?
Top
User avatar
Joe User
Project Manager
Project Manager
Posts: 11165
Joined: 2003-02-27 01:00
Location: Hamburg

Re: 1&1 Rootserver L64 bootet nicht mehr

Post by Joe User »

Ja, achte auf die Bootmeldungen und berichte wo er genau hängen bleibt.
PayPal.Me/JoeUser ● FreeBSD Remote Installation
Wings for Life ● Wings for Life World Run

„If there’s more than one possible outcome of a job or task, and one
of those outcomes will result in disaster or an undesirable consequence,
then somebody will do it that way.“ -- Edward Aloysius Murphy Jr.
Top
skyscrap
Posts: 18
Joined: 2006-11-02 00:22

Re: 1&1 Rootserver L64 bootet nicht mehr

Post by skyscrap »

Code: Select all

rescue:~# shutdown -r now
INIT: Sending processes the TERM signal
IStopping periodic command scheduler: cron.
Stopping MTA: exim4.
Stopping internet superserver: inetd.
Stopping openntpd: start-stop-daemon: warning: failed to kill 1532: No such process
ntpd.
Stopping powernowd: powernowd.
Stopping rsync daemon: rsync.
Stopping S.M.A.R.T. daemon: smartd.
Stopping OpenBSD Secure Shell server: sshd.
Stopping NTP server: ntpd.
Saving the System Clock time to the Hardware Clock...
Hardware Clock updated to Wed Jun  6 11:31:08 CEST 2007.
Stopping RAID monitor daemon: mdadm -F.
Stopping quota service: rpc.rquotad.
Turning off quotas.
Stopping kernel log daemon: klogd.
Stopping system log daemon: syslogd.
Sending all processes the TERM signal...done.
 Sending all processes the KILL signal...done.
Saving random seed...done.
Unmounting remote and non-toplevel virtual filesystems...done.
Deconfiguring network interfaces...Internet Systems Consortium DHCP Client V3.0.1
Copyright 2004 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/eth0/00:30:05:bb:97:ab
Sending on   LPF/eth0/00:30:05:bb:97:ab
Sending on   Socket/fallback
DHCPRELEASE on eth0 to 87.106.14.250 port 67
done.
Cleaning up ifupdown...done.
Deactivating swap...done.
Unmounting local filesystems...done.
Shutting down LVM Volume Groups...
  No volume groups found
Rebooting... md: stopping all md devices.
md: md1 switched to read-only mode.
md: md5 switched to read-only mode.
md: md6 switched to read-only mode.
md: md7 switched to read-only mode.
md: md8 switched to read-only mode.
md: md0 switched to read-only mode.
Synchronizing SCSI cache for disk sdb:
Synchronizing SCSI cache for disk sda:
Restarting system.
.
machine restart
Danach passiert nix mehr. Liegt das daran, dass die serielle Konsole die Verbindung verloren hat?
Top
User avatar
Joe User
Project Manager
Project Manager
Posts: 11165
Joined: 2003-02-27 01:00
Location: Hamburg

Re: 1&1 Rootserver L64 bootet nicht mehr

Post by Joe User »

Installiere bitte den Bootloader und auch den Kernel neu.
PayPal.Me/JoeUser ● FreeBSD Remote Installation
Wings for Life ● Wings for Life World Run

„If there’s more than one possible outcome of a job or task, and one
of those outcomes will result in disaster or an undesirable consequence,
then somebody will do it that way.“ -- Edward Aloysius Murphy Jr.
Top
skyscrap
Posts: 18
Joined: 2006-11-02 00:22

Re: 1&1 Rootserver L64 bootet nicht mehr

Post by skyscrap »

Joe User wrote:Installiere bitte den Bootloader und auch den Kernel neu.
Ok :) Bootloader neu geht mit:

Code: Select all

lilo -M /dev/sda
Oder? Und Kernel?

Danke für deine Hilfe übrigens, du glaubst gar nicht, wie toll das ist. Wenn du in der Gegend (Bochum/Düsseldorf) bist, lade ich dich auf ein Bier ein :)
Top
User avatar
Joe User
Project Manager
Project Manager
Posts: 11165
Joined: 2003-02-27 01:00
Location: Hamburg

Re: 1&1 Rootserver L64 bootet nicht mehr

Post by Joe User »

Grober Ablauf:

Code: Select all

# Festplatte nach /mnt mounten

cp /etc/resolv.conf /mnt/etc/resolv.conf
chroot /mnt /bin/env -i HOME=/root TERM=$TERM PS1='u:w$ ' PATH=/usr/sbin:/usr/bin:/sbin:/bin /bin/bash +h

# Bootloader installieren
# Kernel installieren
# Bootloader konfigurieren

exit

# Festplatte unmounten

reboot
Da ich überzeugter nicht-Debian-Nutzer bin, musst Du die Einzelheiten selbst recherchieren, oder warten bis ein Debianer vorbeischaut und Mitleid mit Dir hat ;)
PayPal.Me/JoeUser ● FreeBSD Remote Installation
Wings for Life ● Wings for Life World Run

„If there’s more than one possible outcome of a job or task, and one
of those outcomes will result in disaster or an undesirable consequence,
then somebody will do it that way.“ -- Edward Aloysius Murphy Jr.
Top
skyscrap
Posts: 18
Joined: 2006-11-02 00:22

Re: 1&1 Rootserver L64 bootet nicht mehr

Post by skyscrap »

Joe User wrote:Grober Ablauf:
Da ich überzeugter nicht-Debian-Nutzer bin, musst Du die Einzelheiten selbst recherchieren, oder warten bis ein Debianer vorbeischaut und Mitleid mit Dir hat ;)
Ok, ich werde beides parallel ausführen (auf einen debianer warten und selbst die einzelheiten recherchieren gehen) :) Danke für deine Hilfe soweit!
Top
skyscrap
Posts: 18
Joined: 2006-11-02 00:22

Re: 1&1 Rootserver L64 bootet nicht mehr

Post by skyscrap »

Was ich jetzt erst realisiere (respekt vor den authoritäten :) ), wie kommst du eigentlich auf debian? Das rescue system ist debian, aber wenn ich nicht völlig falsch liege ist das server system SUSE (es gibt jedenfalls ein /sbin/YaST :) )
Top
User avatar
Joe User
Project Manager
Project Manager
Posts: 11165
Joined: 2003-02-27 01:00
Location: Hamburg

Re: 1&1 Rootserver L64 bootet nicht mehr

Post by Joe User »

Wenn es SUSE ist, dann ist grub der Bootloader.
Zum Reinstallieren im Chroot Folgendes eintippen:

Code: Select all

grub --no-floppy
root (hd0,0)
setup (hd0)
quit
Gegebenenfalls bitte die Plattenkennung anpassen.

Zum Rekonfigurieren im Chroot Folgendes eintippen:

Code: Select all

$EDITOR /boot/grub/menu.lst
Die Reinstallation des Kernels solltest Du Dir sparen können.
PayPal.Me/JoeUser ● FreeBSD Remote Installation
Wings for Life ● Wings for Life World Run

„If there’s more than one possible outcome of a job or task, and one
of those outcomes will result in disaster or an undesirable consequence,
then somebody will do it that way.“ -- Edward Aloysius Murphy Jr.
Top
skyscrap
Posts: 18
Joined: 2006-11-02 00:22

Re: 1&1 Rootserver L64 bootet nicht mehr

Post by skyscrap »

Ich hab gerade im YaST geguckt (System -> Bootloader Configuration) und dort war der aktive bootloader auf lilo gesetzt.

Bin jetzt auf dem Weg vom Büro nach Hause und melde mich später wieder. :)
Top
User avatar
Joe User
Project Manager
Project Manager
Posts: 11165
Joined: 2003-02-27 01:00
Location: Hamburg

Re: 1&1 Rootserver L64 bootet nicht mehr

Post by Joe User »

SkyScrap wrote:Ich hab gerade im YaST geguckt (System -> Bootloader Configuration) und dort war der aktive bootloader auf lilo gesetzt.
Ich liebe Provider die grundlos Defaults ignorieren, oder hast Du es selbst auf lilo geändert?
Egal, installiere einfach grub und passe die /boot/grub/menu.lst an:

Code: Select all

chroot # siehe oben
rpm -ivh --force grub
grub --no-floppy
root (hd0,0)
setup (hd0)
quit
$EDITOR /boot/grub/menu.lst
# Einstellung in YaST anpassen
exit
reboot
PayPal.Me/JoeUser ● FreeBSD Remote Installation
Wings for Life ● Wings for Life World Run

„If there’s more than one possible outcome of a job or task, and one
of those outcomes will result in disaster or an undesirable consequence,
then somebody will do it that way.“ -- Edward Aloysius Murphy Jr.
Top
skyscrap
Posts: 18
Joined: 2006-11-02 00:22

Re: 1&1 Rootserver L64 bootet nicht mehr

Post by skyscrap »

Joe User wrote:
SkyScrap wrote:Ich hab gerade im YaST geguckt (System -> Bootloader Configuration) und dort war der aktive bootloader auf lilo gesetzt.
Ich liebe Provider die grundlos Defaults ignorieren, oder hast Du es selbst auf lilo geändert?
Ich hab das ganz bestimmt nicht selbst auf lilo geändert, ich glaube aber auch nicht, dass die änderung grundlos erfolgte. Die lilo.conf erlaubt z.B. die benutzung der seriellen schnittstelle zur steuering, ich vermute dass wenn der lilo funktionieren würde, ich dann dort das image auswählen könnte (wenn ich den reboot über die serielle konsole triggere).

Code: Select all

rescue:/# cat /etc/lilo.conf
boot=/dev/sda
root=/dev/md1

install=/boot/boot.b
vga=normal
timeout=60
prompt
lba32

read-only

default=lxser

serial=0,57600n8
append="console=ttyS0,57600 console=tty0 panic=30"

image=/boot/vmlinuz
        label=lxser
        append="console=tty0 console=ttyS0,57600 panic=30"

image=/boot/vmlinuz
        label=lx

image=/boot/vmlinuz.old
        label=lxserold
        append="console=tty0 console=ttyS0,57600 panic=30"
        optional

image=/boot/vmlinuz.old
        label=lxold
        optional

#image=/boot/memtest86+.bin
#       label=memtest+
#       optional
Was mich auch wundert(e), ist daß keine aktive bootpartition definiert war. Ich hab jetzt /dev/sda1 mal bootbar gemacht, hat aber auch noch nichts geändert.

Dann werd ich mal den MBR und lilo neu erzeugen und schaun, was passiert.

Übrigens, ist es normal, dass bei einem RAID fdisk anmeckert, die partitionen würden keine partitionstabelle besitzen? Einerseits wundere ich mich nicht allzu sehr, da das ja logische/künstliche partitionen sind, andrerseits sollte fdisk das doch irgendwie mitbekommen.

Code: Select all

rescue:~# fdisk -l

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1         123      987966   fd  Linux raid autodetect
/dev/sda2             124         367     1959930   82  Linux swap / Solaris
/dev/sda4             368        9729    75200265    5  Extended
/dev/sda5             368         976     4891761   fd  Linux raid autodetect
/dev/sda6             977        1585     4891761   fd  Linux raid autodetect
/dev/sda7            1586        4018    19543041   fd  Linux raid autodetect
/dev/sda8            4019        9729    45873576   fd  Linux raid autodetect

Disk /dev/sdb: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1         123      987966   fd  Linux raid autodetect
/dev/sdb2             124         367     1959930   82  Linux swap / Solaris
/dev/sdb4             368        9729    75200265    5  Extended
/dev/sdb5             368         976     4891761   fd  Linux raid autodetect
/dev/sdb6             977        1585     4891761   fd  Linux raid autodetect
/dev/sdb7            1586        4018    19543041   fd  Linux raid autodetect
/dev/sdb8            4019        9729    45873576   fd  Linux raid autodetect

Disk /dev/md8: 46.9 GB, 46974435328 bytes
2 heads, 4 sectors/track, 11468368 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md8 doesn't contain a valid partition table

Disk /dev/md7: 20.0 GB, 20012007424 bytes
2 heads, 4 sectors/track, 4885744 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md7 doesn't contain a valid partition table

Disk /dev/md6: 5009 MB, 5009047552 bytes
2 heads, 4 sectors/track, 1222912 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md6 doesn't contain a valid partition table

Disk /dev/md5: 5009 MB, 5009047552 bytes
2 heads, 4 sectors/track, 1222912 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md5 doesn't contain a valid partition table

Disk /dev/md1: 1011 MB, 1011548160 bytes
2 heads, 4 sectors/track, 246960 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md1 doesn't contain a valid partition table
Top
skyscrap
Posts: 18
Joined: 2006-11-02 00:22

Re: 1&1 Rootserver L64 bootet nicht mehr

Post by skyscrap »

GESCHAFFT, GESCHAFFT, GESCHAFFT.

Also irgendwie war die Lösung jetzt ernüchternderweise sehr simpel, fast schon zu einfach. Alles was ich gemacht habe, was "lilo" aufzurufen, damit der Bootloader neu auf /dev/sda geschrieben wird. Und nun geht wieder alles. Also wirklich, den Tipp hätte mir der Support auch ruhig mal geben können! Auch dass man das booten von der seriellen Konsole tatsächlich mitverfolgen kann, dem war ich mir gar nicht bewußt.

Meinen herzlichen Dank an die Hilfe und den Beistand! Auch wenn die Lösung letztendlich einfach war, wenn Ihr mir nicht neue Hoffnung gegeben hättet, dass das Problem noch zu lösen ist, ich hätte wieder bei "Null" angefangen.

Danke :)
Top
franki
Posts: 60
Joined: 2005-05-31 16:23
Location: Dresden

Re: 1&1 Rootserver L64 bootet nicht mehr

Post by franki »

Übrigens, ist es normal, dass bei einem RAID fdisk anmeckert, die partitionen würden keine partitionstabelle besitzen?
Scheint bei Raid-System normal zu sein, kommt bei mir auch, wenn ich fdisk -l eingebe.

Gruß von Franki.
Top
User avatar
Joe User
Project Manager
Project Manager
Posts: 11165
Joined: 2003-02-27 01:00
Location: Hamburg

Re: 1&1 Rootserver L64 bootet nicht mehr

Post by Joe User »

SkyScrap wrote:Die lilo.conf erlaubt z.B. die benutzung der seriellen schnittstelle zur steuering, ich vermute dass wenn der lilo funktionieren würde, ich dann dort das image auswählen könnte (wenn ich den reboot über die serielle konsole triggere).
Das geht auch mit grub:

Code: Select all

cat > /boot/grub/grub.conf << "EOF"
timeout 5
default 0
serial --unit=0 --speed=57600 --word=8 --parity=no --stop=1
terminal serial

title=Gentoo Linux
  root (hd0,0)
  kernel /boot/vmlinuz root=/dev/hda3 console=tty0 console=ttyS0,57600

EOF

cat >> /etc/inittab << "EOF"
s0:12345:respawn:/sbin/agetty -L 57600 ttyS0 vt102
EOF
Schön dass Du das Problem selbst lösen konntest und auch noch etwas gelernt hast.
PayPal.Me/JoeUser ● FreeBSD Remote Installation
Wings for Life ● Wings for Life World Run

„If there’s more than one possible outcome of a job or task, and one
of those outcomes will result in disaster or an undesirable consequence,
then somebody will do it that way.“ -- Edward Aloysius Murphy Jr.
Top
skyscrap
Posts: 18
Joined: 2006-11-02 00:22

Re: 1&1 Rootserver L64 bootet nicht mehr

Post by skyscrap »

franki wrote:
Übrigens, ist es normal, dass bei einem RAID fdisk anmeckert, die partitionen würden keine partitionstabelle besitzen?
Scheint bei Raid-System normal zu sein, kommt bei mir auch, wenn ich fdisk -l eingebe.
Danke für die Bestätigung :) Das beruhigt!
Joe User wrote: Schön dass Du das Problem selbst lösen konntest und auch noch etwas gelernt hast.
Gelernt auf jeden Fall. Ich würde auch ein HowTo befürworten, welche Maßnahmen zu ergreifen sind, wenn der 1&1 server nicht mehr bootet. Laut support scheint das ein häufiges Problem zu sein.
Top
fun4teen
Posts: 92
Joined: 2004-06-18 16:11

Re: 1&1 Rootserver L64 bootet nicht mehr

Post by fun4teen »

Guten Morgen,

ich habe gestern einen neuen Rootserver (auch von 1&1 ) bekommen. Nachdem ich einiges in plesk und von einem anderen server hin und her kopiert habe, hatte ich den server via Konsole über reboot neugestartet.

Aber die kiste meldet sich nicht mehr... fährt irgendwie nicht mehr hoch. Das rescue system kann ich starten, aber was muss ich dann machen?

Hab hier aus dem Threat nicht die Lösung herauslesen können.

Danke
Top

Return to “Betriebssysteme”