I deployed OpenNebula in VMware using Docker Compose. After I finish configuring passwordless SSH, OpenNebula cannot function properly. When I try to login the front-end, there is the error message “OpenNebula is not running or there was a server exception. Please check the server logs.”
I check “docker ps” and find that “opennebula-opennebula-mysql-1” is “unhealthy” status. Then I check the logs of “opennebula-opennebula-mysql-1”. It is in a loop that “mysqld” is entered and is stopped.
Versions of the related components and OS (frontend, hypervisors, VMs):
OS: CentOS-7
Opennebula Version: 6.0
Log for mysql:
2023-10-21 08:14:42 [BOOTSTRAP] 4b148d41c460: FRONTEND: Bootstrap service finished (entered infinity sleep)
2023-10-21 08:14:44,729 INFO spawned: ‘mysqld-upgrade’ with pid 667
2023-10-21 08:14:47,815 INFO success: mysqld entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2023-10-21 08:14:49,863 INFO success: mysqld-upgrade entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2023-10-21 08:14:54,708 INFO spawned: ‘mysqld-configure’ with pid 689
2023-10-21 08:15:00,354 INFO success: mysqld-configure entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2023-10-21 08:15:11,037 INFO exited: mysqld (exit status 1; not expected)
2023-10-21 08:15:11,039 INFO spawned: ‘mysqld’ with pid 813
2023-10-21 08:15:12,037 INFO waiting for mysqld-upgrade to stop
2023-10-21 08:15:12,042 INFO stopped: mysqld-upgrade (terminated by SIGTERM)
2023-10-21 08:15:12,550 INFO waiting for mysqld-configure to stop
2023-10-21 08:15:12,553 INFO stopped: mysqld-configure (terminated by SIGTERM)
2023-10-21 08:15:12,778 INFO spawned: ‘mysqld-upgrade’ with pid 899
2023-10-21 08:15:16,796 INFO success: mysqld entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2023-10-21 08:15:17,797 INFO success: mysqld-upgrade entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2023-10-21 08:15:18,008 INFO spawned: ‘mysqld-configure’ with pid 916
2023-10-21 08:15:23,072 INFO success: mysqld-configure entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2023-10-21 08:15:26,915 INFO exited: mysqld (exit status 1; not expected)
2023-10-21 08:15:27,918 INFO spawned: ‘mysqld’ with pid 1003
2023-10-21 08:15:28,447 INFO waiting for mysqld-upgrade to stop
2023-10-21 08:15:28,449 INFO stopped: mysqld-upgrade (terminated by SIGTERM)
2023-10-21 08:15:28,991 INFO waiting for mysqld-configure to stop
2023-10-21 08:15:28,991 INFO stopped: mysqld-configure (terminated by SIGTERM)
2023-10-21 08:15:29,212 INFO spawned: ‘mysqld-upgrade’ with pid 1089
2023-10-21 08:15:33,232 INFO success: mysqld entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2023-10-21 08:15:34,234 INFO success: mysqld-upgrade entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2023-10-21 08:15:34,527 INFO spawned: ‘mysqld-configure’ with pid 1106
2023-10-21 08:15:40,176 INFO success: mysqld-configure entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2023-10-21 08:15:42,210 INFO exited: mysqld (exit status 1; not expected)
2023-10-21 08:15:43,212 INFO spawned: ‘mysqld’ with pid 1190
2023-10-21 08:15:43,728 INFO waiting for mysqld-upgrade to stop
2023-10-21 08:15:43,729 INFO stopped: mysqld-upgrade (terminated by SIGTERM)
2023-10-21 08:15:44,116 INFO waiting for mysqld-configure to stop
2023-10-21 08:15:44,116 INFO stopped: mysqld-configure (terminated by SIGTERM)
2023-10-21 08:15:44,357 INFO spawned: ‘mysqld-upgrade’ with pid 1276
2023-10-21 08:15:48,408 INFO success: mysqld entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)