Persistent HTTP 503 Error After System Reboot – CloudStack Management Service Fails to Start Properly

[neuratech80]

Good morning, community.

I’ve been facing a recurring issue for quite some time. Almost every time I shut down or restart my server — even with CloudStack fully configured and previously running without issues — I encounter the following error when trying to access the management interface:

HTTP ERROR 503 – Service Unavailable

Even after restarting the CloudStack Management Server service, the problem persists. I’ve verified that the service appears to start, but the web interface remains unavailable.

I would really appreciate any guidance or troubleshooting steps to help resolve this persistent issue.

Thanks in advance for your support.

[rajujith]

@neuratech80 restart the management service and look for ERROR in the logs during the application bootstrap. https://docs.cloudstack.apache.org/en/latest/adminguide/troubleshooting.html

[neuratech80]

I restarted the management service and checked the logs using the following command:

grep -i -E 'exception|unable|fail|invalid|leak|warn|error' /var/log/cloudstack/management/management-server.log

However, it only displays yesterday's logs and does not show any entries from today.

[DaanHoogland]

@neuratech80 did the log not rotate? (it should have)
look at the poutput of systemctl status cloudstack-management at the contents on /var/log/cloudstack/management/management-server.out and /var/log/cloudstack/management/setupManagement.log