Httpd dies, WHM cannot restart

What OS are you running? Is Apache fairly busy request wise at all times or specifically during the overnight hours? What do you have for min, max, start servers? Is keepalive on? What is the keepalive & normal timeout set to? What is MaxRequestsPerChild set to? Are you limiting the amount of mem/cpu/proc a user can use?

cPanel.net Support Ticket Number:

 

Ouch, defaults are bad. That's like driving from Montreal to Toronto (6 hours) in a brand new car without adjusting the seat, mirrors, etc. It's okay to start, but after an hour or so you need a break and eventually you want to stop for the night because you don't want to drive anymore that day.

Here are some decently tweaked settings for a high end P3, mid-range P4 with 1 - 2 GBs of RAM:

Code:

#
# Timeout: The number of seconds before receives and sends time out.
# 
Timeout 12

# 
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

# 
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.  
# We recommend you leave this number high, for maximum performance.
# 
MaxKeepAliveRequests 0
  
#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
# 
KeepAliveTimeout 8
 
#
# Server-pool size regulation.  Rather than making you guess how many
# server processes you need, Apache dynamically adapts to the load it
# sees --- that is, it tries to maintain enough server processes to     
# handle the current load, plus a few spare servers to handle transient
# load spikes (e.g., multiple simultaneous requests from a single
# Netscape browser).
#
# It does this by periodically checking how many servers are waiting
# for a request.  If there are fewer than MinSpareServers, it creates
# a new spare.  If there are more than MaxSpareServers, some of the
# spares die off.  The default values are probably OK for most sites.
# 
MinSpareServers 8
MaxSpareServers 20

# 
# Number of servers to start initially --- should be a reasonable ballpark
# figure.
#       
StartServers 8

# 
# Limit on total number of servers running, i.e., limit on the number
# of clients who can simultaneously connect --- if this limit is ever
# reached, clients will be LOCKED OUT, so it should NOT BE SET TOO LOW.
# It is intended mainly as a brake to keep a runaway server from taking
# the system with it as it spirals down...
# 
MaxClients 850

#
# MaxRequestsPerChild: the number of requests each child process is
# allowed to process before the child dies.  The child will exit so
# as to avoid problems after prolonged use when Apache (and maybe the
# libraries it uses) leak memory or other resources.  On most systems, this
# isn't really needed, but a few (such as Solaris) do have notable leaks
# in the libraries. For these platforms, set to something like 10000
# or so; a setting of 0 means unlimited.
# 
# NOTE: This value does not include keepalive requests after the initial
#       request per connection. For example, if a child process handles
#       an initial request and 10 subsequent "keptalive" requests, it
#       would only count as 1 request towards this limit.
# 
MaxRequestsPerChild 10000

Then anywhere near the top of the conf file, slam the following in to limit CPU/mem usage

Code:

RLimitMEM 103288149
RLimitCPU 240

Restart Apache and hope for the best. In most cases these are good numbers for a busy Apache/PHP/MySQL driven server. The numbers work well for me on a server that pounds out over 10 M hits a month using PHP/MySQL.

cPanel.net Support Ticket Number:

 

I realize that. But the default settings are going to have each connection to the server hanging around for 300 seconds...5 minutes...for no reason. Along with other ill things due to an erroneous default config file. Killing connections off early (within 12 seconds and not 5 minutes--12 seconds is extremely generous) and having decent settings will more than likely correct the issue of Apache failing.

cPanel.net Support Ticket Number:

 

mod_attach

Had the SAME problem.
Did you see "Cannot remove module mod_attach.c: not found in module list"?

Find the line
#AddModule mod_attach.c

Uncomment that.
(remove #)


And you WILL sleep well.

cPanel.net Support Ticket Number: