You are not logged in.

Pages: 1

Topic closed

#1 2013-03-25 23:29:10

lonaowna
Member
Registered: 2013-03-25
Posts: 28

[SOLVED] Cannot start mysqld after switching to MariaDB

Hey guys,

I just switched to MariaDB as recommended.
After installing MariaDB and running 

systemctl start mysqld

, I get this error message: 

Job for mysqld.service failed.

journal:

systemd[1]: Starting MariaDB database server...
mysqld[9358]: 130326  0:27:17 InnoDB: The InnoDB memory heap is disabled
mysqld[9358]: 130326  0:27:17 InnoDB: Mutexes and rw_locks use GCC atomic builtins
mysqld[9358]: 130326  0:27:17 InnoDB: Compressed tables use zlib 1.2.7
mysqld[9358]: 130326  0:27:17 InnoDB: Initializing buffer pool, size = 128.0M
mysqld[9358]: 130326  0:27:17 InnoDB: Completed initialization of buffer pool
mysqld[9358]: 130326  0:27:17 InnoDB: highest supported file format is Barracuda.
mysqld[9358]: 130326  0:27:17  InnoDB: Waiting for the background threads to start
mysqld[9358]: 130326  0:27:18 Percona XtraDB (http://www.percona.com) 5.5.30-MariaDB-30.1 started; log sequence number 46580545
mysqld[9358]: 130326  0:27:18 [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'
mysqld[9358]: 130326  0:27:18 [ERROR] Plugin 'Aria' init function returned error.
mysqld[9358]: 130326  0:27:18 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
mysqld[9358]: 130326  0:27:18 [ERROR] Aria engine is not enabled or did not start. The Aria engine must be enabled to continue as mysqld was configured with --with-aria-tmp-tables
mysqld[9358]: 130326  0:27:18 [ERROR] Aborting
mysqld[9358]: 130326  0:27:18  InnoDB: Starting shutdown...
mysqld[9358]: 130326  0:27:19  InnoDB: Shutdown completed; log sequence number 46580545
mysqld[9358]: 130326  0:27:19 [Note] /usr/bin/mysqld: Shutdown complete
systemd[1]: mysqld.service: main process exited, code=exited, status=1/FAILURE

Last edited by lonaowna (2013-03-26 01:23:20)

Offline

#2 2013-03-25 23:39:28

shox
Member
Registered: 2012-06-20
Posts: 51

Re: [SOLVED] Cannot start mysqld after switching to MariaDB

Hi ! I come here because I have a trouble since the last update of Mysqld :
I cannot start the daemon with 

sudo systemctl start mysqld

I have these problems when i look in journalctl -xn : 

mars 26 00:22:14 server mysqld[11593]: InnoDB: Error: log file ./ib_logfile0 is of different size 0 3174400 bytes
mars 26 00:22:14 server mysqld[11593]: InnoDB: than specified in the .cnf file 0 5242880 bytes!
mars 26 00:22:14 server mysqld[11593]: 130326  0:22:14 [ERROR] Plugin 'InnoDB' init function returned error.
mars 26 00:22:14 server mysqld[11593]: 130326  0:22:14 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
mars 26 00:22:14 server mysqld[11593]: 130326  0:22:14 [ERROR] Unknown/unsupported storage engine: InnoDB
mars 26 00:22:14 server mysqld[11593]: 130326  0:22:14 [ERROR] Aborting
mars 26 00:22:14 server mysqld[11593]: 130326  0:22:14 [Note] /usr/bin/mysqld: Shutdown complete
mars 26 00:22:14 server systemd[1]: mysqld.service: main process exited, code=exited, status=1/FAILURE

When I try with mysqld, I have 

130326  0:23:21 [Warning] Can't create test file /var/lib/mysql/server.lower-test
130326  0:23:21 [Warning] Can't create test file /var/lib/mysql/server.lower-test
mysqld: Can't change dir to '/var/lib/mysql/' (Errcode: 13)
130326  0:23:21 [ERROR] Aborting
130326  0:23:21 [Note] mysqld: Shutdown complete

And when I look in /var/lib/mysql/server.err I have these lines 

130207 23:32:56 mysqld_safe mysqld from pid file /var/lib/mysql/server.pid ended
130322 00:25:27 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
130322  0:25:27 InnoDB: The InnoDB memory heap is disabled
130322  0:25:27 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130322  0:25:27 InnoDB: Compressed tables use zlib 1.2.7
130322  0:25:27 InnoDB: Initializing buffer pool, size = 128.0M
130322  0:25:27 InnoDB: Completed initialization of buffer pool
130322  0:25:27 InnoDB: highest supported file format is Barracuda.
InnoDB: Error: tried to read 65536 bytes at offset 0 3173376.
InnoDB: Was only able to read 1024.
InnoDB: Fatal error: cannot read from file. OS error number 17.
130322  0:25:30  InnoDB: Assertion failure in thread 139785666135872 in file os0file.c line 2538
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
23:25:30 UTC - 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.
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.

key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 134074 K  bytes of memory
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 0x40000
/usr/bin/mysqld(my_print_stacktrace+0x29)[0x78ae99]
/usr/bin/mysqld(handle_fatal_signal+0x471)[0x67ad71]
/usr/lib/libpthread.so.0(+0xf1e0)[0x7f226299a1e0]
/usr/lib/libc.so.6(gsignal+0x35)[0x7f22615612c5]
/usr/lib/libc.so.6(abort+0x148)[0x7f2261562748]
/usr/bin/mysqld[0x8f2ac0]
/usr/bin/mysqld[0x8af1a0]
/usr/bin/mysqld[0x8e187c]
/usr/bin/mysqld[0x8e75ef]
/usr/bin/mysqld[0x834204]
/usr/bin/mysqld[0x7fe61f]
/usr/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x67ccf1]
/usr/bin/mysqld[0x59ad94]
/usr/bin/mysqld(_Z11plugin_initPiPPci+0xa42)[0x59f342]
/usr/bin/mysqld[0x524328]
/usr/bin/mysqld(_Z11mysqld_mainiPPc+0x447)[0x529187]
/usr/lib/libc.so.6(__libc_start_main+0xf5)[0x7f226154da15]
/usr/bin/mysqld[0x51ff89]
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.
130322 00:25:30 mysqld_safe mysqld from pid file /var/lib/mysql/server.pid ended
130326 00:24:58 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
130326  0:24:58 InnoDB: The InnoDB memory heap is disabled
130326  0:24:58 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130326  0:24:58 InnoDB: Compressed tables use zlib 1.2.7
130326  0:24:58 InnoDB: Initializing buffer pool, size = 128.0M
130326  0:24:58 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file ./ib_logfile0 is of different size 0 3174400 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
130326  0:24:58 [ERROR] Plugin 'InnoDB' init function returned error.
130326  0:24:58 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
130326  0:24:58 [ERROR] Unknown/unsupported storage engine: InnoDB
130326  0:24:58 [ERROR] Aborting

130326  0:24:58 [Note] /usr/bin/mysqld: Shutdown complete

130326 00:24:58 mysqld_safe mysqld from pid file /var/lib/mysql/server.pid ended
130326 00:25:33 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql/
130326  0:25:33 InnoDB: The InnoDB memory heap is disabled
130326  0:25:33 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130326  0:25:33 InnoDB: Compressed tables use zlib 1.2.7
130326  0:25:33 InnoDB: Initializing buffer pool, size = 128.0M
130326  0:25:33 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file ./ib_logfile0 is of different size 0 3174400 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
130326  0:25:33 [ERROR] Plugin 'InnoDB' init function returned error.
130326  0:25:33 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
130326  0:25:33 [ERROR] Unknown/unsupported storage engine: InnoDB
130326  0:25:33 [ERROR] Aborting

130326  0:25:33 [Note] /usr/bin/mysqld: Shutdown complete

130326 00:25:33 mysqld_safe mysqld from pid file /var/lib/mysql//server.pid ended

When I try mysqld_safe, here is what I get 

130326 00:24:58 mysqld_safe Logging to '/var/lib/mysql/server.err'.
130326 00:24:58 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
130326 00:24:58 mysqld_safe mysqld from pid file /var/lib/mysql/server.pid ended

Resolution
===== It's a good thing to make a post :
It allows me to order my ideas and I find the solution here http://serverfault.com/questions/104014 … erent-size

I juste deleted the files /var/lib/mysqld/ib_logfile0 and /var/lib/mysql/ib_logfile1
First, I had a problem about the file who is in the future (WTF ?:p) But after, it worked !
Thanks Anyway !

Last edited by shox (2013-03-25 23:51:43)

Offline

#3 2013-03-26 00:15:06

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: [SOLVED] Cannot start mysqld after switching to MariaDB

Merging with the solved Mysqld thread...

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#4 2013-03-26 01:22:47

lonaowna
Member
Registered: 2013-03-25
Posts: 28

Re: [SOLVED] Cannot start mysqld after switching to MariaDB

Thanks! I almost used the same solution: I had to delete 

/var/lib/mysql/aria_log_control

Offline

#5 2013-03-27 10:14:33

Box0
Member
From: Italy
Registered: 2011-09-21
Posts: 218

Re: [SOLVED] Cannot start mysqld after switching to MariaDB

I've tried both solutions but I'm still unable to start the mysqld.service
What else can I try?

code for systemctl status mysqld.service

mysqld.service - MariaDB database server
          Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled)
          Active: activating (start-post) (Result: exit-code) since Wed 2013-03-27 11:23:54 CET; 26s ago
         Process: 26836 ExecStart=/usr/bin/mysqld --pid-file=/run/mysqld/mysqld.pid (code=exited, status=1/FAILURE)
         Control: 26837 (mysqld-post)
          CGroup: name=systemd:/system/mysqld.service
                  └─control
                    ├─26837 /bin/sh /usr/bin/mysqld-post
                    └─27291 sleep 1

