You are not logged in.

#1 2013-03-23 14:26:19

A.J.Rouvoet
Member
From: Naaldwijk, The Netherlands
Registered: 2012-06-30
Posts: 36
Website

mysqld crashes on start

Since my last system upgrade mysqld refuses to start.

Mar 23 14:48:28 Fenix mysqld[424]: 130323 14:48:28  InnoDB: Waiting for the background threads to start
Mar 23 14:48:29 Fenix mysqld[424]: 130323 14:48:29 InnoDB: 5.5.30 started; log sequence number 54315694
Mar 23 14:48:29 Fenix mysqld[424]: 13:48:29 UTC - mysqld got signal 11 ;
Mar 23 14:48:29 Fenix mysqld[424]: This could be because you hit a bug. It is also possible that this binary
Mar 23 14:48:29 Fenix mysqld[424]: or one of the libraries it was linked against is corrupt, improperly built,
Mar 23 14:48:29 Fenix mysqld[424]: or misconfigured. This error can also be caused by malfunctioning hardware.
Mar 23 14:48:29 Fenix mysqld[424]: We will try our best to scrape up some info that will hopefully help
Mar 23 14:48:29 Fenix mysqld[424]: diagnose the problem, but since we have already crashed,
Mar 23 14:48:29 Fenix mysqld[424]: something is definitely wrong and this may fail.
Mar 23 14:48:29 Fenix mysqld[424]: key_buffer_size=16777216
Mar 23 14:48:29 Fenix mysqld[424]: read_buffer_size=262144
Mar 23 14:48:29 Fenix mysqld[424]: max_used_connections=0
Mar 23 14:48:29 Fenix mysqld[424]: max_threads=151
Mar 23 14:48:29 Fenix mysqld[424]: thread_count=0
Mar 23 14:48:29 Fenix mysqld[424]: connection_count=0
Mar 23 14:48:29 Fenix mysqld[424]: It is possible that mysqld could use up to
Mar 23 14:48:29 Fenix mysqld[424]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 134074 K  byte
Mar 23 14:48:29 Fenix mysqld[424]: Hope that's ok; if not, decrease some variables in the equation.
Mar 23 14:48:29 Fenix mysqld[424]: Thread pointer: 0x0
Mar 23 14:48:29 Fenix mysqld[424]: Attempting backtrace. You can use the following information to find out
Mar 23 14:48:29 Fenix mysqld[424]: where mysqld died. If you see no messages after this, something went
Mar 23 14:48:29 Fenix mysqld[424]: terribly wrong...
Mar 23 14:48:29 Fenix mysqld[424]: stack_bottom = 0 thread_stack 0x40000
Mar 23 14:48:29 Fenix mysqld[424]: /usr/bin/mysqld(my_print_stacktrace+0x29)[0x78ae99]
Mar 23 14:48:29 Fenix mysqld[424]: /usr/bin/mysqld(handle_fatal_signal+0x471)[0x67ad71]
Mar 23 14:48:29 Fenix mysqld[424]: /usr/lib/libpthread.so.0(+0xf1e0)[0x7fecdc88d1e0]
Mar 23 14:48:29 Fenix mysqld[424]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Mar 23 14:48:29 Fenix mysqld[424]: information that should help you find out what is causing the crash.
Mar 23 14:48:29 Fenix systemd[1]: mysqld.service: main process exited, code=exited, status=1/FAILURE

I have to see I can extract very little useful information from this log. Anyone?

Offline

#2 2013-03-23 15:39:16

ralvez
Member
From: Canada
Registered: 2005-12-06
Posts: 1,546
Website

Re: mysqld crashes on start

Try

mysqlcheck -A

Also take a look at some of the other options that mysqlcheck gives you in order to help you troubleshoot the problem.

R.

Edit: You should also try mysql_upgrade to assit you with the problem. Here is a link to mysql oracle

Last edited by ralvez (2013-03-23 15:41:59)

Offline

#3 2013-03-25 14:17:04

yutas
Member
Registered: 2013-03-25
Posts: 1

Re: mysqld crashes on start

Having the same issue. Even this lines match:

mysqld[424]: /usr/bin/mysqld(my_print_stacktrace+0x29)[0x78ae99]
mysqld[424]: /usr/bin/mysqld(handle_fatal_signal+0x471)[0x67ad71]
mysqld[424]: /usr/lib/libpthread.so.0(+0xf1e0)[0x7fecdc88d1e0]

