Hello, everybody,
after the server (VM / UCS 4.4-3) with Kopano did not react anymore I switched it off. After that the kopano-server doesn’t start anymore because the mysql-server doesn’t start anymore:
root@saturn:/etc/mysql/conf.d# service mysql restart
Job for mariadb.service failed because a fatal signal was delivered to the control process.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
root@saturn:/etc/mysql/conf.d# service mysql status
● mariadb.service - MariaDB 10.1.38 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Drop-In: /lib/systemd/system/mariadb.service.d
└─univention.conf
Active: activating (auto-restart) (Result: signal) since Sat 2020-03-21 11:10:18 CET; 3s ago
Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/
Process: 16691 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=killed, signal=ABRT)
Process: 16590 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code
Process: 16586 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 16584 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Main PID: 16691 (code=killed, signal=ABRT)
Status: "InnoDB: Fatal: Trying to access page number 6156546 in space 0 space name ./ibdata1, which is outside the tablespace bounds. Byte offset 0, len 16384 i/o type 10.Please check that the configurat
Mär 21 11:10:18 saturn systemd[1]: Failed to start MariaDB 10.1.38 database server.
Mär 21 11:10:18 saturn systemd[1]: mariadb.service: Unit entered failed state.
Mär 21 11:10:18 saturn systemd[1]: mariadb.service: Failed with result 'signal'.
root@saturn:/etc/mysql/conf.d# service mysql status
● mariadb.service - MariaDB 10.1.38 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Drop-In: /lib/systemd/system/mariadb.service.d
└─univention.conf
Active: activating (auto-restart) (Result: signal) since Sat 2020-03-21 11:10:18 CET; 3s ago
Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/
Process: 16691 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=killed, signal=ABRT)
Process: 16590 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code
Process: 16586 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 16584 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Main PID: 16691 (code=killed, signal=ABRT)
Status: "InnoDB: Fatal: Trying to access page number 6156546 in space 0 space name ./ibdata1, which is outside the tablespace bounds. Byte offset 0, len 16384 i/o type 10.Please check that the configurat
Mär 21 11:10:18 saturn systemd[1]: Failed to start MariaDB 10.1.38 database server.
Mär 21 11:10:18 saturn systemd[1]: mariadb.service: Unit entered failed state.
Mär 21 11:10:18 saturn systemd[1]: mariadb.service: Failed with result 'signal'.
root@saturn:/etc/mysql/conf.d#
root@saturn:/etc/mysql/conf.d#
root@saturn:/etc/mysql/conf.d#
root@saturn:/etc/mysql/conf.d#
root@saturn:/etc/mysql/conf.d#
root@saturn:/etc/mysql/conf.d#
root@saturn:/etc/mysql/conf.d#
root@saturn:/etc/mysql/conf.d#
root@saturn:/etc/mysql/conf.d#
root@saturn:/etc/mysql/conf.d#
root@saturn:/etc/mysql/conf.d#
root@saturn:/etc/mysql/conf.d#
root@saturn:/etc/mysql/conf.d#
root@saturn:/etc/mysql/conf.d# journalctl -xe
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit mariadb.service has begun starting up.
Mär 21 11:10:53 saturn mysqld[17470]: 2020-03-21 11:10:53 140638832786816 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB-0+deb9u1) starting as process 17470 ...
Mär 21 11:10:54 saturn systemd[1]: mariadb.service: Main process exited, code=killed, status=6/ABRT
Mär 21 11:10:54 saturn systemd[1]: Failed to start MariaDB 10.1.38 database server.
-- Subject: Unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit mariadb.service has failed.
--
-- The result is failed.
Mär 21 11:10:54 saturn systemd[1]: mariadb.service: Unit entered failed state.
Mär 21 11:10:54 saturn systemd[1]: mariadb.service: Failed with result 'signal'.
Mär 21 11:10:55 saturn kopano-spooler[405]: Logon to file:///var/run/kopano/server.sock: Remote side closed connection.
Mär 21 11:10:55 saturn kopano-spooler[405]: HrLogon server "default:" user "SYSTEM": network error
Mär 21 11:10:55 saturn kopano-spooler[405]: Unable to open admin session: network error (80040115)
Mär 21 11:10:55 saturn kopano-search[415]: [error ] Logon to file:///var/run/kopano/server.sock: Remote side closed connection.
Mär 21 11:10:55 saturn kopano-search[415]: [error ] HrLogon server "default:" user "SYSTEM": network error
Mär 21 11:10:55 saturn kopano-search[415]: 2020-03-21 11:10:55,589 - search - WARNING - could not connect to server at 'default:', retrying in 5 sec
Mär 21 11:10:58 saturn kopano-spooler[405]: Logon to file:///var/run/kopano/server.sock: Remote side closed connection.
Mär 21 11:10:58 saturn kopano-spooler[405]: HrLogon server "default:" user "SYSTEM": network error
Mär 21 11:10:58 saturn kopano-spooler[405]: Unable to open admin session: network error (80040115)
Mär 21 11:10:59 saturn systemd[1]: mariadb.service: Service hold-off time over, scheduling restart.
Mär 21 11:10:59 saturn systemd[1]: Stopped MariaDB 10.1.38 database server.
-- Subject: Unit mariadb.service has finished shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit mariadb.service has finished shutting down.
Mär 21 11:10:59 saturn systemd[1]: Starting MariaDB 10.1.38 database server...
-- Subject: Unit mariadb.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit mariadb.service has begun starting up.
Mär 21 11:10:59 saturn mysqld[17600]: 2020-03-21 11:10:59 140349579808128 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB-0+deb9u1) starting as process 17600 ...
Mär 21 11:11:00 saturn systemd[1]: mariadb.service: Main process exited, code=killed, status=6/ABRT
Mär 21 11:11:00 saturn systemd[1]: Failed to start MariaDB 10.1.38 database server.
-- Subject: Unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit mariadb.service has failed.
--
-- The result is failed.
Mär 21 11:11:00 saturn systemd[1]: mariadb.service: Unit entered failed state.
Mär 21 11:11:00 saturn systemd[1]: mariadb.service: Failed with result 'signal'.
Mär 21 11:11:00 saturn kopano-search[415]: [error ] Logon to file:///var/run/kopano/server.sock: Remote side closed connection.
Mär 21 11:11:00 saturn kopano-search[415]: [error ] HrLogon server "default:" user "SYSTEM": network error
Mär 21 11:11:00 saturn kopano-search[415]: 2020-03-21 11:11:00,595 - search - WARNING - could not connect to server at 'default:', retrying in 5 sec
Hello, everybody,
after the server (VM / UCS 4.4-3) with Kopano did not react anymore I switched it off. After that the kopano-server doesn’t start anymore because the mysql-server doesn’t start anymore:
there is a way to recover the database?
with best
sven