mysqld crashes on startup
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
I'm not sure what's going on. It just stopped working and now it doesn't launch.
130606 20:12:15 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
130606 20:12:15 [Warning] You need to use --log-bin to make --binlog-format work.
130606 20:12:15 [Note] Plugin 'FEDERATED' is disabled.
130606 20:12:15 InnoDB: The InnoDB memory heap is disabled
130606 20:12:15 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130606 20:12:15 InnoDB: Compressed tables use zlib 1.2.3
130606 20:12:15 InnoDB: Using Linux native AIO
130606 20:12:15 InnoDB: Initializing buffer pool, size = 128.0M
130606 20:12:15 InnoDB: Completed initialization of buffer pool
130606 20:12:15 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 668771298910
130606 20:12:15 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 668771504592
17:12:15 UTC - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
Please help us make Percona Server better by reporting any
bugs at http://
key_buffer_
read_buffer_
max_used_
max_threads=153
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x30000
/usr/sbin/
/usr/sbin/
[0xb778d500]
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib/libc.
/usr/sbin/
You may download the Percona Server operations manual by visiting
http://
in the manual which will help you identify the cause of the crash.
130606 20:12:15 mysqld_safe mysqld from pid file /var/run/
root@spudder:
total used free shared buffers cached
Mem: 6144 1230 4913 0 0 955
-/+ buffers/cache: 274 5869
Swap: 3072 0 3072
Changed in percona-server: | |
status: | Incomplete → New |
Changed in percona-server: | |
status: | Incomplete → New |
What exact version of Percona Server do you use?
Please, send the entire error log from this server and your my.cnf file content.