any ideas?

Offline

#4 2013-03-26 11:50:00

A.J.Rouvoet
Member
From: Naaldwijk, The Netherlands
Registered: 2012-06-30
Posts: 36
Website

Re: mysqld crashes on start

ralvez wrote:

Try

mysqlcheck -A

Also take a look at some of the other options that mysqlcheck gives you in order to help you troubleshoot the problem.

R.

Edit: You should also try mysql_upgrade to assit you with the problem. Here is a link to mysql oracle

mysqlcheck simply returns the obvious:

mysqlcheck: Got error: 2002: Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (2) when trying to connect

And I have tried issuing a mysql_upgrade, but that requires a started server; which I can't seem to get working (even in safe mode...)

Offline

#5 2013-03-26 12:17:41

A.J.Rouvoet
Member
From: Naaldwijk, The Netherlands
Registered: 2012-06-30
Posts: 36
Website

Re: mysqld crashes on start

Fixed it using the following steps:

Note that these steps will remove all existing databases, including mysql system tables and have you start from scratch. I'm not sure whether that is needed at all; I just wanted to have a clean start.

# rm -Rf /var/lib/mysql
# pacman -Rdd mysql
# pacman -S mariadb libmariadbclient mariadb-clients
# mysqld_safe --datadir=/var/lib/mysql
# mysqladmin -u root password
# mysqladmin -u root -h <HOSTNAME> password
# systemctl start mysqld.service

Offline

#6 2013-04-03 00:59:38

ES
Member
Registered: 2009-03-13
Posts: 21

Re: mysqld crashes on start

Just in case it can helps someone, I had the same kind of errors and the cause was a full var partition.
A `pacman -Sc` fixed it for me.

Offline

#7 2014-01-06 11:03:14

alexdw
Member
Registered: 2013-03-25
Posts: 38

Re: mysqld crashes on start

ES wrote:

Just in case it can helps someone, I had the same kind of errors and the cause was a full var partition.
A `pacman -Sc` fixed it for me.

Just wanted to say thanks for this - this fixed a similar problem I had with mysqld not starting after a recent pacman update:

[alexdw@AlexPC ~]$ sudo systemctl status mysqld.service -l
mysqld.service - MariaDB database server
   Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled)
   Active: activating (start-post) (Result: exit-code) since Mon 2014-01-06 10:52:29 GMT; 21s ago
  Process: 1088 ExecStart=/usr/bin/mysqld --pid-file=/run/mysqld/mysqld.pid (code=exited, status=1/FAILURE)
 Main PID: 1088 (code=exited, status=1/FAILURE);         : 1089 (mysqld-post)
   CGroup: /system.slice/mysqld.service
           └─control
             ├─1089 /bin/sh /usr/bin/mysqld-post
             └─1965 sleep 1

Jan 06 10:52:29 AlexPC mysqld[1088]: 140106 10:52:29 [ERROR] Plugin 'InnoDB' init function returned error.
Jan 06 10:52:29 AlexPC mysqld[1088]: 140106 10:52:29 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Jan 06 10:52:29 AlexPC mysqld[1088]: 140106 10:52:29 [ERROR] mysqld: Got error 'Size of control file is smaller than expected' when trying to use aria control file '/var/lib/mysql/aria_log_control'
Jan 06 10:52:29 AlexPC mysqld[1088]: 140106 10:52:29 [ERROR] Plugin 'Aria' init function returned error.
Jan 06 10:52:29 AlexPC mysqld[1088]: 140106 10:52:29 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
Jan 06 10:52:29 AlexPC mysqld[1088]: 140106 10:52:29 [Note] Plugin 'FEEDBACK' is disabled.
Jan 06 10:52:29 AlexPC mysqld[1088]: 140106 10:52:29 [ERROR] Unknown/unsupported storage engine: InnoDB
Jan 06 10:52:29 AlexPC mysqld[1088]: 140106 10:52:29 [ERROR] Aborting
Jan 06 10:52:29 AlexPC mysqld[1088]: 140106 10:52:29 [Note] /usr/bin/mysqld: Shutdown complete
Jan 06 10:52:29 AlexPC systemd[1]: mysqld.service: main process exited, code=exited, status=1/FAILURE

Offline

Board footer

Powered by FluxBB