It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Am not able to open the Jira server after migrated

venu Sep 27, 2017

Hi Team,

I have just migrated the JIRa core in Linux . But am not able to open the jira even after i start the service . Please help me as early as possible because it is going ob prod environment .so please try to resolve this

Log message: 

27-Sep-2017 20:52:53.828 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
27-Sep-2017 20:52:53.828 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms1024m
27-Sep-2017 20:52:53.828 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx4096m
27-Sep-2017 20:52:53.829 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.awt.headless=true
27-Sep-2017 20:52:53.829 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Datlassian.standalone=JIRA
27-Sep-2017 20:52:53.829 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true
27-Sep-2017 20:52:53.830 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dmail.mime.decodeparameters=true
27-Sep-2017 20:52:53.830 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory
27-Sep-2017 20:52:53.830 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCDateStamps
27-Sep-2017 20:52:53.831 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:-OmitStackTraceInFastThrow
27-Sep-2017 20:52:53.831 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.endorsed.dirs=/data/apps/jira7.2.1/endorsed
27-Sep-2017 20:52:53.831 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=/data/apps/jira7.2.1
27-Sep-2017 20:52:53.831 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=/data/apps/jira7.2.1
27-Sep-2017 20:52:53.832 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=/data/apps/jira7.2.1/temp
27-Sep-2017 20:52:53.832 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
27-Sep-2017 20:52:54.197 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8080"]
27-Sep-2017 20:52:54.232 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
27-Sep-2017 20:52:54.237 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 1452 ms
27-Sep-2017 20:52:54.257 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service Catalina
27-Sep-2017 20:52:54.257 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.0.33
27-Sep-2017 20:53:19.370 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]
27-Sep-2017 20:53:19.385 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 25147 ms

 

And when i stop and start the Jira service ... it was not stopping propely. in tomcat prompt its showing "stop aborted" and "start aborted" >please find the below details

Server startup logs are located in /data/apps/jira7.2.1/logs/catalina.out
Using CATALINA_BASE: /data/apps/jira7.2.1
Using CATALINA_HOME: /data/apps/jira7.2.1
Using CATALINA_TMPDIR: /data/apps/jira7.2.1/temp
Using JRE_HOME: /data/apps/jira7.2.1/jre/
Using CLASSPATH: /data/apps/jira7.2.1/bin/bootstrap.jar:/data/apps/jira7.2.1/bin/tomcat-juli.jar
Using CATALINA_PID: /data/apps/jira7.2.1/work/catalina.pid
Existing PID file found during start.
Tomcat appears to still be running with PID 17702. Start aborted.
If the following process is not a Tomcat process, remove the PID file and try again:
UID PID PPID C STIME TTY TIME CMD
jira 17702 1 14 20:52 ? 00:01:10 /data/apps/jira7.2.1/jre//bin/ja

1 answer

0 votes
Shannon Spaniol Atlassian Team Sep 28, 2017

Hi Venu,

When you stopped Jira prior to migration, do you remember which command you used? It seems that it was still running.

You can try to force it by using the following process:

catalina.sh stop -force

Try that and let me know if you have any trouble.

Kind Regards,
Shannon

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published in Jira Software

Early Access: If you use Jenkins and Jira Software Cloud, you need to read this!

The Jira Software Cloud Team has been busy working on a simple, secure, and reliable way to integrate your build and deployment information from Jenkins with Jira Software Cloud. This means you don’t...

315 views 0 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you