Join the community today
Become a Member

Upgrade MariaDB MariaDB 10.1.26 fails to load after update

Discussion in 'Install & Upgrades or Pre-Install Questions' started by envmar, Sep 14, 2017.

  1. envmar

    envmar New Member

    10
    3
    3
    Apr 9, 2017
    Ratings:
    +4
    Local Time:
    7:48 PM
    • CentOS Version: 7 (3.10.0-693.2.2.el7.x86_64) on Vultr Host
    • Centmin Mod Version Installed: 123.09beta01
    • Nginx Version Installed: 1.13.5
    • PHP Version Installed: 7.1.3
    • MariaDB MySQL Version Installed: 10.1.26
    • When was last time updated Centmin Mod code base ? : Today, which included Centmin Mod, Kernel and nginx. Used Centmin Mod Menu to update.
    After upgrade I'm not able to start MariaDB using service mysql start.

    Anyone else have the same problem? Any solutions? Is this a permissions problem?

    I can load mysql by running ./mysql start in /etc/init.d.

    Thanks for your time.

    systemctl status mariadb.service output:
    Code:
    mariadb.service - MariaDB database server
       Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
      Drop-In: /etc/systemd/system/mariadb.service.d
               └─migrated-from-my.cnf-settings.conf, openfileslimit.conf, protecthome.conf
       Active: failed (Result: exit-code) since Wed 2017-09-13 23:53:27 UTC; 12min ago
     Main PID: 18214 (code=exited, status=1/FAILURE)
       Status: "MariaDB server is down"
    
    Sep 13 23:53:27 vw1 mysqld[18214]: 2017-09-13 23:53:27 7f9536152900  InnoDB: Error: unable to create temporary file; errno: 30
    Sep 13 23:53:27 vw1 mysqld[18214]: 2017-09-13 23:53:27 140278834211072 [ERROR] Plugin 'InnoDB' init function returned error.
    Sep 13 23:53:27 vw1 mysqld[18214]: 2017-09-13 23:53:27 140278834211072 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
    Sep 13 23:53:27 vw1 mysqld[18214]: 2017-09-13 23:53:27 140278834211072 [Note] Plugin 'FEEDBACK' is disabled.
    Sep 13 23:53:27 vw1 mysqld[18214]: 2017-09-13 23:53:27 140278834211072 [ERROR] Unknown/unsupported storage engine: InnoDB
    Sep 13 23:53:27 vw1 mysqld[18214]: 2017-09-13 23:53:27 140278834211072 [ERROR] Aborting
    Sep 13 23:53:27 vw1 systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Sep 13 23:53:27 vw1 systemd[1]: Failed to start MariaDB database server.
    Sep 13 23:53:27 vw1 systemd[1]: Unit mariadb.service entered failed state.
    Sep 13 23:53:27 vw1 systemd[1]: mariadb.service failed.
    
    • Persistent Config:
    • Code:
      NGINX_PAGESPEED=y
      NGINX_ZLIBCUSTOM='y'
      ORESTY_LUANGINX=n
      NGINX_XSLT='n'
      NGINX_LIBBROTLI='y'
      NGXDYNAMIC_XSLT='n'
      NGXDYNAMIC_IMAGEFILTER='y'
      NGXDYNAMIC_GEOIP='y'
      NGXDYNAMIC_STREAM='y'
      NGXDYNAMIC_HEADERSMORE='y'
      NGXDYNAMIC_SETMISC='y'
      NGXDYNAMIC_ECHO='y'
      NGXDYNAMIC_SRCCACHE='y'
      NGXDYNAMIC_MEMC='y'
      NGXDYNAMIC_REDISTWO='y'
      NGXDYNAMIC_NGXPAGESPEED='y'
      NGXDYNAMIC_BROTLI='y'
      PHPMSSQL='y'
      PHP_PGO='y'
      PHP_PGO_CENTOSSIX='y'
      NGINX_DEVTOOLSETGCC='y'
      GENERAL_DEVTOOLSETGCC='y'
      CLANG='n'
      LIBRESSL_SWITCH='n'
      NGX_GSPLITDWARF='y'
      PHP_GSPLITDWARF='y'
      NGX_LDGOLD='y'
      
     
  2. Jimmy

    Jimmy Premium Member Premium Member

    1,147
    253
    83
    Oct 24, 2015
    East Coast USA
    Ratings:
    +616
    Local Time:
    10:48 PM
    1.13.x
    MariaDB 10.1.x
    I'm not an expert with dbases, but it might have something to do with your my.cnf. I upgraded to that version of mysql awhile ago and haven't have an issue.

    Did you modify your my.cnf file?
     
  3. envmar

    envmar New Member

    10
    3
    3
    Apr 9, 2017
    Ratings:
    +4
    Local Time:
    7:48 PM
    It was running fine before update and I didn't modify it during/after the update. Could be something the update did?

    Found another error with permission problems on the /home/mysqltmp dir. Changing this to just "/tmp" makes it run. Trying to figure out why it won't use the default /home/mysqltmp dir as permissions seem fine.

    Code:
    Sep 14 03:15:04 vw1 mysqld[2086]: 2017-09-14  3:15:04 140519533656320 [ERROR] mysqld: Can't create/write to file '/home/mysqltmp/ib59H3Oz' (Errcode: 30 "Read-only file system")
    Sep 14 03:15:04 vw1 mysqld[2086]: 2017-09-14 03:15:04 7fcd40e33900  InnoDB: Error: unable to create temporary file; errno: 30
    
    /home/ dir permissions.
    Code:
    drwxrwxrwt  2 mysql mysql 4096 Sep 14 03:11 mysqltmp
    
     
  4. Jimmy

    Jimmy Premium Member Premium Member

    1,147
    253
    83
    Oct 24, 2015
    East Coast USA
    Ratings:
    +616
    Local Time:
    10:48 PM
    1.13.x
    MariaDB 10.1.x
    @eva2000 might be able to shed some light on what happened. That directory should be 777 according to my server setup. Try changing it to 777.
     
  5. eva2000

    eva2000 Administrator Staff Member

    30,634
    6,862
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +10,308
    Local Time:
    1:48 PM
    Nginx 1.13.x
    MariaDB 5.5
  6. eva2000

    eva2000 Administrator Staff Member

    30,634
    6,862
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +10,308
    Local Time:
    1:48 PM
    Nginx 1.13.x
    MariaDB 5.5
  7. eva2000

    eva2000 Administrator Staff Member

    30,634
    6,862
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +10,308
    Local Time:
    1:48 PM
    Nginx 1.13.x
    MariaDB 5.5