/status returns state of error but the server is running and I can not find any ERROR in the logs

[ChristopherChilds]

Hi Community, 

This is a strange one. 

I am deploying Jira Data Center via Atlassian Helm chart. 

The readiness probe is listening on /status for RUNNING. As will automatically trigger a re-index after the server if deployed. 

However, something changed! I am not too sure what as there are no errors in the logs. But now Jira wants to start with state of ERROR. Functionally the server appears to be fine. I have investigated plugins but stilll no idea where it is coming from. Does anyone have any ideas?

[Himanshu Tiwary · Accepted solution]

Hi @ChristopherChilds ,
try running these tests o check for the actual cause

check / status?full=true, jira health check,cluster status or any errors with re-indexing, shared home or any startup apps or plugins also try running in safe mode once and check weather anything updated recently that might be the root cause to this.

[ChristopherChilds]

Thank you. I will try this. 

I thought to actually read the readinessprobe against /login? it seems to be working so far. Then I do not need to add any custom probe logic. Instead I can run against httpget.