upgrade to jira 6.2.2 from 6.1.7 problem

I upgraded to jira 6.2.2, now the app won't launch in a browser. The app is running per ps aux | grep java.

This is the bottom of atlassian-jira.log:

JIRA 6.2.2 build: 6258 started. You can now access JIRA through your web browser.
*********************************************************************************

2014-04-15 13:26:28,972 localhost-startStop-1 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number to 6258
2014-04-15 13:26:28,977 localhost-startStop-1 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current version to 6.2.2
2014-04-15 13:26:28,979 localhost-startStop-1 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting downgrade version to 6.1.7
2014-04-15 13:26:30,529 Modification Check:thread-1 INFO [atlassian.jira.startup.JiraStartupLogger]

___ Modifications ___________________________

Modified Files : jira-application.properties
Removed Files : None

2014-04-15 13:26:31,619 localhost-startStop-1 INFO [ext.bamboo.service.PlanStatusUpdateServiceImpl] Job 'com.atlassian.jira.plugin.ext.bamboo.service.PlanStatusUpdateServiceImpl:job' scheduled to run every 60000ms
2014-04-15 13:26:31,620 localhost-startStop-1 INFO [plugins.dvcs.scheduler.DvcsScheduler] DvcsScheduler start planned at Tue Apr 15 13:52:31 CDT 2014, interval=3600000
2014-04-15 13:26:31,664 localhost-startStop-1 INFO [atlassian.plugin.manager.DefaultPluginManager] Returned module for key 'com.pyxis.greenhopper.jira:greenhopper-taskboard-shortcut' was null. Not enabling.
2014-04-15 13:26:31,664 localhost-startStop-1 INFO [atlassian.plugin.manager.DefaultPluginManager] Returned module for key 'com.pyxis.greenhopper.jira:greenhopper-chartboard-shortcut' was null. Not enabling.
2014-04-15 13:26:31,664 localhost-startStop-1 INFO [atlassian.plugin.manager.DefaultPluginManager] Returned module for key 'com.pyxis.greenhopper.jira:greenhopper-releasedboard-shortcut' was null. Not enabling.
2014-04-15 13:26:31,675 localhost-startStop-1 INFO [atlassian.plugin.manager.DefaultPluginManager] Returned module for key 'com.pyxis.greenhopper.jira:greenhopper-delete-shortcut' was null. Not enabling.
2014-04-15 13:26:31,676 localhost-startStop-1 INFO [greenhopper.plugin.sampledata.JiraImportersPluginInstallerImpl] Checking if jira-importers-plugin is present and at version 4.4 or higher
2014-04-15 13:26:31,677 localhost-startStop-1 INFO [greenhopper.plugin.sampledata.JiraImportersPluginInstallerImpl] jira-importers-plugin already at 6.1.3.
2014-04-15 13:26:33,297 localhost-startStop-1 INFO [greenhopper.service.logging.LogSupport]

Managed Issue Types
Epic id=10000 name=Epic
Story id=10001 name=Story


Managed Custom Fields
Epic Colour id=customfield_10009 name=Epic Color type=com.pyxis.greenhopper.jira:gh-epic-color
Epic Link id=customfield_10006 name=Epic Link type=com.pyxis.greenhopper.jira:gh-epic-link
Epic Name id=customfield_10007 name=Epic Name type=com.pyxis.greenhopper.jira:gh-epic-label
Epic Status id=customfield_10008 name=Epic Status type=com.pyxis.greenhopper.jira:gh-epic-status
Default Global Rank id=customfield_10004 name=Rank type=com.pyxis.greenhopper.jira:gh-global-rank
Sprint id=customfield_10005 name=Sprint type=com.pyxis.greenhopper.jira:gh-sprint
Story Points id=customfield_10002 name=Story Points type=com.atlassian.jira.plugin.system.customfieldtypes:float


Managed Issue Link Types
Epic Link Issue Link Type id=10200 name=Epic-Story Link

