"Internal error" after migration from Sqlite to MySQL (error 1046 : No database selected)

Community Support
1

After migration from sqlite to MySQL (Galera MariaDB cluster behind Maxscale, actually), I get in the Sunstone UI [HostPoolInfo] Internal error and [GroupPoolInfo] Internal error popups when viewing the Dashboard.

oned.log states:

Thu Feb 23 14:05:53 2017 [Z0][ReM][D]: Req:1984 UID:0 VirtualMachinePoolAccounting invoked , -2, 1487250353, -1
Thu Feb 23 14:05:53 2017 [Z0][ONE][E]: SQL command was: SELECT body FROM host_pool ORDER BY oid, error 1046 : No database selected
Thu Feb 23 14:05:53 2017 [Z0][ReM][E]: Req:928 UID:0 HostPoolInfo result FAILURE [HostPoolInfo] Internal error
[…]
Thu Feb 23 14:05:53 2017 [Z0][ReM][D]: Req:7760 UID:0 GroupPoolInfo invoked 
Thu Feb 23 14:05:53 2017 [Z0][ONE][E]: SQL command was: SELECT group_pool.body, group_quotas.body FROM group_pool LEFT JOIN group_quotas ON group_pool.oid=group_quotas.group_oid ORDER BY oid, error 1046 : No database selected
Thu Feb 23 14:05:53 2017 [Z0][ReM][E]: Req:7760 UID:0 GroupPoolInfo result FAILURE [GroupPoolInfo] Internal error

Migration was done according to https://docs.opennebula.org/5.2/deployment/references/onedb.html#onedb-sqlite2mysql, i. e.:

systemctl stop opennebula.service 
vi /etc/one/oned.conf 
oned -i
onedb sqlite2mysql --verbose --sqlite one.db --server 10.11.12.13 -d opennebula -u oneadmin -p pasword
systemctl start opennebula.service

System: Ubuntu 16.04, opennebula 5.2.1 packages from downloads.opennebula.org

Everything else seems to work fine, thus I wonder if it’s a bug or a local issue? Not selecting a DB sounds a bit odd for being a migration issue though.

2

Can you stop opennebula and make sure that ps -ef | grep oned does not return any process? It could be a rogue oned botching the DB connection.

If it’s not that, does grep ^DB /var/lib/one/config return the proper database connection settings?

3

I rebooted the VM on Monday and just noted earlier today that I wasn’t getting the error messages for a while. So, yes, I must have forgotten to restart a service or two after changing the DB from SQlite to MySQL.