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; } } }

can't start jira 4.1. after server reboot.

n-rastabarova

If anyone can help with restart of jira 4.1. after server reboot? Any advice highly appreciated! thank you!

Please find details below:
- java, jira, ubuntu versions
- error from catalina.out (atlassian-jira.log doesn't have new data)
- files in CATALINA_HOME dir

java -version
java version "1.6.0_22"

JIRA Standalone Edition
Version : 4.1.1

Distributor ID: Ubuntu
Description: Ubuntu 10.04.1 LTS
Release: 10.04
Codename: lucid

ubuntu@ip-X-X-X-X:~/jira$ /etc/init.d/jira start

JIRA Standalone Edition
Version : 4.1.1

Detecting JVM PermGen support...
PermGen switch is supported. Setting to 256m
If you encounter issues starting or stopping JIRA Standalone Edition, please see the Troubleshooting guide at http://confluence.atlassian.com/display/JIRA/Installation+Troubleshooting+Guide

Using CATALINA_BASE: /opt/jira.new
Using CATALINA_HOME: /opt/jira.new
Using CATALINA_TMPDIR: /opt/jira.new/temp
Using JRE_HOME: /usr/lib/jvm/java-6-sun

ubuntu@ip-X-X-X-X:~/jira$ cat /opt/jira.new/logs/catalina.out
java.lang.ClassNotFoundException: org.apache.catalina.startup.Catalina
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:215)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:390)

ubuntu@ip-X-X-X-X:~/jira$ ll /opt/jira.new
lrwxrwxrwx 1 root root 20 Feb 9 2012 /opt/jira.new -> /media/jira/jira.new/
ubuntu@ip-X-X-X-X:~/jira$ ll /media/jira/jira.new
total 68
drwxr-xr-x 10 jira jira 4096 Aug 16 15:32 ./
drwxr-xr-x 3 root root 4096 Aug 16 15:30 ../
-rwxr-xr-x 1 jira jira 0 Jan 19 2011 .jira-home.lock*
drwxr-xr-x 13 jira jira 4096 Feb 1 2011 atlassian-jira/
-rwxr-xr-x 1 jira jira 26698 Sep 24 2010 atlassian-jira.log*
drwxr-xr-x 2 jira jira 4096 Feb 1 2011 attachments/
drwxr-xr-x 2 jira jira 4096 Feb 1 2011 backup/
drwxr-xr-x 2 jira jira 4096 Aug 16 09:22 bin/
drwxr-xr-x 3 jira jira 4096 Feb 1 2011 caches/
drwxr-xr-x 2 jira jira 4096 Aug 16 14:04 conf/
drwxr-xr-x 3 jira jira 4096 Feb 1 2011 data/
drwxrwxrwx 2 jira jira 4096 Aug 17 09:16 logs/
ubuntu@ip-X-X-X-X:~/jira$ ll /media/jira/jira.new/bin
total 668
drwxr-xr-x 2 jira jira 4096 Aug 16 09:22 ./
drwxr-xr-x 10 jira jira 4096 Aug 16 15:32 ../
-rwxr-xr-x 1 jira jira 17508 Jun 3 2010 bootstrap.jar*
-rwxr-xr-x 1 jira jira 2374 Jun 3 2010 catalina-tasks.xml*
-rwxr-xr-x 1 jira jira 10652 Jun 3 2010 catalina.bat*
-rwxr-xr-x 1 jira jira 13573 Jun 3 2010 catalina.sh*
-rwxr-xr-x 1 jira jira 9341 Jun 3 2010 commons-daemon.jar*
-rwxr-xr-x 1 jira jira 917 Jun 3 2010 config.bat*
-rwxr-xr-x 1 jira jira 1032 Jun 3 2010 config.sh*
-rwxr-xr-x 1 jira jira 1342 Jun 3 2010 cpappend.bat*
-rwxr-xr-x 1 jira jira 2104 Jun 3 2010 digest.bat*
-rwxr-xr-x 1 jira jira 1624 Jun 3 2010 digest.sh*
-rwxr-xr-x 1 jira jira 2039 Jun 3 2010 jirabanner.txt*
-rwxr-xr-x 1 jira jira 74398 Jun 3 2010 jsvc.tar.gz*
-rwxr-xr-x 1 jira jira 229 Jun 3 2010 permgen.bat*
-rwxr-xr-x 1 jira jira 950 Jun 3 2010 permgen.sh*
-rwxr-xr-x 1 jira jira 585 Jun 3 2010 permgenservice.bat*
-rwxr-xr-x 1 jira jira 5100 Jun 3 2010 service.bat*
-rwxr-xr-x 1 jira jira 3452 Jun 3 2010 setclasspath.bat*
-rwxr-xr-x 1 jira jira 4556 Jun 3 2010 setclasspath.sh*
-rwxr-xr-x 1 jira jira 3281 Jun 3 2010 setenv.bat*
-rwxr-xr-x 1 jira jira 2076 Jun 3 2010 setenv.sh*
-rwxr-xr-x 1 jira jira 2096 Jun 3 2010 shutdown.bat*
-rwxr-xr-x 1 jira jira 1563 Jun 3 2010 shutdown.sh*
-rwxr-xr-x 1 jira jira 2097 Jun 3 2010 startup.bat*
-rwxr-xr-x 1 jira jira 1956 Jun 3 2010 startup.sh*
-rwxr-xr-x 1 jira jira 19399 Jun 3 2010 tomcat-juli.jar*
-rwxr-xr-x 1 jira jira 240128 Jun 3 2010 tomcat-native.tar.gz*
-rwxr-xr-x 1 jira jira 57344 Jun 3 2010 tomcat6.exe*
-rwxr-xr-x 1 jira jira 98304 Jun 3 2010 tomcat6w.exe*
-rwxr-xr-x 1 jira jira 3189 Jun 3 2010 tool-wrapper.bat*
-rwxr-xr-x 1 jira jira 3291 Jun 3 2010 tool-wrapper.sh*
-rwxr-xr-x 1 jira jira 2101 Jun 3 2010 version.bat*
-rwxr-xr-x 1 jira jira 1567 Jun 3 2010 version.sh*

Accepted answers

All comments

Nic Brough -Adaptavist-

You need to read through more of the error in the catalina.out, there's not enough of it in your post to start to work out what might be wrong.

n-rastabarova

Ohh ok thank you. we will now see what we can dig out more.
But what we posted above was all we could find in that catalina.out.

Is there anywhere else we should look for an errors?

Nic Brough -Adaptavist-

Your catalina.out is a lot longer than the snippet you posted.

However, you've not explained "won't start". Have you checked it is running? If it is, and "won't start" actually means "won't respond to the browser", then check <jira home>/logs for other logs.

n-rastabarova

We have just checked.. and unfortunately there's no other info in catalina.out

process is not running
ps aux | grep jira
ubuntu 9541 0.0 0.0 1884 660 pts/0 S+ 12:11 0:00 grep --color=auto jira

nothing are on 8080 port (but port was opened via aws console)
sudo netstat -tulpn | grep :8080

and browser doesn't respond

bishoybt

Hi Natalie,

Can you please share the problem root cause and the solution? I am facing the same issue, I can start jira using sudo service jira start and it works fine, but when the PC restarts, the service is not up.

Nic Brough -Adaptavist-

That sounds like you haven't got it enabled in system start up. What OS and distribution is it?

bishoybt

Hi Nic,

I have JIRA 7.6.1 deployed on Ubuntu 17.10 Server
I installed Jira as a service, and I am able to run it successfully using sudo service jira start

I've ran sudo update-rc.d jira defaults but it yielded nothing and still the service is not started when I reboot.

Nic Brough -Adaptavist-

If you can run it with a "service start", then there is something wrong with the start up script. I can't really help you a lot with that without knowing exactly what the startup is doing and how (I tend to use RedHat more than Ubuntu, so I'm less familiar with the startup process)