lmtpd locking continued

2001-10-01 Thread Nick Ustinov

And that's the place, where lmtpd freezes:


Oct  1 14:27:09 satan lmtpd[5687]: duplicate_check:
<[EMAIL PROTECTED]>  user.bforce  0 




Nick Ustinov
Enterprise Solutions Group Director

Vide Infra Grupa SIA
40 Brivibas St, Riga, Latvia, LV 1050
phone: +371 7812294
fax: +371 7812297
http://www.videinfra.com



Re: lmtpd locking continued

2001-10-01 Thread Amos Gouaux

> On Mon, 1 Oct 2001 13:22:27 +0200 ,
> Nick Ustinov <[EMAIL PROTECTED]> (nu) writes:

nu> And that's the place, where lmtpd freezes:
nu> Oct  1 14:27:09 satan lmtpd[5687]: duplicate_check:
nu> <[EMAIL PROTECTED]>  user.bforce  0 

You should probably indicate what version of Cyrus you're using.
At one point you mention 2.1.0pre, but don't specify when you pulled
this from CVS.

-- 
Amos




RE: lmtpd locking continued

2001-10-01 Thread Nick Ustinov

Sorry,

it's 2.1.0pre, pulled sep 26th.

concerning the problem -- i ran reconstruct on this mailbox (user.bforce)
and it went fine, however this doesn't always help (was it a coincedence?)

I enabled another sendmail.mc config with avpkeeper, which works fine now
(non-local mails delivered). However, localmails which are delivered using
cyrus mailer are still freezing after issuing DATA (messages are being
delivered to mailboxes, by the way).

This happens when it tries to connect via UNIX: /var/imap/socket/lmtp
according to sendmail's log. 

Nick

