503 Service Temporarily Unavailable

[David Stevens]

When I run Jira I get the "Service Temporarily Unavailable" error when attempting to access it through http. I discovered why it's giving the issue but I don't know how to fix it. Recently I performed a server migration of our Jira instance to new a server. I was recommended by a help article to copy over the Jira installation and home files to the new server, which I did. I reconfigured dbconfig.xml for the new server as well, but when I run Jira on the new server, I get that error. The weird part is when I run Jira on the old server the error goes away and it connects fine. I believe there is a file still pointing to the old Jira server but I have no clue as to what is.

[Daniel Ebers]

Hi David,

the error message suggests you have some kind of reverse proxy (probably Apache) in place but this is not able to connect to the Tomcat container for some reason.

Can you confirm this is a setup you have?

First check if Jira is running. Further you can debug using "netstat" if the port is open and is the correct one you refer to from reverse proxy.

This is, indeed, all guesswork at the moment. More details can be provided probably if you could share some debug information. Best case along with some lines of log files.

Cheers,
Daniel

[David Stevens]

Hi Daniel,

As I am not very knowledgeable on this would you be able to tell me where to get the debug information and log files?

Thanks,

David

[Daniel Ebers]

That depends on your setup, but highly likely in one of these paths:

• /var/log/apache/access.log
• /var/log/apache2/access.log
• /etc/httpd/logs/access_log

Please in first step make sure a reverse proxy is installed at all - if so, then probably it will be better to review documentation first:
https://confluence.atlassian.com/kb/reverse-proxy-and-application-link-troubleshooting-guide-719095279.html

After some investigation you should be able to tell where the error message originates - it basically means that 'something' is responding, which is good.

For a more detailed advise a better understanding of your setup would be needed. So in case somebody from Community can say more please share some more details.

[David Stevens]

I can verify that there is a reverse proxy installed. I ran the command service httpd status and this was the result:

Redirecting to /bin/systemctl status httpd.service
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; disabled; vendor pres>
Active: active (running) since Tue 2020-11-17 18:24:04 CST; 2min 20s ago
Docs: man:httpd.service(8)
Main PID: 53934 (httpd)
Status: "Running, listening on: port 443"
Tasks: 213 (limit: 23960)
Memory: 32.6M
CGroup: /system.slice/httpd.service
├─53934 /usr/sbin/httpd -DFOREGROUND
├─53935 /usr/sbin/httpd -DFOREGROUND
├─53936 /usr/sbin/httpd -DFOREGROUND
├─53937 /usr/sbin/httpd -DFOREGROUND
└─53938 /usr/sbin/httpd -DFOREGROUND

Nov 17 18:24:04 uajira1.vpua.txstate.edu systemd[1]: Starting The Apache HTTP S>
Nov 17 18:24:04 uajira1.vpua.txstate.edu systemd[1]: Started The Apache HTTP Se>
Nov 17 18:24:04 uajira1.vpua.txstate.edu httpd[53934]: Server configured, liste>
lines 1-18/18 (END)...skipping...
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; disabled; vendor preset: disabled)
Active: active (running) since Tue 2020-11-17 18:24:04 CST; 2min 20s ago
Docs: man:httpd.service(8)
Main PID: 53934 (httpd)
Status: "Running, listening on: port 443"
Tasks: 213 (limit: 23960)
Memory: 32.6M
CGroup: /system.slice/httpd.service
├─53934 /usr/sbin/httpd -DFOREGROUND
├─53935 /usr/sbin/httpd -DFOREGROUND
├─53936 /usr/sbin/httpd -DFOREGROUND
├─53937 /usr/sbin/httpd -DFOREGROUND
└─53938 /usr/sbin/httpd -DFOREGROUND

Nov 17 18:24:04 uajira1.vpua.txstate.edu systemd[1]: Starting The Apache HTTP Server...
Nov 17 18:24:04 uajira1.vpua.txstate.edu systemd[1]: Started The Apache HTTP Server.
Nov 17 18:24:04 uajira1.vpua.txstate.edu httpd[53934]: Server configured, listening on: port 443

I located the error log in /etc/httpd/logs/access_log and the file was empty. I am attaching a picture of the error just in case.

[Daniel Ebers]

Good. The presence of Apache correlates with the kind of error message.

I think you are on a good way - there seems to be a misconfiguration. Debug from remote is tricky why further tips apart from the given will be rarely possible in this step.

You should revise all setup steps and check what is missing.

[David Stevens]

Is it possible the old server is causing an issue with Apache/Httpd still running?

[David Stevens]

I also just realized my the error mentions Apache/2.2.15 when that is the version on the old server but not the new one.

[Daniel Ebers]

There indeed is still some mix up.

Please also make sure the old Jira instance is stopped so the database can be used by the NEW server. 

[David Stevens]

I have double-checked to make sure the old JIRA instance is offline. I also reinstalled Apache and went through the steps again to make a mistake. Do you know if it is possible something on the new JIRA instance is pointing to the old one? I have checked server.xml and dbconfig.xml but I don't see anything pointing to it.