MariaDB consistently crashes in collect_tables on Aria checkpoint execution
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MariaDB |
Fix Released
|
High
|
Michael Widenius |
Bug Description
Hi,
This issue occurs on MariaDB 5.2.10 and 5.3.2-beta
OS info:
$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.6 (Tikanga)
Memory (with MariaDB running):
$ free -m
total used free shared buffers cached
Mem: 16050 14153 1897 0 242 12572
-/+ buffers/cache: 1338 14712
Swap: 4095 89 4006
This occurs just about every 5 minutes on the dot, but sometimes it crashes out of band. mysqld_safe continuously restarts it.
Attached info includes:
cpuinfo (from /proc)
mysql table creation script
my.cnf
mysqld.log
To repro, simply create a db, run the data_tables.sql script to create all the tables and it will start to crash.
Related branches
Changed in maria: | |
milestone: | none → 5.2 |
Changed in maria: | |
importance: | Undecided → High |
Changed in maria: | |
status: | New → In Progress |
Changed in maria: | |
status: | In Progress → Fix Committed |
Changed in maria: | |
status: | Fix Committed → Fix Released |
Hi,
Just creating the tables doesn't seem to cause the crash, at least it isn't crashing for me so far. I used the same settings as you.
Your log suggests that your server is not idle, you have some scheduled activity, in a cronjob or such -- something that connects to the server and apparently executes something. Could you find out what is executed? The connection looks local, that is whatever is running, is probably on the same box.
If you could turn on the general log temporarily, its output could help to understand what flow causes the problem. To turn on logging, set general_log=1 and global general_ log_file= <file location>. If you do it on a running server, please make sure you are changing global variables (set global); but it would be more useful if you could set them in the cnf file, so we see the whole activity from the server restart and till the crash.
One more thing, in the log file, when the problem started, the server complains about mysql.user and mysql.db tables being crashed. Could you please check if they are OK now (run check table on them), just so we know we are not dealing with an underlying condition?
Thank you