2014-04-15 13:26:33,489 localhost-startStop-1 INFO [jira.whatsnew.listeners.WhatsNewUpgradeFinishedListenerImpl] Enabling show-whats-new-flag for all users
2014-04-15 13:26:33,493 localhost-startStop-1 INFO [atlassian.jira.scheduler.JiraSchedulerLauncher] Starting the JIRA Scheduler....
2014-04-15 13:26:33,505 localhost-startStop-1 INFO [atlassian.jira.scheduler.JiraSchedulerLauncher] JIRA Scheduler started.
2014-04-15 13:26:35,069 QuartzScheduler_Worker-0 INFO ServiceRunner Backup Service [jira.bc.dataimport.DefaultExportService] Data export completed in 1389ms. Wrote 14509 entities to export in memory.
2014-04-15 13:26:35,070 QuartzScheduler_Worker-0 INFO ServiceRunner Backup Service [jira.bc.dataimport.DefaultExportService] Attempting to save the Active Objects Backup
2014-04-15 13:26:35,477 QuartzScheduler_Worker-0 INFO ServiceRunner Backup Service [jira.bc.dataimport.DefaultExportService] Finished saving the Active Objects Backup
2014-04-15 13:26:36,648 QuartzScheduler_Worker-1 INFO [atlassian.crowd.directory.DbCachingRemoteDirectory] synchronisation for directory [ 10000 ] starting
2014-04-15 13:26:37,356 CrowdUsnChangedCacheRefresher:thread-2 INFO [directory.ldap.cache.UsnChangedCacheRefresher] found [ 51 ] remote groups in [ 697ms ]
2014-04-15 13:26:38,165 CrowdUsnChangedCacheRefresher:thread-1 INFO [directory.ldap.cache.UsnChangedCacheRefresher] found [ 1265 ] remote users in [ 1505ms ]
2014-04-15 13:26:38,221 QuartzScheduler_Worker-1 INFO [atlassian.crowd.directory.DbCachingRemoteChangeOperations] scanned and compared [ 1265 ] users for delete in DB cache in [ 50ms ]
2014-04-15 13:26:38,221 QuartzScheduler_Worker-1 INFO [atlassian.crowd.directory.DbCachingRemoteChangeOperations] scanned for deleted users in [ 52ms ]
2014-04-15 13:26:38,224 QuartzScheduler_Worker-1 INFO [atlassian.crowd.directory.DbCachingRemoteChangeOperations] scanning [ 1265 ] users to add or update
2014-04-15 13:26:38,238 QuartzScheduler_Worker-1 INFO [atlassian.crowd.directory.DirectoryCacheImplUsingChangeOperations] scanned and compared [ 1265 ] users for update in DB cache in [ 17ms ]
2014-04-15 13:26:38,239 QuartzScheduler_Worker-1 INFO [atlassian.crowd.directory.DirectoryCacheImplUsingChangeOperations] synchronised [ 1265 ] users in [ 18ms ]
2014-04-15 13:26:38,239 QuartzScheduler_Worker-1 INFO [atlassian.crowd.directory.DirectoryCacheImplUsingChangeOperations] scanning [ 51 ] groups to add or update
2014-04-15 13:26:38,246 QuartzScheduler_Worker-1 INFO [atlassian.crowd.directory.DbCachingRemoteChangeOperations] scanned and compared [ 51 ] groups for update in DB cache in [ 7ms ]
2014-04-15 13:26:38,246 QuartzScheduler_Worker-1 INFO [atlassian.crowd.directory.DirectoryCacheImplUsingChangeOperations] synchronized [ 51 ] groups in [ 7ms ]
2014-04-15 13:26:38,250 QuartzScheduler_Worker-1 INFO [atlassian.crowd.directory.DbCachingRemoteChangeOperations] scanned and compared [ 51 ] groups for delete in DB cache in [ 4ms ]
2014-04-15 13:26:38,617 QuartzScheduler_Worker-1 INFO [atlassian.crowd.directory.DbCachingRemoteDirectory] FULL synchronisation complete for directory [ 10000 ] in [ 1969ms ]
[jira@pros-jira log]$ ll
total 122768
-rw------- 1 jira jira 219501 Apr 15 13:26 atlassian-greenhopper.log
-rw------- 1 jira jira 16205992 Apr 15 13:26 atlassian-jira.log
-rw------- 1 jira jira 4370113 Apr 15 13:26 atlassian-jira-security.log
-rw------- 1 jira jira 20971523 Apr 14 14:22 atlassian-jira-security.log.1
-rw------- 1 jira jira 20971630 Apr 10 09:56 atlassian-jira-security.log.2
-rw------- 1 jira jira 20971647 Apr 6 06:26 atlassian-jira-security.log.3
-rw------- 1 jira jira 20971557 Apr 2 08:46 atlassian-jira-security.log.4
-rw------- 1 jira jira 20971582 Mar 29 07:26 atlassian-jira-security.log.5
-rw------- 1 jira jira 749 Mar 26 14:19 atlassian-jira-slow-queries.log

It looks to me like it's working, as it's syncing with our AD.

2 answers

1 accepted

Is it possible that you forget to change running port in server.xml. Can you check localhost:8080 using lynx or links?

I believe it's a firewall issue

That was exactly the problem. We're doing an SSL off-load from our LB, so I'm using 443 -> 8443. The upgrade stepped on the server.xml file. I just had to uncomment it and add the SSL password and I was back in business.

Glad to have discovered this problem while we're still on an eval license, but I'll know what to look for the next time I upgrade Jira, and when I upgrade Confluence and Stash.

In general, I've been quite pleased with the ease of managing these products, but over-writing config files in an upgrade is not cool, Atlassian.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Monday in Jira Software

How large do you think Jira Software can grow?

Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...

555 views 6 12
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you