Replies: 8 comments
-
please check the logs if there are some SQL exceptions or other exceptions |
Beta Was this translation helpful? Give feedback.
-
I am experiencing the same issue. I changed the Cluster IP on the db.properties of the files according to one of the previous tickets. This is from a fresh installation and I am getting a 503. |
Beta Was this translation helpful? Give feedback.
-
I had this same issue and was able to figure this out: Ran this command, restarted cloudstack-management and it works now: |
Beta Was this translation helpful? Give feedback.
-
@weizhouapache There is no "SQL"* error in the logs. However, I used this workaroudn:
|
Beta Was this translation helpful? Give feedback.
-
@MejdiB IMHO, it is a strange issue would it be possible to upload the log ? |
Beta Was this translation helpful? Give feedback.
-
@weizhouapache I try to shrink this, because this above error snippets is generated in a loop-like behaviour. |
Beta Was this translation helpful? Give feedback.
-
maybe just the lines between |
Beta Was this translation helpful? Give feedback.
-
@MejdiB Can you check if you are able to connect to the database from the new management server? It's hard to pin point the exact error without the complete logs. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
problem
When trying to add an additional management server without DB replication, the UI fails with
HTTP ERROR 503 Service Unavailable
due to the following Stack Trace:versions
Please note that this behaviour does not occur on ACS 4.17 (with exact same installation steps)
The steps to reproduce the bug
The db.properties file is setup up correctyl, also the correct organization IPv4 for the management server is derived with cloudstack-setup-databases
What to do about it?
Please provide a workaround and fix this issue
Beta Was this translation helpful? Give feedback.
All reactions