Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
10.4.7
-
Ubuntu 18.04.3, Kernel 5.0.0-25-generic
Description
Server is member of a Master-Master using GTID replication.
Server has been upgraded from latest GA 10.3.
systemctl stop mariadb outputs nothing, but service remains active.
# # systemctl status mariadb
|
â mariadb.service - MariaDB 10.4.7 database server |
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
|
Drop-In: /etc/systemd/system/mariadb.service.d
|
ââMY_SPECIAL.conf, migrated-from-my.cnf-settings.conf, override.conf
|
Active: failed (Result: timeout) since Sun 2019-08-11 18:21:15 CEST; 40s ago |
Docs: man:mysqld(8) |
https://mariadb.com/kb/en/library/systemd/ |
Main PID: 2269 |
Status: "Shutdown in progress" |
Tasks: 27 (limit: 4533) |
CGroup: /system.slice/mariadb.service
|
ââ2269 /usr/sbin/mysqld
|
|
|
Aug 11 18:15:44 srv-nur mysqld[2269]: 2019-08-11 18:15:44 0 [Note] /usr/sbin/mysqld (mysqld 10.4.7-MariaDB-1:10.4.7+maria~bionic-log) starting as process 2269 ... |
Aug 11 18:15:47 srv-nur /etc/mysql/debian-start[2315]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored |
Aug 11 18:15:47 srv-nur /etc/mysql/debian-start[2315]: Looking for 'mysql' as: /usr/bin/mysql |
Aug 11 18:15:47 srv-nur /etc/mysql/debian-start[2315]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck |
Aug 11 18:15:47 srv-nur /etc/mysql/debian-start[2315]: This installation of MariaDB is already upgraded to 10.4.7-MariaDB, use --force if you still need to run mysql_upgrade |
Aug 11 18:19:44 srv-nur systemd[1]: mariadb.service: State 'stop-sigterm' timed out. Skipping SIGKILL. |
Aug 11 18:21:15 srv-nur systemd[1]: mariadb.service: State 'stop-final-sigterm' timed out. Skipping SIGKILL. Entering failed mode. |
Aug 11 18:21:15 srv-nur systemd[1]: mariadb.service: Failed with result 'timeout'. |
and from error.log:
2019-08-11 18:18:14 0 [Note] /usr/sbin/mysqld (initiated by: unknown): Normal shutdown |
2019-08-11 18:18:14 0 [Note] Event Scheduler: Purging the queue. 0 events |
2019-08-11 18:18:14 11 [Note] Error reading relay log event: slave SQL thread was killed |
2019-08-11 18:18:14 0 [Note] InnoDB: FTS optimize thread exiting. |
2019-08-11 18:18:14 11 [Note] Slave SQL thread exiting, replication stopped in log 'cluster-bin.000050' at position 3135870; GTID position '0-1-87716,1-1-11383278,2-2-3302009' |
2019-08-11 18:18:14 10 [Note] Slave I/O thread exiting, read up to log 'cluster-bin.000050', position 3355631; GTID position 1-1-11383278,0-1-87716,2-2-3302520 |
2019-08-11 18:18:34 0 [Warning] /usr/sbin/mysqld: Thread 15 (user : '') did not exit |
2019-08-11 18:18:34 0 [Warning] /usr/sbin/mysqld: Thread 14 (user : '') did not exit |
2019-08-11 18:18:34 0 [Warning] /usr/sbin/mysqld: Thread 13 (user : '') did not exit |
2019-08-11 18:18:34 0 [Warning] /usr/sbin/mysqld: Thread 12 (user : '') did not exit |
Only solution to bring server back is to kill -9 the process and restart the server.
Attachments
Issue Links
- is duplicated by
-
-
- Closed
-