You are not logged in.
Since last update I did, there is a message that
[ *** ] A stop job is running for Mariadb database service
and it take 3mins on shutdown my machine, Acer C720 Chromebook.
$ journalctl -u mariadb.service
says:
Jun 18 16:21:13 mshArch systemd[1]: Stopping MariaDB database server...
Jun 18 16:21:13 mshArch mysqld[380]: 2017-06-18 16:21:13 140454865188608 [Note] InnoDB: FTS optimize thread exiting.
Jun 18 16:21:13 mshArch mysqld[380]: 2017-06-18 16:21:13 140455487286016 [Note] InnoDB: Starting shutdown...
Jun 18 16:21:13 mshArch mysqld[380]: 2017-06-18 16:21:13 140455487286016 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool
Jun 18 16:21:15 mshArch mysqld[380]: 170618 16:21:15 [ERROR] mysqld got signal 11 ;
Jun 18 16:21:15 mshArch mysqld[380]: This could be because you hit a bug. It is also possible that this binary
Jun 18 16:21:15 mshArch mysqld[380]: or one of the libraries it was linked against is corrupt, improperly built,
Jun 18 16:21:15 mshArch mysqld[380]: or misconfigured. This error can also be caused by malfunctioning hardware.
Jun 18 16:21:15 mshArch mysqld[380]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Jun 18 16:21:15 mshArch mysqld[380]: We will try our best to scrape up some info that will hopefully help
Jun 18 16:21:15 mshArch mysqld[380]: diagnose the problem, but since we have already crashed,
Jun 18 16:21:15 mshArch mysqld[380]: something is definitely wrong and this may fail.
Jun 18 16:21:15 mshArch mysqld[380]: Server version: 10.1.24-MariaDB
Jun 18 16:21:15 mshArch mysqld[380]: key_buffer_size=16777216
Jun 18 16:21:15 mshArch mysqld[380]: read_buffer_size=262144
Jun 18 16:21:15 mshArch mysqld[380]: max_used_connections=0
Jun 18 16:21:15 mshArch mysqld[380]: max_threads=153
Jun 18 16:21:15 mshArch mysqld[380]: thread_count=0
Jun 18 16:21:15 mshArch mysqld[380]: It is possible that mysqld could use up to
Jun 18 16:21:15 mshArch mysqld[380]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 137013 K bytes of memory
Jun 18 16:21:15 mshArch mysqld[380]: Hope that's ok; if not, decrease some variables in the equation.
Jun 18 16:21:15 mshArch mysqld[380]: Thread pointer: 0x0
Jun 18 16:21:15 mshArch mysqld[380]: Attempting backtrace. You can use the following information to find out
Jun 18 16:21:15 mshArch mysqld[380]: where mysqld died. If you see no messages after this, something went
Jun 18 16:21:15 mshArch mysqld[380]: terribly wrong...
Jun 18 16:21:15 mshArch mysqld[380]: 2017-06-18 16:21:15 140455487286016 [Note] InnoDB: Shutdown completed; log sequence number 1618107
Jun 18 16:21:18 mshArch mysqld[380]: stack_bottom = 0x0 thread_stack 0x48400
Jun 18 16:22:43 mshArch systemd[1]: mariadb.service: State 'stop-sigterm' timed out. Skipping SIGKILL.
Jun 18 16:24:13 mshArch systemd[1]: mariadb.service: State 'stop-final-sigterm' timed out. Skipping SIGKILL. Entering failed mode.
Jun 18 16:24:13 mshArch systemd[1]: Stopped MariaDB database server.
Jun 18 16:24:13 mshArch systemd[1]: mariadb.service: Unit entered failed state.
Jun 18 16:24:13 mshArch systemd[1]: mariadb.service: Failed with result 'timeout'.
I googled around but found no solution.
Last edited by duyinthee (2017-06-19 08:53:24)
Offline
Offline
Thanks,
Downgrading jemalloc from 5.0.0-2 to 4.5.0-1 works for me.
$ pacman -Ss jemalloc
extra/jemalloc 5.0.0-2 [installed: 4.5.0-1]
General-purpose scalable concurrent malloc implementation
Offline
This Morning, I got jemalloc-1:4.5.0-1 installed by updating system.
It resolved the problem. It is a very quick fix.
Thank maintainer for works and listening to.
Offline