# systemctl status mysql
● mysql.service - LSB: Start and stop the mysql database server daemon
Loaded: loaded (/etc/init.d/mysql)
Active: failed (Result: exit-code) since Tue 2018-02-13 10:09:59 CET; 41s ago
Process: 31320 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE)
Feb 13 10:09:59 DietPi /etc/init.d/mysql[32143]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Feb 13 10:09:59 DietPi /etc/init.d/mysql[32143]: [61B blob data]
Feb 13 10:09:59 DietPi /etc/init.d/mysql[32143]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
Feb 13 10:09:59 DietPi /etc/init.d/mysql[32143]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Feb 13 10:09:59 DietPi /etc/init.d/mysql[32143]:
Feb 13 10:09:59 DietPi mysql[31320]: Starting MySQL database server: mysqld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failed!
Feb 13 10:09:59 DietPi systemd[1]: mysql.service: control process exited, code=exited status=1
Feb 13 10:09:59 DietPi systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
Feb 13 10:09:59 DietPi systemd[1]: Unit mysql.service entered failed state.
Do you suggest that my working mysql installation might have been re-configured by the scripts during upgrade and therefore is not working anymore? By the way, I have no MariaDB installed, and as far as I know the two database servers should be completely compatible for external programs accessing to the database. Besides nextcloud, I had Kodi instances sharing the library through Mysql.
@gaggio:
MySQL logs can be also found within journalctl -r best directly after service restart attempt.
Can you try to remove/backup the /etc/mysql/conf.d/99-dietpi-4byte.cnf and restart mysql?
If it works, you also have to remove the 4byte setting from Nextcloud config.php.
Actually this settings should work with MySQL, but since it was the only thing we touched on 159 update, it is worth trying.
Thanks for your reply. Unfortunatley, even removing that file, the result is still the same. With journalctl -r the messages are the same I posted before, just in reverse order:
Feb 15 09:21:41 DietPi systemd[1]: Unit mysql.service entered failed state.
Feb 15 09:21:41 DietPi systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
Feb 15 09:21:41 DietPi systemd[1]: mysql.service: control process exited, code=exited status=1
Feb 15 09:21:41 DietPi mysql[26670]: Starting MySQL database server: mysqld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failed!
Feb 15 09:21:41 DietPi /etc/init.d/mysql[27457]:
Feb 15 09:21:41 DietPi /etc/init.d/mysql[27457]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Feb 15 09:21:41 DietPi /etc/init.d/mysql[27457]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
Feb 15 09:21:41 DietPi /etc/init.d/mysql[27457]: [61B blob data]
Feb 15 09:21:41 DietPi /etc/init.d/mysql[27457]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in