Error 503 : Service Unavailable


#1

Hi

I used bitnami installer to instal v2.1 . Ever since my APIs go intermittently unavailable with error 503.
Error message says "Server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later "

I have hosted this on EC2 (AWS) and the server is running absolutely fine . On restart (using ctlscript) , everything works fine untill next occurence of this issue.

Any pointers to what I should look at to resolve this ?


#2

Here is what I got in apache log

[Fri Apr 01 08:25:30.251071 2016] [proxy_fcgi:error] [pid 11342:tid 140504897226496] (70007)The timeout specified has expired: [client 14.141.151.210:56518] AH01075: Error dispatching request to : (polling)
[Fri Apr 01 08:27:06.614506 2016] [core:warn] [pid 11337:tid 140505630828352] AH00045: child process 11342 still did not exit, sending a SIGTERM
[Fri Apr 01 08:27:06.614579 2016] [core:warn] [pid 11337:tid 140505630828352] AH00045: child process 11476 still did not exit, sending a SIGTERM
[Fri Apr 01 08:27:08.616788 2016] [core:warn] [pid 11337:tid 140505630828352] AH00045: child process 11342 still did not exit, sending a SIGTERM
[Fri Apr 01 08:27:08.616827 2016] [core:warn] [pid 11337:tid 140505630828352] AH00045: child process 11476 still did not exit, sending a SIGTERM
[Fri Apr 01 08:27:10.619056 2016] [core:warn] [pid 11337:tid 140505630828352] AH00045: child process 11342 still did not exit, sending a SIGTERM
[Fri Apr 01 08:27:10.619092 2016] [core:warn] [pid 11337:tid 140505630828352] AH00045: child process 11476 still did not exit, sending a SIGTERM
[Fri Apr 01 08:27:12.621314 2016] [core:error] [pid 11337:tid 140505630828352] AH00046: child process 11342 still did not exit, sending a SIGKILL
[Fri Apr 01 08:27:12.621353 2016] [core:error] [pid 11337:tid 140505630828352] AH00046: child process 11476 still did not exit, sending a SIGKILL
[Fri Apr 01 08:27:13.622634 2016] [mpm_event:notice] [pid 11337:tid 140505630828352] AH00491: caught SIGTERM, shutting down
[Fri Apr 01 08:27:57.555926 2016] [ssl:warn] [pid 12368:tid 140361250264896] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Fri Apr 01 08:27:57.605099 2016] [ssl:warn] [pid 12369:tid 140361250264896] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name

#3

You have a problem with the SSL certs. Try generating it again and make sure that the key / cert pair match


#4

You may also want to investigate what is issuing the SIGTERM signal…sys restart, or some other process


#5

Thanks for these pointers. I noticed that SIGTERM is generated when i restart all the services (after the APIs stop responding) .

About ssl issue - can that cause APIs to not respond. I am using http in my API calls…

Did anyone not have this issue at all ??

Really need some help as the DF APIs have just started behaving very randomly and stop responding almost everyday . I am having to restart all service to regain the resposnes (ctlscript restart)

Regards
Abhijit


#6

I surely have seen at least 1 case of Apache not starting up right cos of improperly configured certs.As a matter of fact it might even be the easiest to isolate as you can create real SSL certs for free that would work for 90 days before it needs renewal - that’s a lot of time to test. That way you will be able to get 1 of the suspects out of the way. Cheers.