mysqld will nach reboot nicht mehr

B

benshman

New Member
Moin!
Nutze einen VServer (Ubuntu) mit Plesk8.
Gestern habe ich der Webserver Konfiguration rumgedoktert, restart und reload, alles lief gut. Ein System-Reboot hatte dann jedoch mysql nicht mehr gern gehabt... Ich habe eben noch ein mal einen Reboot vollzogen, um euch den aktuellsten Stand zu präsentieren.

Mysql läuft nicht und bietet mir folgendes an:
Code: 
ben@myserver123:~$ mysql
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)

Ein Auschnitt aus der syslog:
Code: 
Feb 17 22:58:09 myserver123 syslogd 1.4.1#17ubuntu7.1: restart.
Feb 17 22:58:10 myserver123 mysqld_safe[15948]: started
Feb 17 22:58:11 myserver123 mysqld[15951]: 080217 22:58:11  InnoDB: Started; log sequence number 0 2185475
Feb 17 22:58:11 myserver123 mysqld[15951]: ^G/usr/sbin/mysqld: File '' not found (Errcode: 2)
Feb 17 22:58:11 myserver123 mysqld[15951]: 080217 22:58:11 [ERROR] Failed to open log (file '', errno 2)
Feb 17 22:58:11 myserver123 mysqld[15951]: 080217 22:58:11 [ERROR] Could not open log file
Feb 17 22:58:11 myserver123 mysqld[15951]: 080217 22:58:11 [ERROR] Can't init tc log
Feb 17 22:58:11 myserver123 mysqld[15951]: 080217 22:58:11 [ERROR] Aborting
Feb 17 22:58:11 myserver123 mysqld[15951]: 
Feb 17 22:58:11 myserver123 mysqld[15951]: 080217 22:58:11  InnoDB: Starting shutdown...
Feb 17 22:58:13 myserver123 mysqld[15951]: 080217 22:58:13  InnoDB: Shutdown completed; log sequence number 0 2185475
Feb 17 22:58:13 myserver123 mysqld[15951]: 080217 22:58:13 [Note] /usr/sbin/mysqld: Shutdown complete
Feb 17 22:58:13 myserver123 mysqld[15951]: 
Feb 17 22:58:13 myserver123 mysqld_safe[15997]: ended
Feb 17 22:58:25 myserver123 /etc/init.d/mysql[16114]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Feb 17 22:58:25 myserver123 /etc/init.d/mysql[16114]: ^G/usr/bin/mysqladmin: connect to server at 'localhost' failed
Feb 17 22:58:25 myserver123 /etc/init.d/mysql[16114]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
Feb 17 22:58:25 myserver123 /etc/init.d/mysql[16114]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Feb 17 22:58:25 myserver123 /etc/init.d/mysql[16114]: 
Feb 17 22:58:25 myserver123 xinetd[16133]: Reading included configuration file: /etc/xinetd.d/chargen [file=/etc/xinetd.conf] [line=1]
Feb 17 22:58:25 myserver123 xinetd[16133]: Reading included configuration file: /etc/xinetd.d/daytime [file=/etc/xinetd.d/daytime] [line=28]
Feb 17 22:58:25 myserver123 xinetd[16133]: Reading included configuration file: /etc/xinetd.d/echo [file=/etc/xinetd.d/echo] [line=26]
Feb 17 22:58:25 myserver123 xinetd[16133]: Reading included configuration file: /etc/xinetd.d/smtp_psa [file=/etc/xinetd.d/smtp_psa] [line=26]
Feb 17 22:58:25 myserver123 xinetd[16133]: Reading included configuration file: /etc/xinetd.d/smtps_psa [file=/etc/xinetd.d/smtps_psa] [line=11]
Feb 17 22:58:25 myserver123 xinetd[16133]: Reading included configuration file: /etc/xinetd.d/time [file=/etc/xinetd.d/time] [line=11]
Feb 17 22:58:25 myserver123 xinetd[16133]: added service ftp [file=/etc/inetd.conf] [line=2]
Feb 17 22:58:25 myserver123 xinetd[16133]: inetd.conf - Bad value for wait: nowait/1000 [file=/etc/inetd.conf] [line=5]
Feb 17 22:58:25 myserver123 xinetd[16133]: added service poppassd [file=/etc/inetd.conf] [line=5]
Feb 17 22:58:25 myserver123 xinetd[16133]: inetd.conf - Unknown user: svnowner [file=/etc/inetd.conf] [line=8]
Feb 17 22:58:25 myserver123 xinetd[16133]: removing chargen
Feb 17 22:58:25 myserver123 xinetd[16133]: removing chargen
Feb 17 22:58:25 myserver123 xinetd[16133]: removing daytime
Feb 17 22:58:25 myserver123 xinetd[16133]: removing daytime
Feb 17 22:58:25 myserver123 xinetd[16133]: removing echo
Feb 17 22:58:25 myserver123 xinetd[16133]: removing echo
Feb 17 22:58:25 myserver123 xinetd[16133]: removing time
Feb 17 22:58:25 myserver123 xinetd[16133]: removing time
Feb 17 22:58:25 myserver123 xinetd[16133]: xinetd Version 2.3.14 started with libwrap loadavg options compiled in.
Feb 17 22:58:25 myserver123 xinetd[16133]: Started working: 4 available services
Feb 17 22:58:27 myserver123 named[16150]: starting BIND 9.3.2 -t /var/named/run-root -c /etc/named.conf -u bind
Feb 17 22:58:27 myserver123 named[16150]: found 1 CPU, using 1 worker thread
Feb 17 22:58:27 myserver123 named[16150]: loading configuration from '/etc/named.conf'
Feb 17 22:58:27 myserver123 named[16150]: no IPv6 interfaces found
Feb 17 22:58:27 myserver123 named[16150]: listening on IPv4 interface lo, 127.0.0.1#53
Feb 17 22:58:27 myserver123 named[16150]: listening on IPv4 interface venet0:0, 87.230.93.211#53
Feb 17 22:58:27 myserver123 named[16150]: command channel listening on 127.0.0.1#953
Feb 17 22:58:27 myserver123 named[16150]: zone 0.0.127.IN-ADDR.ARPA/IN: loaded serial 20010622
Feb 17 22:58:27 myserver123 named[16150]: zone XX.XXX.XX.in-addr.arpa/IN: loaded serial 1203203027
Feb 17 22:58:27 myserver123 named[16150]: zone someweb.de/IN: loaded serial 1203203027
Feb 17 22:58:27 myserver123 named[16150]: zone someother.de/IN: loaded serial 1199994945
Feb 17 22:58:27 myserver123 named[16150]: zone myserver123.net/IN: loaded serial 1203197159
Feb 17 22:58:27 myserver123 named[16150]: running
Feb 17 22:58:27 myserver123 named[16150]: zone unionsundown.de/IN: sending notifies (serial 1199994945)
Feb 17 22:58:28 myserver123 mysqld_safe[16246]: started
Feb 17 22:58:28 myserver123 mysqld[16249]: 080217 22:58:28  InnoDB: Started; log sequence number 0 2185475
Feb 17 22:58:28 myserver123 mysqld[16249]: ^G/usr/sbin/mysqld: File '' not found (Errcode: 2)
Feb 17 22:58:28 myserver123 mysqld[16249]: 080217 22:58:28 [ERROR] Failed to open log (file '', errno 2)
Feb 17 22:58:28 myserver123 mysqld[16249]: 080217 22:58:28 [ERROR] Could not open log file
Feb 17 22:58:28 myserver123 mysqld[16249]: 080217 22:58:28 [ERROR] Can't init tc log
Feb 17 22:58:28 myserver123 mysqld[16249]: 080217 22:58:28 [ERROR] Aborting
Feb 17 22:58:28 myserver123 mysqld[16249]: 
Feb 17 22:58:28 myserver123 mysqld[16249]: 080217 22:58:28  InnoDB: Starting shutdown...
Feb 17 22:58:31 myserver123 mysqld[16249]: 080217 22:58:31  InnoDB: Shutdown completed; log sequence number 0 2185475
Feb 17 22:58:31 myserver123 mysqld[16249]: 080217 22:58:31 [Note] /usr/sbin/mysqld: Shutdown complete
Feb 17 22:58:31 myserver123 mysqld[16249]: 
Feb 17 22:58:31 myserver123 mysqld_safe[16293]: ended
Feb 17 22:58:43 myserver123 /etc/init.d/mysql[17473]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Feb 17 22:58:43 myserver123 /etc/init.d/mysql[17473]: ^G/usr/bin/mysqladmin: connect to server at 'localhost' failed
Feb 17 22:58:43 myserver123 /etc/init.d/mysql[17473]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
Feb 17 22:58:43 myserver123 /etc/init.d/mysql[17473]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Feb 17 22:58:43 myserver123 /etc/init.d/mysql[17473]: 
Feb 17 22:58:44 myserver123 qmail: 1203285524.043178 status: local 0/10 remote 0/20
Feb 17 22:58:55 myserver123 /usr/sbin/cron[17725]: (CRON) INFO (pidfile fd = 3)
Feb 17 22:58:55 myserver123 /usr/sbin/cron[17726]: (CRON) STARTUP (fork ok)
Feb 17 22:58:55 myserver123 /usr/sbin/cron[17726]: (CRON) INFO (Running @reboot jobs)
Feb 17 22:58:55 myserver123 init: no more processes left in this runlevel

