After upgrade bamboo stuck in redirect loop

memoryleak March 4, 2019

Upgrading Bamboo from 6.6 to 6.8, with following ocnfiguration for the connector (behind a SSL terminating load balancer):

<Connector
port="8085"
protocol="HTTP/1.1"

maxThreads="150" minSpareThreads="25"
connectionTimeout="20000"
disableUploadTimeout="true"
acceptCount="100"

enableLookups="false"
maxHttpHeaderSize="8192"

useBodyEncodingForURI="true"
URIEncoding="UTF-8"
secure="true"
scheme="https"
proxyName="bamboo.exmaple.com"
proxyPort="443"
redirectPort="443">
<UpgradeProtocol className="org.apache.coyote.http2.Http2Protocol" />
</Connector>

When starting bamboo it loops through some setup pages:

 

04-Mar-2019 17:34:12.959 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin [SetPropertiesRule]{Server/Service/Engine/Valve} Setting property 'resolveHosts' to 'false' did not find a matching property.
04-Mar-2019 17:34:12.967 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: [/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib]
04-Mar-2019 17:34:13.011 INFO [main] org.apache.coyote.http11.AbstractHttp11Protocol.configureUpgradeProtocol The ["http-nio-8085"] connector has been configured to support HTTP upgrade to [h2c]
04-Mar-2019 17:34:13.011 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8085"]
04-Mar-2019 17:34:13.034 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
04-Mar-2019 17:34:13.043 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 542 ms
04-Mar-2019 17:34:13.056 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
04-Mar-2019 17:34:13.056 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.34
04-Mar-2019 17:34:23.898 INFO [localhost-startStop-1] 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.
2019-03-04 17:34:24,225 INFO [localhost-startStop-1] [BootstrapLoaderListener] Starting BootstrapLoaderListener
2019-03-04 17:34:24,226 INFO [localhost-startStop-1] [lifecycle] *******************************
2019-03-04 17:34:24,226 INFO [localhost-startStop-1] [lifecycle] * Bamboo is starting up *
2019-03-04 17:34:24,226 INFO [localhost-startStop-1] [lifecycle] *******************************
2019-03-04 17:34:24,227 INFO [localhost-startStop-1] [ServletContextHolder] Setting servlet context: Bamboo
2019-03-04 17:34:24,320 INFO [localhost-startStop-1] [lifecycle] atlassian.org.osgi.framework.bootdelegation set to javax.servlet,javax.servlet.*,sun.*,com.sun.*,org.w3c.dom.*,org.apache.xerces.*,org.jboss.byteman.*,jdk.internal.reflect
2019-03-04 17:34:24,332 INFO [localhost-startStop-1] [BootstrapLoaderListener] App classloader is the same as web app classloader
2019-03-04 17:34:25,507 INFO [localhost-startStop-1] [lifecycle] Starting Bamboo 6.8.0 (build #60803 Wed Jan 30 13:37:58 UTC 2019) using Java 1.8.0_191 from Oracle Corporation
2019-03-04 17:34:25,507 INFO [localhost-startStop-1] [lifecycle] Real path of servlet context: /data/atlassian-bamboo-6.8.0/atlassian-bamboo/
2019-03-04 17:34:25,670 FATAL [localhost-startStop-1] [DefaultBootstrapManager] Unable to run pre-bootstrap upgrade tasks as your support period has ended
2019-03-04 17:34:25,671 INFO [localhost-startStop-1] [lifecycle] Bamboo home directory: /home/bamboo
2019-03-04 17:34:25,671 INFO [localhost-startStop-1] [lifecycle] Default charset: UTF-8, file name ecoding: UTF-8
2019-03-04 17:34:25,679 INFO [localhost-startStop-1] [UpgradeLauncher] Upgrades not performed since the application has not been set up yet.
2019-03-04 17:34:25,726 INFO [localhost-startStop-1] [CompressingFilter] CompressingFilter has initialized
2019-03-04 17:34:26,229 INFO [localhost-startStop-1] [SpringObjectFactoryProxy] Deferring initialisation of com.atlassian.bamboo.plugin.xwork.SpringObjectFactoryProxy
2019-03-04 17:34:27,148 INFO [localhost-startStop-1] [Dispatchers] Dispatcher org.apache.struts2.dispatcher.Dispatcher initialised
2019-03-04 17:34:27,222 INFO [localhost-startStop-1] [SpringObjectFactoryProxy] Deferring initialisation of com.atlassian.bamboo.plugin.xwork.SpringObjectFactoryProxy
2019-03-04 17:34:27,873 INFO [localhost-startStop-1] [AccessLogFilter] AccessLogFilter initialized. Format is: <user> <url> <starting memory free (kb)> +- <difference in free mem (kb)> <query time (ms)>
2019-03-04 17:34:27,950 INFO [localhost-startStop-1] [SpringObjectFactoryProxy] Deferring initialisation of com.atlassian.bamboo.plugin.xwork.SpringObjectFactoryProxy
2019-03-04 17:34:28,024 INFO [localhost-startStop-1] [Dispatchers] Dispatcher org.apache.struts2.dispatcher.Dispatcher initialised
2019-03-04 17:34:28,076 INFO [localhost-startStop-1] [SpringObjectFactoryProxy] Deferring initialisation of com.atlassian.bamboo.plugin.xwork.SpringObjectFactoryProxy
04-Mar-2019 17:34:28.190 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8085"]
04-Mar-2019 17:34:28.202 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 15159 ms
2019-03-04 17:34:28,357 INFO [http-nio-8085-exec-1] [JohnsonFilter] The application is not yet setup. Redirecting request from '/start.action' to '/bootstrap/selectSetupStep.action'
2019-03-04 17:34:28,357 INFO [http-nio-8085-exec-6] [JohnsonFilter] The application is not yet setup. Redirecting request from '/start.action' to '/bootstrap/selectSetupStep.action'
2019-03-04 17:34:28,357 INFO [http-nio-8085-exec-5] [JohnsonFilter] The application is not yet setup. Redirecting request from '/rest/api/latest/plan/favicon/NB-MG20' to '/bootstrap/selectSetupStep.action'
2019-03-04 17:34:28,357 INFO [http-nio-8085-exec-3] [JohnsonFilter] The application is not yet setup. Redirecting request from '/start.action' to '/bootstrap/selectSetupStep.action'
2019-03-04 17:34:28,357 INFO [http-nio-8085-exec-2] [JohnsonFilter] The application is not yet setup. Redirecting request from '/chain/admin/ajax/getChains.action' to '/bootstrap/selectSetupStep.action'
2019-03-04 17:34:28,357 INFO [http-nio-8085-exec-4] [JohnsonFilter] The application is not yet setup. Redirecting request from '/rest/api/latest/server' to '/bootstrap/selectSetupStep.action'
2019-03-04 17:34:28,428 INFO [http-nio-8085-exec-7] [AccessLogFilter] 172.16.8.34 GET https://bamboo.example.com/bootstrap/selectSetupStep.action 407664kb
2019-03-04 17:34:28,716 INFO [http-nio-8085-exec-7] [SelectSetupStepAction] Current setup step is /setup/complete.action
2019-03-04 17:34:28,773 INFO [http-nio-8085-exec-8] [AccessLogFilter] 172.16.8.34 GET https://bamboo.example.com/bootstrap/selectSetupStep.action 537934kb
2019-03-04 17:34:28,777 INFO [http-nio-8085-exec-9] [AccessLogFilter] 172.16.8.34 GET https://bamboo.example.com/setup/complete.action 533709kb
2019-03-04 17:34:28,780 INFO [http-nio-8085-exec-8] [SelectSetupStepAction] Current setup step is /setup/complete.action
2019-03-04 17:34:28,831 INFO [http-nio-8085-exec-10] [AccessLogFilter] 172.16.8.34 GET https://bamboo.example.com/bootstrap/selectSetupStep.action 525259kb
2019-03-04 17:34:28,835 INFO [http-nio-8085-exec-10] [SelectSetupStepAction] Current setup step is /setup/complete.action
2019-03-04 17:34:28,852 INFO [http-nio-8085-exec-11] [AccessLogFilter] 172.16.8.34 GET https://bamboo.example.com/setup/complete.action 522443kb
.
.
.
.
.
.
.
.

 Any hints on what could be the issue?

2 answers

1 accepted

1 vote
Answer accepted
Foong
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 5, 2019
2019-03-04 17:34:25,670 FATAL [localhost-startStop-1] [DefaultBootstrapManager] Unable to run pre-bootstrap upgrade tasks as your support period has ended

Its a bug https://jira.atlassian.com/browse/BAM-20334

Workaround:

  1. Shutdown Bamboo
  2. Replace the license in the file /home/bamboo/bamboo.cfg.xml with the new license in https://my.atlassian.com , for example:
        <property name="license.string">license line 1
    license line 2
    license line 3
    license line 4
    ... license line #</property>
  3. Restart Bamboo
memoryleak March 7, 2019

Hi @Foong 

That was exaclty the problem and the workaround worked! Thanks.

Like Foong likes this
0 votes
Edwin Kyalangalilwa
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 4, 2019

Hi @memoryleak ,

 

2019-03-04 17:34:25,671 INFO [localhost-startStop-1] [lifecycle] Bamboo home directory: /home/bamboo

Please confirm that /home/bamboo is the correct Bamboo home directory specified in 

<bamboo-install-dir>/atlassian-bamboo/WEB-INF/classes/bamboo-init.properties

Locating important directories and files

memoryleak March 4, 2019

Hi Edwin, thanks for your reply. The home folder is set correctly:

[ 06:58:56 root@ip-172-16-4-185 atlassian-bamboo-6.8.0 ] cat atlassian-bamboo/WEB-INF/classes/bamboo-init.properties
## You can specify your bamboo.home property here or in your system environment variables.
bamboo.home=/home/bamboo
[ 06:58:59 root@ip-172-16-4-185 atlassian-bamboo-6.8.0 ] ls /home/bamboo
analytics-logs artifacts backups bamboo.cfg.xml bamboo-mail.cfg.xml caches docker_env.sh exports index jms-store logs plugins serverState temp templates test.retry xml-data

 

I've copied over settings from the previous installation (6.6) and until that version it worked by copying over the settings for home folder and the connector.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events