Stuck: Please wait while Bamboo sets up your database

Question

Run start-bamboo.bat, and got the following log. Then, stuck build database.

Could you please give your comemtns. ?

C:\Program Files\Bamboo\bin>start-bamboo.bat

To run Bamboo in the foreground, start the server with start-bamboo.bat /fg

Bamboo Data Center
Version : 9.0.1

JAVA_HOME "C:\Program Files\Java\jdk-11.0.2" contains spaces. Please change to a location without spaces if this causes problems.

If you encounter issues starting or stopping Bamboo Server, please see the Troubleshooting guide at https://confluence.atlassian.com/display/BAMBOO/Installing+Bamboo+on+Windows

Using CATALINA_BASE: "C:\Program Files\Bamboo"
Using CATALINA_HOME: "C:\Program Files\Bamboo"
Using CATALINA_TMPDIR: "C:\Program Files\Bamboo	emp"
Using JRE_HOME: "C:\Program Files\Java\jdk-11.0.2"
Using CLASSPATH: "C:\Program Files\Bamboo\bin\bootstrap.jar;C:\Program Files\Bamboo\bin	omcat-juli.jar"
Using CATALINA_OPTS: ""
C:\Program Files\Bamboo\bin>

NOTE: Picked up JDK_JAVA_OPTIONS: --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED
28-Nov-2022 17:56:55.279 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded Apache Tomcat Native library [1.2.35] using APR version [1.7.0].
28-Nov-2022 17:56:55.282 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true], UDS [true].
28-Nov-2022 17:56:55.282 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR/OpenSSL configuration: useAprConnector [false], useOpenSSL [true]
28-Nov-2022 17:56:55.290 INFO [main] org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL successfully initialized [OpenSSL 1.1.1q 5 Jul 2022]
28-Nov-2022 17:56:55.584 INFO [main] org.apache.coyote.http11.AbstractHttp11Protocol.configureUpgradeProtocol The ["http-nio-8085"] connector has been configured to support HTTP upgrade to [h2c]
28-Nov-2022 17:56:55.584 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8085"]
28-Nov-2022 17:56:55.609 INFO [main] org.apache.catalina.startup.Catalina.load Server initialization in [583] milliseconds
28-Nov-2022 17:56:55.648 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
28-Nov-2022 17:56:55.649 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/9.0.65]
28-Nov-2022 17:57:13.312 INFO [main] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
28-Nov-2022 17:57:22.356 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8085"]
28-Nov-2022 17:57:22.383 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in [26772] milliseconds

Jeremy Owen · Answer

We recently had a bug which caused failures when connecting to an unsupported database version to fail silently and present the endless spinner:

* BAM-22010: Bamboo setup on an unsupported database such as PostgreSQL 9 fails and does not communicate anything

It may be that. What version of PostgreSQL are you connecting to? Bamboo 9.0 supports PostgreSQL 11, 12, 13 and 14.

Nic Brough -Adaptavist- · Answer

Ok, that implies Bamboo has simply got stuck somewhere.  If it were your database settings, you would usually get a screen saying "can't access database" and an error message at the end of the log.

There's not much we can do without knowing what it is doing internally now, but if you were to stop it, give it a sec to shutdown properly, then restart it, you may get a different error message in the log, telling us what is broken (or it might just complete the job!)

Five Ten · Answer

There is no other log.  I don't if postgres configuration right or not