Prev: Compile problem Sendmail 8.13.6
Next: dsn=5.0.0, stat=Service unavailable
From: Frankie Wish on 31 Mar 2006 06:15

Please help ! I have searched everywhere but there is no similar
issue.

Two problems :
(a) Resource temporarily unavailable
(b) Broken pipe.

See below :

I am getting these type of errors after upgrading from 8.12.10 to
8.13.6 on Solaris 8 :

SYSERR(root): timeout writing message to abcd.com.: Resource
temporarily unavailable

and


[ID 801593 mail.crit] k2V0vQ4r004871: SYSERR(root): timeout writing
message to abcd.com.: Broken pipe
[ID 801593 mail.debug] k2V0vQ4r004871: 0: fl=0x0, mode=20666: CHR:
dev=0/0, ino=229642, nlink=1, u/gid=0/3, size=0
[ID 801593 mail.debug] k2V0vQ4r004871: 1: fl=0x1, mode=20666: CHR:
dev=0/0, ino=229642, nlink=1, u/gid=0/3, size=0
[ID 801593 mail.debug] k2V0vQ4r004871: 2: fl=0x1, mode=20666: CHR:
dev=0/0, ino=229642, nlink=1, u/gid=0/3, size=0
[ID 801593 mail.debug] k2V0vQ4r004871: 3: fl=0x2000, mode=150444:
dev=0/0, ino=39520, nlink=1, u/gid=0/0, size=0
[ID 801593 mail.debug] k2V0vQ4r004871: 4: fl=0x0, mode=20000: CHR:
dev=0/0, ino=1792, nlink=0, u/gid=0/0, size=0
[ID 801593 mail.debug] k2V0vQ4r004871: 5: fl=0x1, mode=20666: CHR:
dev=0/0, ino=229638, nlink=1, u/gid=0/3, size=0
[ID 801593 mail.debug] k2V0vQ4r004871: 6: fl=0x2, mode=100600:
dev=0/5, ino=18293, nlink=1, u/gid=110/6, size=1003
[ID 801593 mail.debug] k2V0vQ4r004871: 7: fl=0x2000, mode=100600:
dev=0/0, ino=229608, nlink=1, u/gid=110/6, size=2048
[ID 801593 mail.debug] k2V0vQ4r004871: 8: fl=0x2000, mode=100600:
dev=0/0, ino=229607, nlink=1, u/gid=110/6, size=4096
[ID 801593 mail.debug] k2V0vQ4r004871: 9: fl=0x0, mode=100600:
dev=0/5, ino=18226, nlink=1, u/gid=110/6, size=5562143
[ID 801593 mail.debug] k2V0vQ4r004871: 10: fl=0x82, mode=140666: SOCK
[IPv6:::]/0->(Transport endpoint is not connected)
[ID 801593 mail.debug] k2V0vQ4r004871: 11: fl=0x82, mode=140666: SOCK
[IPv6:::]/0->(Transport endpoint is not connected)
[ID 801593 mail.debug] k2V0vQ4r004871: MCI(a)0x0: NULL
[ID 801593 mail.debug] k2V0vQ4r004871: MCI(a)0x119ad4:
flags=4004c<CACHED,ESMTP,8BITMIME,PIPELINED>, errno=32, herrno=1,
exitstat=75, state=8, pid=0, maxsize=0, phase=client DATA 354,
mailer=esmtp, status=4.4.2, rstatus=(null), host=abcd.com., lastuse=Fri
Mar 31 09:00:40 2006


Thanks.

/Frankie

From: hans m43 on 2 Apr 2006 13:23

hi Frankie



In article <1143803754.785523.52390(a)g10g2000cwb.googlegroups.com>,
Frankie Wish <Wisheey(a)gmail.com> wrote:
>
>Please help ! I have searched everywhere but there is no similar
>issue.
>
>Two problems :
>(a) Resource temporarily unavailable
>(b) Broken pipe.
>
>See below :
>
>I am getting these type of errors after upgrading from 8.12.10 to
>8.13.6 on Solaris 8 :
>
>SYSERR(root): timeout writing message to abcd.com.: Resource
>temporarily unavailable
>

are some of the files on a nfs-share ?


--
best regards from vienna
hans


From: Frankie Wish on 4 Apr 2006 23:59
I now know the reason behind the error. I'm using mailertable to send
outbound mails to ISP ,

/etc/mail/mailertable
===============
.. esmtp:[cluster5.isp.com]

and all queued mail will retry every 1 hour. Due to huge numbers of
mail in the queues and on top of that, most of them with big
attachments,
each time the queue is processed, it takes a long time to transmit each
mail to the ISP server. Sometimes, the each queue can be as big as 700
messages.
Most of the time, the ISP server will close the connection during the
queue processing (example 120 of 700) and the remaining messages in
the queue will not
be transmitted to ISP (example 121 to 700). Reason behind this is
because Sendmail uses the cached SMTP session to send the mails for
each queue.
And if the cached SMTP session is abruptly terminated by the ISP, the
remaining mails in the queue will get error "timeout writing message to
cluser5.isp.com".
Therefore, it takes a long time to clear the queues.

What I am doing now is to distribute the load to more queues by
creating more subdirectories in the /var/spool/mqueue/q*.

Question : Is there a way to configure Sendmail not to use the active
cached SMTP connection ? Can Sendmail establish new SMTP session for
each mail that is processed in the queue ?

I believe the same scenario will happen to SMARTHOST settings as well
(i.e. using the cached SMTP connection).

Any ideas ?

thanks,
Frankie

 | 
Pages: 1
Prev: Compile problem Sendmail 8.13.6
Next: dsn=5.0.0, stat=Service unavailable