Ich findes es schon mal sehr merkwürdig, dass in der Zeile
Code: 
Feb 17 22:58:28 myserver123 mysqld[16249]: ^G/usr/sbin/mysqld: File '' not found (Errcode: 2)
gar kein Dateinamen für die Log Datei gesetzt ist?!

Meine my.conf
Code: 
[client]
port            = 3306
socket          = /var/run/mysqld/mysqld.sock

[mysqld_safe]
socket          = /var/run/mysqld/mysqld.sock
nice            = 0
skip-bdb
set-variable = innodb_buffer_pool_size=2M
set-variable = innodb_additional_mem_pool_size=500K
set-variable = innodb_log_buffer_size=500K
set-variable = innodb_thread_concurrency=2

[mysqld]
set-variable=local-infile=0
user            = mysql
pid-file        = /var/run/mysqld/mysqld.pid
socket          = /var/run/mysqld/mysqld.sock
port            = 3306
basedir         = /usr
datadir         = /var/lib/mysql
tmpdir          = /tmp
language        = /usr/share/mysql/english
skip-external-locking
old_passwords   = 1
key_buffer              = 16M
max_allowed_packet      = 16M
thread_stack            = 128K
query_cache_limit       = 1048576
query_cache_size        = 16777216
query_cache_type        = 1
log-bin                 = /var/log/mysql/mysql-bin.log
expire-logs-days        = 20
max_binlog_size         = 104857600
skip-bdb
set-variable = innodb_buffer_pool_size=2M
set-variable = innodb_additional_mem_pool_size=500K
set-variable = innodb_log_buffer_size=500K
set-variable = innodb_thread_concurrency=2

