Cannot change ComponentManager status from NOT_STARTED to PLUGINSYSTEM_STARTED

Since we've upgraded our server from Win 2012R2 to Win 2016 every time the server is restarted, JIRA Server presents the message "Cannot change ComponentManager status from NOT_STARTED to PLUGINSYSTEM_STARTED". I have to restart the Jira Service to keep it working again.

I had already changed the Startup Type from "Automatic" to "Automatic (delayed start)", no changes on this strange behaviour.

Is anybody else facing the same issue? Any hints?

1 answer

Inspecting the logfile, we've found this message:

JIRA-Bootstrap ERROR      [c.a.jira.startup.ComponentContainerLauncher] A fatal error occurred during initialisation. JIRA has been locked.
com.atlassian.plugin.osgi.container.OsgiContainerException: Unable to clean the cache directory: C:\Program Files\Atlassian\Application Data\JIRA\plugins\.osgi-plugins\felix

The strange thing is that a restart on service succeeds, without cnahging any security permissions on this folder.

 

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Julia Dillon
Posted Tuesday in Jira

Tell us how your team runs on Jira!

Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...

199 views 1 18
Join discussion

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