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; } } }

"Jira Software functionality is not available" after TRYING to update

Jasper

Hi,

I'm on Jira Software 7.0.1 and tried to update to the latest version.

This is my Update screen:

Schermafdruk 2018-06-08 11.43.22_preview.png But when clicking on it, it shows me:

Schermafdruk 2018-06-08 11.43.30_preview.png

I can't figure out which logs I should take a look.

But there actually did happen something, because now for some reason the "Software" of Jira is not installed anymore..

See:

Schermafdruk 2018-06-08 11.45.34_preview.png

As you can see, when creating a new project, it's not available anymore:

Schermafdruk 2018-06-08 11.46.17_preview.png

But I use Jira only for Software development, so this is impacting our business a lot...!

Accepted answers

All comments

Marc Jason Mutuc

Turn OFF your JIRA Instance, then turn it back ON. Aftwards, do a locked reindex if allowable.

Ricardo Caeiro

Hi Jasper,

How did you upgrade your Jira instance? Did you do it from within the application?

I recommend you to use the installer. I've seen several situations in which users try to upgrade from within Jira and the upgrade fails for several reasons.

I think you can best upgrade by using this method.

Regards,

Ricardo

Jasper

Yes, from the application.

@Ricardo Caeiro

Tried to do it manually , but then I got this and no option to 'update'. Just to install it. Schermafdruk 2018-06-08 12.00.25_preview.png

Jasper

@Ricardo Caeiro any idea what I do wrong?

Andy Heinzer

Given that you were on 7.0.1 and are upgrading to 7.10, I'm confident from your description that the Jira Software plugin did not load on start up. But why that is, I can't say yet. Looking at your $JIRAHOME/log/atlassian-jira.log would probably help us to understand why this failed to load. One reason could be that the upgrade of this plugin failed for some reason. If that happens, we should be able to see that in the logs. Another possible reason is that typically on an upgrade the setenv.sh file is usually overwritten in an upgrade.

This file contains the startup option for Jira such as Xmx values (the max heap size of Java), and upgrades tend to revert this to a default of 768m. That's usually fine for an initial install, but it's woefully inadequate for medium to large Jira installs.

But first I'd like to see your log file here to better understand the appropriate next steps.

I suspect that these steps will help resolve this, but I am still interested to see the logs first:

Stop Jira
Follow the Increasing Jira memory guide to bump the memory here. Might also help to consult the Jira sizing guide to pick an appropriate Xmx value and make sure your system can run this application well. If you're not sure, 1024m or 2048m should be good provided the system has 8-16GB of system memory.
It's possible you have old plugin versions that could cause problems with loading this Jira Software plugin on start up. Navigate to $JIRAHOME/plugins/installed-plugins/ and move all the files in this directory to a temp folder outside the JIRAHOME directory
It's possible there are other system plugins that could have been disabled on a database level, you can clear these with a command in SQL like this:
```
truncate table pluginstate;
```
Start Jira
Return to the Cog Icon -> Applications -> Versions and licenses. From this page you can then attempt to install the latest Jira Software plugin to your Jira site. If all goes well, you should then be typically prompted to reindex at which point you should have access to all the other Software features again.

If you followed these steps, you would also need to reinstall compatible versions of all your previous plugins. I'd recommend doing this via the UPM in Jira (Cog Icon -> Add-ons -> Find new add-ons). Using this method to install these plugins via our marketplace listing should help prevent an incompatible plugin version from being loaded in Jira.

Jasper

Stopping Jira did destroy it all...

See this error:

https://pastebin.com/CJtQVwEA

Andy Heinzer

Well I see 2 errors here:

09-Jun-2018 13:43:54.698 SEVERE [main] org.apache.coyote.AbstractProtocol.init Failed to initialize end point associated with ProtocolHandler ["http-nio-8080"]

java.net.BindException: Adres is al in gebruik

Which indicates that this startup of Jira can't use port 8080 because some other process on the system is already using that port. How do you start jira in your environment normally? Via the .sh script? Or via a service? Something on that system is still using port 8080. It could be a Jira process that is still running, or some other application.

Also this error:

09-Jun-2018 13:44:16.554 SEVERE [Catalina-startStop-1] org.apache.catalina.startup.HostConfig.start Unable to create directory for deployment: /opt/atlassian/jira/conf/Catalina/localhost

Is an indication that the user you are starting Jira with does not have permissions needed for Jira to start correctly. In which case the KB How to fix JIRA Directories permission in Linux might help. But this is only really needed if you are starting Jira with a different linux user than jira is normally started with.

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server