[mysqldump]
quick
quote-names
max_allowed_packet      = 16M

[mysql]
#no-auto-rehash # faster start of mysql but no tab completition

[isamchk]
key_buffer              = 16M

# [MYSQL_CLUSTER]
# ndb-connectstring=127.0.0.1

Blöde ist halt, dass Plesk auch mit mysql arbeitet und ich jetzt keine Chance habe hier weiter zu doktorn...
Wäre schön was von euch zu hören. Kann ja sein, dass da jemand schon mal Probleme mit hatte....
ich weiss echt nicht mehr weiter!
 
Das ^G verwundert mich auch ein bisschen.
Guck mal in das Startscript rein: /etc/init.d/mysqld ob da alles stimmt.
 
Du findest meistens ein kleines unbedeutendes Logfile wenn Du Dich im MySQL-Datenverzeichnis umschaust: /var/lib/mysql/mysqld.log

huschi.
 
bernsteinkater said:
Editiere die Datei /var/log/mysql/mysql-bin.index und nehme dort die "@"-Zeichen raus.
Click to expand...
Code: 
root@myserver123:/var/log/mysql# ls -l
total 869
-rw-rw---- 1 mysql adm 801769 Feb 13 23:57 mysql-bin.000015
-rw-rw---- 1 mysql adm  79240 Feb 17 01:08 mysql-bin.000016
-rw-rw---- 1 mysql adm    117 Feb 14 00:07 mysql-bin.000017
-rw-rw---- 1 mysql adm    288 Feb 14 00:07 mysql-bin.index

Super Tip! Läuft! Nur warum zu Hölle wurde die überhaupt editert? Ich wars nicht. Oder passiert das beim Reboot? Oder Fehler beim Update? Hat Plesk oder HostEurope ne auto-Update Routine?! Weiß das vielleicht jemand?
Wenn das so wäre, sollte der Admin doch wenigstens mal informiert werden... also ich!


@Huschi: Danke, aber das File existiert bei mir nicht. Aber hat sich ja auch... bernsteinkater's Tip hats gebracht.
 
^G ist der Escape Code für die Bell (piepsen mit dem PC-Speaker) und das Initskript loggt wohl alle Ausgaben stupide über den Syslog-Daemon.
 
Ah, wieder was gelernt :)

Wie gut, dass Rootserver keinen Speaker haben...ich glaube ich würde es sonst keine 2 Minin einem RZ aushalten.... ;)
 
benshman said:
Super Tip! Läuft! Nur warum zu Hölle wurde die überhaupt editert? Ich wars nicht. Oder passiert das beim Reboot? Oder Fehler beim Update? Hat Plesk oder HostEurope ne auto-Update Routine?! Weiß das vielleicht jemand?
Click to expand...
Ich habe leider keine Ahnung wie die Zeichen in die Datei gekommen sind, habe es aber schon oefter beobachten koennen.
 
You must log in or register to reply here.
Back
Top