Dbmail + IMAP = Unstable

Hi All,

I've noticed some similar elements from a post before
(http:// 
www.mail-archive.com/dbmaildbmail.org/msg13421.html),
but I can't  
reply to that post, because I've just joined the list.

I've setup an Dbmail (2.2.6-2 debian) instance with
postgresql where  
people directly connect to POP3 and also use Squirrelmail
with  
imapproxy for webmail. (Some people directory connect with
imapd, but  
that is really less)

When dbmail is running for a period ( can be half hour, can
be 1  
hour, can be more) errors start to occur :

# /var/log/dbmail/dbmail.err
Sep 21 16:54:31 pretpark dbmail-imapd[32136]:
Error:[imapsession]  
dbmail-imapsession.c,dbmail_imap_session_printf(+1515):
write to  
client socket failed
Sep 21 16:54:31 pretpark dbmail-imapd[30991]:
Error:[imapsession]  
dbmail-imapsession.c,dbmail_imap_session_printf(+1515):
write to  
client socket failed
Sep 21 16:55:18 pretpark dbmail-imapd[31109]: Error:[imap] 

imap4.c,IMAPClientHandler(+139): [Illegal seek] on
read-stream
Sep 21 16:55:31 pretpark dbmail-imapd[31563]:
Error:[imapsession]  
dbmail-imapsession.c,dbmail_imap_session_printf(+1515):
write to  
client socket failed
Sep 21 16:56:35 pretpark dbmail-imapd[30868]: Error:[imap] 

imap4.c,IMAPClientHandler(+139): [Illegal seek] on
read-stream
Sep 21 16:56:41 pretpark dbmail-imapd[30991]: Error:[imap] 

imap4.c,IMAPClientHandler(+139): [Illegal seek] on
read-stream
Sep 21 16:56:41 pretpark dbmail-imapd[1820]: Error:[imap]  
imap4.c,IMAPClientHandler(+139): [Illegal seek] on
read-stream
Sep 21 16:57:31 pretpark dbmail-imapd[32261]:
Error:[imapsession]  
dbmail-imapsession.c,dbmail_imap_session_printf(+1515):
write to  
client socket failed
Sep 21 16:57:41 pretpark dbmail-imapd[30991]:
Error:[imapsession]  
dbmail-imapsession.c,dbmail_imap_session_readln(+1585):
timeout  
occurred in dbmail_imap_session_readln
Sep 21 16:57:45 pretpark dbmail-imapd[30837]: Error:[imap] 

imap4.c,IMAPClientHandler(+139): [Illegal seek] on
read-stream
Sep 21 16:57:45 pretpark dbmail-imapd[30817]: Error:[imap] 

imap4.c,IMAPClientHandler(+139): [Illegal seek] on
read-stream
Sep 21 16:57:45 pretpark dbmail-imapd[31109]: Error:[imap] 

imap4.c,IMAPClientHandler(+139): [Illegal seek] on
read-stream
Sep 21 16:57:45 pretpark dbmail-imapd[30811]: Error:[imap] 

imap4.c,IMAPClientHandler(+139): [Illegal seek] on
read-stream
Sep 21 16:57:51 pretpark dbmail-imapd[30841]: Error:[imap] 

imap4.c,IMAPClientHandler(+139): [Illegal seek] on
read-stream
Sep 21 16:57:53 pretpark dbmail-imapd[30966]: Error:[imap] 

imap4.c,IMAPClientHandler(+139): [Illegal seek] on
read-stream

What often happens here is that dmail-imapd doesn't respond
anymore.  
Telnetting to port 143 doesn't give me any answer.

Squirrelmail, Thunderbird and others just give a imap
timeout

At this point POP3 is still working like a charm (about 20
users  
logging in at the same time), the system doesn't have much
load, and  
the database still has enough resources.

I have to restart dbmail to get dbmail-imapd working again.

Does this help in analyzing the problem? Do you need more
info? Do  
you have an idea what's going on?

Sincerely,

