Sorry for the double post - I though I killed the one sent from the wrong account.

So this is a case of Mailman not giving up on a Sendmail problem/bug? Been digging through the logs trying to gain more insight, don't know if any of this helps.

My main mail logs have this entry 11 times in one second.

Jul 18 22:30:31 svr01 sendmail[24527]: h6J3UVp24527: 7: fl=0x0, mode=100644: size=12288
Jul 18 22:30:31 svr01 sendmail[24527]: h6J3UVp24527: SYSERR(root): cannot flock(/etc/mail/access.db, fd=7, type=1, omode
=37777777777, euid=0): No locks available


Then this:

Jul 18 22:30:31 svr01 sendmail[24527]: h6J3UVp24527: from=<[EMAIL PROTECTED]>, size=4278, class=0, nrcpts=0, proto=ESMTP, daemon=MTA, relay=localhost.localdomain [127.0.0.1]

Which seems to be the end of it - except that mail man would not let go. I let it run 15 minutes the second time, to see if it would die on it's own.

I have found that both individuals belong to two lists, and in each case one of the two messages send went out just fine (half an hour apart at most) and both e-mails worked one days before and after the problem.


At 10:57 AM 7/20/2003, you wrote:
Message: 2
Date: Sat, 19 Jul 2003 11:32:37 -0500
From: Paul H Byerly <[EMAIL PROTECTED]>
Subject: [Mailman-Users] run away process - cannot flock
To: [EMAIL PROTECTED]
Message-ID:
        <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"; format=flowed


Twice now my CPU has pegged after a message went through Mailman. Top shows a python2.2 process belonging to Mailman. Shutting Mailman down stops it, but it comes right back when Mailman is restarted. Killing the process ends the problem. In digging through the logs I found similar entries in mailman/logs/smtp-failure:

Jul 17 23:06:57 2003 (2643) delivery to [EMAIL PROTECTED] failed with code
451: 4.0.0 cannot flock(/etc/mail/access.db, fd=7, type=1,
omode=37777777777, euid=0): No locks available

Jul 18 22:30:49 2003 (22481) delivery to [EMAIL PROTECTED] failed with code
451: 4.0.0 cannot flock(/etc/mail/access.db, fd=7, type=1,
omode=37777777777, euid=0): No locks available

      As this is the only two times I have such an entry and each proceeds
the runaway process to the minute, I assume it's related.  Google produced
nothing that enlightened me.

Mailman 2.1.2
Redhat 7.1
Python 2.2.2

TIA, Paul

<>< Paul ------------------------------------------------------
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/


This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Reply via email to