Page 1 of 5 123 ... LastLast
Results 1 to 10 of 47

Thread: Can't start MySQL - 13.1

  1. #1

    Default Can't start MySQL - 13.1

    I'm trying to get mythtv running on 13.1 (64-bit). I was having some trouble with MariaDB, so I uninstalled it and replaced it with MySql Community. However, when I try to start MySql, I get the following:

    # /etc/init.d/mysql start
    redirecting to systemctl start mysql
    Job for mysql.service failed. See 'systemctl status mysql.service' and 'journalctl -xn' for details.

    When I look at the first of those two, I get:

    # systemctl status mysql.service
    mysql.service - LSB: Start the MySQL database server
    Loaded: loaded (/etc/init.d/mysql)
    Active: failed (Result: exit-code) since Mon 2013-11-25 14:39:49 CST; 58s ago
    Process: 29217 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE)

    Nov 25 14:39:49 Tonka-htpc systemd[1]: Starting LSB: Start the MySQL databa.....
    Nov 25 14:39:49 Tonka-htpc mysql[29217]: You are upgrading from different st...!
    Nov 25 14:39:49 Tonka-htpc mysql[29217]: Make sure you to make backup of you...!
    Nov 25 14:39:49 Tonka-htpc systemd[1]: mysql.service: control process exite...=1
    Nov 25 14:39:49 Tonka-htpc systemd[1]: Failed to start LSB: Start the MySQL...r.
    Nov 25 14:39:49 Tonka-htpc systemd[1]: Unit mysql.service entered failed state.
    Hint: Some lines were ellipsized, use -l to show in full.

    When I run the second one, I get this:

    # journalctl -xn
    -- Logs begin at Thu 2013-11-21 17:18:25 CST, end at Mon 2013-11-25 14:42:21 CST
    Nov 25 14:39:49 Tonka-htpc mysql[29217]: If you want to continue upgrading your
    Nov 25 14:39:49 Tonka-htpc mysql[29217]: touch /var/lib/mysql/.force_upgrade
    Nov 25 14:39:49 Tonka-htpc mysql[29217]: rcmysql restart
    Nov 25 14:39:49 Tonka-htpc mysql[29217]: ..failed
    Nov 25 14:39:49 Tonka-htpc systemd[1]: mysql.service: control process exited, co
    Nov 25 14:39:49 Tonka-htpc systemd[1]: Failed to start LSB: Start the MySQL data
    -- Subject: Unit mysql.service has failed
    -- Defined-By: systemd
    -- Support: systemd-devel Info Page
    -- Documentation: http://www.freedesktop.org/wiki/Soft.../catalog/be02c
    --
    -- Unit mysql.service has failed.
    --
    -- The result is failed.
    Nov 25 14:39:49 Tonka-htpc systemd[1]: Unit mysql.service entered failed state.
    Nov 25 14:40:17 Tonka-htpc kernel: SFW2-INext-DROP-DEFLT IN=enp5s12 OUT= MAC=00:
    Nov 25 14:41:12 Tonka-htpc kernel: SFW2-INext-DROP-DEFLT IN=enp5s12 OUT= MAC=00:
    Nov 25 14:42:21 Tonka-htpc kernel: SFW2-INext-DROP-DEFLT IN=enp5s12 OUT= MAC=00:

    If I try to start it through Services Manager, I get the full text:

    Could not stop mysql which is currently enabled. mysql.service - LSB: Start the MySQL database server
    Loaded: loaded (/etc/init.d/mysql)
    Active: failed (Result: exit-code) since Mon 2013-11-25 14:29:56 CST; 22ms ago
    Process: 28896 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE)

    Nov 25 14:29:56 Tonka-htpc mysql[28896]: You are upgrading from different stable version of MySQL!
    Nov 25 14:29:56 Tonka-htpc mysql[28896]: Make sure you to make backup of your data (mostly /var/lib/mysql)!
    Nov 25 14:29:56 Tonka-htpc mysql[28896]: If you want to continue upgrading your database, run following commands:
    Nov 25 14:29:56 Tonka-htpc mysql[28896]: touch /var/lib/mysql/.force_upgrade
    Nov 25 14:29:56 Tonka-htpc mysql[28896]: rcmysql restart
    Nov 25 14:29:56 Tonka-htpc mysql[28896]: ..failed
    Nov 25 14:29:56 Tonka-htpc systemd[1]: mysql.service: control process exited, code=exited status=1
    Nov 25 14:29:56 Tonka-htpc systemd[1]: Failed to start LSB: Start the MySQL database server.
    Nov 25 14:29:56 Tonka-htpc systemd[1]: Unit mysql.service entered failed state.

    Running the commands in that error message give me the first error message above. I believe those messages are just a log of what the system attempted.

    I found this thread http://forums.opensuse.org/english/g...ils-start.html that seems to be a similar problem, but I have nothing in /var/log/mysql.

    Any suggestions on how I can find more info so I can get it running? I'm a complete noob to MySql.

  2. #2

    Default Re: Can't start MySQL - 13.1

    As the message says, run:
    Code:
    sudo touch /var/lib/mysql/.force_upgrade
    And restart mysql.
    Code:
    sudo rcmysql restart
    And then post the output again if it doesn't work.

    I had the same problem and fixed it somehow, can't remember anymore how exactly.
    But I started like this and got a clue...

  3. #3

    Default Re: Can't start MySQL - 13.1

    As I said above, I tried that already:

    # touch /var/lib/mysql/.force_upgrade
    # rcmysql restart
    redirecting to systemctl restart mysql
    Job for mysql.service failed. See 'systemctl status mysql.service' and 'journalctl -xn' for details.

    I assumed that was the same result, but it's not. When I ran those two commands, this is what I got:

    # systemctl status mysql.service -l
    mysql.service - LSB: Start the MySQL database server
    Loaded: loaded (/etc/init.d/mysql)
    Active: failed (Result: exit-code) since Mon 2013-11-25 15:32:35 CST; 2min 26s ago
    Process: 30183 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE)

    Nov 25 15:32:34 Tonka-htpc mysql[30183]: mysql.time_zone_name OK
    Nov 25 15:32:34 Tonka-htpc mysql[30183]: mysql.time_zone_transition OK
    Nov 25 15:32:34 Tonka-htpc mysql[30183]: mysql.time_zone_transition_type OK
    Nov 25 15:32:34 Tonka-htpc mysql[30183]: mysql.user OK
    Nov 25 15:32:34 Tonka-htpc mysql[30183]: Running 'mysql_fix_privilege_tables'...
    Nov 25 15:32:34 Tonka-htpc mysql[30183]: Running 'mysqlcheck' with connection arguments: '--socket=/var/tmp/mysql-protected.jG4IzN/mysql.sock'
    Nov 25 15:32:34 Tonka-htpc mysql[30183]: ..failed
    Nov 25 15:32:35 Tonka-htpc systemd[1]: mysql.service: control process exited, code=exited status=1
    Nov 25 15:32:35 Tonka-htpc systemd[1]: Failed to start LSB: Start the MySQL database server.
    Nov 25 15:32:35 Tonka-htpc systemd[1]: Unit mysql.service entered failed state.

    # journalctl -xn -l
    -- Logs begin at Thu 2013-11-21 17:18:25 CST, end at Mon 2013-11-25 15:36:06 CST
    Nov 25 15:32:34 Tonka-htpc mysql[30183]: Running 'mysql_fix_privilege_tables'...
    Nov 25 15:32:34 Tonka-htpc mysql[30183]: Running 'mysqlcheck' with connection ar
    Nov 25 15:32:34 Tonka-htpc mysql[30183]: ..failed
    Nov 25 15:32:35 Tonka-htpc systemd[1]: mysql.service: control process exited, co
    Nov 25 15:32:35 Tonka-htpc systemd[1]: Failed to start LSB: Start the MySQL data
    -- Subject: Unit mysql.service has failed
    -- Defined-By: systemd
    -- Support: systemd-devel Info Page
    -- Documentation: http://www.freedesktop.org/wiki/Soft.../catalog/be02c
    --
    -- Unit mysql.service has failed.
    --
    -- The result is failed.
    Nov 25 15:32:35 Tonka-htpc systemd[1]: Unit mysql.service entered failed state.
    Nov 25 15:32:51 Tonka-htpc kernel: SFW2-INext-DROP-DEFLT IN=enp5s12 OUT= MAC=00:
    Nov 25 15:34:10 Tonka-htpc kernel: SFW2-INext-DROP-DEFLT IN=enp5s12 OUT= MAC=00:
    Nov 25 15:35:08 Tonka-htpc kernel: SFW2-INext-DROP-DEFLT IN=enp5s12 OUT= MAC=00:
    Nov 25 15:36:06 Tonka-htpc kernel: SFW2-INext-DROP-DEFLT IN=enp5s12 OUT= MAC=00:

    However, that doesn't help me. I don't know what any of that means. Any suggestions on where to go from here?

  4. #4
    Join Date
    Jun 2008
    Location
    West Yorkshire, UK
    Posts
    3,450

    Default Re: Can't start MySQL - 13.1

    The MySQL version supplied with 13.1 is 5.6. This is not compatible with MariaDB and there is no intention to make MariaDB compatible with MySQL after 5.5.

    If you want to switch back to MySQL, your best bet is to reinstall MariaDB, open a console and enter
    Code:
    mysqldump -u root -p --all-databases > /path/to/backup.sql
    Then reinstall MySQL and restore the backup with
    Code:
    mysql -u root
    source /path/to/backup.sql;
    flush privileges;
    If you do not want to be committed to MySQL, you need to sort out the problems within MariaDB.

  5. #5

    Default AW: Re: Can't start MySQL - 13.1

    Quote Originally Posted by john_hudson View Post
    The MySQL version supplied with 13.1 is 5.6. This is not compatible with MariaDB and there is no intention to make MariaDB compatible with MySQL after 5.5.

    If you want to switch back to MySQL, your best bet is to reinstall MariaDB, open a console and enter
    Code:
    mysqldump -u root -p --all-databases > /path/to/backup.sql
    Then reinstall MySQL and restore the backup with
    Code:
    mysql -u root
    source /path/to/backup.sql;
    flush privileges;
    If you do not want to be committed to MySQL, you need to sort out the problems within MariaDB.
    Well, as I said, I had the same problem after upgrading to 13.1 and MySQL 5.6.
    But I managed to fix it without dumping and restoring the database tables.

    I can't help more at the moment though, but I will be back in about 8-9 hours if you're willing to wait...

  6. #6
    Join Date
    Jun 2008
    Location
    West Yorkshire, UK
    Posts
    3,450

    Default Re: AW: Re: Can't start MySQL - 13.1

    Quote Originally Posted by wolfi323 View Post
    Well, as I said, I had the same problem after upgrading to 13.1 and MySQL 5.6.
    But I managed to fix it without dumping and restoring the database tables.
    I am not surprised; I don't think the differences will be all that great at present and some configurations will encounter few if any problems. It may remain possible to swap simple configurations for the foreseeable future.

    But the MariaDB folks are making quite clear that they will no longer guarantee compatibility other than via mysqldump for the foreseeable future.

  7. #7

    Default Re: Can't start MySQL - 13.1

    Quote Originally Posted by john_hudson View Post
    The MySQL version supplied with 13.1 is 5.6. This is not compatible with MariaDB and there is no intention to make MariaDB compatible with MySQL after 5.5.

    If you want to switch back to MySQL, your best bet is to reinstall MariaDB, open a console and enter
    Code:
    mysqldump -u root -p --all-databases > /path/to/backup.sql
    Nothing's easy.....

    I uninstalled MySql-community, then re-installed MariaDb. I ran this line and got:

    # mysqldump -u root -p --all-databases > backup.sql
    Enter password:
    mysqldump: Got error: 2002: "Can't connect to local MySQL server through socket '/var/run/mysql/mysql.sock' (2)" when trying to connect

  8. #8

    Default Re: Can't start MySQL - 13.1

    Quote Originally Posted by Yippee38 View Post
    Nothing's easy.....

    I uninstalled MySql-community, then re-installed MariaDb. I ran this line and got:

    # mysqldump -u root -p --all-databases > backup.sql
    Enter password:
    mysqldump: Got error: 2002: "Can't connect to local MySQL server through socket '/var/run/mysql/mysql.sock' (2)" when trying to connect
    Have you started MariaDB?

    Regarding the original MySQL problem, I think I did this to get MySQL running:
    Code:
    rm /var/lib/mysql/.run-mysql_upgrade
    And remove /var/lib/mysql/.force_upgrade as well of course if it exists now.
    I got that idea from https://bugzilla.novell.com/show_bug.cgi?id=827505 .

    Then MySQL should not try to upgrade the tables on start, which worked for me.
    I have to say that I haven't used MariaDB before though. So it was an upgrade from MySQL 5.5 to MySQL 5.6.

    But OTOH, I decided to "downgrade" (or should I say "sidegrade"?) to MariaDB 5.5 afterwards (MySQL 5.6 took too much RAM and I didn't want to play with the configuration; I wanted to try out MariaDB since a while already anyway), which worked as well with the existing database files.
    For this I had to remove /var/lib/mysql/ib_logfile0 and /var/lib/mysql/ib_logfile1 though, because MariaDB complained they have the wrong size. But then everything went smooth, and no dataloss!

    That said, it's good to have a backup of /var/lib/mysql/ before playing around of course...

  9. #9

    Default Re: Can't start MySQL - 13.1

    Quote Originally Posted by wolfi323 View Post
    Have you started MariaDB?
    See the title of the thread.

    I can't start the DB.

  10. #10

    Default Re: Can't start MySQL - 13.1

    Quote Originally Posted by Yippee38 View Post
    See the title of the thread.

    I can't start the DB.
    Right, the title of the thread and the first post is about you not being able to start _MySQL_.

    But my question was if you started _MariaDB_ after installing it.
    You didn't say so, or that you cannot start it (or any error message you get when you start it).

    Have you tried the other thing I wrote in that post?
    You would have to install MySQL first of course.

Page 1 of 5 123 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •