Hi, i install new jira (atlassian-jira-5.2.5-x64.bin) on CentOS release 6.3 (Final)
Linux version 2.6.32-279.el6.x86_64 (email@example.com) (gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Fri Jun 22 12:19:21 UTC 2012
I have: The connection has timed out problem(The server at ... is taking too long to respond.)
I was tried install by default and install changing ports from 8080(8005) to non default
cat /proc/meminfo MemTotal: 3911552 kB MemFree: 1778956 kB Buffers: 152444 kB Cached: 1129568 kB
My catalina.out finishing this lines
___ Plugin System Started _________________ 2013-02-04 15:52:47,098 localhost-startStop-1 INFO [jira.config.database.SystemTenantDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/application-data/jira/dbconfig.xml 2013-02-04 15:52:47,118 localhost-startStop-1 INFO [jira.instrumentation.external.DatabaseExternalGauges] Installing DBCP monitoring instruments: DatabaseExternalGauges.JiraDbcpInstruments[instruments=[DBCP_MAX, DBCP_ACTIVE, DBCP_IDLE],objectName=com.atlassian.jira:name=BasicDataSource] 2013-02-04 15:52:47,239 localhost-startStop-1 INFO [jira.config.database.DatabaseConfigurationManagerImpl] The database is not yet configured 2013-02-04 15:52:47,239 localhost-startStop-1 INFO [jira.config.database.DatabaseConfigurationManagerImpl] Enqueuing Database Checklist Launcher' on post-database-configured-but-pre-database-activated queue 2013-02-04 15:52:47,241 localhost-startStop-1 INFO [jira.config.database.DatabaseConfigurationManagerImpl] The database is not yet configured 2013-02-04 15:52:47,241 localhost-startStop-1 INFO [jira.config.database.DatabaseConfigurationManagerImpl] Enqueuing Post database-configuration launchers' on post-database-activated queue Feb 4, 2013 3:52:47 PM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler ["http-bio-9090"] Feb 4, 2013 3:52:47 PM org.apache.catalina.startup.Catalina start INFO: Server startup in 21913 ms
The good news is, everything in the logs seems fine. But could you perhaps clarify on where and/or how you are facing the connection timeout? Is it when you are trying to access the instance?
If so, could you try accessing it via localhost (if you are not doing so currently)?
See if you can access the application locally as suggested before:
Then if can access locally, test if the port is accessible for remote access, trying to telnet it from a different computer, eg:
telnet jiraipaddress jiraport
If you can't connect to the port, you will need to allow access to this port on your server or Firewall so as to enable remote access to the application.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot