Skip to content

Bug: UI fails with 503 just after a successful install #8218

Closed
Closed
Bug: UI fails with 503 just after a successful install#8218
Labels
distro:ubuntustatus:not-a-bug
Milestone
4.19.0.0

Description

@tampler
tampler
opened on Nov 10, 2023
ISSUE TYPE
  • Bug Report
COMPONENT NAME
Setup, UI
CLOUDSTACK VERSION
4.19.0.0-snapshot.20231106
CONFIGURATION

Initial setup of management and KVM server on a single host

Possibly related to #7358

OS / ENVIRONMENT

Ubuntu 22.04.3
Java: openjdk 11.0.20.1 2023-08-24
MySQL: 8.0.35-0ubuntu0.22.04.1

SUMMARY

2023-11-10 13:45:27,306 ERROR [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:null) (logid:) Failed to load module [redfish] due to: [Error creating bean with name 'org.spr
ingframework.beans.factory.config.PropertyPlaceholderConfigurer#0' defined in URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.19.0.0-snapshot.20231106.jar!/M
ETA-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]: Cannot resolve reference to bean 'DefaultConfigResources' while setting bean property 'locations'; ne
sted exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'DefaultConfigResources' available].
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0' defined in
URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.19.0.0-snapshot.20231106.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]: Cannot
resolve reference to bean 'DefaultConfigResources' while setting bean property 'locations'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionExcept
ion: No bean named 'DefaultConfigResources' available

STEPS TO REPRODUCE
1. Install management and agent servers on a local host
2. Validate systemctl services:

> systemctl status cloudstack-management.service
● cloudstack-management.service - CloudStack Management Server
     Loaded: loaded (/lib/systemd/system/cloudstack-management.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2023-11-10 13:44:10 UTC; 19min ago

> systemctl status cloudstack-agent.service
● cloudstack-agent.service - CloudStack Agent
     Loaded: loaded (/lib/systemd/system/cloudstack-agent.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2023-11-10 13:44:12 UTC; 19min ago

3. Check UI:
admin@acs:~$ curl -I localhost:8080/client/
HTTP/1.1 503 Service Unavailable
EXPECTED RESULTS
UI starts on the management server host
ACTUAL RESULTS
UI fails with 503 due to the bean error

Activity

  1. tampler commented on Nov 10, 2023

    @tampler
    tampler
    on Nov 10, 2023
    Author

    As a possible fix, SO says it's needed to create a new directory resources

  2. weizhouapache commented on Nov 10, 2023

    @weizhouapache
    weizhouapache
    on Nov 10, 2023
    Member
    1. are the jar files in /usr/share/cloudstack-management/lib/ correct ? better to upload the list.
    2. does the user "admin" have root previledge ?

  3. tampler commented on Nov 10, 2023

    @tampler
    tampler
    on Nov 10, 2023
    Author

    Hello Wei

    1. Here's my list:
    admin@acs:~$ ls /usr/share/cloudstack-management/lib/
bcpkix-jdk15on-1.70.jar  cloud-plugin-storage-volume-linstor-4.19.0.0-snapshot.20231106.jar   mysql-connector-java-8.0.19.jar
bcprov-jdk15on-1.70.jar  cloud-plugin-storage-volume-storpool-4.19.0.0-snapshot.20231106.jar
bctls-jdk15on-1.70.jar   cloudstack-4.19.0.0-snapshot.20231106.jar
    1. Yes, "admin" is in a sudoers list, if you mean that
    2. Java
    admin@acs:~$ java --version
openjdk 11.0.20.1 2023-08-24
OpenJDK Runtime Environment (build 11.0.20.1+1-post-Ubuntu-0ubuntu122.04)

  4. tampler commented on Nov 10, 2023

    @tampler
    tampler
    on Nov 10, 2023
    Author
         at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)                                                                         [42/504]
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)                                                                               
        at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)                                                                            
        at org.eclipse.jetty.server.Server.start(Server.java:423)                                                                                                            
        at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)                                                                          
        at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)                                        
        at org.eclipse.jetty.server.Server.doStart(Server.java:387)                                                                                                          
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)         
        at org.apache.cloudstack.ServerDaemon.start(ServerDaemon.java:193)                                                                                                   
        at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:108)                                                                                                    
Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'DefaultConfigResources' available
        at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanDefinition(DefaultListableBeanFactory.java:874)
        at org.springframework.beans.factory.support.AbstractBeanFactory.getMergedLocalBeanDefinition(AbstractBeanFactory.java:1358)
        at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:309)
        ... 57 more                                                                                                                                                          
2023-11-10 13:45:27,322 DEBUG [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:null) (logid:) Trying to obtain module [bootstrap] context.
2023-11-10 13:45:27,322 ERROR [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:null) (logid:) Failed to start module [bootstrap] due to: [No bean named 'moduleStartup' avail
able].                                                                                                                                                                       
org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'moduleStartup' available
        at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanDefinition(DefaultListableBeanFactory.java:874)
        at org.springframework.beans.factory.support.AbstractBeanFactory.getMergedLocalBeanDefinition(AbstractBeanFactory.java:1358)
        at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:309)
        at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:283)
  5. DaanHoogland
    added this to the 4.19.0.0 milestone on Nov 10, 2023
  6. DaanHoogland
    added
    distro:ubuntu
    on Nov 10, 2023
  7. tampler
    changed the title [-]BUG: Management UI [/-] [+]Bug: UI fails with 503 just after a successful install[/+] on Nov 10, 2023

  8. tampler commented on Nov 13, 2023

    @tampler
    tampler
    on Nov 13, 2023
    Author

    The issue is bigger here since I don't see any post-installation activities, including a lower than usual memory footprint and not writing to a management operation log file.

  9. weizhouapache commented on Nov 13, 2023

    @weizhouapache
    weizhouapache
    on Nov 13, 2023
    Member

    @tampler
    I am able to reproduce the same issue on ubuntu22
    https://download.cloudstack.org/testing/nightly/latest/debian/4.19/

  10. GutoVeronezi commented on Nov 13, 2023

    @GutoVeronezi
    GutoVeronezi
    on Nov 13, 2023
    Contributor

    @tampler could you send us the full logs?

  11. tampler commented on Nov 13, 2023

    @tampler
    tampler
    on Nov 13, 2023
    Author

    Would this be enough? 🤔
    Otherwise let me know. I'll restart the installation on my VM and provide larger logs
    BTW, I experience the same issue with 4.18.2.0 nightly.

  12. weizhouapache commented on Nov 13, 2023

    @weizhouapache
    weizhouapache
    on Nov 13, 2023
    Member

    @tampler
    I have closed the PR #8229 which might be unnessary.

    I fixed the issue by

    • install mysql-server
    • setup cloudstack database by cloudstack-setup-databases

  13. GutoVeronezi commented on Nov 13, 2023

    @GutoVeronezi
    GutoVeronezi
    on Nov 13, 2023
    Contributor

    Would this be enough? 🤔 Otherwise let me know. I'll restart the installation on my VM and provide bigger logs BTW, I experience the same issue with 4.18.2.0 nightly.

    The full logs would be necessary for this troubleshooting, as the message Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'DefaultConfigResources' available seems just an indication of a previous error.

  14. tampler commented on Nov 13, 2023

    @tampler
    tampler
    on Nov 13, 2023
    Author

    @tampler I have closed the PR #8229 which might be unnessary.

    I fixed the issue by

    * install mysql-server

* setup cloudstack database by `cloudstack-setup-databases`

    You don't wanna have a local MySQL server for prod deployments

    I use cloudstack-setup-databases cloud:cloud@mysql --deploy-as=root -i 192.168.0.20 following this working tutorial. It would be fair to reproduce following that article

  15. weizhouapache commented on Nov 14, 2023

    @weizhouapache
    weizhouapache
    on Nov 14, 2023
    Member

    @tampler I have closed the PR #8229 which might be unnessary.
    I fixed the issue by

    * install mysql-server

* setup cloudstack database by `cloudstack-setup-databases`

    You don't wanna have a local MySQL server for prod deployments

    I use cloudstack-setup-databases cloud:cloud@mysql --deploy-as=root -i 192.168.0.20 following this working tutorial. It would be fair to reproduce following that article

    @tampler
    I guess the startup process might depend on some records in database, so we need to setup database correctly.
    The database can be local or remote, both are supported.

    can you please setup a local/remote database and retry ?

  16. 38 remaining items

  17. WowYouCanReallyDance commented on Feb 7, 2024

    @WowYouCanReallyDance
    WowYouCanReallyDance
    on Feb 7, 2024

    I use mariadb@10.6.5 and reproduced this problem.

    @WowYouCanReallyDance can you use root user to setup the database ?

    I am now deploying again, this is logs:

    2024-02-07 06:19:23,459 DEBUG [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:null) (logid:) Trying to obtain module [redfish] context.
2024-02-07 06:19:23,459 DEBUG [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:null) (logid:) Trying to load module [redfish] context.
2024-02-07 06:19:23,459 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:null) (logid:) Loading module context [redfish] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.19.0.0.jar!/META-INF/cloudstack/redfish/spring-redfish-context.xml]
2024-02-07 06:19:23,459 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:null) (logid:) Loading module context [redfish] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.19.0.0.jar!/META-INF/cloudstack/outofbandmanagement/spring-core-lifecycle-outofbandmanagement-context-inheritable.xml]
2024-02-07 06:19:23,459 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:null) (logid:) Loading module context [redfish] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.19.0.0.jar!/META-INF/cloudstack/core/spring-core-lifecycle-core-context-inheritable.xml]
2024-02-07 06:19:23,459 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:null) (logid:) Loading module context [redfish] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.19.0.0.jar!/META-INF/cloudstack/system/spring-core-system-context-inheritable.xml]
2024-02-07 06:19:23,460 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:null) (logid:) Loading module context [redfish] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.19.0.0.jar!/META-INF/cloudstack/system/spring-framework-config-system-context-inheritable.xml]
2024-02-07 06:19:23,460 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:null) (logid:) Loading module context [redfish] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.19.0.0.jar!/META-INF/cloudstack/system/spring-contrail-system-context-inheritable.xml]
2024-02-07 06:19:23,460 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:null) (logid:) Loading module context [redfish] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.19.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
2024-02-07 06:19:23,481 WARN  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:null) (logid:) Failed to start module [redfish] due to: [Error creating bean with name 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0' defined in URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.19.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]: Cannot resolve reference to bean 'DefaultConfigResources' while setting bean property 'locations'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'DefaultConfigResources' available].
2024-02-07 06:19:23,481 DEBUG [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:null) (logid:) module start failure of module [redfish] was due to:
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0' defined in URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.19.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]: Cannot resolve reference to bean 'DefaultConfigResources' while setting bean property 'locations'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'DefaultConfigResources' available
	at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:342)
	at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:113)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1707)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1452)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:619)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:542)
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335)
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234)
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:333)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:213)
	at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:171)
	at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:748)
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:564)
	at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:171)
	at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$2.with(DefaultModuleDefinitionSet.java:140)
	at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:271)
	at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:276)
	at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:276)
	at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:276)
	at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:276)
	at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:259)
	at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContexts(DefaultModuleDefinitionSet.java:128)
	at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.load(DefaultModuleDefinitionSet.java:78)
	at org.apache.cloudstack.spring.module.factory.ModuleBasedContextFactory.loadModules(ModuleBasedContextFactory.java:37)
	at org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.init(CloudStackSpringContext.java:70)
	at org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.<init>(CloudStackSpringContext.java:57)
	at org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.<init>(CloudStackSpringContext.java:61)
	at org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener.contextInitialized(CloudStackContextLoaderListener.java:52)
	at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:1073)
	at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:572)
	at org.eclipse.jetty.server.handler.ContextHandler.contextInitialized(ContextHandler.java:1002)
	at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:765)
	at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:379)
	at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1449)
	at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1414)
	at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:916)
	at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:288)
	at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:524)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
	at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
	at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
	at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
	at org.eclipse.jetty.server.handler.gzip.GzipHandler.doStart(GzipHandler.java:426)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
	at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
	at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117)
	at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
	at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
	at org.eclipse.jetty.server.Server.start(Server.java:423)
	at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
	at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
	at org.eclipse.jetty.server.Server.doStart(Server.java:387)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
	at org.apache.cloudstack.ServerDaemon.start(ServerDaemon.java:199)
	at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:112)
Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'DefaultConfigResources' available
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanDefinition(DefaultListableBeanFactory.java:874)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getMergedLocalBeanDefinition(AbstractBeanFactory.java:1358)
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:309)
	... 57 more
