Learn about Centmin Mod LEMP Stack today
Become a Member

MariaDB Upgrade MariaDB 10.3.x to MariaDB 10.4.x

Discussion in 'Nginx, PHP-FPM & MariaDB MySQL' started by Investrum, Jun 20, 2019.

  1. Investrum

    Investrum New Member

    7
    1
    3
    Jun 19, 2019
    Ratings:
    +3
    Local Time:
    7:38 PM
    1.17.0
    MariaDB 10.3.16
    Hi!
    How i can upgrade MariaDB? Centmin Mod 123.09beta01. I choose 11) MariaDB MySQL Upgrade & Management in main menu and then 8) MariaDB 10.3.x to MariaDB 10.4.x YUM upgrade. And get:
    Code (Text):
    Place holder for now until MariaDB 10.4.x is ready to be added
    What does it mean?
    Thank.
     
  2. pamamolf

    pamamolf Premium Member Premium Member

    3,584
    345
    83
    May 31, 2014
    Ratings:
    +667
    Local Time:
    6:38 PM
    Nginx-1.17.x
    MariaDB 10.3.x
    That he is working on that function :)

    Sure it will be great to have that option but it may be a bot early even if they release a stable version of 10.4.x as many things changed and a proper testing and understanding of changes in my opinion is a must !
     
    • Like Like x 2
  3. eva2000

    eva2000 Administrator Staff Member

    42,376
    9,569
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +14,747
    Local Time:
    2:38 AM
    Nginx 1.17.x
    MariaDB 5.5/10.x
    yeah currently in private testing right now by me :)

    But as I recently learnt MariaDB 10.4 is breaking away from being drop in compatible with Oracle MySQL - so it's one way without a way back to non-MariaDB MySQL like Oracle MySQL eventually MariaDB - Interesting look at what's new in MariaDB 10.4. So MariaDB 10.3 might be more suited if you ever want to be able to switch easily between MariaDB and Oracle and Percona MySQL versions.
     
    • Like Like x 1
  4. eva2000

    eva2000 Administrator Staff Member

    42,376
    9,569
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +14,747
    Local Time:
    2:38 AM
    Nginx 1.17.x
    MariaDB 5.5/10.x
  5. negative

    negative Active Member

    360
    40
    28
    Apr 11, 2015
    Ratings:
    +82
    Local Time:
    6:38 PM
    1.9.10
    10.1.11
    Hello
    I'm here for same thing.

    While upgrading the mariadb 10.3 to 10.4, i got these errors (after yum upgrade complete for 10.4 mariadb)

    Code (Text):
    *************************************************
    * Adjust old MariaDB 10.x /etc/my.cnf
      for MariaDB 10.4.x my.cnf compatibility
    *************************************************
    
    service mysql start
    Redirecting to /bin/systemctl start mysql.service
    Failed to start mysql.service: Unit not found.
    service mysql restart
    Redirecting to /bin/systemctl restart mysql.service
    Failed to restart mysql.service: Unit not found.
    
    ## !! mysql failed to start properly !! ##
    journalctl -xn
    -- Logs begin at Thu 2019-09-05 02:59:52 +03, end at Thu 2019-09-05 03:04:47 +03. --
    Sep 05 03:04:12 webserver systemd[1]: Configuration file /etc/systemd/system/disable-thp.service is marked executable. Please remove executable permission bits. Proceeding anyway.
    Sep 05 03:04:12 webserver systemd[1]: [/etc/systemd/system/redis.service.d/after-rc-local.conf:2] Failed to add dependency on rc.local, ignoring: Invalid argument
    Sep 05 03:04:12 webserver useradd[6316]: failed adding user 'mysql', exit code: 9
    Sep 05 03:04:23 webserver yum[5965]: Installed: MariaDB-server-10.4.7-1.el7.centos.x86_64
    Sep 05 03:04:26 webserver yum[5965]: Updated: MariaDB-devel-10.4.7-1.el7.centos.x86_64
    Sep 05 03:04:27 webserver yum[5965]: Updated: MariaDB-shared-10.4.7-1.el7.centos.x86_64
    Sep 05 03:04:32 webserver polkitd[1373]: Registered Authentication Agent for unix-process:6554:28119 (system bus name :1.28 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
    Sep 05 03:04:32 webserver polkitd[1373]: Unregistered Authentication Agent for unix-process:6554:28119 (system bus name :1.28, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
    Sep 05 03:04:47 webserver polkitd[1373]: Registered Authentication Agent for unix-process:6683:29622 (system bus name :1.29 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
    Sep 05 03:04:47 webserver polkitd[1373]: Unregistered Authentication Agent for unix-process:6683:29622 (system bus name :1.29, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
    
    tail -50 /var/log/mysqld.log
    2019-06-18 10:25:07 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
    2019-06-18 10:25:07 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
    2019-06-18 10:25:07 0 [Note] InnoDB: 10.3.16 started; log sequence number 1631253; transaction id 21
    2019-06-18 10:25:07 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
    2019-06-18 10:25:07 0 [Note] Plugin 'FEEDBACK' is disabled.
    2019-06-18 10:25:07 0 [Note] Server socket created on IP: '::'.
    2019-06-18 10:25:07 0 [Note] /usr/sbin/mysqld: ready for connections.
    Version: '10.3.16-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
    2019-06-18 10:25:07 0 [Note] InnoDB: Buffer pool(s) load completed at 190618 10:25:07
    2019-06-18 10:37:03 0 [Note] /usr/sbin/mysqld (initiated by: unknown): Normal shutdown
    2019-06-18 10:37:03 0 [Note] Event Scheduler: Purging the queue. 0 events
    2019-06-18 10:37:03 0 [Note] InnoDB: FTS optimize thread exiting.
    2019-06-18 10:37:03 0 [Note] InnoDB: Starting shutdown...
    2019-06-18 10:37:03 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
    2019-06-18 10:37:03 0 [Note] InnoDB: Buffer pool(s) dump completed at 190618 10:37:03
    2019-06-18 10:37:04 0 [Note] InnoDB: Shutdown completed; log sequence number 1631262; transaction id 24
    2019-06-18 10:37:04 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
    2019-06-18 10:37:04 0 [Note] /usr/sbin/mysqld: Shutdown complete
    
    2019-06-18 10:37:18 0 [Note] InnoDB: Using Linux native AIO
    2019-06-18 10:37:18 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    2019-06-18 10:37:18 0 [Note] InnoDB: Uses event mutexes
    2019-06-18 10:37:18 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
    2019-06-18 10:37:18 0 [Note] InnoDB: Number of pools: 1
    2019-06-18 10:37:18 0 [Note] InnoDB: Using SSE2 crc32 instructions
    2019-06-18 10:37:18 0 [Note] InnoDB: Initializing buffer pool, total size = 8G, instances = 8, chunk size = 128M
    2019-06-18 10:37:19 0 [Note] InnoDB: Completed initialization of buffer pool
    2019-06-18 10:37:19 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
    2019-06-18 10:37:19 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
    2019-06-18 10:37:19 0 [Note] InnoDB: Creating shared tablespace for temporary tables
    2019-06-18 10:37:19 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
    2019-06-18 10:37:19 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
    2019-06-18 10:37:19 0 [Note] InnoDB: Waiting for purge to start
    2019-06-18 10:37:19 0 [Note] InnoDB: 10.3.16 started; log sequence number 1631262; transaction id 21
    2019-06-18 10:37:19 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
    2019-06-18 10:37:19 0 [Note] Plugin 'FEEDBACK' is disabled.
    2019-06-18 10:37:19 0 [Note] Server socket created on IP: '::'.
    2019-06-18 10:37:19 0 [Note] InnoDB: Buffer pool(s) load completed at 190618 10:37:19
    2019-06-18 10:37:19 0 [Note] /usr/sbin/mysqld: ready for connections.
    Version: '10.3.16-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
    2019-06-18 10:59:36 0 [Note] /usr/sbin/mysqld (initiated by: unknown): Normal shutdown
    2019-06-18 10:59:36 0 [Note] Event Scheduler: Purging the queue. 0 events
    2019-06-18 10:59:36 0 [Note] InnoDB: FTS optimize thread exiting.
    2019-06-18 10:59:36 0 [Note] InnoDB: Starting shutdown...
    2019-06-18 10:59:36 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
    2019-06-18 10:59:36 0 [Note] InnoDB: Buffer pool(s) dump completed at 190618 10:59:36
    2019-06-18 10:59:38 0 [Note] InnoDB: Shutdown completed; log sequence number 1631271; transaction id 22
    2019-06-18 10:59:38 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
    2019-06-18 10:59:38 0 [Note] /usr/sbin/mysqld: Shutdown complete
    
    possible errors / warnings
    
    possible unknown or incompatible /etc/my.cnf set options below
    maybe need to comment out or remove these in /etc/my.cnf
    
    attempting auto commenting out of invalid options
    service mysql restart
    Redirecting to /bin/systemctl restart mysql.service
    Failed to restart mysql.service: Unit not found.
    
    total 1.6G
    -rw-rw----. 1 mysql mysql    0 Jun 18 13:23 multi-master.info
    drwx------. 2 mysql mysql 4.0K Jun 18 13:24 mysql
    drwx------. 2 mysql mysql   20 Jun 18 13:24 performance_schema
    -rw-r--r--. 1 mysql mysql   16 Jun 18 13:24 mysql_upgrade_info
    drwxr-xr-x. 2 mysql mysql   84 Jun 18 13:25 cmsetiofiotest
    drwx------  2 mysql mysql  20K Jun 18 21:39 forum2
    -rw-rw----  1 mysql mysql 1.9M Sep  4 15:24 ib_buffer_pool
    -rw-rw----. 1 mysql mysql 768M Sep  5 03:00 ib_logfile1.bak
    -rw-rw----. 1 mysql mysql 768M Sep  5 03:02 ib_logfile0.bak
    -rw-rw----. 1 mysql mysql  74M Sep  5 03:02 ibdata1
    -rw-rw----. 1 mysql mysql   52 Sep  5 03:02 aria_log_control
    -rw-rw----. 1 mysql mysql  16K Sep  5 03:02 aria_log.00000001
    mysql_upgrade --verbose
    Looking for 'mysql' as: mysql
    Looking for 'mysqlcheck' as: mysqlcheck
    Version check failed. Got the following error when calling the 'mysql' command line client
    ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
    FATAL ERROR: Upgrade failed
    ------------------------------------------------
    Installing MariaDB 10 plugins
    ------------------------------------------------
    mysql -e "INSTALL SONAME 'metadata_lock_info';"
    ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
    mysql -e "INSTALL SONAME 'query_cache_info';"
    ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
    mysql -e "INSTALL SONAME 'query_response_time';"
    ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
    mysql -t -e "SELECT * FROM mysql.plugin;"
    ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
    mysql -t -e "SHOW PLUGINS;"
    ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
    mysql -t -e "SHOW ENGINES;"
    ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
    service mysql restart
    Redirecting to /bin/systemctl restart mysql.service
    Failed to restart mysql.service: Unit not found.
    systemctl enable mariadb.service
    Created symlink from /etc/systemd/system/mysql.service to /usr/lib/systemd/system/mariadb.service.
    Created symlink from /etc/systemd/system/mysqld.service to /usr/lib/systemd/system/mariadb.service.
    Created symlink from /etc/systemd/system/multi-user.target.wants/mariadb.service to /usr/lib/systemd/system/mariadb.service.
    
    mysqladmin: connect to server at 'localhost' failed
    error: 'Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)'
    Check that mysqld is running and that the socket: '/var/lib/mysql/mysql.sock' exists!
    
    ------------------------------------------------
    MariaDB 10.4.x Upgrade completed
    ------------------------------------------------
    



    After all of these errors, i run the service mysql start command and database server looks work now. it was inactive (dead) after upgrade that is very interesting!
    (it works but i dont know something missed or wrong for next)


    What was the problem ?
    Is it like socket, host problem?

    P.S: I just tried to upgrade the mariadb server on test board to 10.4 from 10.3 now.
    In live server, i have mariadb 10.1 so my job is will be harder i though.
    Actually, I fair that even backed up full of all databases. :D

    And if something fails and can't start the database server, may i have possibility to turn back any mariadb version? Because, centmin doesn't have fresh or re-install the mariadb database server with specific version like nginx although full database backup.

    Did you explain manuel process for install mariadb server if fail something while upgrading the mariadb @eva2000 ?
     
  6. eva2000

    eva2000 Administrator Staff Member

    42,376
    9,569
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +14,747
    Local Time:
    2:38 AM
    Nginx 1.17.x
    MariaDB 5.5/10.x
    could be false error as centos 7 in later MariaDB versions changed the alias service command from mysql from mysql to mysqld

    without d
    Code (Text):
    service mysql status
     ERROR! MariaDB is running but PID file could not be found
    

    with d in mysqld
    Code (Text):
    service mysqld status
    Redirecting to /bin/systemctl status mysqld.service
    ● mariadb.service - MariaDB 10.3.17 database server
       Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
      Drop-In: /etc/systemd/system/mariadb.service.d
               └─jemalloc.conf, migrated-from-my.cnf-settings.conf, openfileslimit.conf, protecthome.conf
       Active: active (running) since Sun 2019-08-04 04:45:46 UTC; 1 months 1 days ago
         Docs: man:mysqld(8)
               https://mariadb.com/kb/en/library/systemd/
     Main PID: 15258 (mysqld)
       Status: "Taking your SQL requests now..."
        Tasks: 27
       Memory: 92.2M
       CGroup: /system.slice/mariadb.service
               └─15258 /usr/sbin/mysqld
    

    If it fails only 100% sure way is fresh Centmin Mod install on new VPS/server and move your mysql data and files to new server. Unless you 100% know what you're doing and looking out for or hire someone, anything else could possible miss important steps which could result in irreversible data loss.

    Code (Text):
    ------------------------------------------------
    Installing MariaDB 10 plugins
    ------------------------------------------------
    mysql -e "INSTALL SONAME 'metadata_lock_info';"
    ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
    

    did you have working /root/.my.cnf mysql root password there ?
    what do you get from SSH command below ?
    Code (Text):
    mysqladmin ver

    Really would need full mariadb centmin.sh menu upgrade logs which would be in /root/centminlogs labelled as such

    below command will list name of actual log files in /root/centminlogs
    Code (Text):
    cd /root/centminlogs
    ls -lahrt | egrep 'mariadb_10-1-to-10-2_upgrade.log|mariadb_10-2-to-10-3_upgrade.log|mariadb_10-3-to-10-4_upgrade.log'
    

    You can private conversion message me with link to the logs posted via pastebin or gist.github.com
     
  7. negative

    negative Active Member

    360
    40
    28
    Apr 11, 2015
    Ratings:
    +82
    Local Time:
    6:38 PM
    1.9.10
    10.1.11
    It is your centminmod beta fresh install, i didn't modify something in my webserver but that is interesting point. I though, unit not found after upgrade to 10.4 because normally, service mysql status command works even right now.. service mysql status and service mysqld status returns same and working, so service mysql restart command works too.

    But, something happening after yum install upgrade completed while beginning the upgrade, mysql unit lost. So it can't restart and getting many many errors.

    Yes,
    Code (Text):
    mysqladmin ver
    mysqladmin  Ver 9.1 Distrib 10.4.7-MariaDB, for Linux on x86_64
    Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
    
    Server version          10.4.7-MariaDB
    Protocol version        10
    Connection              Localhost via UNIX socket
    UNIX socket             /var/lib/mysql/mysql.sock
    Uptime:                 1 min 15 sec
    
    Threads: 7  Questions: 1  Slow queries: 0  Opens: 17  Flush tables: 1  Open tables: 11  Queries per second avg: 0.013


    Thank you for your help, i though should be need some code modifications for your upgrade scripts due this errors i don't know. I've sent the all details to you on private conversation anyway.

    And please note that, database server looks work but may be critical errors in next , i don't know because if i look the errors, mysql user tables didn't modified because fails of the mysql service restarts / starts i though.

    Thanks
     
  8. eva2000

    eva2000 Administrator Staff Member

    42,376
    9,569
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +14,747
    Local Time:
    2:38 AM
    Nginx 1.17.x
    MariaDB 5.5/10.x
    i think you should be fine just need to manually run a few of these commands which might have been skipped due to the false reported service mysql status being down (which it wasn't)
    Code (Text):
    mysql_upgrade --verbose
    mysql -e "INSTALL SONAME 'metadata_lock_info';"
    mysql -e "INSTALL SONAME 'query_cache_info';"
    mysql -e "INSTALL SONAME 'query_response_time';"
    mysql -t -e "SELECT * FROM mysql.plugin;"
    mysql -t -e "SHOW PLUGINS;"
    mysql -t -e "SHOW ENGINES;"
    

    post the command outputs for these commands in CODE bbcode tags
     
  9. negative

    negative Active Member

    360
    40
    28
    Apr 11, 2015
    Ratings:
    +82
    Local Time:
    6:38 PM
    1.9.10
    10.1.11
    mysql_upgrade --verbose command status is OK.
    query cache and query response is OK too.

    mysql -t -e "SELECT * FROM mysql.plugin;"
    Code (Text):
    +---------------------------+------------------------+
    | name                      | dl                     |
    +---------------------------+------------------------+
    | METADATA_LOCK_INFO        | metadata_lock_info.so  |
    | QUERY_CACHE_INFO          | query_cache_info.so    |
    | QUERY_RESPONSE_TIME       | query_response_time.so |
    | QUERY_RESPONSE_TIME_AUDIT | query_response_time.so |
    +---------------------------+------------------------+


    mysql -t -e "SHOW PLUGINS;"
    Code (Text):
    | INNODB_CMP_PER_INDEX          | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
    | INNODB_CMP_PER_INDEX_RESET    | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
    | INNODB_BUFFER_PAGE            | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
    | INNODB_BUFFER_PAGE_LRU        | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
    | INNODB_BUFFER_POOL_STATS      | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
    | INNODB_METRICS                | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
    | INNODB_FT_DEFAULT_STOPWORD    | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
    | INNODB_FT_DELETED             | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
    | INNODB_FT_BEING_DELETED       | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
    | INNODB_FT_CONFIG              | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
    | INNODB_FT_INDEX_CACHE         | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
    | INNODB_FT_INDEX_TABLE         | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
    | INNODB_SYS_TABLES             | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
    | INNODB_SYS_TABLESTATS         | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
    | INNODB_SYS_INDEXES            | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
    | INNODB_SYS_COLUMNS            | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
    | INNODB_SYS_FIELDS             | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
    | INNODB_SYS_FOREIGN            | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
    | INNODB_SYS_FOREIGN_COLS       | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
    | INNODB_SYS_TABLESPACES        | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
    | INNODB_SYS_DATAFILES          | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
    | INNODB_SYS_VIRTUAL            | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
    | INNODB_MUTEXES                | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
    | INNODB_SYS_SEMAPHORE_WAITS    | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
    | INNODB_TABLESPACES_ENCRYPTION | ACTIVE   | INFORMATION SCHEMA | NULL                   | BSD     |
    | INNODB_TABLESPACES_SCRUBBING  | ACTIVE   | INFORMATION SCHEMA | NULL                   | BSD     |
    | PERFORMANCE_SCHEMA            | ACTIVE   | STORAGE ENGINE     | NULL                   | GPL     |
    | SEQUENCE                      | ACTIVE   | STORAGE ENGINE     | NULL                   | GPL     |
    | unix_socket                   | ACTIVE   | AUTHENTICATION     | NULL                   | GPL     |
    | FEEDBACK                      | DISABLED | INFORMATION SCHEMA | NULL                   | GPL     |
    | user_variables                | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
    | partition                     | ACTIVE   | STORAGE ENGINE     | NULL                   | GPL     |
    | METADATA_LOCK_INFO            | ACTIVE   | INFORMATION SCHEMA | metadata_lock_info.so  | GPL     |
    | QUERY_CACHE_INFO              | ACTIVE   | INFORMATION SCHEMA | query_cache_info.so    | BSD     |
    | QUERY_RESPONSE_TIME           | ACTIVE   | INFORMATION SCHEMA | query_response_time.so | GPL     |
    | QUERY_RESPONSE_TIME_AUDIT     | ACTIVE   | AUDIT              | query_response_time.so | GPL     |
    +-------------------------------+----------+--------------------+------------------------+---------+


    mysql -t -e "SHOW ENGINES;"
    Code (Text):
    +--------------------+---------+-------------------------------------------------------------------------------------------------+--------------+------+------------+
    | Engine             | Support | Comment                                                                                         | Transactions | XA   | Savepoints |
    +--------------------+---------+-------------------------------------------------------------------------------------------------+--------------+------+------------+
    | CSV                | YES     | Stores tables as CSV files                                                                      | NO           | NO   | NO         |
    | MRG_MyISAM         | YES     | Collection of identical MyISAM tables                                                           | NO           | NO   | NO         |
    | MEMORY             | YES     | Hash based, stored in memory, useful for temporary tables                                       | NO           | NO   | NO         |
    | Aria               | YES     | Crash-safe tables with MyISAM heritage. Used for internal temporary tables and privilege tables | NO           | NO   | NO         |
    | MyISAM             | YES     | Non-transactional engine with good performance and small data footprint                         | NO           | NO   | NO         |
    | SEQUENCE           | YES     | Generated tables filled with sequential values                                                  | YES          | NO   | YES        |
    | InnoDB             | DEFAULT | Supports transactions, row-level locking, foreign keys and encryption for tables                | YES          | YES  | YES        |
    | PERFORMANCE_SCHEMA | YES     | Performance Schema                                                                              | NO           | NO   | NO         |
    +--------------------+---------+-------------------------------------------------------------------------------------------------+--------------+------+------------+


    So everything looks good now ?

    Btw, why mysql service command occurs errors while upgrade do you think?
     
  10. eva2000

    eva2000 Administrator Staff Member

    42,376
    9,569
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +14,747
    Local Time:
    2:38 AM
    Nginx 1.17.x
    MariaDB 5.5/10.x
  11. negative

    negative Active Member

    360
    40
    28
    Apr 11, 2015
    Ratings:
    +82
    Local Time:
    6:38 PM
    1.9.10
    10.1.11
  12. eva2000

    eva2000 Administrator Staff Member

    42,376
    9,569
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +14,747
    Local Time:
    2:38 AM
    Nginx 1.17.x
    MariaDB 5.5/10.x
    i fixed all mariadb upgrades for 10.2, 10.3 and 10.4 :)
     
    • Like Like x 1
  13. negative

    negative Active Member

    360
    40
    28
    Apr 11, 2015
    Ratings:
    +82
    Local Time:
    6:38 PM
    1.9.10
    10.1.11
    Btw, i please you that share the instructions for uninstall and install mariadb on the server manually if if something go wrong and crash the database server while these upgrading processes.

    Because, you are talking and directing for full backup before upgrade it is okay, but if occur an error and database server crash, you don't have some instructions for uninstall and re-install the mariadb server.

    I thought, it must be without move all files to another server(!) ornew fresh centminmod etc. instead of very hard processes. I'm telling that because of you advice me move all files and install fresh centminmod....

    It is not possible that uninstall mariadb and install again manually really?

    Thanks
     
  14. eva2000

    eva2000 Administrator Staff Member

    42,376
    9,569
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +14,747
    Local Time:
    2:38 AM
    Nginx 1.17.x
    MariaDB 5.5/10.x
    Database crashes may not necessarily need uninstall/re-install of MariaDB so providing such instructions for folks not able to distinguish when to uninstall/reinstall and when to troubleshoot through the error messages can be dangerous.

    The idea for backup of mysql via mysqldump before upgrade is so if there is problem, you setup a fresh new centos 7 server, install fresh centmin mod 123.09beta01 and then migrate data file sand mysql sql backups to new server and restore sql database backups to new server. Thus, ensuring 100% working system again.

    It's possible, but I wouldn't be providing free support or guidance for such as the process if done incorrectly could mean you loose all your MySQL data if you don't follow the instructions properly. And this is provided that MariaDB MySQL was the ONLY problem with the upgrade and nothing else on your server to begin with. I on the outside, wouldn't be privy to any other issues you may have already or introduced during the upgrade process. So the safest thing, is migrating the data to a new fresh CentOS 7/centmin mod installation.

    So if you 100% know what you're doing, sure you can uninstall and reinstall MariaDB MySQL the Centmin Mod way and configure it as such.