Can't access JIRA standalone localhost:8080 Edited

Last night our sys admins did their monthly patching of our Linux servers, I imagine that after patching and rebooting this issue was caused. I can no longer display the jira web page:  http://localhost:8080, I get a 404 not found.

I've dug into the logs and found these errors:


[jira@servername log]$ tail -200 atlassian-jira.log | grep ERROR
2018-01-18 19:55:25,661 ThreadPoolAsyncTaskExecutor::Thread 12 ERROR      [o.e.g.b.e.i.util.concurrent.RunnableTimedExecution] Closing runnable for context NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.jira.plugins.jira-admin-helper-plugin, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the thread still hangs
2018-01-18 19:55:25,663 ThreadPoolAsyncTaskExecutor::Thread 12 ERROR      [o.e.g.b.e.internal.support.ExtenderConfiguration] Application context refresh failed (NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.jira.plugins.jira-admin-helper-plugin, config=osgibundle:/META-INF/spring/*.xml))
2018-01-18 19:55:25,667 ThreadPoolAsyncTaskExecutor::Thread 12 ERROR      [o.e.g.b.e.i.dependencies.startup.DependencyWaiterApplicationContextExecutor] Unable to create application context for [com.atlassian.jira.plugins.jira-admin-helper-plugin], unsatisfied dependencies: none

What is happening here? Is it a Java issue or did something else change?

Thank you.

2 answers

Something else I found in the log at a prior time:

 

java.lang.IllegalStateException: Unable to create a tracker when osgi is not running

0 vote

What do you see at the end of the JIRA logs? Did it start fine? Is it still running?

If so, it might be an issue with the port being blocked. Maybe a firewall that was not running earlier is running now. You can check iptables, selinux etc as well.

Hi Jobin,

Even though the ../start-jira.sh script runs without errors, this is what I'm seeing at the end of the log:

        at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:103)
        at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:157)
        at java.lang.Thread.run(Thread.java:745)
2018-01-18 19:59:57,655 localhost-startStop-1 INFO      [c.a.jira.startup.DefaultJiraLauncher] Stopping launchers
2018-01-18 19:59:57,678 localhost-startStop-1 INFO      [c.a.plugin.manager.DefaultPluginManager] Preparing to shut down the plugin system
2018-01-18 19:59:57,681 localhost-startStop-1 INFO      [c.a.plugin.manager.DefaultPluginManager] Shutting down the plugin system
2018-01-18 19:59:57,969 localhost-startStop-1 WARN      [c.a.plugin.servlet.DefaultServletModuleManager] PluginController passed via the PluginFrameworkShutdownEvent did not match that passed via PluginFrameworkStartedEvent
2018-01-18 19:59:58,383 Gemini Blueprint context shutdown thread2 INFO      [c.a.j.plugins.monitor.MonitoringScheduler] Unscheduling metrics collector...
2018-01-18 19:59:58,384 Gemini Blueprint context shutdown thread2 INFO      [c.a.j.plugins.monitor.MonitorLauncher] Stopped JIRA monitoring
2018-01-18 19:59:58,990 localhost-startStop-1 INFO      [c.a.jira.startup.DefaultJiraLauncher] JIRA launchers stopped in 1332ms

 

I have not yet checked the SELinux, but when I run a netstat -noa I do see port 8080 listening.

By the way, the version of Jira I'm running is 7.5.1, and the version of java on this server is:

openjdk version "1.8.0_151"
OpenJDK Runtime Environment (build 1.8.0_151-b12)
OpenJDK 64-Bit Server VM (build 25.151-b12, mixed mode)

Java was updated during the patching.

Thank you.

I see that you are checking only the last 200 lines of atlassian-jira.log file. Can you go further up and check where the errors start?

Hi the errors repeat themselves, this is from every restart I've done so far, the log error dates and times repeat with every restart of the service. The entries I've posted so far are from the /var/atlassian/application-data/jira/log/atlassian-jira.log log file.

These below are from the catalina.out file under /opt/atlassian/jira/logs, which also repeat again and again:

2018-01-19 10:01:15,892 JIRA-Bootstrap ERROR      [c.a.plugin.loaders.ScanningPluginLoader] Unable to deploy plugin 'com.atlassian.jira.plugins.jira-software-monitor-plugin' from 'Unit: /var/atlassian/application-data/jira/plugins/installed-plugins/jira-software-monitor-plugin-0.1.0-D20150923T085539.jar (1508190750000)'.
2018-01-19 10:01:15,892 JIRA-Bootstrap ERROR      [c.a.plugin.loaders.ScanningPluginLoader] Because of the following exception:
2018-01-19 10:01:15,895 JIRA-Bootstrap ERROR      [c.a.plugin.loaders.ScanningPluginLoader] Unable to deploy plugin 'com.atlassian.jira.plugins.jira-software-plugin' from 'Unit: /var/atlassian/application-data/jira/plugins/installed-plugins/jira-software-plugin-2.2.0.jar (1508190750000)'.
2018-01-19 10:01:15,895 JIRA-Bootstrap ERROR      [c.a.plugin.loaders.ScanningPluginLoader] Because of the following exception:
2018-01-19 10:01:15,909 JIRA-Bootstrap ERROR      [c.a.plugin.loaders.ScanningPluginLoader] Unable to deploy plugin 'com.atlassian.jira.plugins.jira-transition-triggers-plugin' from 'Unit: /var/atlassian/application-data/jira/plugins/installed-plugins/jira-transition-triggers-plugin-4.0.10.jar (1508190750000)'.
2018-01-19 10:01:15,909 JIRA-Bootstrap ERROR      [c.a.plugin.loaders.ScanningPluginLoader] Because of the following exception:
2018-01-19 10:01:15,972 JIRA-Bootstrap ERROR      [c.a.jira.upgrade.PluginSystemLauncher] A fatal error occured during initialisation. JIRA has been locked.
2018-01-19 10:01:15,997 JIRA-Bootstrap ERROR      [c.a.jira.health.HealthChecks] We couldn't start JIRA
2018-01-19 10:01:15,997 JIRA-Bootstrap ERROR      [c.a.jira.health.HealthChecks] An error occurred while trying to start JIRA. We can't give you any more detail right now, we suggest checking the logs for more detail and contacting our support team.
2018-01-19 10:01:17,800 JIRA-Bootstrap ERROR      [c.a.jira.health.HealthChecks] Could not execute health check, DatabaseConfigurationManager not available.
2018-01-19 10:01:17,800 JIRA-Bootstrap ERROR      [c.a.jira.health.HealthChecks] Could not execute health check, DatabaseConfigurationManager not available.
2018-01-19 10:01:17,801 JIRA-Bootstrap ERROR      [c.a.jira.startup.DefaultJiraLauncher] JIRA has failed to start because of the following errors: [(Event: Level = (EventLevel: fatal) , Key = (EventType: startup-unexpected) , Desc = We couldn't start JIRA , Exception = An error occurred while trying to start JIRA. We can't give you any more detail right now, we suggest checking the logs for more detail and contacting our support team.<br/>See our documentation for more information on contacting our support team and creating a support zip.), (Event: Level = (EventLevel: fatal) , Key = (EventType: database) , Desc = Could not execute health check, DatabaseConfigurationManager not available. , Exception = ]

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 May 21, 2018 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...

1,221 views 10 18
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