LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices

Reply
 
Search this Thread
Old 07-15-2004, 07:08 PM   #1
kloppster
LQ Newbie
 
Registered: Jul 2004
Posts: 22

Rep: Reputation: 15
apache segmentation fault


We recently had to migrate servers from Redhat 7.3 to Redhat Enterprise. We are running a very high traffic site on a dual 2.4 GHZ 2 gig ram machine. Our software is PHP/Mysql intensive. Now most of our migration went relatively smoothly however we are running into problems with the apache 2 that came with Redhat Enterprise.

Every couple of hours our sites become all unreachable and after checking the error_log files we see this as the last thing to log:

[Thu Jul 15 16:52:57 2004] [notice] child pid 22527 exit signal Segmentation fault (11)
[Thu Jul 15 16:52:59 2004] [notice] child pid 22528 exit signal Segmentation fault (11)


I have tried tweaking the conf files as much as possible but can't get around this error. At the time this happened I happened to catch the server status information and it said 130 requests currently being processed and 0 idle workers.

Now 130 is the number of MaxClients we have setup in the conf file.

Any ideas on this would be very helpful.
 
Old 07-16-2004, 11:06 AM   #2
kloppster
LQ Newbie
 
Registered: Jul 2004
Posts: 22

Original Poster
Rep: Reputation: 15
Actually I am not sure if it is the seg faults that are choaking apache. It is wierd because the I just did a grep for Segmentation Fault of the error_logs and find seg faults every hour, however our server hasn't gone done for the last 5 hours (holding breath). Anything that would cause apache to just stop operating?

When it happens all the apache processes are still there, it is just you can't connect or pull any pages from it. So we basically have to run apachectl stop like 3 times to get it to die and finally restart. After the restart the server runs lightning fast for a good little while...

Last edited by kloppster; 07-16-2004 at 11:28 AM.
 
Old 07-16-2004, 05:28 PM   #3
kscott121
Member
 
Registered: Jul 2003
Location: NC
Distribution: Fedora,Mepis,Debian
Posts: 84

Rep: Reputation: 15
I have seen segmentation faults occur due to faulty (usually new) memory. Did you happen to upgrade memory also or shift to a new machine?

You can run memtest for a few hours and see if it turns up anything.
cheers.
Ken
 
Old 07-16-2004, 05:42 PM   #4
kloppster
LQ Newbie
 
Registered: Jul 2004
Posts: 22

Original Poster
Rep: Reputation: 15
Yeah we did just move machines so maybe that is the problem. I will try a memtest and see what it resolves. thanks.
 
Old 07-17-2004, 11:31 PM   #5
kloppster
LQ Newbie
 
Registered: Jul 2004
Posts: 22

Original Poster
Rep: Reputation: 15
Humm after watching this server for the last couple of days (and watching it die every so often) I am seeing some trends in the server-status. I notice that it doesn't seem to be finishing requests, or rather closing them. People are view the pages fine but it seems after that a few connections stay stuck or something... Currently we have:

204 requests currently being processed, 8 idle workers

Which is WAY higher than it should be for this time of day. Also I have noticed that in the list of processes that the top of the list doesn't seem to change, they just sit there stuck on Gracefully finishing but never finish... Has anyone know why this is happening and if this is possibly why my server just stops working after a while?
 
Old 07-19-2004, 12:22 PM   #6
kloppster
LQ Newbie
 
Registered: Jul 2004
Posts: 22

Original Poster
Rep: Reputation: 15
After further investigation we find that certain scripts of ours are not finishing and thus causing the httpd process it was working on to be left in a constant state of waiting. This process is then riddled useless and I think is the reason why our server eventually stop working (too many processes or connections or something). Anyway is there anyway to make this process just die, or timeout or something?
 
Old 07-19-2004, 01:56 PM   #7
kscott121
Member
 
Registered: Jul 2003
Location: NC
Distribution: Fedora,Mepis,Debian
Posts: 84

Rep: Reputation: 15
This is way over my head but perhaps you could (or somebody could) fashion some sort of Cron job that monitored the health of that process and killed it if it was frozen.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Apache segmentation fault with with default index files paijm021 Linux - Software 13 04-22-2004 08:51 AM
HELP PLEASE! Apache Segmentation Fault gabriele_101 Linux - Software 4 08-01-2003 12:56 AM
Apache: child pid XXX exit signal Segmentation fault (11) gabriele_101 Linux - Hardware 1 07-23-2003 06:12 PM
Apache CGI Segmentation Fault Jon- Linux - Software 1 07-15-2003 09:16 AM
Apache Segmentation Fault.... morbo Linux - General 2 12-14-2001 03:14 PM


All times are GMT -5. The time now is 08:22 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration