Web Hosting Talk







View Full Version : Apache / Cpanel issues


Laws
12-30-2004, 07:21 AM
I have a Cpanel server that is experiencing numerous apache problems…

Apache runs fine, however during the graceful restarts Cpanel does throughout the course of the day it seems to crash…

Various log examples –

[Wed Dec 29 02:23:51 2004] [notice] child pid 20070 exit signal Segmentation fault (11)
[Wed Dec 29 02:39:47 2004] [notice] child pid 20085 exit signal Segmentation fault (11)
[Wed Dec 29 06:01:08 2004] [notice] child pid 19911 exit signal Segmentation fault (11)
[Wed Dec 29 06:03:04 2004] [notice] child pid 20089 exit signal Segmentation fault (11)
[Wed Dec 29 06:50:14 2004] [notice] child pid 19926 exit signal Segmentation fault (11)
[Wed Dec 29 07:36:43 2004] [notice] child pid 20075 exit signal Segmentation fault (11)
[Wed Dec 29 07:56:45 2004] [notice] child pid 19916 exit signal Segmentation fault (11)
[Wed Dec 29 07:57:13 2004] [notice] child pid 19912 exit signal Segmentation fault (11)
[Wed Dec 29 08:07:55 2004] [notice] child pid 15518 exit signal Segmentation fault (11)
[Wed Dec 29 08:12:42 2004] [notice] child pid 12174 exit signal Segmentation fault (11)
[Wed Dec 29 08:33:36 2004] [notice] child pid 595 exit signal Segmentation fault (11)
[Wed Dec 29 11:26:26 2004] [warn] child process 19909 did not exit, sending another SIGHUP
[Wed Dec 29 11:26:26 2004] [warn] child process 32370 did not exit, sending another SIGHUP
[Wed Dec 29 11:26:26 2004] [warn] child process 19910 did not exit, sending another SIGHUP
[Wed Dec 29 11:26:26 2004] [warn] child process 17187 did not exit, sending another SIGHUP
[Wed Dec 29 11:26:26 2004] [warn] child process 32375 did not exit, sending another SIGHUP
[Wed Dec 29 11:26:26 2004] [warn] child process 19913 did not exit, sending another SIGHUP
[Wed Dec 29 11:26:26 2004] [warn] child process 19915 did not exit, sending another SIGHUP
[Wed Dec 29 11:26:26 2004] [warn] child process 19919 did not exit, sending another SIGHUP
[Wed Dec 29 11:26:26 2004] [warn] child process 32387 did not exit, sending another SIGHUP
[Wed Dec 29 11:26:26 2004] [warn] child process 19922 did not exit, sending another SIGHUP
[Wed Dec 29 11:26:26 2004] [warn] child process 19927 did not exit, sending another SIGHUP
[Wed Dec 29 11:26:26 2004] [warn] child process 21394 did not exit, sending another SIGHUP
[Wed Dec 29 11:26:26 2004] [warn] child process 20253 did not exit, sending another SIGHUP
[Wed Dec 29 11:26:26 2004] [warn] child process 22287 did not exit, sending another SIGHUP
[Wed Dec 29 11:26:26 2004] [warn] child process 15516 did not exit, sending another SIGHUP
[Wed Dec 29 11:26:26 2004] [warn] child process 17191 did not exit, sending another SIGHUP
[Wed Dec 29 11:26:28 2004] [warn] child process 19909 still did not exit, sending a SIGTERM
[Wed Dec 29 11:26:28 2004] [warn] child process 32370 still did not exit, sending a SIGTERM
[Wed Dec 29 11:26:28 2004] [warn] child process 19910 still did not exit, sending a SIGTERM
[Wed Dec 29 11:26:28 2004] [warn] child process 17187 still did not exit, sending a SIGTERM
[Wed Dec 29 11:26:28 2004] [warn] child process 32375 still did not exit, sending a SIGTERM
[Wed Dec 29 11:26:28 2004] [warn] child process 19913 still did not exit, sending a SIGTERM
[Wed Dec 29 11:26:28 2004] [warn] child process 19915 still did not exit, sending a SIGTERM
[Wed Dec 29 11:26:28 2004] [warn] child process 19919 still did not exit, sending a SIGTERM
[Wed Dec 29 11:26:28 2004] [warn] child process 32387 still did not exit, sending a SIGTERM
[Wed Dec 29 11:26:28 2004] [warn] child process 19922 still did not exit, sending a SIGTERM
[Wed Dec 29 11:26:28 2004] [warn] child process 19927 still did not exit, sending a SIGTERM
[Wed Dec 29 11:26:28 2004] [warn] child process 21394 still did not exit, sending a SIGTERM
[Wed Dec 29 11:26:28 2004] [warn] child process 20253 still did not exit, sending a SIGTERM
[Wed Dec 29 11:26:28 2004] [warn] child process 22287 still did not exit, sending a SIGTERM
[Wed Dec 29 11:26:28 2004] [warn] child process 15516 still did not exit, sending a SIGTERM
[Wed Dec 29 11:26:28 2004] [warn] child process 17191 still did not exit, sending a SIGTERM
[Wed Dec 29 11:26:32 2004] [error] child process 19909 still did not exit, sending a SIGKILL
[Wed Dec 29 11:26:35 2004] [error] child process 32370 still did not exit, sending a SIGKILL
[Wed Dec 29 11:26:35 2004] [error] child process 19910 still did not exit, sending a SIGKILL
[Wed Dec 29 11:26:35 2004] [error] child process 17187 still did not exit, sending a SIGKILL
[Wed Dec 29 11:26:35 2004] [error] child process 32375 still did not exit, sending a SIGKILL
[Wed Dec 29 11:26:35 2004] [error] child process 19913 still did not exit, sending a SIGKILL
[Wed Dec 29 11:26:35 2004] [error] child process 19915 still did not exit, sending a SIGKILL
[Wed Dec 29 11:26:35 2004] [error] child process 19919 still did not exit, sending a SIGKILL
[Wed Dec 29 11:26:35 2004] [error] child process 32387 still did not exit, sending a SIGKILL
[Wed Dec 29 11:26:35 2004] [error] child process 19922 still did not exit, sending a SIGKILL
[Wed Dec 29 11:26:35 2004] [error] child process 19927 still did not exit, sending a SIGKILL
[Wed Dec 29 11:26:35 2004] [error] child process 21394 still did not exit, sending a SIGKILL
[Wed Dec 29 11:26:35 2004] [error] child process 20253 still did not exit, sending a SIGKILL
[Wed Dec 29 11:26:35 2004] [error] child process 22287 still did not exit, sending a SIGKILL
[Wed Dec 29 11:26:35 2004] [error] child process 15516 still did not exit, sending a SIGKILL
[Wed Dec 29 11:26:35 2004] [error] child process 17191 still did not exit, sending a SIGKILL

