This is a known issue in IBM's 2.0.47 port of Apache (IHS), which was
fixed in a later upstream version (possibly by the 2.2.8 port, but I
really can't say for sure). It would take a lot of digging for me to
locate the specific version, so I'm going to pass on that one. At least
in my case, this message was completely harmless and could be ignored.
What version of Apache are you running? Does this message appear in the
latest stable release?
Thanks,
Rick Houser
Auto-Owners Insurance
Systems Support
(517)703-2580
-Original Message-
From: Jaysingh Samuel [mailto:jayasingh.sam...@hotmail.com]
Sent: Tuesday, September 08, 2009 7:55 AM
To: modules-dev@httpd.apache.org
Subject: RE: Repetitive warnings on ErrorLogs.
Hi soren,
Thanks for useful information on this.
We are not spawning children from the pre/post config, but
still i could see the long lost child alerts. This alerts is
coming only on graceful restart(SIGUSR) of the server and not
on restart on the server.
When i did debug on the worker server_main function i could
see that after the run config is done for all the modules,
there are many process ID thrown with long lost child, and
after that the server resumes with the children.
Iam wondering is the alerts are showing because of the custom
modules what we are using a longer time to finish with?.
Please throw some light on this.
Thanks in advance. Jaysingh Samuel
Date: Mon, 7 Sep 2009 08:51:25 +0200
Subject: Re: Repetitive warnings on ErrorLogs.
From: sor...@gmail.com
To: modules-dev@httpd.apache.org
On Mon, Sep 7, 2009 at 08:41, Jaysingh
Samueljayasingh.sam...@hotmail.com wrote:
Hi,
We are getting the following warning's on the error Logs.
The warning are shown at graceful restart of apache server.
[warn] long lost child came home! (pid 31188)
We are doing graceful restart of apache server every 30
minutes and we get these warning repetitively, i have tested
with the apache restart and that's not showing warning.
Is this a fatal error?. More light on this regarding the
cause and solution to stop this will be very helpful.
Thanks in advance,Jaysingh Samuel.
Apache keeps its children in a table of process IDs, called the
scoreboard. Then, the main server, the one that has created and
started the children processes, waits on them. When the child exits,
the main server looks up the PID of the exiting child in the
scoreboard. If the child is not in the scoreboard, you get this
warning.
It may occur if you start children from your main server
(for example
in the pre/post_config hooks). As you start them yourself,
they won't
be managed by apache, so their PIDs do not appear in the scoreboard.
This would be a harmless way in which you could get the
warning when
you shut down your children.
S
--
A: Because it reverses the logical flow of conversation.
Q: Why is top-posting frowned upon?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
_
We all see it as it is. But on MSN India, the difference lies
in perspective.
http://in.msn.com