2024-02-07 06:19:23,481 DEBUG [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:null) (logid:) Trying to obtain module [bootstrap] context.
2024-02-07 06:19:23,481 DEBUG [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:null) (logid:) Could not get module [bootstrap] context bean.
2024-02-07 06:19:23,481 DEBUG [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:null) (logid:) Trying to obtain module [system] context.
2024-02-07 06:19:23,481 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:null) (logid:) Starting module [system].
2024-02-07 06:19:23,481 INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) (logid:) Starting CloudStack Components
2024-02-07 06:19:23,483 INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) (logid:) Done Starting CloudStack Components
2024-02-07 06:19:23,483 DEBUG [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:null) (logid:) Trying to obtain module [core] context.

  18. WowYouCanReallyDance commented on Feb 7, 2024

    @WowYouCanReallyDance
    WowYouCanReallyDance
    on Feb 7, 2024

    I'v deployed many times. And the strange thing is : it's not runned broken all the time. Sometimes it worked well.

  19. weizhouapache commented on Feb 7, 2024

    @weizhouapache
    weizhouapache
    on Feb 7, 2024
    Member

    I'v deployed many times. And the strange thing is : it's not runned broken all the time. Sometimes it worked well.

    @WowYouCanReallyDance
    the root cause could be the database (connection issue, or misconfiguration).
    can you restart mgmt server and share the new logs ?

  20. WowYouCanReallyDance commented on Feb 7, 2024

    @WowYouCanReallyDance
    WowYouCanReallyDance
    on Feb 7, 2024

    I'v deployed many times. And the strange thing is : it's not runned broken all the time. Sometimes it worked well.

    @WowYouCanReallyDance the root cause could be the database (connection issue, or misconfiguration). can you restart mgmt server and share the new logs ?

    I don't know why, but it's working nice now. The same DB type and version mysql:5.7, nothing changed since last time. If you need the logs, I will provide to timely.

  21. weizhouapache commented on Feb 8, 2024

    @weizhouapache
    weizhouapache
    on Feb 8, 2024
    Member

    I'v deployed many times. And the strange thing is : it's not runned broken all the time. Sometimes it worked well.

    @WowYouCanReallyDance the root cause could be the database (connection issue, or misconfiguration). can you restart mgmt server and share the new logs ?

    I don't know why, but it's working nice now. The same DB type and version mysql:5.7, nothing changed since last time. If you need the logs, I will provide to timely.

    @WowYouCanReallyDance
    did you make some changes on the database ?

  22. WowYouCanReallyDance commented on Feb 9, 2024

    @WowYouCanReallyDance
    WowYouCanReallyDance
    on Feb 9, 2024

    I'v deployed many times. And the strange thing is : it's not runned broken all the time. Sometimes it worked well.

    @WowYouCanReallyDance the root cause could be the database (connection issue, or misconfiguration). can you restart mgmt server and share the new logs ?

    I don't know why, but it's working nice now. The same DB type and version mysql:5.7, nothing changed since last time. If you need the logs, I will provide to timely.

    @WowYouCanReallyDance

    did you make some changes on the database ?

    No. I use the database on containers by podman. Everytime I drop it and run again to take a start with totally same steps. Then I would runcloudstack-setup-database… and cloudstack-setup-management.

  23. adietrich-ussignal commented on Mar 6, 2024

    @adietrich-ussignal
    adietrich-ussignal
    on Mar 6, 2024

    @tampler I am experiencing a similar issue, but re-running the database setup procedure does not appear to resolve the issue. When the management-server loads, it fails to load nearly every module, however, no notable SQL errors appear in the logs for the install.

  24. adietrich-ussignal commented on Mar 6, 2024

    @adietrich-ussignal
    adietrich-ussignal
    on Mar 6, 2024

    Not sure if this is related, but I found that in setting up the db.properties file, the cluster.node.IP was getting set to 127.0.1.1, which, is not configured on any of the virtual machine interfaces on my single-node. Changing this to the VM's proper loopback, (in this case 127.0.0.1), resolved my issue with the 503.

  25. weizhouapache
    added
    status:not-a-bug
    on Mar 7, 2024

  26. rightkick commented on Apr 22, 2024

    @rightkick
    rightkick
    on Apr 22, 2024

    I confirm that after setting the cluster.node.IP at /etc/cloudstack/management/db.properties to be the VM IP where ACS is installed, and restarting cloudstack-management.service I got the login prompt.

  27. nizigama commented on Jun 11, 2024

    @nizigama
    nizigama
    on Jun 11, 2024

    Not sure if this is related, but I found that in setting up the db.properties file, the cluster.node.IP was getting set to 127.0.1.1, which, is not configured on any of the virtual machine interfaces on my single-node. Changing this to the VM's proper loopback, (in this case 127.0.0.1), resolved my issue with the 503.

    updating 127.0.1.1 to 127.0.0.1 in /etc/cloudstack/management/db.properties fixed the issue for me

  28. dataseeek commented on Jul 17, 2024

    @dataseeek
    dataseeek
    on Jul 17, 2024

    I confirm changing cluster.node.IP=127.0.0.1 on /etc/cloudstack/management/db.properties worked for me as well.

  29. gobiursus commented on Oct 17, 2024

    @gobiursus
    gobiursus
    on Oct 17, 2024

    I have same issue, change to 127.0.0.1 doesn't fix it.

  30. apraba05 commented on Jun 3, 2025

    @apraba05
    apraba05
    on Jun 3, 2025

    Still having the same issue even after using 127.0.0.1

  31. nischalnischal2020 commented on Sep 29, 2025

    @nischalnischal2020
    nischalnischal2020
    on Sep 29, 2025

    I am a little late but I had to add this,

    My hosts file or DNS entry was pointing to a different IP in the system and so I got this error, I took the easier way and fixed my DNS entry to a proper IP and then
    cloudstack-setup-database…
    and
    cloudstack-setup-management

    and the UI came up

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    distro:ubuntustatus:not-a-bug

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions