[MDEV-4331] MariaDB could not start and throw some exception Created: 2013-03-26  Updated: 2014-06-20  Resolved: 2013-03-26

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 5.5.30
Fix Version/s: None

Type: Bug Priority: Major
Reporter: zhifeng hu Assignee: Elena Stepanova
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

CentOS 5.9 I586

Attachments: File la.isrv.us.err    

 Description   

130326 8:15:56 [ERROR] mysqld got signal 6 ;
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.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

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.

Server version: 5.5.30-MariaDB
key_buffer_size=16384
read_buffer_size=262144
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 50326 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0
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 = 0x0 thread_stack 0x3c000
(my_addr_resolve failure: fork)
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x2d)[0x865f9dd]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x472)[0x82c52c2]
/lib/libpthread.so.0[0xb7f730f8]
/lib/libc.so.6(abort+0x101)[0xb7cc0741]
/usr/local/mysql/bin/mysqld[0x84f4a69]
/usr/local/mysql/bin/mysqld[0x85a41dc]
/usr/local/mysql/bin/mysqld[0x855fad3]
/usr/local/mysql/bin/mysqld[0x84d02b8]
/lib/libpthread.so.0[0xb7f6a912]
/lib/libc.so.6(clone+0x5e)[0xb7d6b60e]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
130326 08:15:56 mysqld_safe mysqld from pid file /usr/local/mysql/data/la.isrv.us.pid ended

 Comments   
Comment by zhifeng hu [ 2013-03-26 ]

My type mistake. the title of this problem should be : MariaDB could not start up and throw some exception.

Comment by Elena Stepanova [ 2013-03-26 ]

Hi,
Please provide full contents of the error log.
Thanks.

The summary changed as suggested.

Comment by zhifeng hu [ 2013-03-26 ]

the error log file

Comment by zhifeng hu [ 2013-03-26 ]

had upload the err file, hope it will be helpful.

now i can start mariadb . but i do not know why it could not start up in that time.

Comment by Elena Stepanova [ 2013-03-26 ]

Here is why it didn't work before:

InnoDB: Error: log file ./ib_logfile0 is of different size 0 5242880 bytes
InnoDB: than specified in the .cnf file 0 1048576 bytes!
130326 8:22:05 [ERROR] Plugin 'InnoDB' init function returned error.

That's expected behavior. If you already have ib_data* or ib_log* files in your datadir, either your server should be configured with the same file sizes, or, if you don't care about the contents of those files, they need to be removed, so that InnoDB could create new ones.

After the failure you apparently removed the old ib_logfile* (or somebody else did), because on the next attempt InnoDB didn't find it and created a new one, of the size it wants:

130326 8:22:36 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 1 MB
InnoDB: Database physically writes the file full: wait...
130326 8:22:36 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 1 MB

Generated at Thu Feb 08 06:55:36 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.