Web Hosting Forum | Lunarpages


*
Welcome, Guest. Please login or register.
Did you miss your activation email?



Login with username, password and session length
May 25, 2012, 10:17:52 AM

Pages: [1]   Go Down
  Print  
Author Topic: Web Server (Apache) service stops running  (Read 3202 times)
Aneurysm
All around nice guy
Intergalactic Cowboy
*****
Offline Offline

Posts: 65


I'm not drunk (anymore), I'm just stupid!


WWW
« on: April 07, 2010, 11:33:48 PM »

I keep getting the following 2 emails 5-10 times a day, How do I figure out what is causing the service to stop? I have done some searching but can't come up with anything, where I should start looking for clues?

1st email
The Web Server (Apache) service on host vps.mydomain.com  is down.
The problem was discovered on Apr  7, 2010 10:49 PM.

2nd email
The Web Server (Apache) service on host vps.mydomain.com  has been started on Apr  7, 2010 10:55 PM.
« Last Edit: April 10, 2010, 08:01:02 AM by Aneurysm » Logged

www.copytechnet.com - tech forum and technical help for copier, laser printer, and fax repair technicians.
AdrianAvadani
zombie
SysAdmin
Trekkie
*****
Offline Offline

Posts: 15


WWW
« Reply #1 on: April 08, 2010, 05:46:28 PM »

Hello,

The apache error log file (/usr/local/apache/logs/error_log for CPanel servers or /var/log/httpd/error_log for the other environments) would usually contain the reason for the shutdown. If you can not grab the needed information from the error_log, a support ticket sent to the Dedicated department can have one of my our admins look into these particular occurrences and what might be causing them


Thank you..
Logged

Adrian Avadani
System Administrator Team

Telephone: 1-714-521-8150
Fax: 1-714-521-8195
Aneurysm
All around nice guy
Intergalactic Cowboy
*****
Offline Offline

Posts: 65


I'm not drunk (anymore), I'm just stupid!


WWW
« Reply #2 on: April 10, 2010, 08:19:04 AM »

Here is what my log indicates at the time of the problem (I will work on the zend upgrade but I don't think that is it because I was having the same issue before I upgraded my PHP a few months ago.

Code:
[Sat Apr 10 07:37:35 2010] [notice] caught SIGTERM, shutting down
[Sat Apr 10 07:37:36 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Apr 10 07:37:36 2010] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Apr 10 07:37:36 2010] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Apr 10 07:37:36 2010] [notice] Digest: generating secret for digest authentication ...
[Sat Apr 10 07:37:36 2010] [notice] Digest: done
[Sat Apr 10 07:37:36 2010] [notice] LDAP: Built with OpenLDAP LDAP SDK
[Sat Apr 10 07:37:36 2010] [notice] LDAP: SSL support unavailable
PHP Warning:  Zend Optimizer does not support this version of PHP - please upgrade to the latest version of Zend Optimizer in Unknown on line 0
[Sat Apr 10 07:37:37 2010] [notice] mod_python: Creating 4 session mutexes based on 10 max processes and 0 max threads.
[Sat Apr 10 07:37:37 2010] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Apr 10 07:37:37 2010] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Apr 10 07:37:37 2010] [notice] Apache/2.0.52 (CentOS) configured -- resuming normal operations
[Sat Apr 10 07:37:46 2010] [error] server reached MaxClients setting, consider raising the MaxClients setting
Logged

www.copytechnet.com - tech forum and technical help for copier, laser printer, and fax repair technicians.
AdrianAvadani
zombie
SysAdmin
Trekkie
*****
Offline Offline

Posts: 15


WWW
« Reply #3 on: April 11, 2010, 09:58:05 PM »

Hello,

We're missing exactly the line (if there's any) before the 'stop' request (the 'SIGTERM' command). Based on what follows, though, I can confirm that:
- the Zend issue is not a critical error and doesnt influences the running state of Apache - it just tells you that 'zend opt wont be used';
- the MaxClients setting is what might cause the issue. It doesnt actually render your website as 'down', but one might think so; what it does is queuing each connection past the number X (where 'X' is defined in a 'MaxClients X' line in httpd.conf) in order to prevent Apache from serving too many webpages to too many visitors simultaneously - a variable set to ensure that you wont run out of the needed RAM memory. A ticket could help us have a quick look through your configuration and we'd then be able to advise you whether the limitation can be safely raised or if you're simply using too much RAM, or, by contrary, if the issue lies somewhere else.


Thank you.
Logged

Adrian Avadani
System Administrator Team

Telephone: 1-714-521-8150
Fax: 1-714-521-8195
Aneurysm
All around nice guy
Intergalactic Cowboy
*****
Offline Offline

Posts: 65


I'm not drunk (anymore), I'm just stupid!


WWW
« Reply #4 on: April 12, 2010, 09:31:18 PM »

I have nothing before the 'SIGTERM' in the logs for the time frame of the crashes.  I made some changes to my robots.txt to slow down the search engines but that didn't make any difference.   

...I guess it is time to open a ticket.  

Thanks for the help!
« Last Edit: April 12, 2010, 09:43:03 PM by Aneurysm » Logged

www.copytechnet.com - tech forum and technical help for copier, laser printer, and fax repair technicians.
Aneurysm
All around nice guy
Intergalactic Cowboy
*****
Offline Offline

Posts: 65


I'm not drunk (anymore), I'm just stupid!


WWW
« Reply #5 on: April 16, 2010, 12:03:15 AM »

FYI...  MaxUsers was the cause, Support took care of it for me and it has been good for a few days. 

Thanks!!
Logged

www.copytechnet.com - tech forum and technical help for copier, laser printer, and fax repair technicians.
AdrianAvadani
zombie
SysAdmin
Trekkie
*****
Offline Offline

Posts: 15


WWW
« Reply #6 on: April 17, 2010, 01:12:47 AM »

Hello,

Glad to hear it's all working now  Thumbs Up


Logged

Adrian Avadani
System Administrator Team

Telephone: 1-714-521-8150
Fax: 1-714-521-8195
Pages: [1]   Go Up
  Print  
 
Jump to: