Hello @F Maring ,
The error "502 Bad gateway" is a tricky one, as its more of a symptom of other issues rather than the direct outcome of anything specific.
A 502 can mean that either the server can't handle what you are doing, or the network you are on cannot carry the action to completion with a plethora of causes possible on each point of failure. Because of this you will need to look at both the server performance and network performance and try to locate additional errors occuring that could lead to the error and help narrow down the scope of the issue.
I recomend starting with general server performance and network troubleshooting covered in these guides:
Also check the logging to see if there is any other explicit errors noted that could help narrow down the cause.
But one more thing that is catching my attention from your description is the mention of deleting "catalina.pid" on the restart is required, indications that something is hanging in your Tomcat startup which usually stems from a OOME (Out of Memory Event) Error, when lookling at the logging do a search for "OOME" to see if anything comes up, and if so a bump to the memory should help here "Increasing Jira application memory" making sure to Confirm that you're not receiving Perm Gen or GC Overhead errors as noted in the warning block at the top of that page.
But overall let me know if you find any additional errors in the logging and I can take a closer look.
Regards,
Earl
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.