software can not launch

[Fei Chen]

I am deploying JIRA in a docker container. It works fine for months. However it stops working few days ago. I am not sure whether it has relationship with the license expired problem. So I renew my license yesterday. Now I get my new license, while I still don’t know how to launch the JIRA so that I have the opportunity to input the new license. Following are some output of the JIRA when I try to access JIRA in chrome.

2020-02-22 14:48:33,616 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Memory Usage:
---------------------------------------------------------------------------------
Heap memory : Used: 658 MiB. Committed: 1120 MiB. Max: 1994 MiB
Non-heap memory : Used: 256 MiB. Committed: 280 MiB. Max: 1536 MiB
---------------------------------------------------------------------------------
TOTAL : Used: 914 MiB. Committed: 1400 MiB. Max: 3530 MiB
---------------------------------------------------------------------------------
2020-02-22 14:48:33,949 Caesium-1-4 INFO ServiceRunner [c.a.jira.startup.IndexRecoveryLauncher] Running start-index-recovery
2020-02-22 14:48:34,350 Caesium-1-4 INFO ServiceRunner [c.a.jira.startup.IndexRecoveryLauncher] Indexing issues from=2020-02-17 02:25:35.0 to=Mon Feb 17 02:25:35 GMT 2020 (time span of 750ms)
2020-02-22 14:48:34,633 Caesium-1-2 INFO [c.a.jira.startup.CacheWarmerLauncher] Warming up 3 caches.
2020-02-22 14:48:35,992 Caesium-1-4 INFO ServiceRunner [c.a.jira.startup.IndexRecoveryLauncher] Progress=60%, task=Recovering, message=Recovered added and updated issues
2020-02-22 14:48:36,104 Caesium-1-4 INFO ServiceRunner [c.a.jira.startup.IndexRecoveryLauncher] Progress=80%, task=Recovering, message=Cleaned removed issues
2020-02-22 14:48:36,105 Caesium-1-4 INFO ServiceRunner [c.a.jira.startup.IndexRecoveryLauncher] Finished start-index-recovery
2020-02-22 14:48:50,289 Caesium-1-2 INFO [c.a.jira.startup.CacheWarmerLauncher] Warmed cache(s) in 15652 ms.
2020-02-22 14:49:26,856 Caesium-1-1 INFO ServiceRunner [c.a.jira.upgrade.UpgradeScheduler] Running scheduled upgrades
2020-02-22 14:49:26,867 Caesium-1-1 INFO ServiceRunner [c.a.jira.upgrade.LoggingUpgradeService] run upgrades has started
2020-02-22 14:49:26,936 Caesium-1-1 INFO ServiceRunner [c.a.j.upgrade.util.BuildNumberDao] Setting current build number to 802002
2020-02-22 14:49:26,964 Caesium-1-1 INFO ServiceRunner [c.a.jira.upgrade.UpgradeIndexManager] There is no reindex requests of type [IMMEDIATE, DELAYED] so none will be run
2020-02-22 14:49:26,964 Caesium-1-1 INFO ServiceRunner [c.a.j.upgrade.util.BuildNumberDao] Setting current version to 8.2.2
2020-02-22 14:49:26,979 Caesium-1-1 INFO ServiceRunner [c.a.j.upgrade.util.BuildNumberDao] Setting downgrade version to 7.1.2
2020-02-22 14:49:27,005 Caesium-1-1 INFO ServiceRunner [c.a.jira.upgrade.LoggingUpgradeService] run upgrades has finished successfully, and took 139 milliseconds to process.
2020-02-22 14:49:27,006 Caesium-1-1 INFO ServiceRunner [c.a.jira.upgrade.UpgradeScheduler] JIRA upgrades completed successfully
2020-02-22 14:49:27,016 Caesium-1-1 INFO ServiceRunner [c.a.jira.upgrade.UpgradeScheduler] Plugins upgrades completed successfully
2020-02-22 14:49:27,018 Caesium-1-1 INFO ServiceRunner [c.a.jira.upgrade.UpgradeIndexManager] Reindexing is not allowed after this upgrade and there is no immediate reindex requests
22-Feb-2020 14:50:04.421 INFO [http-nio-8080-exec-1] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header
Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.
java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:430)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:684)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:808)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1498)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Unknown Source)

[Andy Heinzer]

Hi,

Sorry to hear that there are problems with getting Jira running here. I understand you have recently renewed a license, but are so far unable to apply this new license to Jira. I can see that the log snippet you included is indicative of trying to access Jira using HTTPS on an endpoint that is not yet HTTPS enabled.

So I'd be interested to learn more about the address and port number you are trying to use to access this Jira site. I understand if you do not wish to post such data here directly. But the work-around to that specific error might be as simple as trying to make a request to the Jira site using http instead of https here.

If that doesn't help, I'd be interested to know more about your configuration to better understand what might be causing your problems with accessing Jira. In this case, I would be interested to see the contents of your

• $JIRAINSTALL/logs/catalina.out
• $JIRAINSTALL/conf/server.xml file.

The catalina.out file is created by the Tomcat webserver Jira is using. It contains startup logs for Jira that could be helpful here.  This xml file tells us what ports/addresses Jira will listen to when it starts up.  By default it has port 8080 for a single connector, but if you're using Jira in conjunction with a reverse proxy, then you might have different connector settings here so that Jira can understand how its traffic is expected to be managed here. 

If you could zip these files up, and then you could upload these files to a service like dropbox, google drive, or alike, and then share with us the link to these files.  I would be interested to take a closer look at your environment here to see what can learn to help troubleshoot this problem.

Regards,

Andy