ERROR! The server quit without updating PID file (/var/lib/mysql/*hostname*.pid)

Maarten

New member
Joined
Jul 31, 2015
Messages
1
I upgraded my MySQL server to 5.5 using CustomBuild. However, I keep getting this error when I try to start the MySQL server again.

here are the latest entries from the hostname_error.log

Code:
150731 18:59:07 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
150731 18:59:07 [Warning] options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-slave-statements have no effect if --log_slow_queries is not set
150731 18:59:07 [Note] /usr/sbin/mysqld (mysqld 5.5.45-log) starting as process 39308 ...
150731 18:59:07 [Note] Plugin 'FEDERATED' is disabled.
150731 18:59:07 InnoDB: The InnoDB memory heap is disabled
150731 18:59:07 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150731 18:59:07 InnoDB: Compressed tables use zlib 1.2.3
150731 18:59:07 InnoDB: Using Linux native AIO
150731 18:59:07 InnoDB: Initializing buffer pool, size = 128.0M
150731 18:59:07 InnoDB: Completed initialization of buffer pool
InnoDB: Error: space header page consists of zero bytes in data file ./ibdata1
150731 18:59:07 InnoDB: Could not open or create data files.
150731 18:59:07 InnoDB: If you tried to add new data files, and it failed here,
150731 18:59:07 InnoDB: you should now edit innodb_data_file_path in my.cnf back
150731 18:59:07 InnoDB: to what it was, and remove the new ibdata files InnoDB created
150731 18:59:07 InnoDB: in this failed attempt. InnoDB only wrote those files full of
150731 18:59:07 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
150731 18:59:07 InnoDB: remove old data files which contain your precious data!
150731 18:59:07 [ERROR] Plugin 'InnoDB' init function returned error.
150731 18:59:07 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
150731 18:59:07 [ERROR] Unknown/unsupported storage engine: InnoDB
150731 18:59:07 [ERROR] Aborting

150731 18:59:07 [Note] /usr/sbin/mysqld: Shutdown complete

150731 18:59:07 mysqld_safe mysqld from pid file /var/lib/mysql/AHV-ID-2333.vps.awcloud.nl.pid ended

And here is my my.cnf

Code:
 Example MySQL config file for large systems.
#
# This is for a large system with memory = 512M where the system runs mainly
# MySQL.
#
# MySQL programs look for option files in a set of
# locations which depend on the deployment platform.
# You can copy this option file to one of those
# locations. For information about these locations, see:
# http://dev.mysql.com/doc/mysql/en/option-files.html
#
# 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/lib/mysql/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port            = 3306
socket          = /var/lib/mysql/mysql.sock
skip-external-locking
key_buffer_size = 256M
max_allowed_packet = 1M
table_open_cache = 256
sort_buffer_size = 1M
read_buffer_size = 1M
read_rnd_buffer_size = 4M
myisam_sort_buffer_size = 64M
thread_cache_size = 8
query_cache_size= 16M
# Try number of CPU's*2 for thread_concurrency
thread_concurrency = 8

# 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

# 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 = 256M
#innodb_additional_mem_pool_size = 20M
# Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 256M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 2
innodb_thread_concurrency = 2
innodb_flus_method = normal
#innodb_lock_wait_timeout = 50

[mysqldump]
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 = 128M
sort_buffer_size = 128M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout

If I remove the my.cnf file completely nothing changes.
 
Hello,

Your InnoDB tables seem to be corrupted:

InnoDB: Error: space header page consists of zero bytes in data file ./ibdata1
...
...
...
150731 18:59:07 [ERROR] Plugin 'InnoDB' init function returned error.
150731 18:59:07 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
150731 18:59:07 [ERROR] Unknown/unsupported storage engine: InnoDB

You might need to recover your MySQL data. Please search the forums for instructions, as there are already several similar threads here.
 
Back
Top