How can I tell if a Bamboo export is still running?

Jason Horn December 21, 2016

I am running Bamboo behind Apache.  I kicked off an export, but I think my proxy has timed out (getting 502 on the /admin/export page) before the export has completed.  Is there anything I can look at to see if the export is still running?  I am running bamboo on RHEL linux.

Thanks!

2 answers

1 vote
rsperafico
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 22, 2016

Hello Jason,

You could do the following:

  1. run the following REST API call

    curl -k -u BAMBOO_ADMIN -p -H "Content-type: application/json" -X GET BAMBOO_BASE_URL/rest/api/latest/info

    As a response, you would get:

    <info>
      <version>5.14.1</version>
      <edition/>
      <buildDate>2016-11-04T08:05:38.000-02:00</buildDate>
      <buildNumber>51413</buildNumber>
      <state>PAUSED</state>
    </info>
  2. look for the following entries on Bamboo logs:

    201X-XX-XX 13:23:31,235 INFO [http-bio-8085-exec-11] [XmlMigrator] Finished updating zip
    201X-XX-XX 13:23:31,235 INFO [http-bio-8085-exec-11] [XmlMigrator] Ensuring the the file has been unmounted
    201X-XX-XX 13:23:31,237 INFO [http-bio-8085-exec-11] [XmlMigrator] Unmounted <bamboo-home>/exports/export_bambooVersion_release_20XXXX20.zip
    201X-05-20 13:23:31,237 INFO [http-bio-8085-exec-11] [XmlMigrator] Export completed. 0:00:31.788

Kind regards,

Rafael

0 votes
Jonas Andersson
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.
December 21, 2016

I see this quite often but i allow the traffic to pass without rewrites on the high portnumbers which were never used by our organization anyway. This has been a blessing while doing POC of Atlassians other tools, as it allowed me to quickly link applications that not yet had shared SSL certs in each others keystores, without the imports and restart of the whole application stack. This means that if i know i am about to do a reindex/backup/restore i connect to http://bamboo:8085 rather than https://bamboo

The correct workaround would be to increase the session timeout on the apache, but if any of the applicationservers behind the proxy goes down, it might build up connections that zombies, ultimately reaching the apaches max connections, and killing the service.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events