Hello,
I updated MySQL to v8.0.26 from v8.0.23 via CustomBuild v2.0.0 (rev: 2740) and it threw an error during that:
This happened on Debian 10.09.
Can I ignore this? It looks like MySQL is running fine afterwards: phpmyadmin works, Service Monitor shows no error and DirectAdmin can create new databases from admin role view.
Best Regards,
I updated MySQL to v8.0.26 from v8.0.23 via CustomBuild v2.0.0 (rev: 2740) and it threw an error during that:
2021-09-05 02:38:09 (7.14 MB/s) - 'mysql-8.0.26-linux-glibc2.12-x86_64.tar.xz' saved [914806904/914806904]
mv: 'mysql-8.0.26-linux-glibc2.12-x86_64.tar.xz' and '/usr/local/mysql-8.0.26-linux-glibc2.12-x86_64.tar.xz' are the same file
tar: write error
Stopping mysqld ...
Linking /usr/local/mysql/bin/mysql_migrate_keyring -> /usr/local/bin/mysql_migrate_keyring...
Ensuring local-infile is disabled for security reasons in MySQL configuration file...
Giving mysqld a few seconds to start up...
Giving mysqld a another few seconds to start up...
Giving mysqld last 20 seconds to start up...
Restarting MySQL.
Installation completed.
Done!
This happened on Debian 10.09.
Can I ignore this? It looks like MySQL is running fine afterwards: phpmyadmin works, Service Monitor shows no error and DirectAdmin can create new databases from admin role view.
Best Regards,