From: Gyorgy Knyihar (no email)
Date: Sun Sep 09 2007 - 07:24:25 EDT
Hello Simon,
I tried you suggestion and there are no more
"Sep 3 07:45:59 srv1 deliver[20650]:
connect(/var/lib/imap/socket/lmtp) failed: Connection refused"
messages appearing in the error log file.
Many thanks for your help.
I run postfix chrooted so a hardlink pointing to
/var/lib/imap/socket/lmtp was required in
/var/spool/postfix/var/lib/imap/socket directory. This needs to be
refreshed every time cyrus is restarted.
But my collegaues told me that this is not the only problem. Cyrus
pop3, pop3s, imap and imaps services become unavailable time to time.
And only restart helps.
Delivery from postfix to cyrus mailboxes via this new setup (direct
lmtp) is OK during the outage of pop3, pop3s, imap, imaps service. The
services don't die at the same time. Sometimes imap dies but pop3
still works. Restart helps. It is really strange. It was a stable
system before and nothing was changed. I could find only the following
errormessages in the log files:
Sep 8 01:35:00 srv1 pop3s[15591]: Fatal error: tls_start_servertls() failed
Sep 8 01:37:09 srv1 imaps[15687]: Fatal error: tls_start_servertls() failed
and
Sep 8 02:17:47 srv1 cyrus-master[20423]: pop3 has -5 workers?!?
There are many of such messages. I can access my mailbox using TLS
without any problem.
Any help would be appreciated.
Thanks, Gyorgy
Idézet (Simon Matter <simon dot matter at invoca dot ch>):
>> Hello,
>>
>> We had a properly working postfix + cyrus-imap system till 23rd of
>> July. Then messages like the below one started to appear in the log
>> file.
>>
>> Sep 3 07:45:59 srv1 deliver[20650]:
>> connect(/var/lib/imap/socket/lmtp) failed: Connection refused
>>
>> The postfix log shows:
>>
>> Sep 3 07:45:59 srv1 postfix/pipe[19972]: B88D01DC8EF8: to=<xxx@
>> srv1.xxx.xx>, orig_to=<xxx at xxx dot xx>, relay=cyrus-deliver, delay=2
>> 49424, status=deferred (temporary failure. Command output: couldn't
>> connect to l
>> mtpd: Connection refused_ 421 4.3.0 deliver: couldn't connect to lmtpd_ )
>>
>>
>> Do you have any ideas what could happen? It worked fine before.
>>
>>
>> cyrus.conf contains:
>>
>> # at least one LMTP is required for delivery
>> # lmtp cmd="lmtpd" listen="lmtp" prefork=0
>> lmtpunix cmd="lmtpd" listen="/var/lib/imap/socket/lmtp" prefork=5
>>
>>
>> postfix/master.cf contains:
>>
>> cyrus-deliver unix - n n - - pipe
>> user=cyrus argv=/usr/lib/cyrus-imapd/deliver -e -r ${sender} -m
>> ${extension} ${user}
>>
>>
>> postfix/main.cf contains:
>>
>> mailbox_transport = cyrus-deliver
>
> Hi,
>
> I don't know why things suddenly fail but you shouldn't use the cyrus
> transport anymore. You should use lmtp as a mailtransport directly. If
> your postfix setup isn't somehow exotic you should be able to simply
> switch with this config:
> mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp
>
> Maybe you could give it a try.
>
> Simon
>
>
---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
|
|
|