Results 1 to 16 of 16

Thread: MariaDB 5.5.60 update to 5.5.61 issue

  1. #1
    Join Date
    Mar 2018
    Posts
    70

    MariaDB 5.5.60 update to 5.5.61 issue

    I run ./build mariadb and received error

    ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/usr/local/mysql/data/mysql.sock' (2)
    mv: ‘mariadb-5.5.61-linux-glibc_214-x86_64.tar.gz’ and ‘/usr/local/mariadb-5.5.61-linux-glibc_214-x86_64.tar.gz’ are the same file
    And now cannot return to the same version

    180917 10:05:01 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
    180917 10:05:01 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.5.60-MariaDB) starting as process 26873 ...
    180917 10:05:01 InnoDB: The InnoDB memory heap is disabled
    180917 10:05:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    180917 10:05:01 InnoDB: Compressed tables use zlib 1.2.3
    180917 10:05:01 InnoDB: Using Linux native AIO
    180917 10:05:01 InnoDB: Initializing buffer pool, size = 128.0M
    180917 10:05:01 InnoDB: Completed initialization of buffer pool
    180917 10:05:01 InnoDB: highest supported file format is Barracuda.
    180917 10:05:01 InnoDB: Waiting for the background threads to start
    180917 10:05:02 Percona XtraDB (http://www.percona.com) 5.5.59-MariaDB-38.11 started; log sequence number 11513921
    180917 10:05:02 [Note] Plugin 'FEEDBACK' is disabled.
    180917 10:05:02 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
    180917 10:05:02 [Note] Server socket created on IP: '0.0.0.0'.
    180917 10:05:02 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'host' is read only
    180917 10:05:02 mysqld_safe mysqld from pid file /usr/local/mysql/data/mysqld.pid ended
    180917 10:05:06 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
    180917 10:05:06 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.5.60-MariaDB) starting as process 27235 ...
    180917 10:05:06 InnoDB: The InnoDB memory heap is disabled
    180917 10:05:06 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    180917 10:05:06 InnoDB: Compressed tables use zlib 1.2.3
    180917 10:05:06 InnoDB: Using Linux native AIO
    180917 10:05:06 InnoDB: Initializing buffer pool, size = 128.0M
    180917 10:05:06 InnoDB: Completed initialization of buffer pool
    180917 10:05:06 InnoDB: highest supported file format is Barracuda.
    180917 10:05:06 InnoDB: Waiting for the background threads to start
    180917 10:05:07 Percona XtraDB (http://www.percona.com) 5.5.59-MariaDB-38.11 started; log sequence number 11513921
    180917 10:05:07 [Note] Plugin 'FEEDBACK' is disabled.
    180917 10:05:07 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
    180917 10:05:07 [Note] Server socket created on IP: '0.0.0.0'.
    180917 10:05:07 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'host' is read only
    180917 10:05:07 mysqld_safe mysqld from pid file /usr/local/mysql/data/mysqld.pid ended
    my.cnf
    [mysqld]
    local-infile=0
    innodb_file_per_table

    [client]
    socket=/usr/local/mysql/data/mysql.sock
    How possible solve issue now

  2. #2
    Join Date
    Apr 2005
    Location
    GMT +7.00
    Posts
    13,750
    Hello,

    It's a Debian related issue.

    Change/add datadir= in /etc/my.cnf from /home/mysql/ and move databases to /var/lib/mysql/:


    Code:
    datadir                        = /var/lib/mysql/
    and MariaDB 10.0.36 should start fine.

    If you don't know how to do it, contact me for a paid service.
    Regards, Alex G.

    - Get the best commercial DirectAdmin support and hire me on poralix.com
    - Follow and like @Poralix on Facebook

  3. #3
    Join Date
    Mar 2018
    Posts
    70
    Thanks for your help. MySQL service started again

  4. #4
    Join Date
    Mar 2018
    Posts
    70
    Issue still have

    FATAL ERROR: Upgrade failed
    Restarting MySQL.
    180917 11:00:14 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

    180917 11:00:14 [Note] InnoDB: Using mutexes to ref count buffer pool pages
    180917 11:00:14 [Note] InnoDB: The InnoDB memory heap is disabled
    180917 11:00:14 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    180917 11:00:14 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
    180917 11:00:14 [Note] InnoDB: Compressed tables use zlib 1.2.3
    180917 11:00:14 [Note] InnoDB: Using Linux native AIO
    180917 11:00:14 [Note] InnoDB: Using CPU crc32 instructions
    180917 11:00:14 [Note] InnoDB: Initializing buffer pool, size = 128.0M
    180917 11:00:14 [Note] InnoDB: Completed initialization of buffer pool
    180917 11:00:14 [Note] InnoDB: Highest supported file format is Barracuda.
    180917 11:00:14 [Note] InnoDB: Starting crash recovery from checkpoint LSN=49463
    180917 11:00:14 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
    180917 11:00:14 [Note] InnoDB: Starting final batch to recover 11 pages from redo log
    180917 11:00:15 [Note] InnoDB: 128 rollback segment(s) are active.
    180917 11:00:15 [Note] InnoDB: Waiting for purge to start
    180917 11:00:15 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.39-83.1 started; log sequence number 1600607
    180917 11:00:15 [Note] Plugin 'FEEDBACK' is disabled.
    180917 11:00:15 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
    180917 11:00:15 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
    180917 11:00:15 [Note] Server socket created on IP: '::'.
    180917 11:00:15 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist
    180917 11:00:15 mysqld_safe mysqld from pid file /usr/local/mysql/data/mysqld.pid ended
    180917 11:00:19 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
    180917 11:00:19 [Note] /usr/local/mysql/bin/mysqld (mysqld 10.0.36-MariaDB) starting as process 18022 ...
    180917 11:00:19 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

    180917 11:00:19 [Note] InnoDB: Using mutexes to ref count buffer pool pages
    180917 11:00:19 [Note] InnoDB: The InnoDB memory heap is disabled
    180917 11:00:19 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    180917 11:00:19 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
    180917 11:00:19 [Note] InnoDB: Compressed tables use zlib 1.2.3
    180917 11:00:19 [Note] InnoDB: Using Linux native AIO
    180917 11:00:19 [Note] InnoDB: Using CPU crc32 instructions
    180917 11:00:19 [Note] InnoDB: Initializing buffer pool, size = 128.0M
    180917 11:00:19 [Note] InnoDB: Completed initialization of buffer pool
    180917 11:00:19 [Note] InnoDB: Highest supported file format is Barracuda.
    180917 11:00:19 [Note] InnoDB: Starting crash recovery from checkpoint LSN=49463
    180917 11:00:19 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
    180917 11:00:19 [Note] InnoDB: Starting final batch to recover 11 pages from redo log
    180917 11:00:20 [Note] InnoDB: 128 rollback segment(s) are active.
    180917 11:00:20 [Note] InnoDB: Waiting for purge to start
    180917 11:00:20 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.39-83.1 started; log sequence number 1600607
    180917 11:00:20 [Note] Plugin 'FEEDBACK' is disabled.
    180917 11:00:20 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
    180917 11:00:20 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
    180917 11:00:20 [Note] Server socket created on IP: '::'.
    180917 11:00:20 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist
    180917 11:00:20 mysqld_safe mysqld from pid file /usr/local/mysql/data/mysqld.pid ended

  5. #5
    Join Date
    Apr 2005
    Location
    GMT +7.00
    Posts
    13,750
    180917 11:00:20 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
    Regards, Alex G.

    - Get the best commercial DirectAdmin support and hire me on poralix.com
    - Follow and like @Poralix on Facebook

  6. #6
    Join Date
    Mar 2018
    Posts
    70
    Service temporary started and kill again.
    Issue solved copy mysql tables from another working server.

    Thank you for your help

  7. #7
    Join Date
    Mar 2018
    Posts
    70
    Maybe you have some recommendations for issue on Debian? Do you upgrade your servers with Debian?

  8. #8
    Join Date
    Apr 2005
    Location
    GMT +7.00
    Posts
    13,750
    I provided the idea which worked for me a week ago. When I faced the same issue on Debian 8 with upgrading MariaDB 10.0.35 to MariaDB 10.0.36.

    I've got the following posts (written by me on the matter):

    - https://help.poralix.com/articles/ma...t-is-read-only
    - https://dba.stackexchange.com/questi...i-is-read-only

    I still have no idea what is behind this. Probably something changed recently in Debian 8.
    Regards, Alex G.

    - Get the best commercial DirectAdmin support and hire me on poralix.com
    - Follow and like @Poralix on Facebook

  9. #9
    Join Date
    Mar 2018
    Posts
    70
    I checked another my server

    mysql_backup_gzip=no
    mysql_backup_dir=/usr/local/directadmin/custombuild/mysql_backups
    dovecot=yes
    dovecot_conf=yes
    pigeonhole=no
    exim=no
    eximconf=no
    eximconf_release=4.5
    blockcracking=no
    easy_spam_fighter=no
    phpmyadmin=yes
    phpmyadmin_ver=4
    squirrelmail=no
    roundcube=yes
    webapps_inbox_prefix=yes
    awstats=no
    webalizer=yes
    autoconf=yes
    automake=yes
    libtool=yes
    curl=yes
    new_pcre=no
    autover=no
    clean_old_tarballs=yes
    clean_old_webapps=yes
    cleanapache=yes
    custombuild=2.0
    cron=no
    cron_frequency=weekly
    email=email@domain.com
    notifications=yes
    da_autoupdate=no
    updates=no
    webapps_updates=yes
    php_ini=no
    spamd=
    spamd=
    spamd=
    spamd=
    spamd=
    spamd=
    spamd=
    spamd=
    spamd=
    spamd=
    spamd=
    spamd=
    spamd=
    spamd=
    spamd=
    spamd=
    spamd=
    spamd=
    spamd=
    Last edited by staff_nowa; 09-17-2018 at 07:09 AM.

  10. #10
    Join Date
    Mar 2018
    Posts
    70
    Something not good after DA update Nice to have fix in DA support in reality

  11. #11
    Join Date
    May 2014
    Posts
    112
    @zEitEr,

    Is this problem only a problem if you didn't have a custom /home partition? (so /home is on /)

  12. #12
    Join Date
    Apr 2005
    Location
    GMT +7.00
    Posts
    13,750
    It should not really matter whether or not /home is mounted as a separate partition.
    Regards, Alex G.

    - Get the best commercial DirectAdmin support and hire me on poralix.com
    - Follow and like @Poralix on Facebook

  13. #13
    Join Date
    May 2014
    Posts
    112
    Quote Originally Posted by zEitEr View Post
    It should not really matter whether or not /home is mounted as a separate partition.
    Thank you! The strange thing is that we have no problems with all MariaDB versions and /home/mysql. So there must be a logical explanation that you have problems and we do not. We use Debian 8 Jessie and Debian 9 Stretch. This should be another problem, but what

  14. #14
    Join Date
    Apr 2005
    Location
    GMT +7.00
    Posts
    13,750
    Is /home/mysql a directory or a link?

    Do you have 711 on /home/ ?
    Regards, Alex G.

    - Get the best commercial DirectAdmin support and hire me on poralix.com
    - Follow and like @Poralix on Facebook

  15. #15
    Join Date
    May 2014
    Posts
    112
    Hello zEitEr,

    We have a normal /home/mysql directory and the permissions 711 for /home. (755 for /home/mysql)

  16. #16
    Join Date
    Apr 2005
    Location
    GMT +7.00
    Posts
    13,750
    Lucky you are

    Here you can find some insights from DA team: https://www.directadmin.com/features.php?id=2182

    Probably you can check your server in details yourself or contact DA support for it.
    Regards, Alex G.

    - Get the best commercial DirectAdmin support and hire me on poralix.com
    - Follow and like @Poralix on Facebook

Posting Permissions

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