> -----Original Message----- > From: Graham Frank [mailto:gfrank@xxxxxxxxxxxxxx] > Sent: Montag, 5. Dezember 2005 20:55 > To: users@xxxxxxxxxxxxxxxx > Subject: RE: [users@httpd] Child errors causing Apache to exit > > > You also asked about how the crash works? When the child > returns the error, the Apache parent process dies and Apache > goes completely offline. I have to manually restart Apache. You need to cross-ref the access logs to see what request is doing this... Rgds, Owen Boyle Disclaimer: Any disclaimer attached to this message may be ignored. > > ----------------------------------- > Graham Frank > (608) 359-1593 > Neoservers LLC - http://www.neoservers.com/ > Founder/Owner > > -----Original Message----- > From: Boyle Owen > Date: 12/5/05 7:31 am > To: users@xxxxxxxxxxxxxxxx > Subj: RE: [users@httpd] Child errors causing Apache to exit > > > > > -----Original Message----- > > From: Graham Frank [mailto:gfrank@xxxxxxxxxxxxxx] > > Sent: Montag, 5. Dezember 2005 09:47 > > To: users@xxxxxxxxxxxxxxxx > > Subject: RE: [users@httpd] Child errors causing Apache to exit > > > > > > Sorry for the lack of info. > > > > OS: Redhat Enterprise Linux 3 > > Apache 1.3.34 > > PHP 4.4.0 > > mod_security > > > > This server only keeps an error log and loglevel crit because > > of how active it is. Access, transfer, and other logs > > actually end up causing the system to slow down. This isn't > > a hardware issue, but instead it is just extremely active. > > > > We've never had these issues before. They just started > > showing up a few weeks ago. > > And what happened then? Did you add a new PHP > page/functionality, by any chance? > > > > > I will see about running the access log for a short period of time. > > Logging is an important part of web-serving. If your server > is so busy that you have to cut corners by suppressing > logging, that would be a good reason to invest in a more > powerful server. > > BTW, it wasn't clear from your original post - do the alerts > you see coincide with the entire apache server hanging or > crashing? Or is it just one daemon that dies (ie, the browser > session dies but you can access from elsewhere)? > > Rgds, > Owen Boyle > Disclaimer: Any disclaimer attached to this message may be ignored. > > > > > Thanks. > > > > ----------------------------------- > > Graham Frank > > (608) 359-1593 > > Neoservers LLC - http://www.neoservers.com/ > > Founder/Owner > > > > -----Original Message----- > > From: Boyle Owen > > Date: 12/5/05 2:26 am > > To: users@xxxxxxxxxxxxxxxx > > Subj: RE: [users@httpd] Child errors causing Apache to exit > > > > > -----Original Message----- > > > From: Graham Frank [mailto:gfrank@xxxxxxxxxxxxxx] > > > Sent: Sonntag, 4. Dezember 2005 02:46 > > > To: users@xxxxxxxxxxxxxxxx > > > Subject: [users@httpd] Child errors causing Apache to exit > > > > > > > > > > > > So I've been paying attention to my ErrorLog lately as Apache > > > has been crashing > > > about once per day with errors such as: > > > > > > [Thu Dec 1 10:00:02 2005] [alert] Child 27698 returned a > > > Fatal error... > > > \nApache is exiting! > > > [Fri Dec 2 07:05:02 2005] [alert] Child 30200 returned a > > > Fatal error... > > > \nApache is exiting! > > > > > > Well, that's fine and all that it is at least telling me that > > > it crashed, but > > > how about a little more information? > > > > How about a little more information? OS? Apache version? What > > modules are compiled in & loaded? What additional > > applications are involved (mod_perl, SSL, PHP, SQL etc)? > > > > Also, cross reference the alerts with the access list using > > the timestamp and identify the requests that are causing the > > crashes. Then re-issue the request and try to reproduce it. > > > > Note that the error condition is arising in a low-level call > > which may not be aware which application called it - hence > > the lack of details... > > > > Rgds, > > Owen Boyle > > Disclaimer: Any disclaimer attached to this message may be ignored. > > > > > > > > Is there any way I can get Apache to be a bit more useful > > > when it comes to > > > figuring out why the children are returning fatal errors? I > > > can't fix the > > > problem if I don't know what the problem is or any clues > > > hinting to it. > > > > > > Thanks! > > > > > > -------------------------------------------------------------- > > > ------------------ > > > Graham Frank > > > (608) 359-1593 > > > Neoservers LLC (http://www.neoservers.com/) > > > Founder and Owner > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > The official User-To-User support forum of the Apache HTTP > > > Server Project. > > > See <URL:http://httpd.apache.org/userslist.html> for more info. > > > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > > > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > > > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > > > > > > > > Diese E-mail ist eine private und persönliche Kommunikation. > > Sie hat keinen Bezug zur Börsen- bzw. Geschäftstätigkeit der > > SWX Gruppe. This e-mail is of a private and personal nature. > > It is not related to the exchange or business activities of > > the SWX Group. Le présent e-mail est un message privé et > > personnel, sans rapport avec l'activité boursière du Groupe SWX. > > > > > > This message is for the named person's use only. It may > > contain confidential, proprietary or legally privileged > > information. No confidentiality or privilege is waived or > > lost by any mistransmission. If you receive this message in > > error, please notify the sender urgently and then immediately > > delete the message and any copies of it from your system. > > Please also immediately destroy any hardcopies of the > > message. You must not, directly or indirectly, use, disclose, > > distribute, print, or copy any part of this message if you > > are not the intended recipient. The sender's company reserves > > the right to monitor all e-mail communications through their > > networks. Any views expressed in this message are those of > > the individual sender, except where the message states > > otherwise and the sender is authorised to state them to be > > the views of the sender's company. > > > > > --------------------------------------------------------------------- > > The official User-To-User support forum of the Apache HTTP > > Server Project. > > See <URL:http://httpd.apache.org/userslist.html> for more info. > > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > > > > > > > > > --------------------------------------------------------------------- > > The official User-To-User support forum of the Apache HTTP > > Server Project. > > See <URL:http://httpd.apache.org/userslist.html> for more info. > > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > > > > > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP > Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > > > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP > Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|