Mysql / MariaDB can't start after upgrade from Debian 8 to Stretch 9.11

Discussion in 'Installation/Configuration' started by MiniMe, Dec 26, 2019.

  1. MiniMe

    MiniMe Member

    for some reason i'm having issues starting mysql / mariadb, i have checked the logs but not much info there except for below :

    [email protected] /etc/init.d # ./mysql restart
    [....] Restarting mysql (via systemctl): mysql.serviceexiJob for mariadb.service failed because a timeout was exceeded.
    See "systemctl status mariadb.service" and "journalctl -xe" for details.
    failed!

    Anyone that could help - if paid service is needed that's no prob - the faster i get help the better :/
     
  2. Taleman

    Taleman Well-Known Member HowtoForge Supporter

  3. MiniMe

    MiniMe Member

    Sorry but i'm not sure where exactly to look :)
     
  4. MiniMe

    MiniMe Member

    extra info : i can start mysql manually but for some reason the automated startup at boot ( mariadb.service & mysql.service ) do not work ...
     
  5. till

    till Super Moderator Staff Member ISPConfig Developer

    The error message tells you which command you must run to find out the reason for the error:

    journalctl -xe

    run that command right after you restarted mysql.
     
  6. MiniMe

    MiniMe Member

    i only have stuff there regarding to other things using mysql :

    Dec 26 17:17:30 Aphrodite-Artemis postfix/smtpd[24374]: connect from unknown[45.125.66.215]
    Dec 26 17:17:30 Aphrodite-Artemis saslauthd[829]: pam_mysql - SELECT returned no result.
    Dec 26 17:17:30 Aphrodite-Artemis saslauthd[829]: pam_mysql - SELECT returned no result.
    Dec 26 17:17:30 Aphrodite-Artemis saslauthd[829]: DEBUG: auth_pam: pam_authenticate failed: User not known to the underlying authentication module
    Dec 26 17:17:30 Aphrodite-Artemis saslauthd[829]: : auth failure: [service=smtp] [realm=] [mech=pam] [reason=PAM auth error]
    Dec 26 17:17:30 Aphrodite-Artemis postfix/smtpd[24374]: warning: unknown[45.125.66.215]: SASL LOGIN authentication failed: authentication failure
    Dec 26 17:17:30 Aphrodite-Artemis postfix/smtpd[24374]: lost connection after AUTH from unknown[45.125.66.215]
    Dec 26 17:17:30 Aphrodite-Artemis postfix/smtpd[24374]: disconnect from unknown[45.125.66.215] ehlo=1 auth=0/1 commands=1/2
    Dec 26 17:17:31 Aphrodite-Artemis saslauthd[832]: pam_mysql - SELECT returned no result.
    Dec 26 17:17:31 Aphrodite-Artemis saslauthd[832]: pam_mysql - SELECT returned no result.
    Dec 26 17:17:31 Aphrodite-Artemis saslauthd[832]: DEBUG: auth_pam: pam_authenticate failed: User not known to the underlying authentication module
    Dec 26 17:17:31 Aphrodite-Artemis saslauthd[832]: : auth failure: [service=smtp] [realm=evilhannie.eu] [mech=pam] [reason=PAM auth error]
    Dec 26 17:17:31 Aphrodite-Artemis postfix/smtpd[25399]: warning: unknown[46.38.144.117]: SASL LOGIN authentication failed: authentication failure
    Dec 26 17:17:32 Aphrodite-Artemis postfix/smtpd[25399]: disconnect from unknown[46.38.144.117] ehlo=1 auth=0/1 rset=1 quit=1 commands=3/4
    Dec 26 17:17:33 Aphrodite-Artemis saslauthd[829]: pam_mysql - SELECT returned no result.
    Dec 26 17:17:33 Aphrodite-Artemis saslauthd[829]: pam_mysql - SELECT returned no result.
    Dec 26 17:17:33 Aphrodite-Artemis saslauthd[829]: DEBUG: auth_pam: pam_authenticate failed: User not known to the underlying authentication module
    Dec 26 17:17:33 Aphrodite-Artemis saslauthd[829]: : auth failure: [service=smtp] [realm=evilhannie.eu] [mech=pam] [reason=PAM auth error]
    Dec 26 17:17:33 Aphrodite-Artemis postfix/smtpd[23797]: warning: unknown[46.38.144.17]: SASL LOGIN authentication failed: authentication failure
    Dec 26 17:17:34 Aphrodite-Artemis postfix/smtpd[23797]: disconnect from unknown[46.38.144.17] ehlo=1 auth=0/1 rset=1 quit=1 commands=3/4

    if i check mysql status from /etc/init.d i get : ( starting mysql from here just shows time out & failure )

    [email protected] /etc/init.d # ./mysql status
    ● mariadb.service - MariaDB 10.1.41 database server
    Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
    Active: failed (Result: timeout) since Thu 2019-12-26 17:16:51 CET; 3min 12s ago
    Docs: man:mysqld(8)
    https://mariadb.com/kb/en/library/systemd/
    Process: 25500 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
    Process: 25423 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
    Process: 25419 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
    Process: 25415 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
    Main PID: 25500 (code=exited, status=1/FAILURE)
    Status: "MariaDB server is down"

    Dec 26 17:14:38 Aphrodite-Artemis systemd[1]: Starting MariaDB 10.1.41 database server...
    Dec 26 17:14:39 Aphrodite-Artemis mysqld[25500]: 2019-12-26 17:14:39 139937831091584 [Note] /usr/sbin/mysqld (mysqld 10.1.41-MariaDB-0+deb9u1) starting as process 25500 ...
    Dec 26 17:16:09 Aphrodite-Artemis systemd[1]: mariadb.service: Start operation timed out. Terminating.
    Dec 26 17:16:51 Aphrodite-Artemis systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
    Dec 26 17:16:51 Aphrodite-Artemis systemd[1]: Failed to start MariaDB 10.1.41 database server.
    Dec 26 17:16:51 Aphrodite-Artemis systemd[1]: mariadb.service: Unit entered failed state.
    Dec 26 17:16:51 Aphrodite-Artemis systemd[1]: mariadb.service: Failed with result 'timeout'.
     
  7. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    Have you read database logs in /var/log/mysql/ -directory?
     
  8. MiniMe

    MiniMe Member

    it's a really big log since ive been trying all day, but here is the last few lines :
     
  9. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    Have you already used Internet Search Engines with the error messages you got? Like for instance
    Code:
    InnoDB: Unable to lock ./ibdata1, error: 11
     
  10. MiniMe

    MiniMe Member

    thats probably because mysql is now started manually ...
     
  11. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    True, you may get that error if the database is running already and you start it manually. You could stop it first, and then start. And maybe check if any database processes are left after stop.
    The database should be mariadb instead of mysql now that debian is upgraded. Have you checked mariadb is properly installed now and mysql is indeed removed? If you have modified the startup scripts that may cause mixups now that mysql is replaced by mariadb.
     
  12. MiniMe

    MiniMe Member

    i honestly have no clue how to check if its installed properly, i didnt get any errors during the upgrade process and have not changed any scripts ...
     
  13. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    How did you do the upgrade from Debian 8 to Debian 9? The release notes I posted a link to tells how to do the upgrade so it works. If you upgraded with some other way, that may be the reason it is broken now.
     
  14. MiniMe

    MiniMe Member

  15. MiniMe

    MiniMe Member

    this is frigging weird, i just stopped the manual instance and tried to run service mysql start again , now everything is working … what the hell xD
     
  16. MiniMe

    MiniMe Member

    im so sorry to waste your time, but its working now :/
     

Share This Page