Re: Repeating imap processes crashes with signal 11 after imapc-client timeout leak
> On 01/06/2023 17:25 EEST Nikolaos Pyrgiotis wrote: > > > Hello, > We run a 5 instances dovecot cluster ondebian 11 virtual machines, a dovecot > proxy,2directors and2dovecot backends. > All dovecot instances run version2.3.20. We use a glusterfs mounted volume on > the backends forthe mail storage. Our users all use thunderbird mail client > and they do not report any issue with the imap service. > Since we have configured the dovecot cluster we see multiple random imap > crashes with signal 11 and timeout leaks in the logs on both the backends for > multiple users. > > Is this is a configuration problem or a bug with imapc or imap; I would > appreciate if you could assist us to debug this further. > A coredump is attached if it helps. > Thank you for reporting this, we'll take a look Aki ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: Timeout Leak
On Thu, 16 Mar 2017 13:48:27 +0200 Aki Tuomi wrote: > These are always worth looking into. Please do post, also any auth debug > logs are welcome. Ok. Theese the logfile lines: Mar 14 18:06:12 master: Warning: Killed with signal 15 (by pid=7390 uid=0 code=kill) Mar 14 18:06:20 auth: Error: net_connect_unix(auth-worker) failed: Connection refused Mar 14 18:06:42 auth: Warning: Timeout leak: 0x805e480 (auth-request-handler.c:550) Mar 14 18:06:42 auth: Warning: Timeout leak: 0x805e480 (auth-request-handler.c:550) Mar 14 18:06:42 auth: Warning: Timeout leak: 0x805e480 (auth-request-handler.c:550) Here is the logfile.info of the relevant minute (a bit longish, passwors censored :)... Mar 14 18:06:01 pop3(l.radice_dls): Info: Disconnected: Logged out top=0/0, retr=0/0, del=0/7415, size=950442332 Mar 14 18:06:01 auth: Debug: auth client connected (pid=7375) Mar 14 18:06:01 auth: Debug: client in: AUTH3 LOGIN service=smtp nologin lip=212.45.144.70 rip=89.248.171.132 Mar 14 18:06:01 auth: Debug: client passdb out: CONT3 VXNlcm5hbWU6 Mar 14 18:06:01 auth: Debug: client in: CONT3 (previous base64 data may contain sensitive data) Mar 14 18:06:01 auth: Debug: client passdb out: CONT3 UGFzc3dvcmQ6 Mar 14 18:06:01 auth: Debug: client in: CONT3 (previous base64 data may contain sensitive data) Mar 14 18:06:01 auth-worker(6538): Debug: pam(ad...@bilink.net,89.248.171.132): lookup service=dovecot Mar 14 18:06:01 auth-worker(6538): Debug: pam(ad...@bilink.net,89.248.171.132): #1/1 style=1 msg=Password: Mar 14 18:06:02 auth: Debug: auth client connected (pid=7377) Mar 14 18:06:02 auth: Debug: client in: AUTH1 PLAIN service=pop3 session=zgbC17NKLOvAqAvRlip=192.168.134.44 rip=192.168.11.209lport=110 rport=60204 Mar 14 18:06:02 auth: Debug: client passdb out: CONT1 Mar 14 18:06:02 auth: Debug: client in: CONT1 (previous base64 data may contain sensitive data) Mar 14 18:06:02 auth-worker(7121): Debug: pam(m.castrechini_mms,192.168.11.209,): lookup service=dovecot Mar 14 18:06:02 auth-worker(7121): Debug: pam(m.castrechini_mms,192.168.11.209,): #1/1 style=1 msg=Password: Mar 14 18:06:02 auth: Debug: client passdb out: OK 1 user=m.castrechini_mms Mar 14 18:06:03 auth: Debug: master in: REQUEST 2912419841 73771 e4d4a4c42ae38c0214a0def0bb0f0915session_pid=7378 Mar 14 18:06:03 auth: Debug: passwd(m.castrechini_mms,192.168.11.209,): userdb cache hit: system_groups_user=m.castrechini_mmsuid=3002gid=111 home=/home/m.castrechini_mms Mar 14 18:06:03 auth: Debug: master userdb out: USER2912419841 m.castrechini_mms system_groups_user=m.castrechini_mmsuid=3002 gid=111 home=/home/m.castrechini_mms Mar 14 18:06:03 pop3-login: Info: Login: user=, method=PLAIN, rip=192.168.11.209, lip=192.168.134.44, mpid=7378, session= Mar 14 18:06:03 pop3(m.castrechini_mms): Info: Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Mar 14 18:06:03 auth-worker(6538): Info: pam(ad...@bilink.net,89.248.171.132): unknown user Mar 14 18:06:05 auth: Debug: client passdb out: FAIL3 user=ad...@bilink.net Mar 14 18:06:06 auth: Debug: auth client connected (pid=7380) Mar 14 18:06:06 auth: Debug: client in: AUTH1 PLAIN service=pop3 session=khD317NKD+PAqAtYlip=192.168.134.44 rip=192.168.11.88 lport=110 rport=58127 resp= (previous base64 data may contain sensitive data) Mar 14 18:06:06 auth-worker(6538): Debug: pam(a.zurlo_mms,192.168.11.88,): lookup service=dovecot Mar 14 18:06:06 auth-worker(6538): Debug: pam(a.zurlo_mms,192.168.11.88,): #1/1 style=1 msg=Password: Mar 14 18:06:06 auth: Debug: client passdb out: OK 1 user=a.zurlo_mms Mar 14 18:06:06 auth: Debug: master in: REQUEST 3493330945 73801 e4c2a1b6ab1b7ede85f4fd8611a960c8session_pid=7382 Mar 14 18:06:06 auth: Debug: passwd(a.zurlo_mms,192.168.11.88,): userdb cache hit: system_groups_user=a.zurlo_mms uid=3005gid=111 home=/home/a.zurlo_mms Mar 14 18:06:06 auth: Debug: master userdb out: USER3493330945 a.zurlo_mms system_groups_user=a.zurlo_mms uid=3005gid=111 home=/home/a.zurlo_mms Mar 14 18:06:06 pop3-login: Info: Login: user=, method=PLAIN, rip=192.168.11.88, lip=192.168.134.44, mpid=7382, session= Mar 14 18:06:06 pop3(a.zurlo_mms): Info: Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Mar 14 18:06:06 auth: Debug: auth client connected (pid=7383) Mar 14 18:06:06 auth: Debug: client in: AUTH1 PLAIN service=pop3 session=KP/817NKEuPAqAtYlip=192.168.134.44 rip=192.168.11.88 lport=110 rport=58130 resp= (previous base64 data may c
Re: Timeout Leak
On 16.03.2017 12:32, Luciano Mannucci wrote: > Hello all, > > I've got 3 occurences of this message in my log file: > > auth: Warning: Timeout leak: 0x805e480 (auth-request-handler.c:550) > > Can I ignore it, or is it a syhmptom of something wrong? > > I'm running dovecot 2.2.28 (bed8434). I'll post my doveconf -n if it > is worth investigating further... > > Cheers, > > Luciano. These are always worth looking into. Please do post, also any auth debug logs are welcome. Aki
Timeout Leak
Hello all, I've got 3 occurences of this message in my log file: auth: Warning: Timeout leak: 0x805e480 (auth-request-handler.c:550) Can I ignore it, or is it a syhmptom of something wrong? I'm running dovecot 2.2.28 (bed8434). I'll post my doveconf -n if it is worth investigating further... Cheers, Luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL/ E-MAIL: posthams...@sublink.sublink.org / \ AND POSTINGS/ WWW: http://www.lesassaie.IT/
segfault in imap "Warning: Timeout leak: 0x7fd584e8e050 (line 399)"
Corresponding log entry:
Apr 29 17:14:07 mproxy dovecot: imap(v**d): copy from INBOX: box=Trash,
uid=512, msgid=, size=error
Apr 29 17:14:07 mproxy dovecot: imap(v**d): expunge: box=INBOX, uid=3322,
msgid=, size=22485
Apr 29 17:14:19 mproxy dovecot: imap(v**d): copy from INBOX: box=Trash,
uid=513, msgid=, size=error
Apr 29 17:14:19 mproxy dovecot: imap(v**d): expunge: box=INBOX, uid=3288,
msgid=, size=60236
Apr 29 17:14:19 mproxy dovecot: imap(v**d): Warning: Timeout leak:
0x7fd584e8e050 (line 399)
Apr 29 17:14:19 mproxy dovecot: imap(v**d): Connection closed (IDLE running
for 0.043 + waiting input for 6654.979 secs, 2 B in + 10+10 B out,
state=wait-input) in=7582 out=5928297
Apr 29 17:14:19 mproxy dovecot: imap(v**d): Fatal: master: service(imap):
child 30554 killed with signal 11 (core dumped)
Backtrace:
Reading symbols from /usr/lib/dovecot/imap...Reading symbols from
/usr/lib/debug/.build-id/5a/15dc6951744d026af424747e7b72a4fb550c6b.debug...done.
done.
[New LWP 30554]
Core was generated by `dovecot/imap'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7fd584b8daa7 in timeout_remove (_timeout=0x7fd5875b5048)
at ioloop.c:307
#0 0x7fd584b8daa7 in timeout_remove (_timeout=0x7fd5875b5048)
at ioloop.c:307
timeout = 0x7fd5875b8720
ioloop = 0x0
#1 0x7fd584e8df0b in imapc_client_mailbox_close (
_box=_box@entry=0x7fd5875b3b38) at imapc-client.c:362
box = 0x7fd5875b5030
connp =
#2 0x7fd584e8c3af in imapc_mailbox_close (box=0x7fd5875b3850)
at imapc-storage.c:651
mbox = 0x7fd5875b3850
#3 0x7fd584e411aa in mailbox_close (box=0x7fd5875b5048)
at mail-storage.c:1242
No locals.
#4 0x7fd584e41233 in mailbox_free (_box=_box@entry=0x7fd5875a3f00)
at mail-storage.c:1262
box = 0x7fd5875b3850
#5 0x7fd585584f74 in client_default_destroy (client=0x7fd5875a3e60,
reason=) at imap-client.c:367
cmd = 0x0
#6 0x7fd584b8e06c in io_loop_call_io (io=0x7fd5875a18d0) at ioloop.c:564
ioloop = 0x7fd587563740
t_id = 2
__FUNCTION__ = "io_loop_call_io"
#7 0x7fd584b8f4d1 in io_loop_handler_run_internal (
ioloop=ioloop@entry=0x7fd587563740) at ioloop-epoll.c:220
ctx = 0x7fd587565250
io =
tv = {tv_sec = 4, tv_usec = 738842}
events_count =
msecs =
ret = 1
i = 0
j =
call =
__FUNCTION__ = "io_loop_handler_run_internal"
#8 0x7fd584b8e0f5 in io_loop_handler_run (
ioloop=ioloop@entry=0x7fd587563740) at ioloop.c:612
No locals.
#9 0x7fd584b8e298 in io_loop_run (ioloop=0x7fd587563740) at ioloop.c:588
__FUNCTION__ = "io_loop_run"
#10 0x7fd584b23e63 in master_service_run (service=0x7fd5875635e0,
callback=) at master-service.c:640
No locals.
#11 0x7fd585577b32 in main (argc=1, argv=0x7fd587563390) at main.c:460
set_roots = {0x7fd5857a1700 ,
0x7fd585340400 , 0x0}
login_set = {auth_socket_path = 0x7fd58755b048 "\001",
postlogin_socket_path = 0x0, postlogin_timeout_secs = 60,
callback = 0x7fd5855919d0 ,
failure_callback = 0x7fd5855912e0 ,
request_auth_token = 1}
service_flags =
storage_service_flags =
username = 0x0
auth_socket_path = 0x7fd58559a34e "auth-master"
c =
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin Franklin
Hindenburgdamm 30 | D-12203 Berlin
Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
ralf.hildebra...@charite.de | http://www.charite.de
Re: [Dovecot] Timeout leak in get quota
On 08/10/2011 15:09, Nikita Koshikov wrote:
> On Thu, 29 Sep 2011 15:05:53 +0200
> Danilo wrote:
>
>> Hello!
>> I wrote perl script for read current quota usage, it works but when I run the
>> program I receive a warning in Dovecot log:
>>
>> 2011-09-29 14:45:30 doveadm(gu...@testmail.com): Warning: Timeout leak:
>> 0x7f14800ad970
>>
>> This is the script:
>> ===
>> #!/usr/bin/perl
>>
>> use strict;
>> use Socket;
>> use IO::Handle;
>>
>> socket(TSOCK, PF_UNIX, SOCK_STREAM,0);
>> connect(TSOCK, sockaddr_un("/var/run/dovecot/doveadm-server")) or
>> print("ERROR!");
>>
>> print "VERSION\tdoveadm-server\t1\t0\n";
>> print "\tguest\@testmail.com\tquota get\n";
>> print "=" x 20 . "\n";
>>
>> if (defined(my $messg = )) {
>>
>> print $messg;
>>
>> print TSOCK "VERSION\tdoveadm-server\t1\t0\n";
>> TSOCK->flush;
>>
>> print TSOCK "\tguest\@testmail.com\tquota get\n";
>> TSOCK->flush;
>>
>> $messg = ;
>> print $messg;
>>
>> $messg = ;
>> print $messg;
>>
>> close TSOCK;
>> }
>> =
>> I hope someone could help me to fix the warning.
>> Thanks in advance,
>>Dany
>
> I'm using doveadm socket too for getting quota values. No warning. The main
> difference from yours script that I'm also using auth:
>
> print TSOCK "VERSION\tdoveadm-server\t1\t0\n";
> print TSOCK "PLAIN\tbase64_encoded_pass_here\n";
> print TSOCK "\t$local_part\@$domain\tquota get\n";
> TSOCK->flush;
>
> Dovecot version 2.0.15
Thanks,
I had update dovecot to 2.0.15 version, now works without warning.
Dany
Re: [Dovecot] Timeout leak in get quota
On Thu, 29 Sep 2011 15:05:53 +0200
Danilo wrote:
> Hello!
> I wrote perl script for read current quota usage, it works but when I run the
> program I receive a warning in Dovecot log:
>
> 2011-09-29 14:45:30 doveadm(gu...@testmail.com): Warning: Timeout leak:
> 0x7f14800ad970
>
> This is the script:
> ===
> #!/usr/bin/perl
>
> use strict;
> use Socket;
> use IO::Handle;
>
> socket(TSOCK, PF_UNIX, SOCK_STREAM,0);
> connect(TSOCK, sockaddr_un("/var/run/dovecot/doveadm-server")) or
> print("ERROR!");
>
> print "VERSION\tdoveadm-server\t1\t0\n";
> print "\tguest\@testmail.com\tquota get\n";
> print "=" x 20 . "\n";
>
> if (defined(my $messg = )) {
>
> print $messg;
>
> print TSOCK "VERSION\tdoveadm-server\t1\t0\n";
> TSOCK->flush;
>
> print TSOCK "\tguest\@testmail.com\tquota get\n";
> TSOCK->flush;
>
> $messg = ;
> print $messg;
>
> $messg = ;
> print $messg;
>
> close TSOCK;
> }
> =
> I hope someone could help me to fix the warning.
> Thanks in advance,
>Dany
I'm using doveadm socket too for getting quota values. No warning. The main
difference from yours script that I'm also using auth:
print TSOCK "VERSION\tdoveadm-server\t1\t0\n";
print TSOCK "PLAIN\tbase64_encoded_pass_here\n";
print TSOCK "\t$local_part\@$domain\tquota get\n";
TSOCK->flush;
Dovecot version 2.0.15
Re: [Dovecot] Timeout leak in get quota
Hi!
I've the same problem.
I use the same input string inside a Java standalone application.
The request would appear correct and I receive always a correct response
but Dovecot print the same warning into the log...
My Dovecot version is 2.0.13.
Thanks in advance for any help!
Francesco
On 29/09/11 15:05, Danilo wrote:
> Hello!
> I wrote perl script for read current quota usage, it works but when I run the
> program I receive a warning in Dovecot log:
>
> 2011-09-29 14:45:30 doveadm(gu...@testmail.com): Warning: Timeout leak:
> 0x7f14800ad970
>
> This is the script:
> ===
> #!/usr/bin/perl
>
> use strict;
> use Socket;
> use IO::Handle;
>
> socket(TSOCK, PF_UNIX, SOCK_STREAM,0);
> connect(TSOCK, sockaddr_un("/var/run/dovecot/doveadm-server")) or
> print("ERROR!");
>
> print "VERSION\tdoveadm-server\t1\t0\n";
> print "\tguest\@testmail.com\tquota get\n";
> print "=" x 20 . "\n";
>
> if (defined(my $messg = )) {
>
> print $messg;
>
> print TSOCK "VERSION\tdoveadm-server\t1\t0\n";
> TSOCK->flush;
>
> print TSOCK "\tguest\@testmail.com\tquota get\n";
> TSOCK->flush;
>
> $messg = ;
> print $messg;
>
> $messg = ;
> print $messg;
>
> close TSOCK;
> }
> =
> I hope someone could help me to fix the warning.
> Thanks in advance,
>Dany
signature.asc
Description: OpenPGP digital signature
[Dovecot] Timeout leak in get quota
Hello!
I wrote perl script for read current quota usage, it works but when I run the
program I receive a warning in Dovecot log:
2011-09-29 14:45:30 doveadm(gu...@testmail.com): Warning: Timeout leak:
0x7f14800ad970
This is the script:
===
#!/usr/bin/perl
use strict;
use Socket;
use IO::Handle;
socket(TSOCK, PF_UNIX, SOCK_STREAM,0);
connect(TSOCK, sockaddr_un("/var/run/dovecot/doveadm-server")) or
print("ERROR!");
print "VERSION\tdoveadm-server\t1\t0\n";
print "\tguest\@testmail.com\tquota get\n";
print "=" x 20 . "\n";
if (defined(my $messg = )) {
print $messg;
print TSOCK "VERSION\tdoveadm-server\t1\t0\n";
TSOCK->flush;
print TSOCK "\tguest\@testmail.com\tquota get\n";
TSOCK->flush;
$messg = ;
print $messg;
$messg = ;
print $messg;
close TSOCK;
}
=
I hope someone could help me to fix the warning.
Thanks in advance,
Dany
Re: [Dovecot] IMAP Timeout Leak
On Tue, 2010-12-07 at 11:00 -0500, qm...@top-consulting.net wrote: > (gdb) x 0x80ff950 > 0x80ff950 :0x53e58955 > > Is it a problem with the ACL plugin ? Can you reproduce it? It's not dangerous, but it looks like some deinit function isn't being called. I looked at the code, but couldn't find any reason why that would happen.
[Dovecot] IMAP Timeout Leak
My Dovecot config is as follows: # 1.2.14: /usr/local/etc/dovecot.conf # OS: FreeBSD 6.3-RELEASE i386 protocols: imap pop3 imaps pop3s listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995 ssl_ca_file: /usr/local/certs/gd_bundle.crt ssl_cert_file: /usr/local/certs/imap.crt ssl_key_file: /usr/local/certs/rsa.imap.key disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_greeting: MAIL ready. login_processes_count: 50 login_max_processes_count: 500 max_mail_processes: 798 mail_max_userip_connections(default): 100 mail_max_userip_connections(imap): 100 mail_max_userip_connections(pop3): 10 verbose_proctitle: yes first_valid_uid: 89 first_valid_gid: 89 mail_privileged_group: mail mail_uid: 89 mail_gid: 89 mail_location: maildir:~/Maildir mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes lock_method: dotlock mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota fts fts_solr antispam virtual acl imap_acl mail_plugins(imap): quota imap_quota fts fts_solr antispam virtual acl imap_acl mail_plugins(pop3): virtual mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh namespace: type: private separator: . inbox: yes list: yes subscriptions: yes namespace: type: private separator: . prefix: INBOX. hidden: yes list: no subscriptions: yes namespace: type: private separator: . prefix: Labels. location: virtual:~/Maildir/Labels:INDEX=MEMORY list: yes subscriptions: yes namespace: type: shared separator: . prefix: shared.%%n. location: maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u list: children lda: sendmail_path: /usr/sbin/sendmail auth default: mechanisms: plain login digest-md5 cram-md5 username_format: %Lu verbose: yes passdb: driver: vpopmail args: webmail=192.168.1.4 userdb: driver: vpopmail args: quota_template=quota_rule=*:backend=%q socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: vpopmail plugin: fts: solr fts_solr: break-imap-search url=http://192.168.1.4:8983/solr/ quota: maildir quota_rule: ?:storage=0 antispam_signature: X-DSPAM-Signature antispam_trash: trash;Trash;Deleted Items antispam_spam: Spam antispam_dspam_binary: /usr/local/bin/dspam antispam_dspam_args: --client;--user;vpopmail acl: vfile acl_shared_dict: proxy::acl dict: acl: mysql:/usr/local/etc/dovecot-dict-sql.conf and I see the following error in the logs: Timeout leak: 0x80ff950 Running it through gdb, I get this: (gdb) x 0x80ff950 0x80ff950 :0x53e58955 Is it a problem with the ACL plugin ?
Re: [Dovecot] What is that error all about: "Timeout leak: 0x4bd230"
On Mon, 2010-11-22 at 13:45 +0100, Christian Rohmann wrote: > we are running dovecot 1.2.15 and are seeing some odd errors in our > logfiles: > > --- dovecot.log --- > 2010-11-22 12:34:56 imapserver local2.warning dovecot dovecot: > IMAP(usern...@domain.tld): Timeout leak: 0x4bd230 It's not really anything to worry about. Dovecot just notices at exit that the code didn't remove one timeout handler. It would be good to fix it though. You could see what function that address points to with gdb: gdb /usr/local/libexec/dovecot/imap x 0x4bd230
[Dovecot] What is that error all about: "Timeout leak: 0x4bd230"
Hey dovecot-users, we are running dovecot 1.2.15 and are seeing some odd errors in our logfiles: --- dovecot.log --- 2010-11-22 12:34:56 imapserver local2.warning dovecot dovecot: IMAP(usern...@domain.tld): Timeout leak: 0x4bd230 --- /dovecot.log --- Those errors only appear if connections are done using IMAP (via Horde's IMP Webmail). With POP3 we don't see any of those errors. We actually don't see anything in general being broken or wrong (no errors on the webmail machines, no user complaints), but these errors are constantly being logged. Where would one start to look for the cause? Thanks for your help, Regards Christian
Re: [Dovecot] Timeout leak with dovecot version dovecot1.2(8985:f43bebab3dac)
On Wed, 2009-04-29 at 14:52 -0400, jsie...@psu.edu wrote: > This is 64bit AIX 5.3. Looking through previous versions of dovecot, I see > this warning. I didn't realize this was something bad until today. > My environment uses mbox/mbox-snarf plugin. > > The message in the logs is: > > local0.log.20090429:Apr 29 12:41:16 hostname dovecot: > IMAP(jsiegle): Timeout leak: 1100054c0 Fixed: http://hg.dovecot.org/dovecot-1.2/rev/66b6cd495702 signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Timeout leak with dovecot version dovecot1.2(8985:f43bebab3dac)
On Apr 30, 2009, at 3:06 PM, Timo Sirainen wrote: On Thu, 2009-04-30 at 15:04 -0400, Jonathan Siegle wrote: telnet localhost 143 1 login user pass 2 select inbox 3 logout Does it get logged? What if you select some other mailbox instead? Yes it gets logged. I did your steps and reproduced. I also did login;select;close;logout and that also gave me the error. What about another mailbox than INBOX? If it happens only with INBOX, the problem is mbox-snarf plugin. It doesn't do it on folders. so login;select folder;logout doesn't produce the error. smime.p7s Description: S/MIME cryptographic signature
Re: [Dovecot] Timeout leak with dovecot version dovecot1.2(8985:f43bebab3dac)
On Thu, 2009-04-30 at 15:04 -0400, Jonathan Siegle wrote: > > telnet localhost 143 > > 1 login user pass > > 2 select inbox > > 3 logout > > > > Does it get logged? What if you select some other mailbox instead? > > > > Yes it gets logged. I did your steps and reproduced. I also did > login;select;close;logout and that also gave me the error. What about another mailbox than INBOX? If it happens only with INBOX, the problem is mbox-snarf plugin. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Timeout leak with dovecot version dovecot1.2(8985:f43bebab3dac)
On Apr 29, 2009, at 2:58 PM, Timo Sirainen wrote: On Wed, 2009-04-29 at 14:52 -0400, jsie...@psu.edu wrote: This is 64bit AIX 5.3. Looking through previous versions of dovecot, I see this warning. I didn't realize this was something bad until today. It's not exactly bad. It gets logged only when the process is exiting. But it shouldn't be happening either. local0.log.20090429:Apr 29 12:41:16 hostname dovecot: IMAP(jsiegle): Timeout leak: 1100054c0 How easily can you reproduce this? For example if you do: telnet localhost 143 1 login user pass 2 select inbox 3 logout Does it get logged? What if you select some other mailbox instead? Yes it gets logged. I did your steps and reproduced. I also did login;select;close;logout and that also gave me the error. smime.p7s Description: S/MIME cryptographic signature
Re: [Dovecot] Timeout leak with dovecot version dovecot1.2(8985:f43bebab3dac)
On Wed, 29 Apr 2009, Timo Sirainen wrote: On Wed, 2009-04-29 at 14:52 -0400, jsie...@psu.edu wrote: This is 64bit AIX 5.3. Looking through previous versions of dovecot, I see this warning. I didn't realize this was something bad until today. It's not exactly bad. It gets logged only when the process is exiting. But it shouldn't be happening either. local0.log.20090429:Apr 29 12:41:16 hostname dovecot: IMAP(jsiegle): Timeout leak: 1100054c0 How easily can you reproduce this? For example if you do: telnet localhost 143 1 login user pass 2 select inbox 3 logout Oh lovely. Now when I do these steps I see in the logs: Apr 30 08:06:23 tr27n12.aset.psu.edu syslog: PSU mbox-snarf name is INBOX Apr 30 08:06:23 tr27n12.aset.psu.edu dovecot: Panic: IMAP(tstem38): file istream-mail-stats.c: line 75: assertion failed: (ret != -1 || stream->istream.eof || stream->istream.stream_errno != 0) Apr 30 08:06:23 tr27n12.aset.psu.edu dovecot: child 630886 (imap) killed with signal 6 I don't get this error for other folders, just the INBOX. I don't get the timeout leak very often. Maybe 15 times a day total for multiple users. I'll do some more debugging of that problem and report back. -Jonathan smime.p7s Description: S/MIME Cryptographic Signature
Re: [Dovecot] Timeout leak with dovecot version dovecot1.2(8985:f43bebab3dac)
On Wed, 2009-04-29 at 14:52 -0400, jsie...@psu.edu wrote: > This is 64bit AIX 5.3. Looking through previous versions of dovecot, I see > this warning. I didn't realize this was something bad until today. It's not exactly bad. It gets logged only when the process is exiting. But it shouldn't be happening either. > local0.log.20090429:Apr 29 12:41:16 hostname dovecot: > IMAP(jsiegle): Timeout leak: 1100054c0 How easily can you reproduce this? For example if you do: telnet localhost 143 1 login user pass 2 select inbox 3 logout Does it get logged? What if you select some other mailbox instead? > (dbx) set $unsafegoto > (dbx) gotoi 0x1100054c0 > stopped in cmd-append. at 0x1100054c0 I don't think this is correct, because there are no timeout callbacks in cmd-append.c. signature.asc Description: This is a digitally signed message part
[Dovecot] Timeout leak with dovecot version dovecot1.2(8985:f43bebab3dac)
This is 64bit AIX 5.3. Looking through previous versions of dovecot, I see this warning. I didn't realize this was something bad until today. My environment uses mbox/mbox-snarf plugin. The message in the logs is: local0.log.20090429:Apr 29 12:41:16 hostname dovecot: IMAP(jsiegle): Timeout leak: 1100054c0 In dbx(the AIX debugger) I see: $ dbx imap Type 'help' for help. reading symbolic information ... (dbx) gotoi 0x1100054c0 Goto address is not within current function or block. (set $unsafegoto to override) (dbx) set $unsafegoto (dbx) gotoi 0x1100054c0 stopped in cmd-append. at 0x1100054c0 0x1100054c0 (???) 0001 Invalid opcode. (dbx) where cmd-append.() at 0x1100054c0 If you need more info, don't hesitate to ask. Thanks, Jonathan
Re: [Dovecot] Timeout leak
Timo Sirainen wrote: > On Mon, 2007-10-01 at 14:24 +0200, Lars Stavholm wrote: >> In my development environment I sometimes get: >> >> dovecot: IMAP(stava): Timeout leak: 0x4425d0 >> >> Does anyone know what it means or how I can use this information? > > It means timeout_add() was called, but the returned struct wasn't passed > to timeout_remove(). The number above is a pointer and with gdb's help > you can figure out what function it points to: > > gdb /usr/local/libexec/dovecot/imap > l *0x4425d0 Thanks! /L
Re: [Dovecot] Timeout leak
On Mon, 2007-10-01 at 14:24 +0200, Lars Stavholm wrote: > In my development environment I sometimes get: > > dovecot: IMAP(stava): Timeout leak: 0x4425d0 > > Does anyone know what it means or how I can use this information? It means timeout_add() was called, but the returned struct wasn't passed to timeout_remove(). The number above is a pointer and with gdb's help you can figure out what function it points to: gdb /usr/local/libexec/dovecot/imap l *0x4425d0 signature.asc Description: This is a digitally signed message part
[Dovecot] Timeout leak
In my development environment I sometimes get: dovecot: IMAP(stava): Timeout leak: 0x4425d0 Does anyone know what it means or how I can use this information? Cheers /Lars
