GitHub user dR3b added a comment to the discussion: [HTTP ERROR 503 Service
Unavailable]
Yes that's right.
Jepp, that's certainly rare.
GitHub link:
https://github.com/apache/cloudstack/discussions/11534#discussioncomment-14282936
This is an automatically sent email
GitHub user kenneth0595 added a comment to the discussion: [HTTP ERROR 503
Service Unavailable]
Yes I did resolve the issue.
On Mon, Sep 1, 2025 at 23:44 dahn ***@***.***> wrote:
> So your issue is resolved now, @kenneth0595
> <https://github.com/kenneth0595> ?
>
> —
GitHub user weizhouapache closed the discussion with a comment: [HTTP ERROR 503
Service Unavailable]
closing this ticket, as @kenneth0595 and @dR3b have fixed their issues.
GitHub link:
https://github.com/apache/cloudstack/discussions/11534#discussioncomment-14284322
This is an
GitHub user dR3b edited a comment on the discussion: [HTTP ERROR 503 Service
Unavailable]
@DaanHoogland I don't use selinux and the user was `root`.
I think the question is: When is this file [1] created? After the package
installation, or after configuring and deploying a zone? I didn
GitHub user DaanHoogland closed the discussion with a comment: [HTTP ERROR 503
Service Unavailable]
I am still trying to @dR3b ’s scenario and will create an issue from the
comments if I can reproduce. but, yes, we can close.
GitHub link:
https://github.com/apache/cloudstack/discussions
GitHub user dR3b closed the discussion with a comment: [HTTP ERROR 503 Service
Unavailable]
Thanks for the information and your time!
GitHub link:
https://github.com/apache/cloudstack/discussions/11534#discussioncomment-14286063
This is an automatically sent email for users
GitHub user DaanHoogland closed the discussion with a comment: [HTTP ERROR 503
Service Unavailable]
I replayed the scenario as we described it @dR3b , but there must be an extra
factor. The upgrade went smoothly without any errors.
GitHub link:
https://github.com/apache/cloudstack
GitHub user kenneth0595 closed a discussion: [HTTP ERROR 503 Service
Unavailable]
### problem
I upgraded CloudStack from version 4.20.1 to 4.21.0, and when I tried to access
the portal, I encountered a 503 error.
I just checked log from managent server log.
The error log shown as below
GitHub user DaanHoogland added a comment to the discussion: [HTTP ERROR 503
Service Unavailable]
and when on 4.20 you just started the MS without creating a zone, right?
This is not a usual scenario, but seems like it should work.
GitHub link:
https://github.com/apache/cloudstack
GitHub user DaanHoogland added a comment to the discussion: [HTTP ERROR 503
Service Unavailable]
that is a very interesting question @dR3b . do you have selinux configured?
Usually this works out of the box, but for security it might not be allowed.
Or maybe you did (part of) the
GitHub user dR3b added a comment to the discussion: [HTTP ERROR 503 Service
Unavailable]
* install 4.20
* start the management server -> `ok`
* install 4.21
* start the management server -> `error`
GitHub link:
https://github.com/apache/cloudstack/discussions/11534#discussioncomment-14
GitHub user DaanHoogland added a comment to the discussion: [HTTP ERROR 503
Service Unavailable]
So your issue is resolved now, @kenneth0595 ?
GitHub link:
https://github.com/apache/cloudstack/discussions/11534#discussioncomment-14277039
This is an automatically sent email for users
GitHub user DaanHoogland added a comment to the discussion: [HTTP ERROR 503
Service Unavailable]
@dR3b , so your scenario was
- install version 1
- install version 2
- start the management server
- problem...
right?
GitHub link:
https://github.com/apache/cloudstack/discussions/11534
GitHub user DaanHoogland edited a comment on the discussion: [HTTP ERROR 503
Service Unavailable]
@dR3b , so your scenario was
- install version 1
- install version 2
- start the management server
- problem…
right?
GitHub link:
https://github.com/apache/cloudstack/discussions/11534
GitHub user kenneth0595 added a comment to the discussion: [HTTP ERROR 503
Service Unavailable]
Hi!
This is Kenneth, who opened this case first.
In my case, there was a problem when upgrading the database table.
With the introduction of new Kubernetes feature updates, several additional
GitHub user dR3b edited a comment on the discussion: [HTTP ERROR 503 Service
Unavailable]
@DaanHoogland I don't use selinux and the user was `root`.
I think the question is: When is this file [1] created? After the package
installation, or after configuring and deploying a zone? I didn
GitHub user dR3b edited a comment on the discussion: [HTTP ERROR 503 Service
Unavailable]
@DaanHoogland I don't use selinux and the user was `root`.
I think the question is: When is this file [1] created? After the package
installation, or after configuring and deploying a zone? I didn
GitHub user dR3b added a comment to the discussion: [HTTP ERROR 503 Service
Unavailable]
@DaanHoogland I don't use selinux and the user was `root`.
I think the question is: When is this file [1] created? After the package
installation, or after configuring and deploying a zone? I didn
GitHub user kenneth0595 edited a comment on the discussion: [HTTP ERROR 503
Service Unavailable]
@weizhouapache
server.properties log shown below.
```
[root@Oracle-kvm-hypervisor-01 ~]# tail -n +379667
/var/log/cloudstack/management/management-server.log | grep -i Exception -A5
2025-08-29
GitHub user weizhouapache edited a comment on the discussion: [HTTP ERROR 503
Service Unavailable]
> @weizhouapache Here is my complete log file after updating to 4.21.0:
> [management-server.log](https://github.com/user-attachments/files/22066432/management-server.log)
>
found t
GitHub user dR3b edited a comment on the discussion: [HTTP ERROR 503 Service
Unavailable]
^^ This! Thanks! Its up and running. So is this a bug or did i miss something?
GitHub link:
https://github.com/apache/cloudstack/discussions/11534#discussioncomment-14269409
This is an
GitHub user dR3b added a comment to the discussion: [HTTP ERROR 503 Service
Unavailable]
^^ This! Thanks! Its up and running.
GitHub link:
https://github.com/apache/cloudstack/discussions/11534#discussioncomment-14269409
This is an automatically sent email for users
GitHub user weizhouapache added a comment to the discussion: [HTTP ERROR 503
Service Unavailable]
> @weizhouapache Here is my complete log file after updating to 4.21.0:
> [management-server.log](https://github.com/user-attachments/files/22066432/management-server.log)
>
found t
GitHub user dR3b added a comment to the discussion: [HTTP ERROR 503 Service
Unavailable]
@weizhouapache Here is my complete log file after updating to 4.21.0:
[management-server.log](https://github.com/user-attachments/files/22066432/management-server.log)
GitHub link:
https://github.com
GitHub user weizhouapache added a comment to the discussion: [HTTP ERROR 503
Service Unavailable]
> I have the same error. I installed version: `4.20.1.0` today without any
> modification. After that i made the upgrade to: `4.21.0.0`:
>
> ``` 2025-08-29 10:03
GitHub user dR3b added a comment to the discussion: [HTTP ERROR 503 Service
Unavailable]
I found this:
```
2025-08-29 13:34:33,221 INFO [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:[])
(logid:) configuring bean NetworkServiceMapDaoImpl.
2025-08-29 13:34:33,222 INFO
GitHub user dR3b added a comment to the discussion: [HTTP ERROR 503 Service
Unavailable]
I have the same error. I installed version: `4.20.1.0` today without any
modification. After that i made the upgrade to: `4.21.0.0`:
``` 2025-08-29 10:03:41,882 WARN [c.c.u.d.T.Transaction] (main
GitHub user dR3b deleted a comment on the discussion: [HTTP ERROR 503 Service
Unavailable]
I have the same error. I installed version: `4.20.1.0` today without any
modification. After that i made the upgrade to: `4.21.0.0`:
``` 2025-08-29 10:03:41,882 WARN [c.c.u.d.T.Transaction] (main
GitHub user dR3b added a comment to the discussion: [HTTP ERROR 503 Service
Unavailable]
I have the same error. I installed version: `4.20.1.0` today without any
modification. After that i made the upgrade to: `4.21.0.0`:
``` 2025-08-29 10:03:41,882 WARN [c.c.u.d.T.Transaction] (main
GitHub user weizhouapache added a comment to the discussion: [HTTP ERROR 503
Service Unavailable]
@kenneth0595
it appears to be a DB configuration issue
GitHub link:
https://github.com/apache/cloudstack/discussions/11534#discussioncomment-14253395
This is an automatically sent email
GitHub user weizhouapache added a comment to the discussion: [HTTP ERROR 503
Service Unavailable]
@kenneth0595
can you search for the last "server.properties" in the log, then search for
"Exception" after the position ?
GitHub link:
https://github.com/apache/cloudsta
GitHub user kenneth0595 created a discussion: [HTTP ERROR 503 Service
Unavailable]
### problem
I upgraded CloudStack from version 4.20.1 to 4.21.0, and when I tried to access
the portal, I encountered a 503 error.
I just checked log from managent server log.
The error log shown as below
GitHub user kenneth0595 added a comment to the discussion: [HTTP ERROR 503
Service Unavailable]
@weizhouapache
server.properties log shown below.
[root@Oracle-kvm-hypervisor-01 ~]# tail -n +379667
/var/log/cloudstack/management/management-server.log | grep -i Exception -A5
2025-08-29 16:05
GitHub user VJayMeyer edited a comment on the discussion: HTTP ERROR 503
Service Unavailable
I have seen this issue during CloudStack deployment. Check your cluster.node.ip
(sudo cat /etc/cloudstack/management/db.properties) value. If its set to the
loopback or a strange IP it can cause
GitHub user VJayMeyer closed the discussion with a comment: HTTP ERROR 503
Service Unavailable
I have seen this issue during CloudStack deployment. Check your cluster.node.ip
(sudo cat /etc/cloudstack/management/db.properties) value. If its set to the
loopback or a strange IP it can cause
GitHub user Chih80 closed the discussion with a comment: HTTP ERROR 503 Service
Unavailable
I also created an issue about this #10960 where I pasted more logs.
GitHub link:
https://github.com/apache/cloudstack/discussions/9880#discussioncomment-13382607
This is an automatically sent
GitHub user Chih80 closed the discussion with a comment: HTTP ERROR 503 Service
Unavailable
After upgrading to 4.20 with java17
root@xx-mgm-01:/var/log/cloudstack/management# tail -f management-server.log
2025-06-05 04:24:49,634 DEBUG [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
(main
GitHub user Chih80 closed the discussion with a comment: HTTP ERROR 503 Service
Unavailable
sorry, I have no idea why it came out with different front size. I just copy
and paste.
GitHub link:
https://github.com/apache/cloudstack/discussions/9880#discussioncomment-13382485
This is an
GitHub user Chih80 closed the discussion with a comment: HTTP ERROR 503 Service
Unavailable
/etc/default/cloudstack-management:
# Licensed to the Apache Software Foundation (ASF) under one
# or more contributor license agreements. See the NOTICE file
# distributed with this work for
GitHub user weizhouapache closed the discussion with a comment: HTTP ERROR 503
Service Unavailable
> I encounter this problem upgrading from 4.19.1.1 to 4.20.0. After upgrade I
> tried to access UI but got the 503 error. After downgrading by selecting java
> 11, I was able to acce
GitHub user Chih80 closed the discussion with a comment: HTTP ERROR 503 Service
Unavailable
I encounter this problem upgrading from 4.19.1.1 to 4.20.0. After upgrade I
tried to access UI but got the 503 error. After downgrading by selecting java
11, I was able to access the UI again. I
GitHub user DaanHoogland closed the discussion with a comment: HTTP ERROR 503
Service Unavailable
closed this for lack of interaction, please reopen or open a new item if
applicable
GitHub link:
https://github.com/apache/cloudstack/discussions/9880#discussioncomment-12995033
This is
GitHub user gobiursus closed a discussion: HTTP ERROR 503 Service Unavailable
# ISSUE TYPE
* Bug Report
503 Unavailable after installation
# COMPONENT NAME
~~~
Management server
~~~
# CLOUDSTACK VERSION
~~~
4.19.1.2
~~~
# CONFIGURATION
# OS / ENVIRONMENT
Debian
GitHub user weizhouapache added a comment to the discussion: HTTP ERROR 503
Service Unavailable
>
> It worked for me as well but SSO via SAML is not working after the upgrade.
@Avneetdabas
Did you have the same issue with db.properties ?
Can you upgrade to 4.19.1.3 ?
GitHub link:
GitHub user Avneetdabas added a comment to the discussion: HTTP ERROR 503
Service Unavailable
> I have the same issue after upgrading from 4.19.0.0 to 4.19.1.2 on Ubuntu
> 22.04. MySQL and the management server are running on the same node. After
> the following steps, the managemen
GitHub user bwcxyk added a comment to the discussion: HTTP ERROR 503 Service
Unavailable
Detected local IP address as 127.0.1.1, That is in
`/etc/cloudstack/management/db.properties
GitHub user penguin2716 added a comment to the discussion: HTTP ERROR 503
Service Unavailable
It looks reasonable. I just confirmed that the management server starts without
503 error on Debian 12.8 / Java 11.0.25+9 (Temurin) / MariaDB 10.11.6.
GitHub link:
https://github.com/apache
GitHub user weizhouapache added a comment to the discussion: HTTP ERROR 503
Service Unavailable
@gobiursus @penguin2716
can we conclude that the issue is due to CloudStack 4.19.x is incompatible with
Java17 which is the default java version on debian12 ?
@purteppers
I cannot reproduce your
GitHub user penguin2716 added a comment to the discussion: HTTP ERROR 503
Service Unavailable
> the db.cloud.password and db.cloud.password are both decrypted as "password",
> are they correct ?
Yes, the db.cloud.password and db.usage.password is both set to "password&q
GitHub user weizhouapache added a comment to the discussion: HTTP ERROR 503
Service Unavailable
right. the doc needs to be fixed.
however, when you downgrade to java11, cloudstack should work well.
I was able to decrypt the values you pasted
```
$ sudo egrep 'secret|password' /etc/
GitHub user penguin2716 added a comment to the discussion: HTTP ERROR 503
Service Unavailable
@weizhouapache
> if you run with cloudstack 4.19 or prior, JAVA 17 is not supported.
> JAVA 17 is supported since 4.20
So the problem was that I followed the `latest` installation guide, whic
GitHub user weizhouapache added a comment to the discussion: HTTP ERROR 503
Service Unavailable
> Java 17 is the default version of Debian 12. Also the default database in
> Debian 12 is MariaDB not MySQL.
> […](#)
> On November 6, 2024 2:45:30 PM UTC, Wei Zhou ***@**
GitHub user gobiursus added a comment to the discussion: HTTP ERROR 503 Service
Unavailable
Java 17 is the default version of Debian 12.
Also the default database in Debian 12 is MariaDB not MySQL.
On November 6, 2024 2:45:30 PM UTC, Wei Zhou ***@***.***> wrote:
>@penguin2716
>i
GitHub user weizhouapache added a comment to the discussion: HTTP ERROR 503
Service Unavailable
When I run cloudstack-management 4.19.1.2 with java17, I got the following error
```
2024-11-06 14:47:42,582 WARN [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
(main:null) (logid:) Failed to start
GitHub user weizhouapache added a comment to the discussion: HTTP ERROR 503
Service Unavailable
@penguin2716
if you run with cloudstack 4.19 or prior, JAVA 17 is not supported.
JAVA 17 is supported since 4.20 (will be released in the coming weeks):
https://github.com/apache/cloudstack/pull
GitHub user penguin2716 added a comment to the discussion: HTTP ERROR 503
Service Unavailable
@weizhouapache
I just set up almost the same environment with a local VM, freshly installed
Ubuntu 22.04, Java 17, MySQL, and the management server. It has the same issue:
It works with Java 11 but
GitHub user weizhouapache added a comment to the discussion: HTTP ERROR 503
Service Unavailable
@penguin2716
can you share some lines in the backup file if the db key and db password is
not confidential ?
```
egrep 'secret|password' /etc/cloudstack/management/db.propertie
GitHub user penguin2716 added a comment to the discussion: HTTP ERROR 503
Service Unavailable
@weizhouapache
Yes, I still have the backup as `db.properties.bak`.
GitHub link:
https://github.com/apache/cloudstack/discussions/9880#discussioncomment-11161731
This is an automatically sent
GitHub user weizhouapache added a comment to the discussion: HTTP ERROR 503
Service Unavailable
> I have the same issue after upgrading from 4.19.0.0 to 4.19.1.2 on Ubuntu
> 22.04. MySQL and the management server are running on the same node. After
> the following steps, the m
GitHub user weizhouapache added a comment to the discussion: HTTP ERROR 503
Service Unavailable
ignore it, thanks anyway @purteppers
GitHub link:
https://github.com/apache/cloudstack/discussions/9880#discussioncomment-11123009
This is an automatically sent email for users
GitHub user weizhouapache added a comment to the discussion: HTTP ERROR 503
Service Unavailable
> I captured some extra stuff, I am not sure if they are related:
> ```
> ● cloudstack-management.service - CloudStack Management Server
> Loaded: loaded (/lib/systemd/syste
GitHub user purteppers added a comment to the discussion: HTTP ERROR 503
Service Unavailable
The management service is currently working with the password with '#' and no
encryption, so I'm not sure what changing the password will accomplish. Do you
want me revert back to
GitHub user weizhouapache added a comment to the discussion: HTTP ERROR 503
Service Unavailable
> Unfortunately since I was just testing the install I do not, I can run
> through the install again on a fresh Alma install if you want and provide the
> results.
Ok
Can you change the
GitHub user purteppers edited a comment on the discussion: HTTP ERROR 503
Service Unavailable
Interesting, this is the second time I've installed on Alma and I had the same
issue both times. The password doesn't matter since this is a test environment.
Here is the output from th
GitHub user purteppers added a comment to the discussion: HTTP ERROR 503
Service Unavailable
Unfortunately since I was just testing the install I do not, I can run through
the install again on a fresh Alma install if you want and provide the results.
GitHub link:
https://github.com/apache
GitHub user weizhouapache added a comment to the discussion: HTTP ERROR 503
Service Unavailable
> Interesting, this is the second time I've installed on Alma and I had the
> same issue both times. The password doesn't matter since this is a test
> environment. Here is
GitHub user purteppers edited a comment on the discussion: HTTP ERROR 503
Service Unavailable
Interesting, this is the second time I've installed on Alma and I had the same
issue both times. The password doesn't matter since this is a test environment.
Here is the output from th
GitHub user purteppers added a comment to the discussion: HTTP ERROR 503
Service Unavailable
Interesting, this is the second time I've installed on Alma and I had the same
issue both times. The password doesn't matter since this is a test environment.
Here is the output from th
GitHub user weizhouapache added a comment to the discussion: HTTP ERROR 503
Service Unavailable
> I installed MariaDB 10.11.6 from Debian 12 Stable repo byapt install
> mariadb-server
I tried mariadb 10 on debian12 and ubuntu 24, also mysql 8.0.x on alma9/rocky9,
no issues found
Pr
GitHub user weizhouapache added a comment to the discussion: HTTP ERROR 503
Service Unavailable
I have tested debian/ubuntu/alma/rocky with different versions, cannot
reproduce the issue unfortunately.
@purteppers
can you share the output of some commands ?
```
egrep 'secret|password&
GitHub user gobiursus added a comment to the discussion: HTTP ERROR 503 Service
Unavailable
I installed MariaDB 10.11.6 from Debian 12 Stable repo byapt install
mariadb-server
On Thursday, October 31, 2024 at 03:37:05 p.m. GMT, Wei Zhou ***@***.***>
wrote:
How did you inst
GitHub user weizhouapache edited a comment on the discussion: HTTP ERROR 503
Service Unavailable
I have tested debian/ubuntu/alma/rocky with different versions, cannot
reproduce the issue unfortunately.
@purteppers
can you share the output of some commands ?
```
egrep 'secret|pas
GitHub user weizhouapache added a comment to the discussion: HTTP ERROR 503
Service Unavailable
> How did you install your MySQL?Please don't use the MySQL from MySQL's
> official repo.
@gobiursus
I installed mysql 8.0.36 from the alma9/rocky9 official repo by
```
dnf
GitHub user gobiursus added a comment to the discussion: HTTP ERROR 503 Service
Unavailable
How did you install your MySQL?Please don't use the MySQL from MySQL's
official repo.
On Thursday, October 31, 2024 at 03:30:46 p.m. GMT, Wei Zhou ***@***.***>
wrote:
GitHub user purteppers edited a comment on the discussion: HTTP ERROR 503
Service Unavailable
I should clarify, my issue wasn't an upgrade. It was a fresh install following
the instructions here ->
https://docs.cloudstack.apache.org/en/latest/installguide/management-server/ .
I
GitHub user purteppers added a comment to the discussion: HTTP ERROR 503
Service Unavailable
I should clarify, my issue wasn't an upgrade. It was a fresh install following
the instructions here ->
https://docs.cloudstack.apache.org/en/latest/installguide/management-server/
Git
GitHub user weizhouapache added a comment to the discussion: HTTP ERROR 503
Service Unavailable
> I was having the exact same issue on AlmaLinux 9.3 and this resolved the
> problem as well.
@purteppers
do you use mysql 8.0 as well ?
GitHub link:
https://github.com/apache/clou
GitHub user gobiursus added a comment to the discussion: HTTP ERROR 503 Service
Unavailable
[Any paste ](https://pastebin.com/R3CT2v5Y)
GitHub link:
https://github.com/apache/cloudstack/discussions/9880#discussioncomment-11109386
This is an automatically sent email for users
GitHub user gobiursus added a comment to the discussion: HTTP ERROR 503 Service
Unavailable
How do I check the connection? How do I fix?
On October 18, 2024 8:35:27 AM UTC, Wei Zhou ***@***.***> wrote:
>@gobiursus
>from my experience, it is mostly caused by db misconfiguration.
GitHub user gobiursus added a comment to the discussion: HTTP ERROR 503 Service
Unavailable
I suggest we shouldn't use MySQL from its official repo, we should use MariaDB
from repo of Debian Stable.
On October 30, 2024 4:02:10 PM UTC, purteppers ***@***.***> wrote:
>> >
GitHub user weizhouapache added a comment to the discussion: HTTP ERROR 503
Service Unavailable
I tested upgrade on debian 12 and alma9 with mysql 8.0, both worked
GitHub link:
https://github.com/apache/cloudstack/discussions/9880#discussioncomment-11109437
This is an automatically
GitHub user weizhouapache added a comment to the discussion: HTTP ERROR 503
Service Unavailable
I did not find any valuable information in the log.
is there anything wrong in the db upgrade ? cc @gobiursus @purteppers
you can search "DatabaseUpgradeChecker" in the log
GitHub li
GitHub user purteppers added a comment to the discussion: HTTP ERROR 503
Service Unavailable
> > I was having the exact same issue on AlmaLinux 9.3 and this resolved the
> > problem as well.
>
> @purteppers do you use mysql 8.0 as well ?
Yes, specifically 8.0.36
G
GitHub user penguin2716 added a comment to the discussion: HTTP ERROR 503
Service Unavailable
I have the same issue after upgrading from 4.19.0.0 to 4.19.1.2 on Ubuntu
22.04. MySQL and the management server are running on the same node. After the
following steps, the management console works
GitHub user purteppers added a comment to the discussion: HTTP ERROR 503
Service Unavailable
> I have the same issue after upgrading from 4.19.0.0 to 4.19.1.2 on Ubuntu
> 22.04. MySQL and the management server are running on the same node. After
> the following steps, the managemen
GitHub user gobiursus added a comment to the discussion: HTTP ERROR 503 Service
Unavailable
There was no error during installation.
GitHub link:
https://github.com/apache/cloudstack/discussions/9880#discussioncomment-11109389
This is an automatically sent email for users
GitHub user gobiursus added a comment to the discussion: HTTP ERROR 503 Service
Unavailable
I captured some extra stuff, I am not sure if they are related:
```
● cloudstack-management.service - CloudStack Management Server
Loaded: loaded (/lib/systemd/system/cloudstack-management.service
GitHub user gobiursus added a comment to the discussion: HTTP ERROR 503 Service
Unavailable
<https://pastebin.com/R3CT2v5Y>
There you go
On October 18, 2024 7:58:39 PM UTC, Wei Zhou ***@***.***> wrote:
>> I captured some extra stuff, I am not sure if they are related:
>>
GitHub user gobiursus added a comment to the discussion: HTTP ERROR 503 Service
Unavailable
I loaded the full log earlier in the link.
On October 18, 2024 7:58:39 PM UTC, Wei Zhou ***@***.***> wrote:
>> I captured some extra stuff, I am not sure if they are related:
>> ```
GitHub user gobiursus added a comment to the discussion: HTTP ERROR 503 Service
Unavailable
```
# apt install mariadb-server-10.5 #I got the error of this issue on MariaDB
v10.11.16+Cloudstack on Noble, this time I am using v10.5 because I changed to
focal.
...
# apt install ./python3
GitHub user weizhouapache added a comment to the discussion: HTTP ERROR 503
Service Unavailable
can you search `Exception` in the management-server.log ?
GitHub link:
https://github.com/apache/cloudstack/discussions/9880#discussioncomment-11109384
This is an automatically sent email
GitHub user gobiursus added a comment to the discussion: HTTP ERROR 503 Service
Unavailable
```
# grep -i -E 'exception' /var/log/cloudstack/management/management-server.log
2024-10-17 21:32:20,090 WARN [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
(main:null) (logid:) Failed to st
GitHub user weizhouapache added a comment to the discussion: HTTP ERROR 503
Service Unavailable
@gobiursus
from my experience, it is mostly caused by db misconfiguration.
in short, the mgmt server cannot connect to the db
can you re-do all steps and share the output ?
GitHub link:
https
I stand corrected:
*HTTP ERROR 503 Service Unavailable* can also be returned *by the server*.
i.e., The server is "reachable" by the client. But the server is
experiencing some sort of failure.
HTH,
Eric Pretorious
Portland, Oregon
On Thu, Jun 4, 2020 at 10:31 PM Practical
Also:
*503 - Service Unavailable*
This signifies that the server is unavailable at the present moment,
usually due to maintenance or overloading. It is generally a temporary
issue and the user should try again later.
"Unavailable" means the server is "unreachable" by the client. This could
be the
169.254. x.x: This is what's called an Automatic Private *IP address*. An
IP in this range means that the computer cannot see the network. (A
computer using DHCP needs to have an external server tell it what *IP
address* to use.)
HTH,
Eric Pretorious,
Portland, Oregon
On Thu, Jun 4, 2020, 12:22 A
Hello,
I'm get Error 503 on management server. Following error is logged:
"Failed to configure ClusterManagerImpl"
Link local IP 169.254.0.1 is assigned on the same machine.
CS version 4.14
Any idea?
97 matches
Mail list logo
