have taken steps for a fallback (again) after a failed 8.7.1 upgrade (from 7.11)
I have disabled apps as per atlassian instructions.
Have run the: atlassian-jira-software-8.6.1-x64.bin and appears to have run ok, created the 'do not re-index' file and then this message appears:
Note: Make sure you only copy over the changes not the entire files."
Why oh why did I think this would be automatic? Well, Mainly because of this statement:
(https://confluence.atlassian.com/adminjiraserver/upgrading-jira-server-manual-938846939.html)
We'll make another check on Jira startup and will show you all the files you might have skipped that still contain changes that have not been copied over. Then you'll be able to click to automatically copy the changes over.
Note that the check will only be run on the following configuration files:
- <jira-home-directory>/atlassian-jira/ directory
- <jira-home-directory>/conf/server.xml
- <jira-home-directory>/bin/setenv.sh
and the automatic transfer will only be supported for ATST plugin 1.20.0 and later.
To automatically transfer the changes, the installer copy of the modified file needs to be the same as in the version you're upgrading to.
and jira presents a page that says it upgraded ok, and in a box there is a tomcat error: "
The Tomcat server.xml has an incorrect configuration:
scheme should be 'https'
proxyName should be 'jira.bodekerscientific.com'
proxyPort should be '443'
So I go thru the old server.xml and update what looks like the correct rev proxy https line to read as above, and comment out default. Restart jira and still nogo.
It looks like there are more issues than just tomcat. Questions:
1/ Is the tomcat config file part of the server.xml config located at: <jira-home-directory>/conf/server.xml? or where do I find this?
2/ How do I check if we are running a reverse proxy?
3/ Jira is pretty well broken now so I'll be rolling back, only get 502 bad gateway messages now (sad face)
Any advice on next step would be appreciated.
Hi @Joe F
if you access your Application via the domain jira.bodekerscientific.com it is highly probable that there is a reverse proxy in front.
Please check the follwing file <JIRA INSTALL>/conf/server.xml
in the Connector Part there should be the variables
scheme=https
proxyName=jira.bodekerscientific.com
proxyPort=443
secure=true
After changing the file Jira needs a restart.
If the message;
still occurs, please don't be frustrated and click the "Ignore this warnings" button :)
Best regards,
Nicolas
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.