Jira installation issue - http://localhost:8080 page not accessible

[Jay Kantaria]

Installed Jira 7.8.1 on RHEL 7.4.

Installation went fine.  Jira installed as service and no visible issues in the service stop/start.

This is on AWS ec2.  I don't have browser installed so hopping I can get to configuration @ http://<<machineIP>>:8080  ?

Not able to access the localhost or with machine IP address.

I see following issues in the log:

=========

[root@ip-10-250-33-52 logs]# cat atlassian-jira-gc-2018-03-28_18-27-41.log.0.current
Java HotSpot(TM) 64-Bit Server VM (25.102-b14) for linux-amd64 JRE (1.8.0_102-b14), built on Jun 22 2016 18:43:17 by "java_re" with gcc 4.3.0 20080428 (Red Hat 4.3.0-8)
Memory: 4k page, physical 7746876k(4303580k free), swap 0k(0k free)
CommandLine flags: -XX:GCLogFileSize=20971520 -XX:InitialHeapSize=402653184 -XX:MaxHeapSize=805306368 -XX:NumberOfGCLogFiles=5 -XX:-OmitStackTraceInFastThrow -XX:+PrintGC -XX:+PrintGCCause -XX:+PrintGCDateStamps -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+UseCompressedClassPointers -XX:+UseCompressedOops -XX:+UseGCLogFileRotation -XX:+UseParallelGC
2018-03-28T18:27:42.309-0400: 1.018: [GC (Allocation Failure) [PSYoungGen: 98304K->12776K(114688K)] 98304K->12784K(376832K), 0.0186220 secs] [Times: user=0.03 sys=0.01, real=0.02 secs]
2018-03-28T18:27:42.752-0400: 1.461: [GC (Allocation Failure) [PSYoungGen: 111080K->15678K(212992K)] 111088K->15686K(475136K), 0.0151753 secs] [Times: user=0.02 sys=0.01, real=0.01 secs]
2018-03-28T18:27:43.172-0400: 1.881: [GC (Allocation Failure) [PSYoungGen: 212286K->16365K(212992K)] 212294K->18007K(475136K), 0.0222369 secs] [Times: user=0.04 sys=0.00, real=0.02 secs]
2018-03-28T18:27:43.519-0400: 2.228: [GC (Allocation Failure) [PSYoungGen: 212973K->16357K(245760K)] 214615K->21240K(507904K), 0.0208132 secs] [Times: user=0.04 sys=0.00, real=0.02 secs]
2018-03-28T18:27:43.921-0400: 2.630: [GC (Allocation Failure) [PSYoungGen: 245733K->16376K(245760K)] 250616K->25410K(507904K), 0.0197225 secs] [Times: user=0.03 sys=0.01, real=0.02 secs]
2018-03-28T18:27:44.410-0400: 3.119: [GC (Allocation Failure) [PSYoungGen: 245752K->16378K(221184K)] 254786K->37289K(483328K), 0.0265096 secs] [Times: user=0.04 sys=0.01, real=0.03 secs]
2018-03-28T18:27:45.106-0400: 3.815: [GC (Allocation Failure) [PSYoungGen: 221178K->13571K(233472K)] 242089K->43214K(495616K), 0.0229175 secs] [Times: user=0.04 sys=0.00, real=0.02 secs]
2018-03-28T18:27:45.490-0400: 4.200: [GC (Metadata GC Threshold) [PSYoungGen: 86622K->9592K(232448K)] 116264K->40890K(494592K), 0.0167571 secs] [Times: user=0.04 sys=0.00, real=0.02 secs]
2018-03-28T18:27:45.507-0400: 4.217: [Full GC (Metadata GC Threshold) [PSYoungGen: 9592K->0K(232448K)] [ParOldGen: 31298K->22600K(262144K)] 40890K->22600K(494592K), [Metaspace: 20602K->20602K(1069056K)], 0.0887448 secs] [Times: user=0.16 sys=0.00, real=0.09 secs]
2018-03-28T18:27:46.212-0400: 4.922: [GC (Allocation Failure) [PSYoungGen: 203776K->6021K(209920K)] 226376K->28630K(472064K), 0.0123003 secs] [Times: user=0.02 sys=0.00, real=0.01 secs]
2018-03-28T18:27:46.884-0400: 5.594: [GC (Allocation Failure) [PSYoungGen: 209797K->13819K(232960K)] 232406K->36428K(495104K), 0.0189515 secs] [Times: user=0.04 sys=0.00, real=0.02 secs]
2018-03-28T18:27:47.487-0400: 6.197: [GC (Allocation Failure) [PSYoungGen: 216571K->4964K(231936K)] 239180K->35984K(494080K), 0.0208244 secs] [Times: user=0.04 sys=0.00, real=0.02 secs]
2018-03-28T18:27:47.970-0400: 6.680: [GC (Metadata GC Threshold) [PSYoungGen: 61788K->4394K(232448K)] 92808K->39665K(494592K), 0.0089016 secs] [Times: user=0.02 sys=0.00, real=0.01 secs]
2018-03-28T18:27:47.979-0400: 6.689: [Full GC (Metadata GC Threshold) [PSYoungGen: 4394K->0K(232448K)] [ParOldGen: 35271K->34427K(262144K)] 39665K->34427K(494592K), [Metaspace: 34276K->34276K(1079296K)], 0.0887076 secs] [Times: user=0.15 sys=0.00, real=0.09 secs]
2018-03-28T18:27:48.927-0400: 7.636: [GC (Allocation Failure) [PSYoungGen: 202752K->9182K(211968K)] 237179K->43609K(474112K), 0.0092693 secs] [Times: user=0.02 sys=0.00, real=0.01 secs]
2018-03-28T18:27:50.816-0400: 9.525: [GC (Allocation Failure) [PSYoungGen: 211934K->16234K(232448K)] 246361K->50670K(494592K), 0.0199520 secs] [Times: user=0.04 sys=0.00, real=0.02 secs]

