Fresh installation of jira standalone on fedora24 fails to start

[Farhan Masud]

[Description]

Fresh installation of JIRA (atlassian-jira-software-7.1.9-x64.bin) is failing to load on an instance of Fedora24. Catalina logs stop abruptly without providing any indication of what the failure is. Entering the ip:8080 results in the following message but the demon appears to be running as shown in the following sections. PLEASE HELP!

"Host Not Found

DNS error (the host name of the page you are looking for does not exist) or Server did not accept the connection.
Please check that the host name has been spelled correctly"

[Versions]

[root@fedora jira]# java -cp lib/catalina.jar org.apache.catalina.util.ServerInfo
Server version: Apache Tomcat/8.0.33
Server built: Mar 18 2016 20:31:49 UTC
Server number: 8.0.33.0
OS Name: Linux
OS Version: 4.5.5-x86_64-linode69
Architecture: amd64
JVM Version: 1.8.0_74-b02
JVM Vendor: Oracle Corporation

[Daemon]

[root@fedora jira]# ps aux | grep jira
jira 22605 0.6 16.5 2867724 339320 ? Sl 22:48 0:27 /opt/atlassian jira/jre//bin/java -Djava.util.logging.c
onfig.file=/opt/atlassian/jira/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Xms384m -Xmx768m -Djava.awt.headless=true -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMI
T_BUFFER=true -Dmail.mime.decodeparameters=true -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory -XX:
+PrintGCDateStamps -XX:-OmitStackTraceInFastThrow -Djava.endorsed.dirs=/opt/atlassian/jira/endorsed -classpath /opt/atla
ssian/jira/bin/bootstrap.jar:/opt/atlassian/jira/bin/tomcat-juli.jar -Dcatalina.base=/opt/atlassian/jira -Dcatalina.home
=/opt/atlassian/jira -Djava.io.tmpdir=/opt/atlassian/jira/temp org.apache.catalina.startup.Bootstrap start
root 22936 0.0 0.0 117148 992 ttyS0 S+ 23:57 0:00 grep --color=auto jira
[root@fedora jira]#

[Catalina Logs Tail]

18-Jul-2016 22:48:39.967 INFO [main] org.apache.catalina.startup.VersionLoggerLi
stener.log OS Version: 4.5.5-x86_64-linode69
18-Jul-2016 22:48:39.967 INFO [main] org.apache.catalina.startup.VersionLoggerLi
stener.log Architecture: amd64
18-Jul-2016 22:48:39.970 INFO [main] org.apache.catalina.startup.VersionLoggerLi
stener.log Java Home: /opt/atlassian/jira/jre
18-Jul-2016 22:48:39.970 INFO [main] org.apache.catalina.startup.VersionLoggerLi
stener.log JVM Version: 1.8.0_74-b02
18-Jul-2016 22:48:39.971 INFO [main] org.apache.catalina.startup.VersionLoggerLi
stener.log JVM Vendor: Oracle Corporation
18-Jul-2016 22:48:39.971 INFO [main] org.apache.catalina.startup.VersionLoggerLi
stener.log CATALINA_BASE: /opt/atlassian/jira
18-Jul-2016 22:48:39.971 INFO [main] org.apache.catalina.startup.VersionLoggerLi
stener.log CATALINA_HOME: /opt/atlassian/jira
18-Jul-2016 22:48:39.972 INFO [main] org.apache.catalina.startup.VersionLoggerLi
[root@fedora jira]# tail /opt/atlassian/jira/logs/catalina.out
2016-07-18 22:49:01,793 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] JIRA pre-database startup checks c
ompleted successfully.
2016-07-18 22:49:01,887 JIRA-Bootstrap INFO [c.a.j.config.database.DatabaseConfigurationManagerImpl] The database i
s not yet configured. Enqueuing Database Checklist Launcher on post-database-configured-but-pre-database-activated queue
2016-07-18 22:49:01,888 JIRA-Bootstrap INFO [c.a.j.config.database.DatabaseConfigurationManagerImpl] The database i
s not yet configured. Enqueuing Post database-configuration launchers on post-database-activated queue
2016-07-18 22:49:01,936 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Memory Usage:
---------------------------------------------------------------------------------
Heap memory : Used: 110 MiB. Committed: 371 MiB. Max: 742 MiB
Non-heap memory : Used: 63 MiB. Committed: 66 MiB. Max: 1264 MiB
---------------------------------------------------------------------------------
TOTAL : Used: 173 MiB. Committed: 437 MiB. Max: 2006 MiB
---------------------------------------------------------------------------------

[Nic Brough -Adaptavist- · Accepted solution]

It really does look like a simple failure to find the server based on the url (whether text or IP based).  The logs look healthy, I'd expect everything to be running from them, and the error message is pointing at DNS/networking, not the server.

[Farhan Masud]

I dont really see the message that says JIRA can now be accessed through the browser. Logs stop after the memory usage message. I have verified that the ip address is working but ip:8080 does not work.