Hi! This is the ezmlm program. I'm managing the
dev httpd.apache.org mailing list.
Messages to you from the dev mailing list seem to
have been bouncing. I've attached a copy of the first
bounce
message I received.
If this message bounces too, I will send you a probe. If the
probe bounces,
I will remove your address from the dev mailing list,
without further notice.
I've kept a list of which messages from the dev mailing list
have
bounced from your address.
Copies of these messages may be in the archive.
To retrieve a set of messages 123-145 (a maximum of 100 per
request),
send a short message to:
<dev-get.123_145httpd.apache.org>
To receive a subject and author list for the last 100 or so
messages,
send a short message to:
<dev-indexhttpd.apache.org>
Here are the message numbers:
59118
59119
59120
59121
59122
59123
59124
59125
59126
59127
59128
59129
59130
59131
59132
59133
59134
59135
59136
59137
59138
59139
59140
59141
59142
59143
59144
59145
59146
59147
59148
59149
59150
59151
59152
59153
59154
59155
59156
59157
59158
59159
59160
59161
59162
59163
59164
59165
59166
59167
59168
59169
59170
59171
59172
59173
59174
59176
59175
59177
59178
59179
59180
59181
59182
59183
59184
59185
59186
--- Enclosed is a copy of the bounce message I received.
Return-Path: <>
Received: (qmail 7246 invoked by uid 99); 26 Oct 2007
11:33:04 -0000
Received: from athena.apache.org (HELO athena.apache.org)
(140.211.11.136)
by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Oct
2007 04:33:04 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
tests=SPF_HELO_PASS
X-Spam-Check-By: apache.org
Received: from [66.98.192.98] (HELO starfire.yahoo.com)
(66.98.192.98)
by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Oct
2007 11:33:06 +0000
Received: by starfire.yahoo.com (Postfix)
id 898094002B4; Fri, 26 Oct 2007 06:32:45 -0500 (CDT)
Date: Fri, 26 Oct 2007 06:32:45 -0500 (CDT)
From: MAILER-DAEMONyahoo.com (Mail Delivery System)
Subject: Undelivered Mail Returned to Sender
To: dev-return-59118-bond=yahoo.comhttpd.apache.org
Auto-Submitted: auto-replied
MIME-Version: 1.0
Content-Type: multipart/report;
report-type=delivery-status;
boundary="6035B208248.1193398365/starfire.yahoo.com&qu
ot;
Content-Transfer-Encoding: 8bit
Message-Id: <20071026113245.898094002B4starfire.yahoo.com>
X-Virus-Checked: Checked by ClamAV on apache.org
This is a MIME-encapsulated message.
--6035B208248.1193398365/starfire.yahoo.com
Content-Description: Notification
Content-Type: text/plain; charset=us-ascii
This is the mail system at host starfire.yahoo.com.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached
below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The mail system
<bondyahoo.com>: cannot update mailbox /var/mail/bond
for user bond. error
writing message: File too large
--6035B208248.1193398365/starfire.yahoo.com
Content-Description: Delivery report
Content-Type: message/delivery-status
Reporting-MTA: dns; starfire.yahoo.com
X-Postfix-Queue-ID: 6035B208248
X-Postfix-Sender: rfc822;
dev-return-59118-bond=yahoo.comhttpd.apache.org
Arrival-Date: Fri, 26 Oct 2007 06:32:45 -0500 (CDT)
Final-Recipient: rfc822; bondyahoo.com
Original-Recipient: rfc822;bondyahoo.com
Action: failed
Status: 5.2.2
Diagnostic-Code: x-unix; input/output error
--6035B208248.1193398365/starfire.yahoo.com
Content-Description: Undelivered Message
Content-Type: message/rfc822
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: amavisd-new at yahoo.com
Received: from starfire.yahoo.com ([127.0.0.1])
by localhost (starfire.yahoo.com [127.0.0.1]) (amavisd-new,
port 10024)
with ESMTP id rZP+B9ulZ0oO for <bondyahoo.com>;
Fri, 26 Oct 2007 06:32:39 -0500 (CDT)
Received: from mail.apache.org (hermes.apache.org
[140.211.11.2])
by starfire.yahoo.com (Postfix) with SMTP id C0C142080F7
for <bondyahoo.com>; Fri, 26 Oct 2007 06:32:38
-0500 (CDT)
Received: (qmail 5750 invoked by uid 500); 26 Oct 2007
11:32:23 -0000
Mailing-List: contact dev-helphttpd.apache.org; run by
ezmlm
Precedence: bulk
Reply-To: devhttpd.apache.org
list-help: <mailto:dev-helphttpd.apache.org>
list-unsubscribe: <mailto:dev-unsubscribehttpd.apache.org>
List-Post: <mailto:devhttpd.apache.org>
List-Id: <dev.httpd.apache.org>
Delivered-To: mailing list devhttpd.apache.org
Received: (qmail 5739 invoked by uid 99); 26 Oct 2007
11:32:23 -0000
Received: from athena.apache.org (HELO athena.apache.org)
(140.211.11.136)
by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Oct
2007 04:32:23 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of trawickgmail.com
designates 64.233.182.187 as permitted sender)
Received: from [64.233.182.187] (HELO
nf-out-0910.google.com) (64.233.182.187)
by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Oct
2007 11:32:27 +0000
Received: by nf-out-0910.google.com with SMTP id
c10so659710nfd
for <devhttpd.apache.org>; Fri, 26 Oct 2007
04:32:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=beta;
h=domainkey-signature:received:received:message-id:date:from
:to:subject:in-reply-to:mime-version:content-type:content-tr
ansfer-encoding:content-disposition:references;
bh=V7+AVqY3WD9z96+hJNEyvZxDUX45SqABGC6uekqq7bM=;
b=PCcEcKpkdB8PF5kiDF5o1soyb+ldGqBwpkQ2onoBiIRZ9A9RCo/sGtqV5J
cfiYGFrPZg3PWrarP2Q0Q9jQa1DiSL1FsTRuiEO3zljpkaepIEvja+Yr7xyC
AJ0tpVsX+MxDodh8u5f0iwMiVomPwoUGJeYBBCsIJ0M6XwktS5B/A=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=beta;
h=received:message-id:date:from:to:subject:in-reply-to:mime-
version:content-type:content-transfer-encoding:content-dispo
sition:references;
b=tpN9SJvRACaesidhJuqktv1hHn79G2xLC4iiD+YnFMhLlowbyit1jOSeta
/eUMTAZDnojxbJsuP8rgeL+XkDQwEW0m2gN3tQ4T9Y6fOcx902O/yFKHu4tn
Bbx/i0fxB97kisf+wbZnUFGybnkWf9YFVLyyo73/EDhRmE44s2ez4=
Received: by 10.78.179.12 with SMTP id
b12mr2207002huf.1193398326244;
Fri, 26 Oct 2007 04:32:06 -0700 (PDT)
Received: by 10.78.183.8 with HTTP; Fri, 26 Oct 2007
04:32:06 -0700 (PDT)
Message-ID:
<cc67648e0710260432s6428e419n6c89cee7121818f5mail.gmail.com>
Date: Fri, 26 Oct 2007 07:32:06 -0400
From: "Jeff Trawick" <trawickgmail.com>
To: devhttpd.apache.org
Subject: Re: bogus "Bad pid (%d) in scoreboard slot
%d" messages when restarting 1.3
In-Reply-To: <93AD0E83-8519-48D8-A660-5E0069593433jaguNET.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References:
<cc67648e0710250800lc09985buee3b3619aecfed88mail.gmail.com>
<93AD0E83-8519-48D8-A660-5E0069593433jaguNET.com>
X-Virus-Checked: Checked by ClamAV on apache.org
On 10/25/07, Jim Jagielski <jimjagunet.com> wrote:
> On Oct 25, 2007, at 11:00 AM, Jeff Trawick wrote:
>
> > I think this is the problem: When a child is
reaped normally after
> > exiting due to MaxSpareServers or
MaxRequestsPerChild, it remains in
> > the scoreboard with status set to SERVER_DEAD, and
it is removed from
> > the pid table.
> >
> > Often that slot will be reused by a child created
subsequently.
> >
> > If it is never reused before termination or hard
restart,
> > reclaim_child_processes() will see it in this code
and complain that
> > it isn't in the pid table:
>
> Yep... that appears to be it. When setting SERVER_DEAD
we
> aren't resetting the pid as well. Instead of working
around
> that, wouldn't the most straightforward approach be to
> sync setting SERVER_DEAD status with also setting pid
to 0?
> This could be done in ap_update_child_status() which
would
> also hopefully address those file-based scoreboards as
well.
sure; I'm lacking cycles at the moment to start looking
through the
code for potential fallout; hope to start looking soon
--6035B208248.1193398365/starfire.yahoo.com--
|