Frodo Larik

186,282 miles per second:

It isn't just a good idea, it's the law!


_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

Frodo Larik wrote:
> Hi All,
> 
> I've noticed some similar elements from a post before
> (http://www.mail-ar
chive.com/dbmaildbmail.org/msg13421.html), but I
> can't reply to that post, because I've just joined the
list.
> 
> I've setup an Dbmail (2.2.6-2 debian) instance with
postgresql where
> people directly connect to POP3 and also use
Squirrelmail with imapproxy
> for webmail. (Some people directory connect with imapd,
but that is
> really less)
> 
> When dbmail is running for a period ( can be half hour,
can be 1 hour,
> can be more) errors start to occur :
> 
> # /var/log/dbmail/dbmail.err
> Sep 21 16:54:31 pretpark dbmail-imapd[32136]:
Error:[imapsession]
> dbmail-imapsession.c,dbmail_imap_session_printf(+1515):
write to client
> socket failed
> Sep 21 16:54:31 pretpark dbmail-imapd[30991]:
Error:[imapsession]
> dbmail-imapsession.c,dbmail_imap_session_printf(+1515):
write to client
> socket failed
> Sep 21 16:55:18 pretpark dbmail-imapd[31109]:
Error:[imap]
> imap4.c,IMAPClientHandler(+139): [Illegal seek] on
read-stream
> Sep 21 16:55:31 pretpark dbmail-imapd[31563]:
Error:[imapsession]
> dbmail-imapsession.c,dbmail_imap_session_printf(+1515):
write to client
> socket failed
> Sep 21 16:56:35 pretpark dbmail-imapd[30868]:
Error:[imap]
> imap4.c,IMAPClientHandler(+139): [Illegal seek] on
read-stream
> Sep 21 16:56:41 pretpark dbmail-imapd[30991]:
Error:[imap]
> imap4.c,IMAPClientHandler(+139): [Illegal seek] on
read-stream
> Sep 21 16:56:41 pretpark dbmail-imapd[1820]:
Error:[imap]
> imap4.c,IMAPClientHandler(+139): [Illegal seek] on
read-stream
> Sep 21 16:57:31 pretpark dbmail-imapd[32261]:
Error:[imapsession]
> dbmail-imapsession.c,dbmail_imap_session_printf(+1515):
write to client
> socket failed
> Sep 21 16:57:41 pretpark dbmail-imapd[30991]:
Error:[imapsession]
> dbmail-imapsession.c,dbmail_imap_session_readln(+1585):
timeout occurred
> in dbmail_imap_session_readln
> Sep 21 16:57:45 pretpark dbmail-imapd[30837]:
Error:[imap]
> imap4.c,IMAPClientHandler(+139): [Illegal seek] on
read-stream
> Sep 21 16:57:45 pretpark dbmail-imapd[30817]:
Error:[imap]
> imap4.c,IMAPClientHandler(+139): [Illegal seek] on
read-stream
> Sep 21 16:57:45 pretpark dbmail-imapd[31109]:
Error:[imap]
> imap4.c,IMAPClientHandler(+139): [Illegal seek] on
read-stream
> Sep 21 16:57:45 pretpark dbmail-imapd[30811]:
Error:[imap]
> imap4.c,IMAPClientHandler(+139): [Illegal seek] on
read-stream
> Sep 21 16:57:51 pretpark dbmail-imapd[30841]:
Error:[imap]
> imap4.c,IMAPClientHandler(+139): [Illegal seek] on
read-stream
> Sep 21 16:57:53 pretpark dbmail-imapd[30966]:
Error:[imap]
> imap4.c,IMAPClientHandler(+139): [Illegal seek] on
read-stream
> 
> What often happens here is that dmail-imapd doesn't
respond anymore.
> Telnetting to port 143 doesn't give me any answer.

interesting 

> Squirrelmail, Thunderbird and others just give a imap
timeout

not good.

