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 Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,147 views 13 19
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot