while starting JIRA server getting HTTP ERROR 404

Question

DPKJ · Answer

Have you check server port?

sankar sankar · Answer

Hi JP and DPK,

As per the logs Catalina.out

Jira up and running ..but when it comes to browser it is showing 404 error.

********************************************************************************************************************************************************************************************************

2019-08-20 12:15:28,043 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Memory Usage:
---------------------------------------------------------------------------------
Heap memory : Used: 673 MiB. Committed: 1948 MiB. Max: 1951 MiB
Non-heap memory : Used: 262 MiB. Committed: 287 MiB. Max: 1536 MiB
---------------------------------------------------------------------------------
TOTAL : Used: 936 MiB. Committed: 2234 MiB. Max: 3487 MiB
---------------------------------------------------------------------------------
2019-08-20 12:15:28,951 Caesium-1-3 INFO ServiceRunner [c.a.jira.startup.IndexRecoveryLauncher] Running start-index-recovery
2019-08-20 12:15:30,612 Caesium-1-3 INFO ServiceRunner [c.a.jira.startup.IndexRecoveryLauncher] Indexing issues from=2019-07-29 14:10:05.0 to=Mon Jul 29 14:10:05 CEST 2019 (time span of 0ms)
2019-08-20 12:15:30,613 Caesium-1-3 INFO ServiceRunner [c.a.jira.startup.IndexRecoveryLauncher] Progress=60%, task=Recovering, message=Recovered added and updated issues
2019-08-20 12:15:32,518 Caesium-1-1 INFO [c.a.jira.startup.CacheWarmerLauncher] Warming up 3 caches.
2019-08-20 12:15:36,471 Caesium-1-3 INFO ServiceRunner [c.a.jira.startup.IndexRecoveryLauncher] Progress=80%, task=Recovering, message=Cleaned removed issues
2019-08-20 12:15:36,471 Caesium-1-3 INFO ServiceRunner [c.a.jira.startup.IndexRecoveryLauncher] Finished start-index-recovery
2019-08-20 12:15:48,894 Caesium-1-1 INFO [c.a.jira.startup.CacheWarmerLauncher] Warmed cache(s) in 16375 ms.
2019-08-20 12:16:17,020 Caesium-1-3 INFO ServiceRunner [c.a.jira.upgrade.UpgradeScheduler] Running scheduled upgrades
2019-08-20 12:16:17,041 Caesium-1-3 INFO ServiceRunner [c.a.jira.upgrade.LoggingUpgradeService] run upgrades has started
2019-08-20 12:16:17,468 Caesium-1-3 INFO ServiceRunner [c.a.j.upgrade.util.BuildNumberDao] Setting current build number to 800010
created com.atlassian.jira.plugins.webhooks.ao.WebhookDaoImpl@e63e481 241427585 with events jira:issue_updated
AO_4AEACD_WEBHOOK_DAO {ID = 21} 57003
created com.atlassian.jira.plugins.webhooks.ao.WebhookDaoImpl@6b4cb59d 1800189341 with events jira:version_released
jira:version_updated
AO_4AEACD_WEBHOOK_DAO {ID = 1} 56983
2019-08-20 12:16:18,320 Caesium-1-3 INFO ServiceRunner [c.a.jira.upgrade.UpgradeIndexManager] There is no reindex requests of type [IMMEDIATE, DELAYED] so none will be run
2019-08-20 12:16:18,320 Caesium-1-3 INFO ServiceRunner [c.a.j.upgrade.util.BuildNumberDao] Setting current version to 8.0.2
2019-08-20 12:16:19,005 Caesium-1-3 INFO ServiceRunner [c.a.j.upgrade.util.BuildNumberDao] Setting downgrade version to 7.1.2
2019-08-20 12:16:19,444 Caesium-1-3 INFO ServiceRunner [c.a.jira.upgrade.LoggingUpgradeService] run upgrades has finished successfully, and took 2403 milliseconds to process.

=========================

getting 404 error.

Thank

Sankar g

JP _AC Bielefeld Leader_ · Answer

Hi,

404 - resource not found. Check your URL & the tomcat & jira application logs.

Best

JP