> At this point POP3 is still working like a charm (about
20 users logging
> in at the same time), the system doesn't have much
load, and the
> database still has enough resources.
> 
> I have to restart dbmail to get dbmail-imapd working
again.
> 
> Does this help in analyzing the problem? Do you need
more info? Do you
> have an idea what's going on?


I actually need to know the imap command that precedes the
error
messages. That said, I suspect it's IDLE.

If it *is* idle, you can disable that command by editing the
dbmail.conf
and setting:

[imap]
capability            = IMAP4 IMAP4rev1 AUTH=LOGIN ACL
NAMESPACE 
  CHILDREN SORT QUOTA THREAD=ORDEREDSUBJECT UNSELECT

Btw, you can always work-around problems in the daemon code
by running
in inetd mode, or by overriding maxconnects in dbmail.conf:

[imap]
maxconnects = 1

P.S. You can produce command sequences by setting the
trace_syslog=4


-- 
 
____________________________________________________________
____
  Paul Stevens                                      paul at
nfg.nl
  NET FACILITIES GROUP                     GPG/PGP:
1024D/11F8CD31
  The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

On Sep 21, 2007, at 9:58 PM, Paul J Stevens wrote:

> I actually need to know the imap command that precedes
the error
> messages. That said, I suspect it's IDLE.

I've set

TRACE_SYSLOG = 4

> If it *is* idle, you can disable that command by
editing the  
> dbmail.conf
> and setting:
>
> [imap]
> capability            = IMAP4 IMAP4rev1 AUTH=LOGIN ACL
NAMESPACE 
>   CHILDREN SORT QUOTA THREAD=ORDEREDSUBJECT UNSELECT

we just have to wait until the problem arises again,
probably will be  
after the weekend.



> [imap]
> maxconnects = 1

I've set this too, the global setting for this is:

MAXCONNECTS = 10000

Hope that is not a problem?

I keep you posted.

Sincerely,

Frodo Larik

_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

On Sep 22, 2007, at 1:41 PM, Frodo Larik wrote:

>> If it *is* idle, you can disable that command by
editing the  
>> dbmail.conf
>> and setting:
>>
>> [imap]
>> capability            = IMAP4 IMAP4rev1 AUTH=LOGIN
ACL NAMESPACE 
>>   CHILDREN SORT QUOTA THREAD=ORDEREDSUBJECT
UNSELECT


It looks like it is the IDLE command:

/var/log/syslog:
Sep 22 13:49:16 pretpark dbmail/imap4d[20039]: Info:[imap] 

imap4.c,IMAPClientHandler(+187): COMMAND: [70 IDLE]
Sep 22 13:49:16 pretpark dbmail/imap4d[20039]: Info:[imap] 

imap4.c,IMAPClientHandler(+298): Executing command idle...

/var/log/dbmail/dbmail.err
Sep 22 13:49:16 pretpark dbmail-imapd[20039]: Error:[imap] 

imap4.c,IMAPClientHandler(+139): [Illegal seek] on
read-stream

I disabled it.


>> [imap]
>> maxconnects = 1

I now get stuff like this as an error (is it really an error
or just  
a NOTICE?):

/var/log/dbmail/dbmail.err
Sep 22 13:54:35 pretpark dbmail-imapd[21239]:
Error:[serverchild]  
serverchild.c, PerformChildTask(+385): maximum number of
connections  
reached, stopping now

Sincerely,

Frodo Larik

_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

On Sat, 2007-09-22 at 13:57 +0200, Frodo Larik wrote:

> >> [imap]
> >> maxconnects = 1
> 
> I now get stuff like this as an error (is it really an
error or just  
> a NOTICE?):
> 
> /var/log/dbmail/dbmail.err
> Sep 22 13:54:35 pretpark dbmail-imapd[21239]:
Error:[serverchild]  
> serverchild.c, PerformChildTask(+385): maximum number
of connections  
> reached, stopping now

I'd like to see that as MESSAGE (level 3) or INFO (4). Any
objections?

Aaron

_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail