Re: [WebDNA] Apache 2 Error Log Entry

This WebDNA talk-list message is from

2009


It keeps the original formatting.
numero = 102688
interpreted = N
texte = Palle Bo Nielsen wrote: > Hi all, > > My Apache Error log is getting full of these warnings. Anyone know what > they are all about? > > My server is getting some what on it's knees these days and this might > be the reason, but I dontt know anything about this error... > > [Mon Jun 08 17:03:57 2009] [warn] child process 3156 still did not exit, > sending a SIGTERM > [Mon Jun 08 17:03:57 2009] [warn] child process 3122 still did not exit, > sending a SIGTERM > [Mon Jun 08 17:03:57 2009] [warn] child process 3123 still did not exit, > sending a SIGTERM > [Mon Jun 08 17:03:57 2009] [warn] child process 3158 still did not exit, > sending a SIGTERM > [Mon Jun 08 17:03:57 2009] [warn] child process 3159 still did not exit, > sending a SIGTERM > [Mon Jun 08 17:03:57 2009] [warn] child process 3166 still did not exit, > sending a SIGTERM > [Mon Jun 08 17:03:57 2009] [warn] child process 3167 still did not exit, > sending a SIGTERM > [Mon Jun 08 17:03:57 2009] [warn] child process 3169 still did not exit, > sending a SIGTERM > [Mon Jun 08 17:03:57 2009] [warn] child process 3206 still did not exit, > sending a SIGTERM > [Mon Jun 08 17:03:59 2009] [notice] caught SIGTERM, shutting down > > Palle Hi Palle, is WebDNA pegging at 100%? You would have to then start troubleshooting all the normal areas. For example, turn on the error reporting features, then check the logfiles that are created etc. If you can anticipate, for example, when your webcatalog processes start to "clog" the pipes, you can use tools such as strace (for very short periods of time) to give you clues. (search the archives for strace). Sometimes, clues can be given if you can't reach certain 'pages'. If you get hints as to where the problem is, you can start "turning off" aspects of your code to see if you can isolate where the problem is. Troubleshooting a server is a process of isolation, I think, using various tools. It is difficult for an outsider to offer help unless a lot of info is offered. Donovan -- Donovan Brooke WebDNA Software Corporation http://www.webdna.us **[Square Bracket Utopia]** Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Apache 2 Error Log Entry (Donovan Brooke 2009)
  2. Re: [WebDNA] Apache 2 Error Log Entry (Palle Bo Nielsen 2009)
  3. Re: [WebDNA] Apache 2 Error Log Entry (Palle Bo Nielsen 2009)
  4. Re: [WebDNA] Apache 2 Error Log Entry (Donovan Brooke 2009)
  5. Re: [WebDNA] Apache 2 Error Log Entry (christophe.billiottet@webdna.us 2009)
  6. [WebDNA] Apache 2 Error Log Entry (Palle Bo Nielsen 2009)
Palle Bo Nielsen wrote: > Hi all, > > My Apache Error log is getting full of these warnings. Anyone know what > they are all about? > > My server is getting some what on it's knees these days and this might > be the reason, but I dontt know anything about this error... > > [Mon Jun 08 17:03:57 2009] [warn] child process 3156 still did not exit, > sending a SIGTERM > [Mon Jun 08 17:03:57 2009] [warn] child process 3122 still did not exit, > sending a SIGTERM > [Mon Jun 08 17:03:57 2009] [warn] child process 3123 still did not exit, > sending a SIGTERM > [Mon Jun 08 17:03:57 2009] [warn] child process 3158 still did not exit, > sending a SIGTERM > [Mon Jun 08 17:03:57 2009] [warn] child process 3159 still did not exit, > sending a SIGTERM > [Mon Jun 08 17:03:57 2009] [warn] child process 3166 still did not exit, > sending a SIGTERM > [Mon Jun 08 17:03:57 2009] [warn] child process 3167 still did not exit, > sending a SIGTERM > [Mon Jun 08 17:03:57 2009] [warn] child process 3169 still did not exit, > sending a SIGTERM > [Mon Jun 08 17:03:57 2009] [warn] child process 3206 still did not exit, > sending a SIGTERM > [Mon Jun 08 17:03:59 2009] [notice] caught SIGTERM, shutting down > > Palle Hi Palle, is WebDNA pegging at 100%? You would have to then start troubleshooting all the normal areas. For example, turn on the error reporting features, then check the logfiles that are created etc. If you can anticipate, for example, when your webcatalog processes start to "clog" the pipes, you can use tools such as strace (for very short periods of time) to give you clues. (search the archives for strace). Sometimes, clues can be given if you can't reach certain 'pages'. If you get hints as to where the problem is, you can start "turning off" aspects of your code to see if you can isolate where the problem is. Troubleshooting a server is a process of isolation, I think, using various tools. It is difficult for an outsider to offer help unless a lot of info is offered. Donovan -- Donovan Brooke WebDNA Software Corporation http://www.webdna.us **[Square Bracket Utopia]** Donovan Brooke

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Pithy questions on webcommerce & siteedit (1997) WC2b15 File Corruption (1997) Emailer setup (1997) 2.0Beta Command Ref (can't find this instruction) (1997) Credit card arrangement (2005) File Uploads: WebCat/SiteEdit (1998) WebCat b15 Mac plug-in (1997) Merging databases (1997) MacAuthorize Directory (2000) Help! WebCat2 bug (1997) OT-JS question (2001) combine search (1998) inconsistent webcat calculation? (1997) re-sorting founditems (2002) Referrer from multiple entry points (1998) Multiple Pulldowns (1997) Questions To Answer (1997) FEW QUESTIONS (1997) AOL Sux and Other Thoughts (2000) [OT] "Hacker Safe" (2007)