-Original Message-
From: Amos Gouaux [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 01, 2001 15:20
To: [EMAIL PROTECTED]
Subject: Re: lmtpd locking continued


>>>>> On Mon, 1 Oct 2001 13:22:27 +0200 ,
>>>>> Nick Ustinov <[EMAIL PROTECTED]> (nu) writes:

nu> And that's the place, where lmtpd freezes:
nu> Oct  1 14:27:09 satan lmtpd[5687]: duplicate_check:
nu> <[EMAIL PROTECTED]>  user.bforce  0 

You should probably indicate what version of Cyrus you're using.
At one point you mention 2.1.0pre, but don't specify when you pulled
this from CVS.

-- 
Amos



Re: lmtpd locking continued

2001-10-01 Thread Ken Murchison



Nick Ustinov wrote:
> 
> Sorry,
> 
> it's 2.1.0pre, pulled sep 26th.

Try pulling it again.  I fixed a file descriptor leak (which I created)
in lmtpd.  Your lmtpd _may_ be running up against the fd limit.  Do you
get any complaints about too many open files?

Ken
-- 
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26  Orchard Park, NY 14127
--PGP Public Key--http://www.oceana.com/~ken/ksm.pgp



RE: lmtpd locking continued

2001-10-01 Thread Nick Ustinov

Ken, just pulled latest cvs version, still the same. 

As for too many files open, I have echo 32768 >/etc/fs/file-max 

-Original Message-
From: Ken Murchison [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 01, 2001 17:59
To: Nick Ustinov
Cc: '[EMAIL PROTECTED]'
Subject: Re: lmtpd locking continued




Nick Ustinov wrote:
> 
> Sorry,
> 
> it's 2.1.0pre, pulled sep 26th.

Try pulling it again.  I fixed a file descriptor leak (which I created)
in lmtpd.  Your lmtpd _may_ be running up against the fd limit.  Do you
get any complaints about too many open files?

Ken
-- 
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26  Orchard Park, NY 14127
--PGP Public Key--http://www.oceana.com/~ken/ksm.pgp



RE: lmtpd locking continued

2001-10-01 Thread Nick Ustinov

Larry,

just did that and it sent 48 out of 721 msgs in mqueue.. And froze here:

Running /var/spool/mqueue/f91HRse04091 (sequence 49 of 721)
>>> RSET
250 2.0.0 ok
<[EMAIL PROTECTED]>... Using cached ESMTP connection to localhost
via cyrus...
>>> MAIL From:<[EMAIL PROTECTED]> SIZE=538
250 2.1.0 ok
>>> RCPT To:
250 2.1.5 ok
>>> DATA
354 go ahead
>>> .


strace shows it's read(7,

Is it somehow related to alarm(300) I see in strace output as well?



Sincererly,
Nick

PS. Pretty weird user name, however it exists, reconstructed and is
accessible via IMAP



-Original Message-
From: Lawrence Greenfield [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 01, 2001 19:46
To: '[EMAIL PROTECTED]'; Nick Ustinov
Subject: Re: lmtpd locking continued


   From: Nick Ustinov <[EMAIL PROTECTED]>
   Date: Mon, 1 Oct 2001 18:02:16 +0200 

   Ken, just pulled latest cvs version, still the same. 

   As for too many files open, I have echo 32768 >/etc/fs/file-max 

Did you nuke your existing duplicate delivery db and run ctl_cyrusdb -r?

As you noticed, the duplicate delivery code was reworked in 2.1 and
may still have some gotchas.

Larry



Re: lmtpd locking continued

2001-10-01 Thread Lawrence Greenfield

   From: Nick Ustinov <[EMAIL PROTECTED]>
   Date: Mon, 1 Oct 2001 18:02:16 +0200 

   Ken, just pulled latest cvs version, still the same. 

   As for too many files open, I have echo 32768 >/etc/fs/file-max 

Did you nuke your existing duplicate delivery db and run ctl_cyrusdb -r?

As you noticed, the duplicate delivery code was reworked in 2.1 and
may still have some gotchas.

Larry




Re: lmtpd locking continued

2001-10-01 Thread Ken Murchison



Nick Ustinov wrote:
> 
> Larry,
> 
> just did that and it sent 48 out of 721 msgs in mqueue.. And froze here:
> 
> Running /var/spool/mqueue/f91HRse04091 (sequence 49 of 721)
> >>> RSET
> 250 2.0.0 ok
> <[EMAIL PROTECTED]>... Using cached ESMTP connection to localhost
> via cyrus...
> >>> MAIL From:<[EMAIL PROTECTED]> SIZE=538
> 250 2.1.0 ok
> >>> RCPT To:
> 250 2.1.5 ok
> >>> DATA
> 354 go ahead
> >>> .

Hmm.  This *should* have given you:

554 5.6.0 Message has no header/body separator

> 
> strace shows it's read(7,

Could you please check to see which file its trying to read from?  Look
for open() = 7.  If the strace is gone, please trace a new
connection.

Ken
-- 
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26  Orchard Park, NY 14127
--PGP Public Key--http://www.oceana.com/~ken/ksm.pgp



Re: lmtpd locking continued

2001-10-01 Thread Lawrence Greenfield

   Date: Mon, 01 Oct 2001 13:47:01 -0400
   From: Ken Murchison <[EMAIL PROTECTED]>

   > >>> MAIL From:<[EMAIL PROTECTED]> SIZE=538
   > 250 2.1.0 ok
   > >>> RCPT To:
   > 250 2.1.5 ok
   > >>> DATA
   > 354 go ahead
   > >>> .

   Hmm.  This *should* have given you:

   554 5.6.0 Message has no header/body separator

No, no, Sendmail never shows the body of the message when it sends
it.  (Ok, maybe on really high debug levels, but not normally.)
It sent a message between the DATA and the .

   > 
   > strace shows it's read(7,

   Could you please check to see which file its trying to read from?  Look
   for open() = 7.  If the strace is gone, please trace a new
   connection.

I think this was an strace of Sendmail, not an strace of lmtpd.

I agree a trace of lmtpd and a gdb backtrace of where lmtpd is when
this happens would be more helpful.

Larry




RE: lmtpd locking continued

2001-10-01 Thread Nick Ustinov

Larry, Ken,

I ran strace on lmtpd and noticed that it sticks with connecting to
notify_unix socket. I recompiled it with-notify=no and it seems to work fine
now (and much faster too :)  

Ken, ignore last email with strace, it was all right (my fault)

Nick

-Original Message-
From: Lawrence Greenfield [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 01, 2001 22:37
To: Nick Ustinov; Ken Murchison
Cc: '[EMAIL PROTECTED]'
Subject: Re: lmtpd locking continued


   Date: Mon, 01 Oct 2001 13:47:01 -0400
   From: Ken Murchison <[EMAIL PROTECTED]>

   > >>> MAIL From:<[EMAIL PROTECTED]> SIZE=538
   > 250 2.1.0 ok
   > >>> RCPT To:
   > 250 2.1.5 ok
   > >>> DATA
   > 354 go ahead
   > >>> .

   Hmm.  This *should* have given you:

   554 5.6.0 Message has no header/body separator

No, no, Sendmail never shows the body of the message when it sends
it.  (Ok, maybe on really high debug levels, but not normally.)
It sent a message between the DATA and the .

   > 
   > strace shows it's read(7,

   Could you please check to see which file its trying to read from?  Look
   for open() = 7.  If the strace is gone, please trace a new
   connection.

I think this was an strace of Sendmail, not an strace of lmtpd.

I agree a trace of lmtpd and a gdb backtrace of where lmtpd is when
this happens would be more helpful.

Larry



Re: lmtpd locking continued

2001-10-01 Thread Jeremy Howard

> I ran strace on lmtpd and noticed that it sticks with connecting to
> notify_unix socket. I recompiled it with-notify=no and it seems to work
fine
> now (and much faster too :)
>
> Ken, ignore last email with strace, it was all right (my fault)
>
I thought notify_unix.c was ignoring failure to connect to the notify
socket. Obviously not! Given we've had 2 problems with this code in the last
week, it sounds like someone who knows C a lot better than me should check
it thoroughly...





RE: lmtpd locking continued

2001-10-02 Thread Nick Ustinov

Jeremy, 

I was using old notify_unix from 2.0.13 since I changed the format of the
output string a little bit; I will try to recompile with the new one and see
if it is any change. By the way, it locked on connect(.../var/notify_unix)
when the traffic was high and kept sendmail and lmtpd in memory. However, at
some point it went thru but could be hanging for 10-20 minutes


Nick

-Original Message-
From: Jeremy Howard [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 02, 2001 04:21
To: Nick Ustinov; 'Lawrence Greenfield'; Ken Murchison
Cc: [EMAIL PROTECTED]
Subject: Re: lmtpd locking continued


> I ran strace on lmtpd and noticed that it sticks with connecting to
> notify_unix socket. I recompiled it with-notify=no and it seems to work
fine
> now (and much faster too :)
>
> Ken, ignore last email with strace, it was all right (my fault)
>
I thought notify_unix.c was ignoring failure to connect to the notify
socket. Obviously not! Given we've had 2 problems with this code in the last
week, it sounds like someone who knows C a lot better than me should check
it thoroughly...