nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why has a Bamboo upgrade to 4.2 completely screwed my system?

David FALLAS

An earlier question (https://answers.atlassian.com/questions/81040/bamboo-4-2-upgrade-error-no-jvm-found) I had asked, indicated that installation of a more recent java runtime would resolve my problems with installing Bamboo 4.2.

Bamboo 4.2 installed OK after the java update, but now it appears that I cannot use my previous Bamboo data (SQLServer database) and worse still, it appears to have disabled access to FishEye where I now get an exception message:

Repository svnDHServices on http://kojira:8060/ failed: Error in remote call to 'FishEye' (http://kojira:8060) [AbstractRestCommand{path='/rest-service-fe/changeset-v1/listChangesets/', params={expand=changesets[-21:-1].revisions[0:29], comment=OLINTAAA-7, p4JobFixed=OLINTAAA-7, rep=svnDHServices}, methodType=GET}] : Connection refused: connect

Can anyone help me understand what may have happened here?

Can anyone assist me to recover to a point where we have a working system again?

This all seems to be far more difficult than it should be.

Accepted answers

Harry Chan5

Hi, did you follow the steps in this guide? https://confluence.atlassian.com/display/BAMBOO/Bamboo+generic+upgrade+guide

Take note that your {BAMBOO_INSTALL} directory needs to be a new or empty directory. The legacy files need to be backed up and cleared away from the directory first.

All comments

Harry Chan5

Hi, did you follow the steps in this guide? https://confluence.atlassian.com/display/BAMBOO/Bamboo+generic+upgrade+guide

Take note that your {BAMBOO_INSTALL} directory needs to be a new or empty directory. The legacy files need to be backed up and cleared away from the directory first.

David FALLAS

Hi Harry,

I believe that I did attempt to follow the steps, but I must've fallen foul of something along the way.

I have a database backup, and three separate directories which are also backed up. This was done prior to commencing the upgrade process.

C:\Users\administrator.SYSMEXNZ\bamboo-home (home)

C:\Program Files\Bamboo (install)

\Bamboo (working/data)

I have downloaded the installer for version 3.4, in the hope that I could restore the system to where it was. However I have failed at that too. I have attached the config file from bamboo-home. Perhaps something wrong there?

If you have any advice that might help me restore the system to a point where I can attempt the upgrade again, I would be very grateful.

(bamboo.cfg.xml.txt)

David FALLAS

In case it helps - I have attached the tail 100k or so of atlassian-bamboo.log (NOTE: this is a zipped file even though it has .log as file type - this page does not permit attaching .zip files).

It appears that there are a considerable number of missing or unresolvable elements.

BTW - this message from the log also leads to a dead link:

"For more details on how to fix this, see http://confluence.atlassian.com/x/1xy6D"

(atlassian-bamboo.log)

David FALLAS

..and a few more clues... these problems I am having all seem to be associated with installing the JDK.

The JDK is jdk1.7.0_06 from Oracle. Apart from that JDK directory, I also now have both jre6 and jre7 directories under the C:\Program Files\Java directory.

Bamboo v3.4 will work under certain conditions - when the JAVA_HOME environment variable is set to C:\Program Files\Java\jre7 - BUT - with this setting, the FishEye service refuses to start (wrapper.log contains the following)

"STATUS | wrapper | 2012/08/28 07:55:35 | --> Wrapper Started as Service

STATUS | wrapper | 2012/08/28 07:55:36 | Launching a JVM...

INFO | jvm 1 | 2012/08/28 07:55:36 | Error: missing `server' JVM at `C:\Program Files\Java\jre7\bin\server\jvm.dll'.

INFO | jvm 1 | 2012/08/28 07:55:36 | Please install or use the JRE or JDK that contains these missing components.

ERROR | wrapper | 2012/08/28 07:55:36 | JVM exited while loading the application."

In note that C:\Program Files\Java\jre7 does not contain a \server sub-directory - whereas \jre6 does

If JAVA_HOME is set back to jre6, the FishEye service WILL start, but still throws that exception when JIRA attempts to display source code check-ins.

It appears that the system I now have has some irreconcilable mismatches between the FishEye version (2.7.8), the Bamboo version (now reverted to 3.4) and Java (jre6, jre7 and jdk1.7.0)

David FALLAS

I have made two posts as comments on the answer - however both have not been added. I note your last question was also lost from the thread

"Can you please repost your Fisheye log in this case - the latest one? I've gone through the old one and it's either a corrupted download or a corrupted plugin in your system somewhere since the Java version should already have been resolved."

I will attempt to add a new comment at this level to see if it remains in the thread

Harry - in answer to the last question, I have followed the suggestions from the link https://confluence.atlassian.com/display/FISHKB/'Timeout+exceeded+waiting+for+service'+Error+Message+After+Upgrade

1. I could not find any duplicate jars in the sub-directories specified

2. There were no entries in pluginstate.properties (apart from a comment)

3. I did not increase the JAR timeout setting - until we rule out other causes, this is just noise as the server is well specced and the timeout was never an issue before

4. As you observed, we believe the java issue has been resolved by adding the bin folder to the PATH environment variable.

I enclose the complete FishEye wrapper.log. It is zipped, but has a .txt file type (as before)

Harry Chan5

Hi David, nothing got lost. If there are too many comments to a post it simply gets hidden. You have to press show all comments. Sorry, do you know which post you attached the logs to? I can't find it.

David FALLAS

Hi Harry, Thans for the advice. I can now see all comments - my apolgoies for not knowing why they were apparently 'missing'.

Perhaps the previous file was too big (620k) or the name was not acceptable. I'll try a rename with .log first - then if that doesn't work - I'll attempt to extract just the last time I tried to connect.

(wrapper.zip.log)

Harry Chan5

Did you upgrade from Java 6 to Java 7? (I think you mentioned you did) Please remove the INST/cache/plugins/osgi-cache directory. Explanation https://jira.atlassian.com/browse/FE-3916. I found this whilst going through your logs.

David FALLAS

Yay!!! - I can now open the FishEye site again. I installed the latest JDK to try to get the Bamboo 4.2 upgrade working. That installed itself in C:\Program Files\Java\jdk1.7.0_06 - so I guess it is Java 7.

Harry, a special thanks for all your patience and for eventually sleuthing out the reason.

Now all I have to do is figure out how to re-create all my Application Links!

rocky janson

Can you please repost your Fisheye log in this case - the latest one? I've gone through the old one and it's either a corrupted download or a corrupted plugin in your system somewhere since the Java version should already have been resolved.

hosting with dedicated ip

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bamboo