I had a few problems with the update of the MySQL server from 5.5.31 to 5.5.33.
apt-get upgrade
only led to
Error: Sub-process /usr/bin/dpkg returned an error code (1)
.
For me it has helped to enter the full path for log-bin
in /etc/mysql/my.cnf
and .to set innodb_data_home_dir
.
I changed
log-bin = mysql-bin
to
log-bin = /var/lib/mysql/mysql-bin
and set innodb_data_home_dir
:
innodb_data_home_dir = /var/lib/mysql
Next, the init script /etc/init.d/mysql
had to be modified: put exit 0
before the first command in the start-case. The reason for this is to run the start block of the script successfully. In this case, although nothing happens, but it looks like there’s all the best. 😉
After that apt-get upgrade
ran without problems.
Finally exit 0
has to be deleted from /etc/init.d/mysqld
and the new mysql-server could be started by /etc/init.d/mysql start
.
Thank you for this! Seems like an apt-get update messed something up on my Debian Wheezy and mysql wasn’t starting.
The second post from this forum linked here: https://www.howtoforge.com/community/threads/mysql-server-5-5.65361/
Executing your post + doing a chown mysql:mysql * in /etc/mysq/ allowed mysql to work again!