• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Mariadb restart error and warnings and on status check

Tonies

New Pleskian
Hi,

When I restart Mariadb and check status (I found the commands today on how to do this), I have the following error and warnings:

Code:
Apr 07 11:18:54 myserver.com mysqld[17688]: 2018-04-07 11:18:54 139961483360000 [Note] InnoDB: Dumping buffer pool(s) not yet started
Apr 07 11:18:54 myserver.com mysqld[17688]: 2018-04-07 11:18:54 139998225299712 [Note] Plugin 'FEEDBACK' is disabled.
Apr 07 11:18:54 myserver.com mysqld[17688]: 2018-04-07 11:18:54 139998225299712 [Note] Server socket created on IP: '127.0.0.1'.
Apr 07 11:18:54 myserver.com mysqld[17688]: 2018-04-07 11:18:54 139998225299712 [Warning] 'proxies_priv' entry '@% root@centos-74-64-minimal' ignored in --skip-name-resolve m                ode.
Apr 07 11:18:54 myserver.com mysqld[17688]: 2018-04-07 11:18:54 139998225299712 [ERROR] Missing system table mysql.roles_mapping; please run mysql_upgrade to create it
Apr 07 11:18:54 myserver.com mysqld[17688]: 2018-04-07 11:18:54 139998224857856 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table                 'mysql.gtid_slave_pos' doesn't exist
Apr 07 11:18:54 myserver.com mysqld[17688]: 2018-04-07 11:18:54 139998225299712 [Note] /usr/sbin/mysqld: ready for connections.
Apr 07 11:18:54 myserver.com mysqld[17688]: Version: '10.1.32-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
Apr 07 11:18:54 myserver.com systemd[1]: Started MariaDB 10.1.32 database server.
Apr 07 11:19:04 myserver.com mysqld[17688]: 2018-04-07 11:19:04 7f53e0719b00 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.

As you can see, there are warnings as follows:

1) Warning] 'proxies_priv' entry ignored in --skip-name-resolve mode.

2) [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table 'mysql.gtid_slave_pos' doesn't exist

And the error:

3) [ERROR] Missing system table MySQL.roles_mapping; please run mysql_upgrade to create it

This error, is it safe to run the "mysql_upgrade" in command line based on the above status?

I searched on Google but no true information on how to resolve these.

Any guidance or info on how to find details to rectify the above would be much appreciated. If anyone had this previously too, then please let me know how you resolved it.

Thanks in advance.
 
Last edited:
After searching and adding "Plesk" at the front of the error, I found and followed this article: Error appears during start of mysql service: Missing system table mysql.roles_mapping; please run mysql_upgrade to create it

1) I run the command suggested: "MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql_upgrade -u admin --host localhost --port 3306" in CLI

2) I had to restart Mariadb to see the new status "systemctl status mariadb.service"

3) New status:

Code:
Apr 07 11:54:50 myserver.com mysqld[18864]: 2018-04-07 11:54:50 140115637242112 [Note] InnoDB: 128 rollback segment(s) are active.
Apr 07 11:54:50 myserver.com mysqld[18864]: 2018-04-07 11:54:50 140115637242112 [Note] InnoDB: Waiting for purge to start
Apr 07 11:54:50 myserver.com mysqld[18864]: 2018-04-07 11:54:50 140115637242112 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.38-83.0 started; log sequence number 173698156079
Apr 07 11:54:50 myserver.com mysqld[18864]: 2018-04-07 11:54:50 140078894511872 [Note] InnoDB: Dumping buffer pool(s) not yet started
Apr 07 11:54:50 myserver.com mysqld[18864]: 2018-04-07 11:54:50 140115637242112 [Note] Plugin 'FEEDBACK' is disabled.
Apr 07 11:54:51 myserver.com mysqld[18864]: 2018-04-07 11:54:51 140115637242112 [Note] Server socket created on IP: '127.0.0.1'.
Apr 07 11:54:51 myserver.com mysqld[18864]: 2018-04-07 11:54:51 140115637242112 [Warning] 'proxies_priv' entry '@% root@centos-74-64-minimal' ignored in --skip-name-resolve mode.
Apr 07 11:54:51 myserver.com mysqld[18864]: 2018-04-07 11:54:51 140115637242112 [Note] /usr/sbin/mysqld: ready for connections.
Apr 07 11:54:51 myserver.com mysqld[18864]: Version: '10.1.32-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server

About the warning:

1) 'proxies_priv' entry ignored in --skip-name-resolve mode.

After researching my server.cnf in /etc/my.cnf.d has skip-name-resolve=1 which am guessing it's causing the above warning.

I found an article here about it: MySQL Bugs: #81441: Warning about localhost when using skip-name-resolve

It states it's a bug "Changing category to server bug." with the severity of "(Non-critical)"

I am guessing I can safely ignore this, if anybody thinks otherwise and can provide further information on how to resolve this somehow, please do provide some guidance on this.

I hope the above helps others who are newbies and not as technical as me and a search engine sends them here.

Thank you.
 
Back
Top