Description
When upgrading MariaDB (steps followed from here: https://notes.apiscp.com/in-place-mariadb-upgrade), the dnf install step finishes with the following output:
Running transaction
Preparing : 1/1
Running scriptlet: MariaDB-server-10.11.9-1.el8.x86_64 1/1
Installing : MariaDB-server-10.11.9-1.el8.x86_64 1/1
Running scriptlet: MariaDB-server-10.11.9-1.el8.x86_64 1/1
[/usr/lib/tmpfiles.d/dovecot.conf:1] Line references path below legacy directory /var/run/, updating /var/run/dovecot → /run/dovecot; please update the tmpfiles.d/ drop-in file accordingly.
[/usr/lib/tmpfiles.d/var.conf:15] Duplicate line for path "/var/log/wtmp", ignoring.
[/usr/lib/tmpfiles.d/var.conf:16] Duplicate line for path "/var/log/btmp", ignoring.
Verifying : MariaDB-server-10.11.9-1.el8.x86_64 1/1
post-transaction-actions: (mysqli_sql_exception) EXCEPTION: No such file or directory
[/usr/local/apnscp/lib/mysql.php:217]
0. mysqli->__construct("localhost", "apnscp", "X", "apnscp", "3306", "/var/lib/mysql/mysql.sock")
[/usr/local/apnscp/lib/mysql.php:217]
1. MySQL->__construct("localhost", "apnscp", "X", "apnscp", null, null)
[/usr/local/apnscp/lib/mysql.php:117]
2. MySQL::initialize()
[/usr/local/apnscp/lib/Opcenter/Database/MySQL.php:175]
3. Opcenter\Database\MySQL::version()
[/usr/local/apnscp/lib/CLI/Yum/Synchronizer/Plugins/Trigger/MariaDBServer.php:51]
4. CLI\Yum\Synchronizer\Plugins\Trigger\MariaDBServer->update("MariaDB-server")
[/usr/local/apnscp/lib/CLI/Yum/Synchronizer/Plugins/Manager.php:52]
5. CLI\Yum\Synchronizer\Plugins\Manager::run("MariaDB-server", "update")
[/usr/local/apnscp/lib/CLI/Yum/Synchronizer.php:102]
6. CLI\Yum\Synchronizer::factory(["/usr/local/apnscp/bin/scripts/yum-post.php", "install", "--update", "MariaDB-server", "10.11.9", "1.el8"])
[/usr/local/apnscp/bin/scripts/yum-post.php:11]
post-transaction-actions: (mysqli_sql_exception) EXCEPTION: No such file or directory
[/usr/local/apnscp/lib/mysql.php:217]
0. mysqli->__construct("localhost", "apnscp", "X", "apnscp", "3306", "/var/lib/mysql/mysql.sock")
[/usr/local/apnscp/lib/mysql.php:217]
1. MySQL->__construct("localhost", "apnscp", "X", "apnscp", null, null)
[/usr/local/apnscp/lib/mysql.php:117]
2. MySQL::initialize()
[/usr/local/apnscp/lib/Opcenter/Database/MySQL.php:175]
3. Opcenter\Database\MySQL::version()
[/usr/local/apnscp/lib/CLI/Yum/Synchronizer/Plugins/Trigger/MariaDBServer.php:51]
4. CLI\Yum\Synchronizer\Plugins\Trigger\MariaDBServer->update("MariaDB-server")
[/usr/local/apnscp/lib/CLI/Yum/Synchronizer/Plugins/Manager.php:52]
5. CLI\Yum\Synchronizer\Plugins\Manager::run("MariaDB-server", "update")
[/usr/local/apnscp/lib/CLI/Yum/Synchronizer.php:102]
6. CLI\Yum\Synchronizer::factory(["/usr/local/apnscp/bin/scripts/yum-post.php", "install", "--update", "MariaDB-server", "10.11.9", "1.el8"])
[/usr/local/apnscp/bin/scripts/yum-post.php:11]
This seems to be happening because the service hadn’t been started yet. My question, is whether this should be any cause for concern, and if so should I take any steps to ensure the service is stable? Note the sites on the panel seem to be functional right now.
Steps to Reproduce
Follow the steps defined here: In-place MariaDB upgrade | ApisCP Notes
Environment
ApisCP version:
[root@s1 apnscp]# cpcmd misc:cp-version
revision: 1814911815b20746dabcad49e0060e32caf3d058
timestamp: 1727297186
ver_maj: 3
ver_min: 2
ver_patch: 45
ver_pre: ''
dirty: false
debug: false
Operating System: 4.18.0-513.9.1.el8_9.x86_64