Upgrade to 7.9, please help

[Robert G. Nadon]

Hi all,

I upgraded from 7.2.6 to 7.9.0 and now I have 2 major problems.  (Well as far as I can tell as the two problems prevent further investigation)

1. I cannot get SSL working, I added back to the server.conf file the 8443 https port and it does not work anymore

2. I cannot login to even the 8080 port non SSL.    I get a login screen type my password and get nothing.  It just returns me to the login with no errors in the atlassian-jira.log and no errors on the web-page.  Just returns me to login

Any help would be greatly appreciated as I have been googling around with no success.

Thanks!

Robert

[Robert G. Nadon · Accepted solution]

OK I got the SSL working.   @atlassian  I BEG of thee.   Please please please do not wipe out the conf/server.xml every upgrade, this is absolutely the most stressful part of upgrading Jira.  

OK this also fixed the login problem.    whew....

[Bryan Bai]

try using the manual upgrade...

[Robert G. Nadon]

Haven't tried that, but that sounds like much more than just updating the server.xml.    However, if it solves the problem then I should look into it.  Thanks.

[Sébastien Tisserand]

hi Robert,

I've got the sames issues.

what is the solution ?

thanks and regards

[Nic Brough -Adaptavist-]

The solution is to read the warnings the upgrade process gives you about the files it is going to replace and look at the differences between old and new.

The installer cannot know what you might have done to the config files, so it has no choice but to replace them with ones that it knows work (as a new version could easily have totally restructured the content or location or even deprecated them).  If you have changed the files for some reason, then it's up to you to replicate the effects of those changes into the new ones.

[Robert G. Nadon]

Yes Nic, that is part of it, but every time I have to change it in a different way.  It was not as if I can just keep the server.xml from the previous release.  I assume that is because they are adding in new options, but not sure.  Given that I believe that there should be intelligence in the installer to accommodate the one file.   

Also Sebastien beware last I tried the majority of the plugins have not been ported to 7.9, including Script Runner, so we decided to use 7.8.1 which upgraded much better  from 7.2.6 and my existing server.xml did work on that one.

So for 7.8.1 I copied off my old 7.2.6 $JIRA_INSTALL/conf/server.xml file and then after upgrade before booting up replaced the new $JIRA_INSTALL/conf/server.xml with the one I saved off.  Best of luck Sebastian.

[Nic Brough -Adaptavist-]

The problem there is that if the installer leaves your files in place, and the format has changed, you're left with a non-working system because it won't be able to cope with all possible changes you might have made.  There isn't much else it can do other than tell you what files it is going to replace.

[Vickey Palzor Lepcha]

Why don't you maintain versioning of your configuration files - helps a lot, and keep it as a standard practice for upgrades.

[ebatech_dkoot]

I also don't understand why the server.xml needs to be replaced completely every update.

In my installation i only changed the http to https-with-proxy but i need to repeat this every time i do an upgrade. I would expect something like this (which also directly gives an error in the front-end) MUST be able to be configured and these settings kept over an upgrade.

during the upgrade it is said that the file is going to be overwritten, but it would be nice if you could do a side-by-side diff and import the new changes into your config file before upgrading and starting.

apt-get does this (at least on debian) when you do an update and a config file has changed, you can look at the changes, and choose to use the new file, keep the old file or make changes in a subshell.

[Dawn Peeples]

I'm having the same issue trying to do a manual upgrade and updating the new server.xml but I still cannot get ssl to work.  I am going to upgrade to 7.8.2 instead.  

[Vickey Palzor Lepcha]

check your ajp ports and connections - match that with your apache conf files - usually that is what gets removed, you can add it back.