Mar 27 11:23:54 emac mysqld[26836]: InnoDB: Restoring possible half-written data pages from the doublewrite
Mar 27 11:23:54 emac mysqld[26836]: InnoDB: buffer...
Mar 27 11:23:54 emac mysqld[26836]: 130327 11:23:54  InnoDB: Waiting for the background threads to start
Mar 27 11:23:55 emac mysqld[26836]: 130327 11:23:55 Percona XtraDB ([url]http://www.percona.com[/url]) 5.5.30-MariaDB-30.1 starte...1597945
Mar 27 11:23:55 emac mysqld[26836]: 130327 11:23:55 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrad...ate it.
Mar 27 11:23:55 emac mysqld[26836]: 130327 11:23:55 [Note] Recovering after a crash using mysql-bin
Mar 27 11:23:55 emac mysqld[26836]: 130327 11:23:55 [Note] Starting crash recovery...
Mar 27 11:23:55 emac mysqld[26836]: 130327 11:23:55 [Note] Crash recovery finished.
Mar 27 11:23:55 emac mysqld[26836]: 130327 11:23:55 [ERROR] Fatal error: Can't open and lock privilege tables: Table '...t exist
Mar 27 11:23:55 emac systemd[1]: mysqld.service: main process exited, code=exited, status=1/FAILURE

code for journalctl -xn

-- Logs begin at Tue 2012-12-04 14:18:06 CET, end at Wed 2013-03-27 11:26:56 CET. --
Mar 27 11:26:54 emac mysqld[29664]: InnoDB: Restoring possible half-written data pages from the doublewrite
Mar 27 11:26:54 emac mysqld[29664]: InnoDB: buffer...
Mar 27 11:26:54 emac mysqld[29664]: 130327 11:26:54  InnoDB: Waiting for the background threads to start
Mar 27 11:26:55 emac mysqld[29664]: 130327 11:26:55 Percona XtraDB (http://www.percona.com) 5.5.30-MariaDB-30.1 started; log sequence number 1597945
Mar 27 11:26:55 emac mysqld[29664]: 130327 11:26:55 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
Mar 27 11:26:55 emac mysqld[29664]: 130327 11:26:55 [Note] Recovering after a crash using mysql-bin
Mar 27 11:26:55 emac mysqld[29664]: 130327 11:26:55 [Note] Starting crash recovery...
Mar 27 11:26:55 emac mysqld[29664]: 130327 11:26:55 [Note] Crash recovery finished.
Mar 27 11:26:56 emac mysqld[29664]: 130327 11:26:56 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist
Mar 27 11:26:56 emac systemd[1]: mysqld.service: main process exited, code=exited, status=1/FAILURE

code for mysql_upgrade

Phase 1/3: Fixing table and database names
mysqlcheck: Got error: 2002: Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (2) when trying to connect
FATAL ERROR: Upgrade failed

Last edited by Box0 (2013-03-27 10:26:32)

Offline

#6 2013-03-27 10:50:09

mrunion
Member
From: Jonesborough, TN
Registered: 2007-01-26
Posts: 1,938
Website

Re: [SOLVED] Cannot start mysqld after switching to MariaDB

As far as I know, you have to get mysql_upgrade to work. Did you use the -p option? If so, did you get the password typed correctly?

Matt

"It is very difficult to educate the educated."

Offline

#7 2013-03-27 12:03:38

Box0
Member
From: Italy
Registered: 2011-09-21
Posts: 218

Re: [SOLVED] Cannot start mysqld after switching to MariaDB

I get the output posted in my previous message after running both mysql_upgrade and mysql_upgrade -p.

I don't even reach the step where it asks to insert your password.

Offline

#8 2013-06-23 13:29:55

harshadura
Member
Registered: 2013-05-08
Posts: 5

Re: [SOLVED] Cannot start mysqld after switching to MariaDB

Hello,
I have the same problem, Tried all the solutions but didn worked for me.
@Box0: Did you able to find a solution for this ?

[root@DuraArch mysql]# journalctl -xn
-- Logs begin at Mon 2007-01-01 05:30:28 IST, end at Sun 2013-06-23 18:58:39 IST. --
Jun 23 18:58:29 DuraArch mysqld[10480]: 130623 18:58:29 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Jun 23 18:58:29 DuraArch mysqld[10480]: 130623 18:58: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'
Jun 23 18:58:29 DuraArch mysqld[10480]: 130623 18:58:29 [ERROR] Plugin 'Aria' init function returned error.
Jun 23 18:58:29 DuraArch mysqld[10480]: 130623 18:58:29 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
Jun 23 18:58:29 DuraArch mysqld[10480]: 130623 18:58:29 [ERROR] Unknown/unsupported storage engine: InnoDB
Jun 23 18:58:29 DuraArch mysqld[10480]: 130623 18:58:29 [ERROR] Aborting
Jun 23 18:58:29 DuraArch mysqld[10480]: 130623 18:58:29 [Note] /usr/bin/mysqld: Shutdown complete
Jun 23 18:58:29 DuraArch systemd[1]: mysqld.service: main process exited, code=exited, status=1/FAILURE
Jun 23 18:58:38 DuraArch systemd-tmpfiles[10347]: stat(/run/user/1000/gvfs) failed: Permission denied
Jun 23 18:58:39 DuraArch systemd[1]: Started Cleanup of Temporary Directories.
-- Subject: Unit systemd-tmpfiles-clean.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/39f53479d3a045ac8e11786248231fbf
-- 
-- Unit systemd-tmpfiles-clean.service has finished starting up.
-- 
-- The start-up result is done.

Offline

#9 2013-07-03 20:55:55

Kalinda
Member
From: Canada
Registered: 2009-02-19
Posts: 75
Website

Re: [SOLVED] Cannot start mysqld after switching to MariaDB

Bumping this, as I think solving it will fix my Amarok crashing problem. I've only just now got around to switching from the outdated mysql to MariaDB. I tried the solutions here and none of them work.

Here's my journalctl -xn output:

-- Logs begin at Wed 2013-07-03 16:35:20 EDT, end at Wed 2013-07-03 16:51:31 EDT. --
Jul 03 16:51:04 tardis mysqld[31313]: 130703 16:51:04 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Jul 03 16:51:04 tardis mysqld[31313]: 130703 16:51:04 [ERROR] mysqld: Got error 'Size of control file is smaller than expected' when
Jul 03 16:51:04 tardis mysqld[31313]: 130703 16:51:04 [ERROR] Plugin 'Aria' init function returned error.
Jul 03 16:51:04 tardis mysqld[31313]: 130703 16:51:04 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
Jul 03 16:51:04 tardis mysqld[31313]: 130703 16:51:04 [ERROR] Unknown/unsupported storage engine: InnoDB
Jul 03 16:51:04 tardis mysqld[31313]: 130703 16:51:04 [ERROR] Aborting
Jul 03 16:51:04 tardis mysqld[31313]: 130703 16:51:04 [Note] /usr/bin/mysqld: Shutdown complete
Jul 03 16:51:04 tardis systemd[1]: mysqld.service: main process exited, code=exited, status=1/FAILURE

and the systemctl status for mysqld.service:

mysqld.service - MariaDB database server
   Loaded: loaded (/usr/lib/systemd/system/mysqld.service; disabled)
   Active: activating (start-post) (Result: exit-code) since Wed 2013-07-03 16:52:34 EDT; 34s ago
  Process: 32051 ExecStart=/usr/bin/mysqld --pid-file=/run/mysqld/mysqld.pid (code=exited, status=1/FAILURE)
  Control: 32052 (mysqld-post)
   CGroup: name=systemd:/system/mysqld.service
           ââcontrol
             ââ32052 /bin/sh /usr/bin/mysqld-post
             ââ32346 sleep 1

Arch Linux Plasma 6 | AMD Ryzen 7 1700 | 64GB DDR4 RAM | Radeon RX 570 / GTX 1050 Ti | RTX 2070 Super (Windows VM)

Offline

#10 2013-10-13 04:36:40

h54
Member
Registered: 2011-11-22
Posts: 96

Re: [SOLVED] Cannot start mysqld after switching to MariaDB

shox wrote:

I juste deleted the files /var/lib/mysqld/ib_logfile0 and /var/lib/mysql/ib_logfile1
First, I had a problem about the file who is in the future (WTF ?:p) But after, it worked !
Thanks Anyway !


I decided to finally upgrade on the home server and ran into the same exact problem.  I can confirm that removing the above two log files also resolved my issue.

Offline

#11 2014-07-30 06:31:37

supershnee
Member
Registered: 2014-06-17
Posts: 2

Re: [SOLVED] Cannot start mysqld after switching to MariaDB

OK, so I had a similar error:

Jul 29 22:50:22 SMILEplug mysqld[4503]: 140729 22:50:22 [Note] Plugin 'FEEDBACK' is disabled.
Jul 29 22:50:22 SMILEplug mysqld[4503]: 140729 22:50:22 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
Jul 29 22:50:22 SMILEplug mysqld[4503]: 140729 22:50:22 [Note] Recovering after a crash using mysql-bin
Jul 29 22:50:22 SMILEplug mysqld[4503]: 140729 22:50:22 [Note] Starting crash recovery...
Jul 29 22:50:22 SMILEplug mysqld[4503]: 140729 22:50:22 [Note] Crash recovery finished.
Jul 29 22:50:22 SMILEplug mysqld[4503]: 140729 22:50:22 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table 'mysql.gtid_slave_pos' doesn't exist
Jul 29 22:50:22 SMILEplug mysqld[4503]: 140729 22:50:22 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
Jul 29 22:50:22 SMILEplug mysqld[4503]: 140729 22:50:22 [Note] Server socket created on IP: '0.0.0.0'.
Jul 29 22:50:22 SMILEplug mysqld[4503]: 140729 22:50:22 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist
Jul 29 22:50:22 SMILEplug systemd[1]: mysqld.service: main process exited, code=exited, status=1/FAILURE


I solved it with the following commands:

1. Delete everything in /var/lib/mysql
2. mysql_install_db --user=mysql --ldata=/var/lib/mysql/ --basedir=/usr

SEE https://bbs.archlinux.org/viewtopic.php?id=137365

Offline

#12 2014-07-31 20:07:35

inkdinky
Member
Registered: 2011-12-08
Posts: 66

Re: [SOLVED] Cannot start mysqld after switching to MariaDB

I had a similar problem and none of the above worked.
Even though I had just installed mariadb and rebooted (shutdown -r now), it seemed that starting over so to speak fixed the problem

   sudo systemctl stop mysqld
   sudo rm -R /var/lib/mysql
   sudo pacman -R mariadb && sudo pacman -S mariadb

Instead of trying to start the service I followed the instructions provided by the mariadb install:

   You can start the MariaDB daemon with:
   cd '/usr' ; sudo /usr/bin/mysqld_safe --datadir='/var/lib/mysql'

I then could run the mysql_upgrade as root.

I **haven't** run the mysqld via systemctl start however.

Offline

#13 2016-07-11 13:11:44

suzzu
Member
From: Kathmandu,Nepal
Registered: 2016-07-11
Posts: 2

Re: [SOLVED] Cannot start mysqld after switching to MariaDB

I have same issue
[suzan@suzzu ~]$ sudo systemctl start mysqld
[sudo] password for suzan:
Job for mysqld.service failed because a timeout was exceeded.
See "systemctl status mysqld.service" and "journalctl -xe" for details.
[suzan@suzzu ~]$ sudo systemctl status mysqld
[sudo] password for suzan:
* mysqld.service - MariaDB database server
   Loaded: loaded (/usr/lib/systemd/system/mysqld.service; disabled; vendor preset: disabled)
   Active: activating (start-post) (Result: exit-code) since Mon 2016-07-11 18:55:13 NPT; 49s ago
  Process: 28647 ExecStart=/usr/bin/mysqld --pid-file=/run/mysqld/mysqld.pid (code=exited, status=1/FAILURE)
Main PID: 28647 (code=exited, status=1/FAILURE);         : 28648 (mysqld-post)
    Tasks: 2 (limit: 512)
   CGroup: /system.slice/mysqld.service
           `-control
             |-28648 /bin/sh /usr/bin/...
             `-29044 sleep 1

Jul 11 18:55:14 suzzu mysqld[28647]: 2016-07-11 18:55:14 139673869412288 [Note] Plugin 'FEEDBACK' is disabled.
Jul 11 18:55:14 suzzu mysqld[28647]: 2016-07-11 18:55:14 139673869412288 [ERROR] Could not open mysql.plugin table. Some plugins may be not l
Jul 11 18:55:14 suzzu mysqld[28647]: 2016-07-11 18:55:14 139673869412288 [Note] Recovering after a crash using mysql-bin
Jul 11 18:55:14 suzzu mysqld[28647]: 2016-07-11 18:55:14 139673869412288 [Note] Starting crash recovery...
Jul 11 18:55:14 suzzu mysqld[28647]: 2016-07-11 18:55:14 139673869412288 [Note] Crash recovery finished.
Jul 11 18:55:14 suzzu mysqld[28647]: 2016-07-11 18:55:14 139673869392640 [Warning] Failed to load slave replication state from table mysql.gt
Jul 11 18:55:14 suzzu mysqld[28647]: 2016-07-11 18:55:14 139673869412288 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers'
Jul 11 18:55:14 suzzu mysqld[28647]: 2016-07-11 18:55:14 139673869412288 [Note] Server socket created on IP: '::'.
Jul 11 18:55:14 suzzu mysqld[28647]: 2016-07-11 18:55:14 139673869412288 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'my
Jul 11 18:55:14 suzzu systemd[1]: mysqld.service: Main process exited, code=exited, status=1/FAILURE
lines 1-21/21 (END)

Offline

#14 2016-07-11 13:29:03

WorMzy
Administrator
From: Scotland
Registered: 2010-06-16
Posts: 12,409
Website

Re: [SOLVED] Cannot start mysqld after switching to MariaDB

If the solution that worked for lonaowna doesn't work for you, then you don't have the same problem. Open a new topic about your issue and link back to this one if you think it is still relevant after three years.

https://wiki.archlinux.org/index.php/Co … bumping.22

Closing.

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

Pages: 1

Topic closed

Board footer

Powered by FluxBB