Apache Web Server Error 503
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and apache 503 error page policies of this site About Us Learn more about Stack Overflow the
Varnish Cache Server Error 503
company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags
Server Error 503 Outlook
Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only
Http Server Error 503
takes a minute: Sign up How to Detect cause of 503 Service Temporarily Unavailable error and handle it? up vote 34 down vote favorite 6 i am getting the error 503 Service Temporarily Unavailable many times in my application and i want to detect why this error occurs, how ? if there's a log file or something like that, since i http server error 503 no available server to handle this request am not familiar with apache. second thing is that, is it possible to handle this error, that when it occurs apache is restarted ? apache tomcat7 tomcat http-status-code-503 share|improve this question edited Jun 10 '11 at 11:53 asked Jun 9 '11 at 20:49 MahmoudS 12k75239387 add a comment| 1 Answer 1 active oldest votes up vote 32 down vote accepted There is of course some apache log files. Search in your apache configuration files for 'Log' keyword, you'll certainly find plenty of them. Depending on your OS and installation places may vary (in a Typical Linux server it would be /var/log/apache2/[access|error].log). Having a 503 error in Apache usually means the proxied page/service is not available. I assume you're using tomcat and that means tomcat is either not responding to apache (timeout?) or not even available (down? crashed?). So chances are that it's a configuration error in the way to connect apache and tomcat or an application inside tomcat that is not even sending a response for apache. Sometimes, in production servers, it can as well be that you get
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more internal server error 503 about Stack Overflow the company Business Learn more about hiring developers or posting ads apache error 404 with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for apache error 403 system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the http://stackoverflow.com/questions/6299086/how-to-detect-cause-of-503-service-temporarily-unavailable-error-and-handle-it top Apache: 503 Service Unavailable up vote 5 down vote favorite I have a web server with apache 2.0 installed. Sometimes, probably when load increase, it serves a blank page with 503 service unavailable. Server load is not too high, is there a solution in apache configuration to solve this problem? Thank you apache-2.2 share|improve this question asked May 28 '09 at 9:37 Alessandro Astarita 28114 Does your apache http://serverfault.com/questions/13620/apache-503-service-unavailable serve as a proxy to another server such as tomcat? –David Rabinowitz May 28 '09 at 11:32 No, it doesn't. –Alessandro Astarita May 30 '09 at 11:12 add a comment| 4 Answers 4 active oldest votes up vote 3 down vote You could try changing to a different MPM, which you can do in the configuration, or tweaking the parameters of your MPM. For example, if you're using the prefork or worker MPMs then you can increase the MaxClients value. In the latter case, ThreadsPerChild might also be a useful configuration value to tweak. You can find information on the MPMs in the standard Apache documentation. However, unless you're running a really busy website, I'm surprised you're seeing 503 errors at all - is it possible that there's some really slow server-side code that's tying up Apache requests for far too long? If so, you might get more mileage improving that than just trying to work around it in Apache. share|improve this answer answered May 28 '09 at 9:48 Cartroo 20612 I'm using prefork MPM. Here is an extract of my httpd.conf: KeepAlive On MaxKeepAliveRequests 100 KeepAliveTimeout 15 StartServers 20 MinSpareServers 25 MaxSpareServers 50 MaxClients 256 MaxRequestsPerChild 50 The problem appears on a simple p
that this is a temporary condition which will be alleviated after some delay. Some servers in this state may also simply refuse the socket connection, in which case a http://www.checkupdown.com/status/E503.html different error may be generated because the socket creation timed out. Fixing 503 errors The Web server is effectively 'closed for repair'. It is still functioning minimally because it can at least respond https://www.digitalocean.com/community/questions/how-do-i-diagnose-fix-a-503-service-unavailable-error with a 503 status code, but full service is impossible i.e. the Web site is simply unavailable. There are a myriad possible reasons for this, but generally it is because of some human server error intervention by the operators of the Web server machine. You can usually expect that someone is working on the problem, and normal service will resume as soon as possible. Please contact the system operators of the Web site (e.g. your ISP) to determine why the service is down. They will be in a much better position to help you than we are for this type of server error 503 error. 503 errors in the HTTP cycle Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle when it communicates with the Web server: Obtain an IP address from the IP name of the site (the site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs). Open an IP socket connection to that IP address. Write an HTTP data stream through that socket. Receive an HTTP data stream back from the Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information. This error occurs in the final step above when the client receives an HTTP status code that it recognises as '503'. Our company also owns these other Web sites: A simple guide to software escrow. Our really simple guide to web hosting (getting your web site and email addresses on the Internet using your own domain name). Convert text to image file (GIF, JPG, PNG etc.) Free to use. Tips if you want to buy a valuable Internet domain name.
have one accepted answer. Are you sure you want to replace the current answer with this one? Yes, I'm sure. Changed your mind? You previously marked this answer as accepted. Are you sure you want to unaccept it? Yes, I'm sure. Sign Up Log In submit Tutorials Questions Projects Meetups Main Site logo-horizontal DigitalOcean Community Menu Tutorials Questions Projects Meetups Main Site Sign Up Log In submit View All Results By: stansmith Subscribe Subscribed Share 0 How do I diagnose/fix a 503 - Service Unavailable Error? December 30, 2013 6.8k views My site PushingSocial.com has been throwing regular 503 Service Unavailable errors. I've upgraded the droplet and still get the error. The server is Ubuntu with a LAMP stack Here's the latest from the Apache Error log: [Sun Dec 29 23:45:07.075133 2013] [core:error] [pid 1075:tid 139640860776256] AH00046: child process 1850 still did not exit, sending a SIGKILL [Sun Dec 29 23:45:07.076712 2013] [core:error] [pid 1075:tid 139640860776256] AH00046: child process 2149 still did not exit, sending a SIGKILL [Sun Dec 29 23:45:07.078243 2013] [core:error] [pid 1075:tid 139640860776256] AH00046: child process 2181 still did not exit, sending a SIGKILL [Sun Dec 29 23:45:07.078294 2013] [core:error] [pid 1075:tid 139640860776256] AH00046: child process 2241 still did not exit, sending a SIGKILL [Sun Dec 29 23:45:07.078562 2013] [core:error] [pid 1075:tid 139640860776256] AH00046: child process 2271 still did not exit, sending a SIGKILL [Sun Dec 29 23:45:08.082003 2013] [mpm_event:notice] [pid 1075:tid 139640860776256] AH00491: caught SIGTERM, shutting down [Sun Dec 29 23:45:23.065270 2013] [auth_digest:notice] [pid 1068:tid 140370826737472] AH01757: generating secret for digest authentication ... [Sun Dec 29 23:45:24.030813 2013] [ssl:warn] [pid 1068:tid 140370826737472] AH01873: Init: Session Cache is not configured [hint: SSLSessionCache] [Sun Dec 29 23:45:24.030909 2013] [lbmethod_heartbeat:notice] [pid 1068:tid 140370826737472] AH02282: No slotmem from mod_heartmonitor [Sun Dec 29 23:45:24.033948 2013] [mpm_event:notice] [pid 1068:tid 140370826737472] AH00489: Apache/2.4.6 (Unix) OpenSSL/1.0.1 configured -- resuming normal operations [Sun Dec 29 23:45:24.033990 2013] [core:notice] [pid 1068:tid 140370826737472] AH00094: Command line: '/opt/sp/apache/bin/httpd' [Mon Dec 30 00:00:04.079698 2013] [auth_digest:notice] [pid 1079:tid 139990628038464] AH01757: generating secret for digest authentication ... [Mon Dec 30 00:00:05.051004 2013] [ssl:warn] [pid 1079:tid 139990628038464] AH01873: Init: Session Cache is not configured [hint: SS