MatthiasDrexler commented on issue #10068: URL: https://github.com/apache/cloudstack/issues/10068#issuecomment-2528764201
> > Thanks for your help. I do not quite understand, why it's working now. The only difference is, that I now did not reboot between executing `cloudstack-setup-databases` and `cloudstack-setup-management`. I did reboot for creating "clean" snapshots the previous times. > > @MatthiasDrexler good to know it is working. from my experience, reboot is not necessary, but it should not cause the issue. I went back to the snapshot and tried to find my problem: I installed mysql on the same node. `cloudstack-setup-databases` sets the local ip (192.168.60.57) as cluster ip. If I run `cloudstack-setup-management` in this case, the application cannot connect to the database (error 503). If I alter the cluster ip and restart the cloudstack-management systemd service, the version table does not look like before:  The time it was working, I adjusted the cluster ip before running `cloudstack-setup-management`, which seems crucial for me (and in all my previous tries, it seems that I did that after running the application). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
