MySQL startet nichtmehr

conym18

Member
Hallo,

nachdem /var auf dem Server voll war, habe ich ein paar Files gelöscht und den kompletten Server neu gestartet.

Seitdem will der MySQL nicht mehr starten.

Fehlermeldung:
Code:
Starting service MySQL warning: /var/run/mysql/mysql.sock didn't appear within 30 seconds
chmod: cannot access `/var/run/mysql/mysqld.pid': No such file or directory


my.cnf:
Code:
# Example MySQL config file for medium systems.
#
# This is for a system with little memory (32M - 64M) where MySQL plays
# an important part, or systems up to 128M where MySQL is used together with
# other programs (such as a web server)
#
# You can copy this file to
# /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is /var/lib/mysql) or
# ~/.my.cnf to set user-specific options.
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.

# The following options will be passed to all MySQL clients
[client]
#password       = your_password
port            = 3306
socket          = /var/run/mysql/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
local-infile=0
set-variable=local-infile=0
port            = 3306
socket          = /var/run/mysql/mysql.sock
# Change following line if you want to store your database elsewhere
datadir = /var/lib/mysql
skip-locking
key_buffer_size = 16M
max_allowed_packet = 1M
table_open_cache = 64
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M

# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
#
#skip-networking

# Replication Master Server (default)
# binary logging is required for replication
log-bin=mysql-bin

# binary logging format - mixed recommended
binlog_format=mixed

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id       = 1

# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
#    the syntax is:
#
#    CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
#    MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
#    where you replace <host>, <user>, <password> by quoted strings and
#    <port> by the master's port number (3306 by default).
#
#    Example:
#
#    CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
#    MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
#    start replication for the first time (even unsuccessfully, for example
#    if you mistyped the password in master-password and the slave fails to
#    connect), the slave will create a master.info file, and any later
#    change in this file to the variables' values below will be ignored and
#    overridden by the content of the master.info file, unless you shutdown
#    the slave server, delete master.info and restart the slaver server.
#    For that reason, you may want to leave the lines below untouched
#    (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id       = 2
#
# The replication master for this slave - required
#master-host     =   <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user     =   <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password =   <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port     =  <port>
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin

# Point the following paths to different dedicated disks
#tmpdir         = /tmp/
#log-update     = /path-to-dedicated-directory/hostname

# Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = /var/lib/mysql/
#innodb_data_file_path = ibdata1:10M:autoextend
#innodb_log_group_home_dir = /var/lib/mysql/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
#innodb_buffer_pool_size = 16M
#innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 5M
#innodb_log_buffer_size = 8M
#innodb_flush_log_at_trx_commit = 1
#innodb_lock_wait_timeout = 50

# The safe_mysqld script
[safe_mysqld]
log-error       = /var/log/mysql/mysqld.log
socket          = /var/run/mysql/mysql.sock

[mysqldump]
socket          = /var/run/mysql/mysql.sock
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[myisamchk]
key_buffer_size = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout

[mysqld_multi]
mysqld     = /usr/bin/mysqld_safe
mysqladmin = /usr/bin/mysqladmin
log        = /var/log/mysqld_multi.log
# user       = multi_admin
# password   = secret

# If you want to use mysqld_multi uncomment 1 or more mysqld sections
# below or add your own ones.

# WARNING
# --------
# If you uncomment mysqld1 than make absolutely sure, that database mysql,
# configured above, is not started.  This may result in corrupted data!
# [mysqld1]
# port       = 3306
# datadir    = /var/lib/mysql
# pid-file   = /var/lib/mysql/mysqld.pid
# socket     = /var/lib/mysql/mysql.sock
# user       = mysql

# [mysqld2]
# port       = 3307
# datadir    = /var/lib/mysql-databases/mysqld2
# pid-file   = /var/lib/mysql-databases/mysqld2/mysql.pid
# socket     = /var/lib/mysql-databases/mysqld2/mysql.sock
# user       = mysql

# [mysqld3]
# port       = 3308
# datadir    = /var/lib/mysql-databases/mysqld3
# pid-file   = /var/lib/mysql-databases/mysqld3/mysql.pid
# socket     = /var/lib/mysql-databases/mysqld3/mysql.sock
# user       = mysql

# [mysqld6]
# port       = 3309
# datadir    = /var/lib/mysql-databases/mysqld6
# pid-file   = /var/lib/mysql-databases/mysqld6/mysql.pid
# socket     = /var/lib/mysql-databases/mysqld6/mysql.sock
# user       = mysql


ls -lah /var/run/mysql:
Code:
drwxrwxrwx  2 mysql mysql 4.0K Feb 24 08:40 .
drwxr-xr-x 20 root  root  4.0K Feb 24 08:24 ..
-rwxrwxrwx  1 root  root     0 Feb 24 08:40 mysql.pid
-rwxrwxrwx  1 root  root    22 Feb 24 08:40 tmpdir


PS -ef | grep mysqld:
Code:
root     16645  7413  0 08:46 pts/1    00:00:00 grep mysqld

Ein manuelles anlegen der /var/run/mysql/mysql.sock mit den rechten 777 (root.root) hat das Ergebniss, dass die Datei beim versuch den MySQL zu starten wieder gelöscht wird.

In der /var/log/mysql/mysqld.log steht folgendes drin:

tail -30 mysqld.log
Code:
140224  8:42:49 [Note] Plugin 'FEDERATED' is disabled.
140224  8:42:49  InnoDB: Started; log sequence number 0 3691670508
/usr/sbin/mysqld: File './mysql-bin.000052' not found (Errcode: 2)
140224  8:42:49 [ERROR] Failed to open log (file './mysql-bin.000052', errno 2)
140224  8:42:49 [ERROR] Could not open log file
140224  8:42:49 [ERROR] Can't init tc log
140224  8:42:49 [ERROR] Aborting

140224  8:42:49  InnoDB: Starting shutdown...
140224  8:42:54  InnoDB: Shutdown completed; log sequence number 0 3691670508
140224  8:42:54 [Note] /usr/sbin/mysqld: Shutdown complete

140224 08:42:54 mysqld_safe mysqld from pid file /var/run/mysql/mysqld.pid ended
140224 08:44:58 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140224  8:44:58 [Warning] /usr/sbin/mysqld: Option '--set-variable' is deprecated. Use --variable-name=value instead.
140224  8:44:58 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
140224  8:44:58 [Note] Plugin 'ndbcluster' is disabled.
140224  8:44:58 [Note] Plugin 'FEDERATED' is disabled.
140224  8:44:58  InnoDB: Started; log sequence number 0 3691670508
/usr/sbin/mysqld: File './mysql-bin.000052' not found (Errcode: 2)
140224  8:44:58 [ERROR] Failed to open log (file './mysql-bin.000052', errno 2)
140224  8:44:58 [ERROR] Could not open log file
140224  8:44:58 [ERROR] Can't init tc log
140224  8:44:58 [ERROR] Aborting

140224  8:44:58  InnoDB: Starting shutdown...
140224  8:45:03  InnoDB: Shutdown completed; log sequence number 0 3691670508
140224  8:45:03 [Note] /usr/sbin/mysqld: Shutdown complete

140224 08:45:03 mysqld_safe mysqld from pid file /var/run/mysql/mysqld.pid ended


Was kann ich noch prüfen/machen das der MySQL wieder läuft?
 
Last edited by a moderator:
ok habe es hinbekommen.

es lag irgendwie am logging.

hab das "log-bin" und "binlog-format" ausgeschaltet und nun geht es wieder.
 
steht ja auch da:
Code:
/usr/sbin/mysqld: File './mysql-bin.000052' not found (Errcode: 2)
140224  8:44:58 [ERROR] Failed to open log (file './mysql-bin.000052', errno 2)
140224  8:44:58 [ERROR] Could not open log file
140224  8:44:58 [ERROR] Can't init tc log
140224  8:44:58 [ERROR] Aborting

"einfach so" binlogs löschen ist keine gute Idee, da gibt's - wenn man nicht weiß, was man wie manuell tun sollte - Befehle innerhalb von MySQL die das sauber für einen erledigen.

Ggf. auch mal nachlesen, für was diese Logfiles denn da sind - nicht daß Du dir bei so einer Aktion noch die DB zerlegst...
 
Back
Top