Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Jira 7.11 to Jira 8.6 upgrade question.

Edited

I am wanting to upgrade from an existing Jira 7.11 to 8.6. Which installer do I need to do this. I'm unsure if I need the:

1/ Jira Core installer (https://www.atlassian.com/software/jira/core/update)  or the

2/ Jira Software installer (https://marketplace.atlassian.com/apps/1213607/jira-software/version-history) and the 8.6.1 installer .obr file.

I am thinking 2/ of the above but want to confirm this. As mentioned we already have a Jira 7.11 instalation running...

3 answers

2 accepted

0 votes
Answer accepted

As Hernan suggested, if you are using scrum and kanban in your jira - you have jira software installed so go for option 2.

But if your jira does not have kanban and scrum boards option - its just jira core so go for option 1.

Also, check your Applications tab under JIRA Admin Console - you will see what is installed , just JIRA Core or JIRA Software and Core.

 

Jira Software is ( Agile + JIRA CORE) while Jira Core is no Agile Boards. 

Thank you gentlemen, we have Jira software 7.11.1 (with an 'upgrade' button) and Jira core 7.11.1 (with a renew before upgrade button). 

So I'm thinking we have jira software AND core.

We use scrum/kanban so I'm still thinking option 2 (the obr file)?

Jira core should come along with Jira Software license so I would focus on upgrading Jira Software only. The obr file should work if you install it from the UI, else you can stop jira, run the server installer and start jira again.

Like Vickey Palzor Lepcha likes this

Right - simple point is when you upgrade Software - it will include core as well. When you upgrade core - it wont include the Agile part . :-)

Thank you again. I will run the .obr file then.

Hernan: you mention the UI, this would be the local web interface would it?

I want to run the update file from terminal if possible. The machine Jira is running on does not have a GUI installed. I have ssh access.

It would be from wherever you access jira on a daily basis. If it's reachable from internet, that would be the place. No need to add the obr from the UI of the server that runs jira. 

If you want to run it from the server... then most likely this is the link you need

https://www.atlassian.com/software/jira/downloads/binary/atlassian-jira-software-8.6.1-x64.bin

assuming this is a linux server

Yes Linux server Ubuntu 16.x

So I can run this file from terminal after the usual precautions (backup, disable apps... etc)

Downloading the above file now and will run when I can plan an outage.

Thank you for the quick reply.

Regards

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:

Upgrade: Custom changes have not been carried over
The listed configuration files contain custom changes. To keep your current configuration, re-apply these custom changes to the new version of the files during upgrade.

  • conf/server.xml
  • bin/setenv.sh

Note: Make sure you only copy over the changes not the entire files.

Now do I locate a backup copy of the server.xml and setenv.sh files and go through each line by line looking for the changes? And why oh why did I think this would be automatic? 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.

Any advice on next step would be appreciated. If I should create a new question for this please advise and I will...

Thank you in advance...

Joe

I have edited the server.xml file with a 1x change from the backup, the setenv.sh seems to be identical. the restarted but still a tomcat error... How do I know if there is a reverse proxy running?

Hi @Joe F  I suppose the fastest way to know if you had a reverse proxy is based on the URL you used for Jira. If you were using the default Jira ports 8080 or 8443 instead of the standard ones, then answer would be no. If you had something like Jira.yourcompany.com then the answer is ye

See if you can access JIRA using the default ports bypassing proxy - that should let you know if jira is running or not ( that is if tomcat is the issue here )  or if its your reverse proxy

Can connect on 192.168.1.53:8080 but not on 8443. I'm pretty sure we are running a rev proxy but no notes from prev Admin about it. 

Here is an excerpt from the server.xml file:

I note this is uncommented and has our details in it, and this is what I enter into the new (8.6.1) server.xml file. HTTPS - Proxying Jira via Apache or Nginx over HTTPS etc (see below)

<?xml version="1.0" encoding="utf-8"?>
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<Server port="8005" shutdown="SHUTDOWN">
<Listener className="org.apache.catalina.startup.VersionLoggerListener"/>
<Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on"/>
<Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener"/>
<Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"/>
<Listener className="org.apache.catalina.core.ThreadLocalLeakPreventionListener"/>

<Service name="Catalina">
<!--
==============================================================================================================
DEFAULT - Direct connector with no proxy for unproxied access to Jira.

If using a http/https proxy, comment out this connector.
==============================================================================================================
-->
<!--
<Connector port="8080" maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false"
maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443"
acceptCount="100" disableUploadTimeout="true" bindOnInit="false"/>
-->
<!--
==============================================================================================================
HTTP - Proxying Jira via Apache or Nginx over HTTP

If you're proxying traffic to Jira over HTTP, uncomment the below connector and comment out the others.
Ensure the proxyName and proxyPort are updated with the appropriate information if necessary as per the docs.

See the following for more information:

Apache - https://confluence.atlassian.com/x/4xQLM
nginx - https://confluence.atlassian.com/x/DAFmGQ
==============================================================================================================
-->

<!--
<Connector port="8080" maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false"
maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443"
acceptCount="100" disableUploadTimeout="true" bindOnInit="false" scheme="http"
proxyName="jira.bodekerscientific.com" proxyPort="80"/>
-->

<!--
==============================================================================================================
HTTPS - Proxying Jira via Apache or Nginx over HTTPS

If you're proxying traffic to Jira over HTTPS, uncomment the below connector and comment out the others.
Ensure the proxyName and proxyPort are updated with the appropriate information if necessary as per the docs.

See the following for more information:

Apache - https://confluence.atlassian.com/x/PTT3MQ
nginx - https://confluence.atlassian.com/x/DAFmGQ
==============================================================================================================
-->


<Connector port="8080" maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false"
maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443"
acceptCount="100" disableUploadTimeout="true" bindOnInit="false" secure="true" scheme="https"
proxyName="jira.bodekerscientific.com" proxyPort="443"/>

<!--
==============================================================================================================
AJP - Proxying Jira via Apache over HTTP or HTTPS

If you're proxying traffic to Jira using the AJP protocol, uncomment the following connector line
See the following for more information:

Apache - https://confluence.atlassian.com/x/QiJ9MQ
==============================================================================================================
-->

<!--
<Connector port="8009" URIEncoding="UTF-8" enableLookups="false" protocol="AJP/1.3" />
-->

<Engine name="Catalina" defaultHost="localhost">
<Host name="localhost" appBase="webapps" unpackWARs="true" autoDeploy="true">

<Context path="" docBase="${catalina.home}/atlassian-jira" reloadable="false" useHttpOnly="true">
<Resource name="UserTransaction" auth="Container" type="javax.transaction.UserTransaction"
factory="org.objectweb.jotm.UserTransactionFactory" jotm.timeout="60"/>
<Manager pathname=""/>
<JarScanner scanManifest="false"/>
</Context>

</Host>
<Valve className="org.apache.catalina.valves.AccessLogValve"
pattern="%a %{jira.request.id}r %{jira.request.username}r %t &quot;%m %U%q %H&quot; %s %b %D &quot;%{Referer}i&quot; &quot;%{User-Agent}i&quot; &quot;%{jira.request.assession.id}r&quot;"/>
</Engine>
</Service>
</Server>

Hello @Joe F if you are managing kanban and scrum  boards then you should use the second one.

Also if you go to the licensing tab you should see there which of the ones you are using.

For anyone else out there, I commented out 'DEFAULT' and uncommented HTTPS proxy over NGINX, changed the redirectPort="8443" to '443' in server.xml. This '443' was the only change from previous efforts.

I ran the 8.6.1 bin installer (not 8.7.1) all seemed to go ok from installer feedback, usual message about indexing (made that file) & setenv.sh and server.xml having changes that were not copied over (even tho' I had updated the req'd info.)

Service stop and service restart did not fix this but it seems a power down and power back on brought everything back up.

So the job is done (from 7.11.1 to 8.6.1.)

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you