nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira service not starting correctly after basic config

Ilai Schechter

Hey There,

Got a vanilla Jira core and SD Version : 7.5.0 - and when checking the status the jira service, the following comes up:

[root@CAA-JIRA01 ~]# systemctl status jira
● jira.service - (null)
Loaded: loaded (/etc/rc.d/init.d/jira; bad; vendor preset: disabled)
Active: active (running) since Tue 2017-10-10 15:47:13 BST; 2s ago
Docs: man:systemd-sysv-generator(8)
Process: 4121 ExecStop=/etc/rc.d/init.d/jira stop (code=exited, status=1/FAILURE)
Process: 4165 ExecStart=/etc/rc.d/init.d/jira start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/jira.service
└─4201 /opt/atlassian/jira/jre//bin/java -Djava.util.logging.config.file=/opt/atlassian/jira/conf/lo...
Oct 10 15:47:13 CAA-JIRA01 jira[4165]: .MMMMMM. .MMMMM~.
Oct 10 15:47:13 CAA-JIRA01 jira[4165]: .MMMMMN .MMMMM?.
Oct 10 15:47:13 CAA-JIRA01 jira[4165]: Atlassian JIRA
Oct 10 15:47:13 CAA-JIRA01 jira[4165]: Version : 7.5.0
Oct 10 15:47:13 CAA-JIRA01 jira[4165]: If you encounter issues starting or stopping JIRA, please see the T...Guide
Oct 10 15:47:13 CAA-JIRA01 jira[4165]: Server startup logs are located in /opt/atlassian/jira/logs/catalina.out
Oct 10 15:47:13 CAA-JIRA01 jira[4165]: Existing PID file found during start.
Oct 10 15:47:13 CAA-JIRA01 jira[4165]: Removing/clearing stale PID file.
Oct 10 15:47:13 CAA-JIRA01 systemd[1]: Started (null).
Oct 10 15:47:13 CAA-JIRA01 jira[4165]: Tomcat started.
Hint: Some lines were ellipsized, use -l to show in full.

When starting jira, the following:

Using CATALINA_PID: /opt/atlassian/jira/work/catalina.pid
Existing PID file found during start.
Removing/clearing stale PID file.
Tomcat started.

Tried removing the catalina.pid when jira was off, and rebooting box, but all i get is a tomcat page when i go tho that URL. - any advice is welcome!

Accepted answers

Ilai Schechter

Got it fixed!

Ran

sudo systemctl restart jira.service

and
systemctl reload-or-restart jira.service

[root@server] systemctl status jira.service
● jira.service - (null)
   Loaded: loaded (/etc/rc.d/init.d/jira; bad; vendor preset: disabled)
   Active: active (running) since Wed 2017-10-11 14:09:26 BST; 15s ago
     Docs: man:systemd-sysv-generator(8)
Process: 10909 ExecStop=/etc/rc.d/init.d/jira stop (code=exited, status=0/SUCCESS)
Process: 10982 ExecStart=/etc/rc.d/init.d/jira start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/jira.service
           └─11016 /opt/atlassian/jira/jre//bin/java -Djava.util.logging.conf...

Oct 11 14:09:26 CAA-JIRA01 jira[10982]: .IMMMM..NMMMMMD.
Oct 11 14:09:26 CAA-JIRA01 jira[10982]: .8MMMMM: :NMMMMN.
Oct 11 14:09:26 CAA-JIRA01 jira[10982]: .MMMMMM.   .MMMMM~.
Oct 11 14:09:26 CAA-JIRA01 jira[10982]: .MMMMMN    .MMMMM?.
Oct 11 14:09:26 CAA-JIRA01 jira[10982]: Atlassian JIRA
Oct 11 14:09:26 CAA-JIRA01 jira[10982]: Version : 7.5.0
Oct 11 14:09:26 CAA-JIRA01 jira[10982]: If you encounter issues starting or ...e
Oct 11 14:09:26 CAA-JIRA01 jira[10982]: Server startup logs are located in /...t
Oct 11 14:09:26 CAA-JIRA01 jira[10982]: Tomcat started.
Oct 11 14:09:26 CAA-JIRA01 systemd[1]: Started (null).
Hint: Some lines were ellipsized, use -l to show in full.

this cleared up the config!

Shout out to Gonchik Tsymzhitov and the gude i googled from DO https://www.digitalocean.com/community/tutorials/how-to-use-systemctl-to-manage-systemd-services-and-units

All comments

Ilai Schechter

Tried following this article, and everything seemed to run fine, but i still have issues
https://community.atlassian.com/t5/Jira-questions/jira-startup-script-in-etc-init-d-fails/qaq-p/317923

Gonchik Tsymzhitov

