Local installation of Jira sofware no longer functional: http://localhost:8080/secure/errors.jsp

[Karl Van Lierde]

I have a trial version of Jira software 7.4.6 installed on my PC since 2 weeks. I worked with it everyday and it went OK. However now I am unable to launch Jira: the only info I have is => http://localhost:8080/secure/errors.jsp.

I tried after restarting my PC, same result.

Please help!

[Paula Pelanda]

Hola! en mi caso me arroja lo siguiente en el log:

2023-11-08 11:14:14,407-0300 http-nio-8080-exec-2 WARN anonymous 674x2x1 - 172.18.18.23 /secure/errors.jsp [c.a.jira.security.JiraSecurityFilter] Rejecting security-sensitive request that bypassed Johnson filter: /secure/errors.jsp
2023-11-08 11:14:14,423-0300 http-nio-8080-exec-2 ERROR anonymous 674x2x1 - 172.18.18.23 /secure/errors.jsp [c.a.j.util.thread.JiraThreadLocalUtils] Error when performing thread local operation: Incompatible magic value 1751279982 in class file com/atlassian/jira/issue/index/IndexDirectoryFactory$Name$1

intenté borrando la carpeta de los indices para que los regenere, sin exito (capaz no lo haga bien?)  por otro lado borra dos archivos de la chache y tampoco.

Como se corrige la propiedad?

Aguardo sugerencias! gracias!

[Jobin Kuruvilla [Adaptavist]]

What do you see in the application logs (atlassian-jira.log) file?

[Karl Van Lierde]

In the meantime I restarted my PC again and Jira is up and running;

However in the log I found:

2018-02-22 13:13:19,506 JIRA-Bootstrap ERROR      [c.a.jira.health.HealthChecks] We couldn't start JIRA
2018-02-22 13:13:19,506 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.
    See our documentation for more information on contacting our support team and creating a support zip.
2018-02-22 13:13:19,506 JIRA-Bootstrap WARN      [c.a.jira.startup.DatabaseLauncher]

Do I have to look for anything in particular because I found several errors?

[Karl Van Lierde]

2018-02-22 13:12:43,943 http-nio-8080-exec-1 ERROR anonymous 792x1x1 - 127.0.0.1 / [c.atlassian.instrumentation.Instrument] Unable to snapshot thread local operations (implementation of OpTimerFactory is not a ThreadLocalOpTimerFactory): null

[Jobin Kuruvilla [Adaptavist]]

Is this snippet from the catalina logs? Can you check atlassian-jira.log file under JIRA_HOME/log folder? See if there are any logs during the startup.

[Karl Van Lierde]

The snippet is from C:\Program Files\Atlassian\Application Data\JIRA\log\atlassian-jira.log

In the catalina log (C:\Program Files\Atlassian\JIRA\logs) I find things like:

23-Feb-2018 10:03:52.109 WARNING [http-nio-8080-exec-2] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI http://localhost:8080/rest/issueNav/latest/preferredSearchLayout, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected.

And in atlassian-jira-gc-2018-02-22_13-34-20.log.0

2018-02-22T13:35:27.051+0100: 67.841: [GC (Allocation Failure) [PSYoungGen: 65536K->10747K(76288K)] 65536K->12168K(251392K), 0.9317366 secs] [Times: user=0.17 sys=0.02, real=0.94 secs]

[Jobin Kuruvilla [Adaptavist]]

Are those the only error logs in atlassian-jira.log? It seems JIRA failed to start but they should be some errors leading to it. Maybe check all the way to the start up logs.

[Karl Van Lierde]

After starup the first error is:

2018-02-22 13:12:43,943 http-nio-8080-exec-1 ERROR anonymous 792x1x1 - 127.0.0.1 / [c.atlassian.instrumentation.Instrument] Unable to snapshot thread local operations (implementation of OpTimerFactory is not a ThreadLocalOpTimerFactory): null

And then:

2018-02-22 13:13:19,037 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
 at com.atlassian.plugin.osgi.container.impl.DefaultOsgiPersistentCache.validate(DefaultOsgiPersistentCache.java:81)

Caused by: java.io.IOException: Unable to delete directory C:\Program Files\Atlassian\Application Data\JIRA\plugins\.osgi-plugins\felix\felix-cache\bundle83.
 at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1337)

[Nic Brough -Adaptavist-]

This is usually caused by running it as the wrong user, then restarting it as the right one.  When run as the wrong user, that user takes ownership of some of the files, rendering the correct user unable to read/write them.

Stop the system, correct the ownership and restart it as the right user.

[Karl Van Lierde]

OK. Thanks.

[Nic Brough -Adaptavist-]

Can't tell you much without the error message you see on that page.

[Karl Van Lierde]

Well internet explorer does not show any message so I tried in Chrome: HTTP ERROR 503

[Nic Brough -Adaptavist-]

That's not what you said earlier - the errors.jsp will report on an internal error.  503 is a different thing meaning the server is overloaded or in maintenance and unable to serve up the errors.jsp in most cases.

Could you explain which one you are getting, or if it is the unusual 503 inside errors.jsp?