I have recompiled apache and updated Cpanel to the newest RELEASE build.

I’ve modified the httpd configuration slightly since this was suggested but it hasn’t helped.

I’d really like to get this server back to having no apache outages during the day….

Haze
12-30-2004, 10:34 AM
What happens in the apache error log when restarting via WHM ? Anything in messages ? what does service httpd configtest show ? Any chance a partition might be full ? ( df -h )

Laws
12-30-2004, 06:07 PM
1) Nothing

2) Nothing in messages

3) Configtest says Syntax OK

4) No Partitions full

Still no luck in finding issue...I hate cpanel!

Steven
12-30-2004, 06:08 PM
Did you install any of the addons, tomcat, mod_security, resin, etc?

Laws
12-30-2004, 06:20 PM
Expires Module
Raise FD_SETSIZE to 16384 (System Wide)
Prevent Users from reading other webroots
Frontpage Module
Raise HARD_SERVER_LIMIT
Php Module (Version 4.3.3)
PHP Version 4.3.9
Bc Math
Calendar Support
FTP
GD
Mcrypt (Version 2.5.7)
Mhash (Version 0.8.18)
Magic Quotes
Mysql Module
Pear
Postgresql (will break 7.2.x or earlier, please make sure you have 7.3.x or later installed)
Sockets
Track Vrs
Zlib
Versioning


These are what Apache was compiled with.

Steven
12-30-2004, 06:23 PM
No not that, I am talking about the "addon modules" in whm

Laws
12-30-2004, 06:30 PM
Sorry, no, no addon modules installed.

Haze
12-30-2004, 11:42 PM
Any reason your installing 2 vulnerable php versions instead of the 1 non vulnerable one ?
I'm not sure if installing 2 versions would cause that error, but it might be.

Website Rob
12-31-2004, 04:48 AM
Segmentation faults can also be caused by badly coded (php) scripts. PHP-Nuke used to be famous for them.

Also, what version of Zend is being used?