Hi!

Have you reviewed your systemd file below this thread?

https://community.atlassian.com/t5/Questions/Instead-of-init-d-use-systemctl/qaq-p/108783

Cheers,

Gonchik Tsymzhitov

Hi!

Have you reviewed your systemd file below this thread?

https://community.atlassian.com/t5/Questions/Instead-of-init-d-use-systemctl/qaq-p/108783

Cheers,

Gonchik Tsymzhitov

Nic Brough -Adaptavist-

The logs you've shown imply things starting up ok, but Jira maybe not running.

Could you look at the application log please? <jira home>/logs/atlassian-jira.log

Ilai Schechter

Hey, cant see that log - any of the below?

jira logs.PNG

Ilai Schechter

This seems to be using Stash - i dont use this?

Ilai Schechter

10-Oct-2017 22:37:57.500 SEVERE [main] org.apache.catalina.core.StandardService.startInternal Failed to start connec$
org.apache.catalina.LifecycleException: Failed to start component [Connector[HTTP/1.1-8080]]
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167)
        at org.apache.catalina.core.StandardService.startInternal(StandardService.java:440)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
        at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:791)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:655)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:355)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:495)
Caused by: org.apache.catalina.LifecycleException: service.getName(): "Catalina"; Protocol handler start failed
        at org.apache.catalina.connector.Connector.startInternal(Connector.java:976)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
        ... 11 more
Caused by: java.net.BindException: Address already in use
        at sun.nio.ch.Net.bind0(Native Method)
        at sun.nio.ch.Net.bind(Net.java:433)
        at sun.nio.ch.Net.bind(Net.java:425)
        at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
        at org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:228)
        at org.apache.tomcat.util.net.AbstractEndpoint.start(AbstractEndpoint.java:874)
        at org.apache.coyote.AbstractProtocol.start(AbstractProtocol.java:590)
        at org.apache.catalina.connector.Connector.startInternal(Connector.java:969)
        ... 12 more

10-Oct-2017 22:37:57.500 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 5095 ms
10-Oct-2017 22:37:57.502 SEVERE [main] org.apache.catalina.core.StandardServer.await StandardServer.await: create[lo$
java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
at java.net.ServerSocket.bind(ServerSocket.java:375)
at java.net.ServerSocket.<init>(ServerSocket.java:237)
at org.apache.catalina.core.StandardServer.await(StandardServer.java:440)
at org.apache.catalina.startup.Catalina.await(Catalina.java:743)
at org.apache.catalina.startup.Catalina.start(Catalina.java:689)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:355)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:495)
10-Oct-2017 22:37:57.502 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio-808$
10-Oct-2017 22:37:57.502 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service Catalina
10-Oct-2017 22:38:09.825 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearRefer$
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:502)
org.objectweb.jonas_timer.TimerManager.batch(TimerManager.java:193)
org.objectweb.jonas_timer.Batch.run(TimerManager.java:65)
10-Oct-2017 22:38:09.827 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearRefer$
java.lang.Thread.sleep(Native Method)
org.objectweb.jonas_timer.TimerManager.clock(TimerManager.java:142)
org.objectweb.jonas_timer.Clock.run(TimerManager.java:46)
10-Oct-2017 22:38:09.837 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio-808$
10-Oct-2017 22:38:09.838 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-ni$

Ilai Schechter

If it helps, this has just started happening in the EXACT same way on the confluence server on the same subnet. Could it be that these servers are being affected by the nginx reverse proxy i have set up?

Here is the error from the confluence server:

    systemctl status confluence
    ● confluence.service - (null)
       Loaded: loaded (/etc/rc.d/init.d/confluence; bad; vendor preset: disabled)
       Active: failed (Result: exit-code) since Tue 2017-10-10 23:17:11 BST; 2min 43s ago
         Docs: man:systemd-sysv-generator(8)
      Process: 10864 ExecStop=/etc/rc.d/init.d/confluence stop (code=exited, status=1/FAILURE)
      Process: 1111 ExecStart=/etc/rc.d/init.d/confluence start (code=exited, status=0/SUCCESS)

    Oct 10 23:17:11 CAA-CON01 confluence[10864]: Server startup logs are located in /opt/atlassian/confluence/log...a.out
    Oct 10 23:17:11 CAA-CON01 confluence[10864]: ----------------------------------------------------------------...-----
    Oct 10 23:17:11 CAA-CON01 confluence[10864]: Using Java: /opt/atlassian/confluence/jre//bin/java
    Oct 10 23:17:11 CAA-CON01 confluence[10864]: 2017-10-10 23:17:11,905 INFO [main] [atlassian.confluence.bootst...uired
    Oct 10 23:17:11 CAA-CON01 confluence[10864]: ----------------------------------------------------------------...-----
    Oct 10 23:17:11 CAA-CON01 confluence[10864]: $CATALINA_PID was set but the specified file does not exist. Is ...rted.
    Oct 10 23:17:11 CAA-CON01 systemd[1]: confluence.service: control process exited, code=exited status=1
    Oct 10 23:17:11 CAA-CON01 systemd[1]: Stopped (null).
    Oct 10 23:17:11 CAA-CON01 systemd[1]: Unit confluence.service entered failed state.
    Oct 10 23:17:11 CAA-CON01 systemd[1]: confluence.service failed.
    Hint: Some lines were ellipsized, use -l to show in full.

and here is what it shows on the page:

    A system error has occurred — our apologies!

    For immediate troubleshooting, consult our (link) for a solution.

    If you would like to receive support from Atlassian's support team, ask your (link) to create a support issue on (Atlassian link) with the following information:

        a description of your problem and what you were doing at the time it occurred
        a copy of the error and system information found below
        a copy of the application logs (if possible).

    Your Confluence administrator can use the support request form (link) to create a support ticket which will include this information.

    We will respond as promptly as possible.
    Thank you!

    Return to site homepage (link)

    The SystemInformationService could not be retrieved from the container. Therefore very limited information is available in this error report.
    The SystemInformationService could not be retrieved due to the following error: java.lang.IllegalStateException: Spring Application context has not been set
    Cause

    com.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.IllegalStateException: Spring Application context has not been set
        at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:149)

    caused by: java.lang.IllegalStateException: Spring Application context has not been set
        at com.atlassian.spring.container.SpringContainerContext.getComponent(SpringContainerContext.java:48)
    Stack Trace:[hide]

    com.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.IllegalStateException: Spring Application context has not been set
       at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:149)
       at com.atlassian.util.concurrent.LazyReference.get(LazyReference.java:112)
       at com.atlassian.confluence.setup.webwork.ConfluenceXWorkTransactionInterceptor.getTransactionManager(ConfluenceXWorkTransactionInterceptor.java:28)
       at com.atlassian.xwork.interceptors.XWorkTransactionInterceptor.intercept(XWorkTransactionInterceptor.java:56)
       at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:165)

and 300 more


    Referer URL

    Unknown

Gonchik Tsymzhitov

Hi!

Could you check stop scripts?

Looks like a problem with stopping jira config.

Caused by: java.net.BindException: Address already in use

As I understand service starts good, but can not stop on restart, stop command.

Could you provide jira service config from systemd?

Thanks

Cheers,

Gonchik Tsymzhitov

Ilai Schechter

Got it fixed!

Ran

sudo systemctl restart jira.service

and
systemctl reload-or-restart jira.service

[root@server] systemctl status jira.service
● jira.service - (null)
   Loaded: loaded (/etc/rc.d/init.d/jira; bad; vendor preset: disabled)
   Active: active (running) since Wed 2017-10-11 14:09:26 BST; 15s ago
     Docs: man:systemd-sysv-generator(8)
Process: 10909 ExecStop=/etc/rc.d/init.d/jira stop (code=exited, status=0/SUCCESS)
Process: 10982 ExecStart=/etc/rc.d/init.d/jira start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/jira.service
           └─11016 /opt/atlassian/jira/jre//bin/java -Djava.util.logging.conf...

Oct 11 14:09:26 CAA-JIRA01 jira[10982]: .IMMMM..NMMMMMD.
Oct 11 14:09:26 CAA-JIRA01 jira[10982]: .8MMMMM: :NMMMMN.
Oct 11 14:09:26 CAA-JIRA01 jira[10982]: .MMMMMM.   .MMMMM~.
Oct 11 14:09:26 CAA-JIRA01 jira[10982]: .MMMMMN    .MMMMM?.
Oct 11 14:09:26 CAA-JIRA01 jira[10982]: Atlassian JIRA
Oct 11 14:09:26 CAA-JIRA01 jira[10982]: Version : 7.5.0
Oct 11 14:09:26 CAA-JIRA01 jira[10982]: If you encounter issues starting or ...e
Oct 11 14:09:26 CAA-JIRA01 jira[10982]: Server startup logs are located in /...t
Oct 11 14:09:26 CAA-JIRA01 jira[10982]: Tomcat started.
Oct 11 14:09:26 CAA-JIRA01 systemd[1]: Started (null).
Hint: Some lines were ellipsized, use -l to show in full.

this cleared up the config!

Shout out to Gonchik Tsymzhitov and the gude i googled from DO https://www.digitalocean.com/community/tutorials/how-to-use-systemctl-to-manage-systemd-services-and-units