Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Could not execute health check, DatabaseConfigurationManager not available.

Gopal Kasat August 17, 2021

Jira does not start and the catalina. out shows following error

 

Could not execute health check, DatabaseConfigurationManager not available.

2 answers

0 votes
Daniel Ebers
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 22, 2021

Hi @Gopal Kasat

adding to what Nic says for the filesystem permissions of the file (foremost probably the one in the error message, /var/atlassian/application-data/jira/plugins/.osgi-plugins/felix/felix-cache) please consider checking the system's overall health if the permission check should not turn out any obvious mistake or even should give back contraditory results.

Coming across cases where a filesystem was damaged also (slowly breaking) hard disks, SSD drives or memory modules (they are the most nasty ones, for sure) could be a cause.

It would be interesting if more files/directories are affected by the problem or if it is just this particular one.

Regards,
Daniel

Gopal Kasat August 23, 2021

Thank you Nic and Daniel,

Seems it was permission issue. For some reason root got permission for all these files. Changed now the ownership to jira user and now I am able to start JIRA and see the logged issues there.

However we created some filters and and sprint etc. Those are not visible now. Could you let us know what could be the reason

Gopal Kasat August 24, 2021

Thank you Nic and Daniel,

 

Now the issue regarding filters is sorted out by doing re-indexing.

Thank you very much for your help

Gopal

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 17, 2021

I suspect there is more to the error than that - what do the logs say?

To get this error though, it suggests a damaged Jira installation, or something has gone wrong internally (like out of memory) and it's not able to load some new stuff from the disk.

Gopal Kasat August 20, 2021

Hello Nic,

thank you for the quick reply. I have uploaded the catalina.out at following location

 

https://tridiagonals-my.sharepoint.com/:u:/g/personal/ftp_user_tridiagonal_com/ERba2-8-w2dDmMLSU00z-ewBMDNDDKHRB8qDQriLfwOE9A?e=dGFbyz

 

Please let me know if this helps to understand where is the problem.

 

Gopal

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 20, 2021

It might do, but it won't open for me.

Gopal Kasat August 20, 2021

Please check if you can download from here

 

https://www.filemail.com/d/mhukcomsdrymtcc

 

Gopal

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 20, 2021

Can't see that either.

Could you just find the error that is being put into the logs at the point of failure and post those few lines?

Gopal Kasat August 20, 2021

Here are some lines from from the log which shows error. Let me know if that helps

Caused by: java.io.IOException: Failed to list contents of /var/atlassian/application-data/jira/plugins/.osgi-plugins/felix/felix-cache
at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1393)
at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1331)
at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:1910)
at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1399)
at com.atlassian.plugin.osgi.container.impl.DefaultOsgiPersistentCache.validate(DefaultOsgiPersistentCache.java:79)
2021-08-17 07:54:40,621 http-nio-8080-exec-12 WARN anonymous 474x5x1 15yz475 136.232.237.6 /secure/errors.jsp [c.a.jira.security.JiraSecurityFilter] Rejecting security-sensitive request that bypassed Johnson filter: /secure/errors.jsp
2021-08-17 07:54:41,939 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] Could not execute health check, DatabaseConfigurationManager not available.
2021-08-17 07:54:41,939 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] Could not execute health check, DatabaseConfigurationManager not available.
2021-08-17 07:54:41,940 JIRA-Bootstrap ERROR [c.a.jira.startup.DefaultJiraLauncher] JIRA has failed to start because of the following errors: [(Event: Level = (EventLevel: fatal) , Key = (EventType: startup-unexpected) , Desc = We couldn't start JIRA , Exception = An error occurred while trying to start JIRA. We can't give you any more detail right now, we suggest checking the logs for more detail and contacting our support team.<br/>See our documentation for more information on contacting our support team and creating a support zip.), (Event: Level = (EventLevel: fatal) , Key = (EventType: database) , Desc = Could not execute health check, DatabaseConfigurationManager not available. , Exception = ]
2021-08-17 07:54:41,960 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Memory Usage:
---------------------------------------------------------------------------------
Heap memory : Used: 235 MiB. Committed: 484 MiB. Max: 742 MiB
Non-heap memory : Used: 77 MiB. Committed: 79 MiB. Max: 1264 MiB
---------------------------------------------------------------------------------
TOTAL : Used: 313 MiB. Committed: 563 MiB. Max: 2006 MiB
---------------------------------------------------------------------------------

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 21, 2021

This suggests that there is a problem reading from the disk.

Check the ownership and permissions of the Jira installation and data directories, they and all of their content need to be read/write for the account running Jira (usually this means someone has run it as the wrong user which has taken ownership of some of the files and that has blocked the actual Jira user)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events