msql will nicht starten
Nach heutigen Neustart unseres Servers wegen neuem kernel startet völlig
überraschend
der maria-db server nicht mehr.
Da brauch ich mal wirklich dringend Hilfe:
also /etc/init.d/mysql start
[....] Starting mysql (via systemctl): mysql.serviceJob for
mysql.service failed because the control process exited with error code.
See "systemctl status mysql.service" and "journalctl -xe" for details.
dann also:
systemctl status mysql.service :
● mysql.service - LSB: Start and stop the mysql database server daemon
Loaded: loaded (/etc/init.d/mysql; generated)
Active: failed (Result: exit-code) since Sat 2020-05-02 12:54:24
CEST; 13min ago
Docs: man:systemd-sysv-generator(8)
Process: 6962 ExecStart=/etc/init.d/mysql start (code=exited,
status=1/FAILURE)
Mai 02 12:53:53 ottoserver systemd[1]: Starting LSB: Start and stop the
mysql database server daemon...
Mai 02 12:54:24 ottoserver mysql[6962]: Starting MariaDB database
server: mysqld . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. failed!
Mai 02 12:54:24 ottoserver systemd[1]: mysql.service: Control process
exited, code=exited, status=1/FAILURE
Mai 02 12:54:24 ottoserver systemd[1]: mysql.service: Failed with result
'exit-code'.
Mai 02 12:54:24 ottoserver systemd[1]: Failed to start LSB: Start and
stop the mysql database server daemon.
und journalctl -xe:
Mai 02 13:10:29 ottoserver /etc/init.d/mysql[8168]: 0 processes alive
and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping'
resulted in
Mai 02 13:10:29 ottoserver /etc/init.d/mysql[8168]: [61B blob data]
Mai 02 13:10:29 ottoserver /etc/init.d/mysql[8168]: error: 'Can't
connect to local MySQL server through socket
'/var/run/mysqld/mysqld.sock' (2)'
Mai 02 13:10:29 ottoserver /etc/init.d/mysql[8168]: Check that mysqld is
running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Mai 02 13:10:29 ottoserver /etc/init.d/mysql[8168]:
Mai 02 13:10:29 ottoserver mysql[7703]: Starting MariaDB database
server: mysqld . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. failed!
Mai 02 13:10:29 ottoserver systemd[1]: mysql.service: Control process
exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mysql.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Mai 02 13:10:29 ottoserver systemd[1]: mysql.service: Failed with result
'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mysql.service has entered the 'failed' state with result
'exit-code'.
Was ist zum Teufel 61B blob data. Weiß jemand wie ich das wieder zum
Laufen kriege?
Die DB wird dringend gebraucht.
System debian 10.3 32 bit, server ohne Gui. Versorgt im Lan die Clients
mit der DB.
Danke
Reply to: