Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Incomplete
-
10.4.6
-
None
-
Ubuntu 16.04 4.15.0-55-generic #60~16.04.2-Ubuntu
Description
We have just upgraded from 10.3 to 10.4 on our slave database server to try and move away from a SEGV(11) issue we were seeing on our master server running 10.3 (no stack trace available for that issue).
The upgrade seemed to happen OK, but I needed to reboot the server after a kernel update, since the reboot the mariadb instance on the slave will not start (master still running 10.3).
error logs shows:
Version: '10.4.6-MariaDB-1:10.4.6+maria~xenial-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
|
2019-07-22 16:05:20 0 [Note] /usr/sbin/mysqld (initiated by: unknown): Normal shutdown
|
2019-07-22 16:05:20 0 [Note] Event Scheduler: Purging the queue. 0 events
|
2019-07-22 16:05:20 0 [Note] InnoDB: FTS optimize thread exiting.
|
2019-07-22 16:05:40 0 [Warning] /usr/sbin/mysqld: Thread 11 (user : '') did not exit
|
|
|
2019-07-22 16:05:40 0 [Warning] /usr/sbin/mysqld: Thread 19 (user : '') did not exit
|
|
|
2019-07-22 16:05:40 0 [Warning] /usr/sbin/mysqld: Thread 18 (user : '') did not exit
|
|
|
2019-07-22 16:05:40 0 [Warning] /usr/sbin/mysqld: Thread 17 (user : '') did not exit
|
|
|
2019-07-22 16:05:40 0 [Warning] /usr/sbin/mysqld: Thread 16 (user : '') did not exit
|
|
|
2019-07-22 16:05:40 0 [Warning] /usr/sbin/mysqld: Thread 15 (user : '') did not exit
|
|
|
2019-07-22 16:05:40 0 [Warning] /usr/sbin/mysqld: Thread 14 (user : '') did not exit
|
|
|
2019-07-22 16:05:40 0 [Warning] /usr/sbin/mysqld: Thread 13 (user : '') did not exit
|
|
|
2019-07-22 16:05:40 0 [Warning] /usr/sbin/mysqld: Thread 12 (user : '') did not exit
|
|
|
2019-07-22 16:05:40 0 [Warning] /usr/sbin/mysqld: Thread 10 (user : '') did not exit
|
Attachments
Issue Links
- duplicates
-
-
- Closed
-