After a upgrade of mysql Bareos works but I receive a warning message in service mysql

[andre...@gmail.com]

Hi,

I did a upgrade today from 5.5 to 5.7 of mysql and bareos stil its working but I receive a lot of warning in the service mysql :

How can I fix it?

Oct 13 17:19:47 backup02 mysqld[12534]: 2020-10-13T15:19:47.727595Z 0 [Warning] Failed to open optimizer cost constant tables
Oct 13 17:19:47 backup02 mysqld[12534]: 2020-10-13T15:19:47.728589Z 0 [Warning] InnoDB: Cannot open table mysql/time_zone_leap_second from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
Oct 13 17:19:47 backup02 mysqld[12534]: 2020-10-13T15:19:47.728609Z 0 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them
Oct 13 17:19:47 backup02 mysqld[12534]: 2020-10-13T15:19:47.729256Z 0 [Warning] InnoDB: Cannot open table mysql/servers from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
Oct 13 17:19:47 backup02 mysqld[12534]: 2020-10-13T15:19:47.729275Z 0 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
Oct 13 17:19:47 backup02 mysqld[12534]: 2020-10-13T15:19:47.731300Z 0 [Note] InnoDB: Buffer pool(s) load completed at 201013 17:19:47
Oct 13 17:19:47 backup02 mysqld[12534]: 2020-10-13T15:19:47.737966Z 0 [Note] Event Scheduler: Loaded 0 events
Oct 13 17:19:47 backup02 mysqld[12534]: 2020-10-13T15:19:47.738202Z 0 [Note] /usr/sbin/mysqld: ready for connections.
Oct 13 17:19:47 backup02 mysqld[12534]: Version: '5.7.30'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
Oct 13 17:19:47 backup02 systemd[1]: Started MySQL Community Server.

[Yavor Marinov]

Helo,

not sure if you missed the news (in case you are using latest bareos version) but there is a purpose behind their decision to move to postgresql. 

If this is the case, just head to latest posts about it.

If it's not i would highly suggest the following:

• roll back to mysql 5.5 (you can first stop the db copy it's directory usually /var/lib/mysql for extra paranoiac safety ;)
• dump the database (Percona's xtrabackup would fit perfectly in the case)
• upgrade to 5.7 and insert the db or use the Xtrabackup prepared dir

In my personal opinion, if you are not too much behind 19.2.7 would highly suggest switching to postgresql - it may frustrate you at first, but it's for good.

Overall, this is my suggestion. Play safe! Just because you "don't have a backup" until you restored - and bareos is excellent doing it.

--
You received this message because you are subscribed to the Google Groups "bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/026e8372-df90-44bf-a1a8-e871c4113d98n%40googlegroups.com.