=====

Tail of catlina.out

===

2018-03-28 18:27:50,968 JIRA-Bootstrap INFO      [c.a.jira.plugin.JiraCacheResetter] Start resetting caches triggered by: onPluginEnabled, jiraIsShuttingDown: false
2018-03-28 18:27:50,968 JIRA-Bootstrap INFO      [c.a.jira.plugin.JiraCacheResetter] Done resetting caches triggered by: onPluginEnabled, timeMillis: 0, jiraIsShuttingDown: false
2018-03-28 18:27:50,968 JIRA-Bootstrap INFO      [c.a.jira.plugin.JiraCacheResetter] Start resetting caches triggered by: onPluginModuleEnabled, jiraIsShuttingDown: false
2018-03-28 18:27:50,968 JIRA-Bootstrap INFO      [c.a.jira.plugin.JiraCacheResetter] Done resetting caches triggered by: onPluginModuleEnabled, timeMillis: 0, jiraIsShuttingDown: false
2018-03-28 18:27:50,968 JIRA-Bootstrap INFO      [c.a.jira.plugin.JiraCacheResetter] Start resetting caches triggered by: onPluginEnabled, jiraIsShuttingDown: false
2018-03-28 18:27:50,969 JIRA-Bootstrap INFO      [c.a.jira.plugin.JiraCacheResetter] Done resetting caches triggered by: onPluginEnabled, timeMillis: 0, jiraIsShuttingDown: false
2018-03-28 18:27:50,969 JIRA-Bootstrap INFO      [c.a.plugin.manager.DefaultPluginManager] Plugin system earlyStartup ended
2018-03-28 18:27:51,090 JIRA-Bootstrap INFO      [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/application-data/jira/dbconfig.xml
2018-03-28 18:27:51,099 JIRA-Bootstrap INFO      [c.a.j.instrumentation.external.DatabaseExternalGauges] Installing DBCP monitoring instruments: DatabaseExternalGauges.JiraDbcpInstruments[instruments=[DBCP_MAX, DBCP_ACTIVE, DBCP_IDLE],objectName=com.atlassian.jira:name=BasicDataSource]
2018-03-28 18:27:51,137 JIRA-Bootstrap INFO      [c.a.jira.startup.JiraStartupLogger] Running JIRA startup checks.
2018-03-28 18:27:51,138 JIRA-Bootstrap INFO      [c.a.jira.startup.JiraStartupLogger] JIRA pre-database startup checks completed successfully.
2018-03-28 18:27:51,166 JIRA-Bootstrap INFO      [c.a.j.config.database.DatabaseConfigurationManagerImpl] The database is not yet configured. Enqueuing Database Checklist Launcher on post-database-configured-but-pre-database-activated queue
2018-03-28 18:27:51,166 JIRA-Bootstrap INFO      [c.a.j.config.database.DatabaseConfigurationManagerImpl] The database is not yet configured. Enqueuing Post database-configuration launchers on post-database-activated queue
2018-03-28 18:27:51,189 JIRA-Bootstrap INFO      [c.a.jira.startup.LauncherContextListener] Memory Usage:
    ---------------------------------------------------------------------------------
      Heap memory     :  Used:  174 MiB.  Committed:  483 MiB.  Max:  740 MiB
      Non-heap memory :  Used:   63 MiB.  Committed:   66 MiB.  Max: 1264 MiB
    ---------------------------------------------------------------------------------
      TOTAL           :  Used:  237 MiB.  Committed:  549 MiB.  Max: 2004 MiB
    ---------------------------------------------------------------------------------

how can I resolve this issue and get to my initial setup page to configure Jira?

[Jay Kantaria · Accepted solution]

It was security blocking traffic between Ec2 and local network.  I ended up using ssh tunnel from local host where I mapped local port to the jira-IP:port.

[Craig Castle-Mead · Accepted solution]

Hey Jay,

feels like the most likely issue is with the security group the ec2 instance is assoaciated with isn’t allowing TCP 8080 traffic.

from your shell session, try:

telnet 127.0.0.1 8080

if that responds, then in your AWS console, find the ec2 instance, then click on its security group, on inbound rules add custom TCP for port 8080 permitted to either your own IP (select “My IP” and it will fill it for you) or “anywhere” which will add 0.0.0.0/0 and permit traffic from anyone.

once you’ve done this, try and load http://<<machineip>>:8080 in your browser

Let isn’t know if that helps

CCM

[Jay Kantaria]

hi Craig - Yes telnet worked.

[root] # telnet 127.0.0.1 8080
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
Connection closed by foreign host.

=======

Asking our EC2 admin to look at if http/https rule added for inbound traffic on port 8080.

Any idea on other errors seen on atlassian-jira-gc-*.current log?  Does this log into say Jira is up and running?

[Craig Castle-Mead]

Given telnet works, try 

curl http://127.0.0.1:8080 and check what the output is. Even if you copy the output, save is on a local machine with a .html extension and load that in your browser. You won’t get the CSS/JS but you should at least get some idea of what is being displayed.

the GC log isn’t the best spot to look, catalina.out is where Jiras primary startup output is. The tail you posted looks pretty clean, so hopefully it’s working.

CCM