[MDEV-6803] weird crash Created: 2014-09-28  Updated: 2014-10-16  Due: 2014-10-14  Resolved: 2014-10-16

Status: Closed
Project: MariaDB Server
Component/s: OTHER
Affects Version/s: 10.0.14
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: Federico Razzoli Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: crash
Environment:

Debian 7



 Description   

I have no idea how/why this happened. MariaDB was unused, on a development server.

Version: '10.0.14-MariaDB-1~wheezy-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
 
Status information:
 
Current dir: /var/lib/mysql/
Running threads: 2  Stack size: 294912
Current locks:
lock: 0x7f8ad2d18388: read
read      : 0x7f8aa6d47368 (9:5); 
 
lock: 0x7f8aa6dec4d8:
 
lock: 0x7f8aa6decbd8:
 
lock: 0x7f8aa6ca0f88:
 
lock: 0x7f8aa6cceb88:
 
lock: 0x7f8aa6cce388:
 
lock: 0x7f8aa6ccdb88:
 
lock: 0x7f8aa6ccd388:
 
lock: 0x7f8aa6cccb88:
 
lock: 0x7f8aa6d4ab88:
 
lock: 0x7f8aa6c9b588:
 
lock: 0x7f8aa6c8a288:
 
lock: 0x7f8aa6c8a148:
 
lock: 0x7f8aa6c98d88:
 
lock: 0x7f8aa6c97988:
 
lock: 0x7f8aa6cc4b88:
 
lock: 0x7f8aa6c95b88:
 
lock: 0x7f8aa6c94788:
 
lock: 0x7f8aa6c91f88:
 
lock: 0x7f8ad2ca9788:
 
lock: 0x7f8ad2c9d788:
 
lock: 0x7f8ad2c7cd88:
 
lock: 0x7f8ad2c7b988:
 
lock: 0x7f8ad2c78788:
 
lock: 0x7f8aa6018508:
 
lock: 0x7f8ad671cfa0:
 
lock: 0x7f8ad671cec0:
 
lock: 0x7f8ad671bf00:
 
lock: 0x7f8ad671be20:
 
lock: 0x7f8ad671bd40:
 
lock: 0x7f8ad671c0c0:
 
lock: 0x7f8ad671a300:
 
lock: 0x7f8ad671cde0:
 
lock: 0x7f8ad671aa00:
 
lock: 0x7f8ad671aca0:
 
lock: 0x7f8ad671a920:
 
lock: 0x7f8ad671abc0:
 
lock: 0x7f8ad671a840:
 
lock: 0x7f8ad671aae0:
 
lock: 0x7f8ad671b020:
 
lock: 0x7f8ad671b100:
 
lock: 0x7f8ad671b1e0:
 
lock: 0x7f8ad671a760:
 
lock: 0x7f8ad671a4c0:
 
lock: 0x7f8ad671a680:
 
lock: 0x7f8ad671a3e0:
 
lock: 0x7f8ad671a5a0:
 
lock: 0x7f8ad671ad80:
 
lock: 0x7f8ad671ae60:
 
lock: 0x7f8ad671af40:
 
lock: 0x7f8ad671ca60:
 
lock: 0x7f8ad671cd00:
 
lock: 0x7f8ad671cc20:
 
lock: 0x7f8ad671cb40:
 
lock: 0x7f8ad671c6e0:
 
lock: 0x7f8ad671c600:
 
lock: 0x7f8ad671c520:
 
lock: 0x7f8ad671c440:
 
lock: 0x7f8ad671c360:
 
lock: 0x7f8ad671c8a0:
 
lock: 0x7f8ad671c280:
 
lock: 0x7f8ad671c1a0:
 
lock: 0x7f8ad671c980:
 
lock: 0x7f8ad671bfe0:
 
lock: 0x7f8ad671bb80:
 
lock: 0x7f8ad671bc60:
 
lock: 0x7f8ad671baa0:
 
lock: 0x7f8ad671b9c0:
 
lock: 0x7f8ad671b640:
 
lock: 0x7f8ad671b8e0:
 
lock: 0x7f8ad671b800:
 
lock: 0x7f8ad671b560:
 
lock: 0x7f8ad671b720:
 
lock: 0x7f8ad671b2c0:
 
lock: 0x7f8ad671b3a0:
 
lock: 0x7f8ad671b480:
 
lock: 0x7f8ad671c7c0:
 
 
Key caches:
default
Buffer_size:             0
Block_size:           1024
Division_limit:        100
Age_threshold:         300
Partitions:              0
blocks used:             0
not flushed:             0
w_requests:              0
writes:                  0
r_requests:              0
reads:                   0
 
 
handler status:
read_key:          305
read_next:           0
read_rnd             0
read_first:          0
write:              26
delete               0
update:              0
 
Table status:
Opened tables:         91
Open tables:           77
Open files:            52
Open streams:           0
 
Alarm status:
Active alarms:   0
Max used alarms: 0
Next alarm time: 0
 
Thread database.table_name          Locked/Waiting        Lock_type
 
9       mysql.user                  Locked - read         Read lock without concurrent inserts
 
 
 
 
Memory status:
Non-mmapped space allocated from system: 0
Number of free chunks:			 1
Number of fastbin blocks:		 0
Number of mmapped regions:		 0
Space in mmapped regions:		 0
Maximum total allocated space:		 0
Space available in freed fastbin blocks: 0
Total allocated space:			 0
Total free space:			 0
Top-most, releasable space:		 0
Estimated memory (with thread stack):    589824
 
 
 
Events status:
LLA = Last Locked At  LUA = Last Unlocked At
WOC = Waiting On Condition  DL = Data Locked
 
Event scheduler status:
State      : RUNNING
Thread id  : 2
LLA        : is_running:616
LUA        : is_running:618
WOC        : NO
Workers    : 0
Executed   : 0
Data locked: NO
 
Event queue status:
Element count   : 0
Data locked     : NO
Attempting lock : NO
LLA             : get_top_for_execution_if_time:587
LUA             : get_top_for_execution_if_time:608
WOC             : YES
Next activation : never
Unsupported sql_command=46
Unsupported sql_command=39
140928  4:14:01 [Note] /usr/sbin/mysqld: Normal shutdown
 
140928  4:14:01 [Note] Event Scheduler: Killing the scheduler thread, thread id 2
140928  4:14:01 [Note] Event Scheduler: Waiting for the scheduler thread to reply
140928  4:14:01 [Note] Event Scheduler: Stopped
140928  4:14:01 [Note] Event Scheduler: Purging the queue. 0 events
140928  4:14:01 server_audit: STOPPED
140928  4:14:01 [Note] InnoDB: FTS optimize thread exiting.
140928  4:14:01 [Note] InnoDB: Starting shutdown...
140928  4:14:03 [Note] InnoDB: Shutdown completed; log sequence number 22121646
140928  4:14:03 [Note] /usr/sbin/mysqld: Shutdown complete



 Comments   
Comment by Elena Stepanova [ 2014-09-28 ]

Hi Federico,

It doesn't really look like a crash, more like somebody (or sometihng) sent SIGHUP and then SIGTERM to the process. Could it have happened? Maybe some watchdog wrongly deduced PID it is supposed to watch, or something?

Comment by Federico Razzoli [ 2014-09-29 ]

A scary hypotesys! I don't know, I'll have to investigate.

Comment by Elena Stepanova [ 2014-10-16 ]

Closing as Incomplete for now, please comment to re-open if you get new information (namely, if you made sure it wasn't an external intervention).

Generated at Thu Feb 08 07:14:42 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.