I have been following this guide: https://confluence.atlassian.com/adminjiraserver/installing-jira-applications-on-linux-938846841.html
and no matter what I try, no matter where I look, absolutely nothing appears on localhost:8080. I'm trying to install Jira on an AWS EC2 (I've tried t2.micro, t3.small, t3.medium), but all I get is the attached image. Can someone please help?
I found out what happened. I was using AWS and the security group was only configured to only traffic into port 22. When I opened the other ports, I was able to see Jira in the web browser.
If Jira was never up I would not worry about a missing dbconfig.xml - it would have been created in the next step, through Setup Wizard (which you cannot reach currently via browser if I got you right).
Here is some more documentation about connection to the database - which not necessarily is the current culprit.
https://confluence.atlassian.com/adminjiraserver/connecting-jira-applications-to-a-database-938846850.html
Cheers,
Daniel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for sending that, Daniel! I noticed that MySQL 8 wasn't listed in the article you provided; does that mean that MySQL 8 isn't completely compatible with Jira?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Sam ,
Did you check that the process is running?
And could you check the logs , if there are some messages that might help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I should mention I'm new to Linux; how would I check that the process is running?
The attached image is what I see when I check the logs:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The strangest part is that I don't get any error messags, but still nothing appears. I don't know where else to look for error messages; which directories would recommend starting with?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is, indeed, a bit hard to say without having a deeper look into log files.
An important log file is atlassian-jira.log - you can find it in your JIRA_HOME/log directory.
To check if the process is running you could use the top, htop or ps command.
It is hard to say if there is something critical missing for your installation without a deeper look into the system.
I'd recommend also to check with the netstat command (netstat -tuan should be a proper start) to see if the port 8080 is really not opened - or if there is just a firewall rule blocking access.
Cheers,
Daniel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your response Daniel,
I found atlassian-jira.log and this what it said:
2020-03-16 13:31:10,347 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/application-data/jira/dbconfig.xml2020-03-16 13:31:10,372 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/application-data/jira/dbconfig.xml2020-03-16 13:31:10,373 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/application-data/jira/dbconfig.xml2020-03-16 13:31:10,899 JIRA-Bootstrap INFO [c.a.j.c.cache.pauser.NonClusteredReplicationPauserManager] Non-clustered mode: ReplicationPauserManager implemented by NonClusteredReplicationPauserManager2020-03-16 13:31:11,726 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/application-data/jira/dbconfig.xml2020-03-16 13:31:11,743 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger]
___ Starting the JIRA Plugin System _________________
2020-03-16 13:31:11,746 JIRA-Bootstrap INFO [c.a.plugin.manager.DefaultPluginManager] Plugin system earlyStartup begun2020-03-16 13:31:15,723 JIRA-Bootstrap INFO [c.a.plugin.loaders.ScanningPluginLoader] No plugins found to be deployed2020-03-16 13:31:16,276 ThreadPoolAsyncTaskExecutor::Thread 5 WARN [c.a.p.s.scanner.util.ProductFilterUtil] Couldn't detect product, will use ProductFilter.ALL2020-03-16 13:31:16,592 JIRA-Bootstrap INFO [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (5): [com.atlassian.jira.jira-less-integration, com.atlassian.plugins.less-transformer-plugin, com.atlassian.soy.soy-template-plugin, tac.jira core.languages.ru_RU, tac.jira core.languages.zh_CN], 300 seconds remaining2020-03-16 13:31:18,036 JIRA-Bootstrap INFO [c.a.plugin.manager.DefaultPluginManager] Plugin system earlyStartup ended2020-03-16 13:31:18,183 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/application-data/jira/dbconfig.xml2020-03-16 13:31:18,195 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]2020-03-16 13:31:18,235 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] Running JIRA startup checks.2020-03-16 13:31:18,235 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] JIRA pre-database startup checks completed successfully.2020-03-16 13:31:18,283 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 queue2020-03-16 13:31:18,284 JIRA-Bootstrap INFO [c.a.j.config.database.DatabaseConfigurationManagerImpl] The database is not yet configured. Enqueuing Post database-configuration launchers on post-database-activated queue2020-03-16 13:31:18,317 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Memory Usage: --------------------------------------------------------------------------------- Heap memory : Used: 215 MiB. Committed: 469 MiB. Max: 742 MiB Non-heap memory : Used: 67 MiB. Committed: 69 MiB. Max: 1264 MiB --------------------------------------------------------------------------------- TOTAL : Used: 282 MiB. Committed: 538 MiB. Max: 2006 MiB ---------------------------------------------------------------------------------
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This does not look so bad! From just seeing log files it is quite hard - but one golden rule is to be on the look out for FATAL errors.
In this case I'd double check if any firewalling is in place - like I said this is just an educated guess as the part of the log file basically looks good!
Cheers,
Daniel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Daniel; I actually think I have it figured out. The problem I'm facing seems to be identical to this: https://community.atlassian.com/t5/Jira-Software-questions/Jira-running-but-web-not-showing/qaq-p/987196
I have other work to do so I can't try it out now, but I have a feeling this is the solution. Thanks for your help!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That wasn't the solution, so now I really don't know what to do. So far I've:
1. Tried allocating more memory in the setenv.sh
2. Made sure that the path context is "" instead of "/jira"
3. Made sure that it can be accessed from my IP address.
I really don't know what else to do now.
Going back to atlassian-jira.log, I see this line:
2020-03-16 16:05:32,400 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/application-data/jira/dbconfig.xml
The find command couldn't find "dbconfig.xml" anywhere in the server, so I think that might have something to do with it. Is it possible I have to change where JIRA tries to read the database configuration and if so, how would I do that?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.