Re: dovecot crash with Panic: file istream-header-filter.c: line 663

[Gerald Galster]

>>> After the above, it's no longer crashing, and my email client's "pending 
>>> operations" have
>>> cleared.
>> 
>> Does your server use ECC memory and if so, are there any errors logged 
>> (bitflip, ...)?
>> 
>> Best regards,
>> Gerald
> 
> I don't have the logs from that time them nor do I see any hardware / memory 
> errors.
> 
> I also haven't had any other odd failures.
> 
> But how can I tell if I have ECC memory or not?

You could install dmidecode and search for ECC (not L1/L2 cpu cache), e.g.

Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: Multi-bit ECC
Maximum Capacity: 128 GB
Error Information Handle: 0x0008
Number Of Devices: 4

It happens rarely but without ECC those errors often go without notice.

With ECC dmesg/kernel log might show warnings like

kernel: [Hardware Error]: Unified Memory Controller Ext. Error Code: 0, DRAM 
ECC error.
kernel: EDAC MC0: 1 CE Cannot decode normalized address on mc#0csrow#2channel#1 
...
kernel: [Hardware Error]: cache level: L3/GEN, tx: GEN, mem-tx: RD
kernel: core: [Hardware Error]: Machine check events logged
kernel: [Hardware Error]: Corrected error, no action required.

Best regards,
Gerald

Re: dovecot crash with Panic: file istream-header-filter.c: line 663

[Patrick Mansfield]

On Mon, Mar 13, 2023 at 04:33:38PM +0100, Gerald Galster wrote:
> > After the above, it's no longer crashing, and my email client's "pending 
> > operations" have
> > cleared.
> 
> Does your server use ECC memory and if so, are there any errors logged 
> (bitflip, ...)?
> 
> Best regards,
> Gerald

I don't have the logs from that time them nor do I see any hardware / memory 
errors.

I also haven't had any other odd failures.

But how can I tell if I have ECC memory or not?

-- Patrick

Re: dovecot crash with Panic: file istream-header-filter.c: line 663

[Gerald Galster]

> After the above, it's no longer crashing, and my email client's "pending 
> operations" have
> cleared.

Does your server use ECC memory and if so, are there any errors logged 
(bitflip, ...)?

Best regards,
Gerald

Re: dovecot crash with Panic: file istream-header-filter.c: line 663

[Patrick Mansfield]

On Mon, Mar 13, 2023 at 11:01:35AM +0200, Timo Sirainen wrote:
> On 12. Mar 2023, at 20.17, Patrick Mansfield  wrote:
> > 
> > Mar 12 10:32:27 goffin dovecot[8269]: imap(patman)<8452>: 
> > Panic: file istream-header-filter.c: line 663 
> > (i_stream_header_filter_snapshot_free): assertion failed: 
> > (snapshot->mstream->snapshot_pending)
> 
> This is unfortunately rather difficult to debug. First you should find out 
> which folder and mail this is happening in. You can do that with gdb:
> 
> > #16 0x7fa3849aa60a in index_mail_parse_headers_internal 
> > (mail=mail@entry=0x56150ea5fc78, headers=headers@entry=0x0) at 
> > index/index-mail-headers.c:465
> 
> fr 16
> p mail.box.vname
> p mail.uid

OK, I had to use a bit different syntax:

(gdb) fr 16
#16 0x7fa3849aa60a in index_mail_parse_headers_internal 
(mail=mail@entry=0x56150ea5fc78, headers=headers@entry=0x0)
at index/index-mail-headers.c:465
465 message_parser_parse_header(data->parser_ctx, 
>hdr_size,
(gdb) p mail->mail.mail->box->vname
$1 = 0x56150ea60840 "INBOX"
(gdb)  p mail->mail.mail->uid
$2 = 33655

> Likely deleting that mail manually from the mbox will fix it. Of course, it 
> would be nice if we were able to reproduce the bug also. Once you've found 
> the broken folder, could you anonymize the mbox file contents and send it to 
> me privately? https://github.com/dovecot/tools/blob/main/mbox-anonymize.pl 
> can help you do it. Although I'm not sure if even that is enough to reproduce 
> the bug - might need the dovecot.index* files also but those contain cached 
> headers from the emails, which can be rather sensitive data.
> 
> Other things besides deleting the mail that might help, and would be useful 
> to know whether they help:
> 
>  * doveadm fetch -u user imap.bodystructure mailbox $folder uid $uid

The above hits the same crash:

$ doveadm fetch -u patman imap.bodystructure mailbox INBOX uid 33655
Error: net_connect_unix(/run/dovecot/stats-writer) failed: Permission denied
doveadm(patman): Panic: file istream-header-filter.c: line 663 
(i_stream_header_filter_snapshot_free): assertion failed: 
(snapshot->mstream->snapshot_pending)
doveadm(patman): Error: Raw backtrace: 
/usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x46) [0x7fd12d418f46] -> 
/usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x22) [0x7fd12d419082] -> 
/usr/lib64/dovecot/libdovecot.so.0(+0x109557) [0x7fd12d423557] -> 
/usr/lib64/dovecot/libdovecot.so.0(+0x109597) [0x7fd12d423597] -> 
/usr/lib64/dovecot/libdovecot.so.0(+0x5e0e1) [0x7fd12d3780e1] -> 
/usr/lib64/dovecot/libdovecot.so.0(+0x59df8) [0x7fd12d373df8] -> 
/usr/lib64/dovecot/libdovecot.so.0(i_stream_snapshot_free+0x1c) 
[0x7fd12d430b6c] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_unref+0x54) 
[0x7fd12d430c14] -> 
/usr/lib64/dovecot/libdovecot.so.0(message_parse_header_deinit+0x19) 
[0x7fd12d401179] -> /usr/lib64/dovecot/libdovecot.so.0(+0xe8ea1) 
[0x7fd12d402ea1] -> 
/usr/lib64/dovecot/libdovecot.so.0(message_parser_parse_next_block+0x4c) 
[0x7fd12d403edc] -> 
/usr/lib64/dovecot/libdovecot.so.0(message_parser_parse_header+0x59) 
[0x7fd12d404029] -> 
/usr/lib64/dovecot/libdovecot-storage.so.0(index_mail_parse_headers_internal+0x11a)
 [0x7fd12d5ce60a] -> 
/usr/lib64/dovecot/libdovecot-storage.so.0(index_mail_parse_headers+0x4e) 
[0x7fd12d5ce71e] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xdd21e) 
[0x7fd12d5d421e] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xdd2b3) 
[0x7fd12d5d42b3] -> 
/usr/lib64/dovecot/libdovecot-storage.so.0(index_mail_get_special+0x20d) 
[0x7fd12d5d46cd] -> 
/usr/lib64/dovecot/libdovecot-storage.so.0(mail_get_special+0xe) 
[0x7fd12d553a1e] -> /usr/bin/doveadm(+0x3893c) [0x5650816db93c] -> 
/usr/bin/doveadm(+0x3e12e) [0x5650816e112e] -> /usr/bin/doveadm(+0x3bba1) 
[0x5650816deba1] -> 
/usr/bin/doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x29b) [0x5650816dfe0b] 
-> /usr/bin/doveadm(doveadm_cmd_run_ver2+0x4ff) [0x5650816ea67f] -> 
/usr/bin/doveadm(doveadm_cmd_try_run_ver2+0x3b) [0x5650816ea6fb] -> 
/usr/bin/doveadm(main+0x282) [0x5650816cbd92] -> /lib64/libc.so.6(+0x27510) 
[0x7fd12cb6a510] -> /lib64/libc.so.6(__libc_start_main+0x89) [0x7fd12cb6a5c9] 
-> /usr/bin/doveadm(_start+0x25) [0x5650816cbfa5]
Aborted (core dumped)

>  * doveadm mailbox cache remove -u user mailbox $folder uid $uid

Ran (not as root):

$ doveadm mailbox cache remove -u patman mailbox INBOX uid 33655
Error: net_connect_unix(/run/dovecot/stats-writer) failed: Permission denied
mailbox uid   result
INBOX   33655 ok

After the above, it's no longer crashing, and my email client's "pending 
operations" have
cleared.

And this now works:

$ doveadm fetch -u patman imap.bodystructure mailbox INBOX uid 33655
Error: net_connect_unix(/run/dovecot/stats-writer) failed: Permission denied
imap.bodystructure: ("text" "plain" ("charset" "utf-8") NIL NIL "8bit"  107 
NIL NIL NIL NIL)("text" "html" ("charset" "utf-8") NIL NIL "8bit" 34300 270 NIL 
NIL NIL NIL) "alternative" 

Re: dovecot crash with Panic: file istream-header-filter.c: line 663

[Timo Sirainen]

On 12. Mar 2023, at 20.17, Patrick Mansfield  wrote:
> 
> Mar 12 10:32:27 goffin dovecot[8269]: imap(patman)<8452>: 
> Panic: file istream-header-filter.c: line 663 
> (i_stream_header_filter_snapshot_free): assertion failed: 
> (snapshot->mstream->snapshot_pending)

This is unfortunately rather difficult to debug. First you should find out 
which folder and mail this is happening in. You can do that with gdb:

> #16 0x7fa3849aa60a in index_mail_parse_headers_internal 
> (mail=mail@entry=0x56150ea5fc78, headers=headers@entry=0x0) at 
> index/index-mail-headers.c:465

fr 16
p mail.box.vname
p mail.uid

Likely deleting that mail manually from the mbox will fix it. Of course, it 
would be nice if we were able to reproduce the bug also. Once you've found the 
broken folder, could you anonymize the mbox file contents and send it to me 
privately? https://github.com/dovecot/tools/blob/main/mbox-anonymize.pl can 
help you do it. Although I'm not sure if even that is enough to reproduce the 
bug - might need the dovecot.index* files also but those contain cached headers 
from the emails, which can be rather sensitive data.

Other things besides deleting the mail that might help, and would be useful to 
know whether they help:

 * doveadm fetch -u user imap.bodystructure mailbox $folder uid $uid
 * doveadm mailbox cache remove -u user mailbox $folder uid $uid

Re: dovecot crash with Panic: file istream-header-filter.c: line 663

[Patrick Mansfield]

On Sun, Mar 12, 2023 at 11:17:43AM -0700, Patrick Mansfield wrote:
> 
> email client is fairemail version 1.2042a on android, but an older version 
> had the same
> problem.
> 
> I mainly use fairemail to read emails on my phone, and that is working fine 
> but I noticed
> that deleted emails were not actually getting deleted, that it has a bunch of 
> "pending
> operations" it has were not running, and that dovecot has been crashing like 
> this since
> about feb 2 (over a month ago). I can't figure out what changed at that time, 
> but my cert
> says it should have expired over a year ago, but the cert as created 26 
> months ago.
> 
> log files only go back to Feb 5 so just missed that.
> 
> I generated a new cert but it's still crashing (I probably still need to do 
> something on
> the client side or my setup is broken).
> 
> I assume there is something wrong or some "snapshot" thing that's stuck, but 
> since it's
> crashing I can't figure out what the undelysing problem is.

Another thing I noticed:

I think I deleted all emails left in the "Trash" folder outside of imap on Feb 
4 (using
mutt locally) - or that that folder was modified on Feb 4, that is also the 
same timestamp
as my ~/Mail/.imap directory, and is about the time I think it started crashing.

And that these were all dated Feb 4:

$ ls -ld ~/Mail/.imap ~/Mail/Trash ~/Mail/.imap/dovecot.list.index
drwx--. 118 patman patman4096 Feb  4 09:29 /home/patman/Mail/.imap
-rw---1 patman patman   14696 Feb  4 09:11 
/home/patman/Mail/.imap/dovecot.list.index
-rw---1 patman patman 1459841 Feb  4 09:11 /home/patman/Mail/Trash

-- Patrick

dovecot crash with Panic: file istream-header-filter.c: line 663

[Patrick Mansfield]

Hi -

I'm hitting a crash in dovecot, I get this logged followed by a terse stack 
trace and
systemd-coredump details not included here - full gdb stack trace and more 
details are
further down:


Mar 12 10:32:26 goffin dovecot[8269]: imap-login: Login: user=, 
method=PLAIN, rip=192.168.1.4, lip=192.168.1.1, mpid=8477, TLS, 
session=<5RvGYLf2RrDAqAEE>
Mar 12 10:32:26 goffin audit[8304]: USER_AUTH pid=8304 uid=0 auid=4294967295 
ses=4294967295 subj=kernel msg='op=PAM:authentication 
grantors=pam_usertype,pam_localuser,pam_unix acct="patman" 
exe="/usr/libexec/dovecot/auth" hostname=192.168.1.4 addr=192.168.1.4 
terminal=dovecot res=success'
Mar 12 10:32:26 goffin audit[8304]: USER_ACCT pid=8304 uid=0 auid=4294967295 
ses=4294967295 subj=kernel msg='op=PAM:accounting 
grantors=pam_unix,pam_localuser acct="patman" exe="/usr/libexec/dovecot/auth" 
hostname=192.168.1.4 addr=192.168.1.4 terminal=dovecot res=success'
Mar 12 10:32:26 goffin dovecot[8269]: imap-login: Login: user=, 
method=PLAIN, rip=192.168.1.4, lip=192.168.1.1, mpid=8479, TLS, 
session=
Mar 12 10:32:27 goffin dovecot[8269]: imap(patman)<8452>: 
Panic: file istream-header-filter.c: line 663 
(i_stream_header_filter_snapshot_free): assertion failed: 
(snapshot->mstream->snapshot_pending)
Mar 12 10:32:27 goffin audit[8452]: ANOM_ABEND auid=4294967295 uid=1000 
gid=1000 ses=4294967295 subj=kernel pid=8452 comm="imap" 
exe="/usr/libexec/dovecot/imap" sig=6 res=1


email client is fairemail version 1.2042a on android, but an older version had 
the same
problem.

I mainly use fairemail to read emails on my phone, and that is working fine but 
I noticed
that deleted emails were not actually getting deleted, that it has a bunch of 
"pending
operations" it has were not running, and that dovecot has been crashing like 
this since
about feb 2 (over a month ago). I can't figure out what changed at that time, 
but my cert
says it should have expired over a year ago, but the cert as created 26 months 
ago.

log files only go back to Feb 5 so just missed that.

I generated a new cert but it's still crashing (I probably still need to do 
something on
the client side or my setup is broken).

I assume there is something wrong or some "snapshot" thing that's stuck, but 
since it's
crashing I can't figure out what the undelysing problem is.

Thanks for any help.

More details:


# dovecot --version
2.3.20 (80a5ac675d)

Running with up to date fedora core 37.



# dovecot -n
# 2.3.20 (80a5ac675d): /etc/dovecot/dovecot.conf
# OS: Linux 6.1.15-200.fc37.x86_64 x86_64 Fedora release 37 (Thirty Seven)
# Hostname: specu
mail_location = mbox:~/Mail:INBOX=~/Mail/inbox
mbox_write_locks = fcntl
namespace inbox {
  inbox = yes
  location =
  mailbox Drafts {
special_use = \Drafts
  }
  mailbox Junk {
special_use = \Junk
  }
  mailbox Sent {
special_use = \Sent
  }
  mailbox "Sent Messages" {
special_use = \Sent
  }
  mailbox Trash {
special_use = \Trash
  }
  prefix =
}
passdb {
  driver = pam
}
ssl = required
ssl_cert =  for more, q to quit, c to continue without paging-- 
#0  __pthread_kill_implementation (threadid=, 
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO 
(ret) : 0;  

(gdb) bt
#0  __pthread_kill_implementation (threadid=, 
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#1  0x7fa3840afec3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#2  0x7fa38405fa76 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
#3  0x7fa3840497fc in __GI_abort () at abort.c:79
#4  0x7fa3847541e3 in default_fatal_finish (status=0, type=LOG_TYPE_PANIC) 
at ../lib/failures.c:465
#5  fatal_handler_real (ctx=, format=, 
args=) at ../lib/failures.c:477
#6  0x7fa3847ff5f7 in i_internal_fatal_handler (ctx=, 
format=, args=) at ../lib/failures.c:879
#7  0x7fa3847540e1 in i_panic (format=0x7fa384844040 "file %s: line %d 
(%s): assertion failed: (%s)") at ../lib/failures.c:530
#8  0x7fa38474fdf8 in i_stream_header_filter_snapshot_free 
(_snapshot=) at ../lib-mail/istream-header-filter.c:663
#9  i_stream_header_filter_snapshot_free (_snapshot=0x56150ea92250) at 
../lib-mail/istream-header-filter.c:655
#10 0x7fa38480cb6c in i_stream_snapshot_free 
(_snapshot=_snapshot@entry=0x56150ea9d2a0) at ../lib/istream.c:253
#11 0x7fa38480cc14 in i_stream_unref (stream=0x56150ea9d338) at 
../lib/istream.c:66
#12 0x7fa3847dd179 in message_parse_header_deinit 
(_ctx=_ctx@entry=0x56150ea9d0c8) at ../lib-mail/message-header-parser.c:52
#13 0x7fa3847deea1 in preparsed_parse_next_header (ctx=0x56150ea9d050, 
block_r=0x7ffc8222ca70) at ../lib-mail/message-parser-from-parts.c:310

Re: Dovecot crash

[DurgaPrasad - DatasoftComnet]

Hello all,
What happens if we are on mdbox with SiS? I read sometime back that deleting of 
indexes is not good is such case.

Rgds/DP
9849111010 

Sent from my iPhone. Pls excuse brevity and typos if any. 

> On 01-Dec-2018, at 1:49 AM, Thomas Durand  wrote:
> 
> Exactly - I removed then with 
> find . -name "dovecot.index*" -type f -delete
> 
> There is no need to restart dovecot. IMAP client will be forced to resync all 
> the emails from the server.
> 
> 
>> Le 28 nov. 2018 à 23:20, JCA <1.41...@gmail.com> a écrit :
>> 
>> Thanks. Assuming that the IMAP mail directory for the account affected is 
>> under /home/xyz/mail, are you talking about the contents of the index 
>> directory, excluding the log file therein?
>> 
>> On Wed, Nov 28, 2018 at 2:29 PM Thomas Durand  wrote:
>>> Hi,
>>> 
>>> I had the similar messages after an upgrade then downgrade. I was able to 
>>> fix by removing all indexes files. 
>>> 
>>> Thomas 
>>> 
>>> > Le 28 nov. 2018 à 22:02, JCA <1.41...@gmail.com> a écrit :
>>> > 
>>> >   This happening when my Thunderbird client is trying to establish a 
>>> > connection with a Dovecot server. Some background first:
>>> > 
>>> >   1) I am running Thunderbird 6.20.1 from a Linux client.
>>> >   2) Other clients (e.g. Maildroid in my Android phone) do not have any  
>>> > issues.
>>> >   3) The Dovecot software is version 2.2.9, running in a Linux server.
>>> >   4) This may be the root of the problem: at some point, the Dovecot 
>>> > software  was changed to  version 2.3.1, and the reverted to 2.2.9. 
>>> > The crash started to appear when this reversion took place.
>>> > 
>>> >   My guess is that upgrading to 2.3.1 will eliminate this problem. 
>>> > However, in  case that does not solve the problem, I would be grateful if 
>>> > anybody could throw some light into exactly what is going on here, and 
>>> > whether it can be fixed even without the need of upgrading to 2.3.1.
>>> > 
>>> >   What follows are the traces generated by Dovecot  2.2.9 when a 
>>> > connection is attempted from Thunderbird, with usernames and IP addresses 
>>> > disguised for privacy, and some blank lines inserted for readability:
>>> > 
>>> > Nov 28 13:36:20 imap-login: Info: Login: user=, method=PLAIN, 
>>> > rip=xxx.yyy.z
>>> > zz.154, lip=aaa.bbb.ccc.7, mpid=29245, TLS, session=
>>> > 
>>> > Nov 28 13:36:20 imap(xyz): Panic: file mail-index-sync-keywords.c: line 
>>> > 227 (key
>>> > words_update_records): assertion failed: (data_offset >= sizeof(struct 
>>> > mail_index_record))
>>> > 
>>> > Nov 28 13:36:20 imap(xyz): Error: Raw backtrace: 
>>> > /usr/lib/dovecot/libdovecot.so.
>>> > 0(+0x65626) [0xb75ae626] -> /usr/lib/dovecot/libdovecot.so.0(+0x6569f) 
>>> > [0xb75ae6
>>> > 9f] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0xb756180e] -> 
>>> > /usr/lib/dove
>>> > cot/libdovecot-storage.so.0(mail_index_sync_keywords+0x707) [0xb76cb6b7] 
>>> > -> /usr
>>> > /lib/dovecot/libdovecot-storage.so.0(mail_index_sync_record+0xf7) 
>>> > [0xb76cc167] -
>>> > > /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x2a4) 
>>> > > [0xb76cd22
>>> > 4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_map+0x57c) 
>>> > [0xb76bcb9c
>>> > ] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xb7c2a) [0xb76b7c2a] -> 
>>> > /usr/lib
>>> > /dovecot/libdovecot-storage.so.0(+0xb7daa) [0xb76b7daa] -> 
>>> > /usr/lib/dovecot/libd
>>> > ovecot-storage.so.0(mail_index_open+0x114) [0xb76b7f54] -> 
>>> > /usr/lib/dovecot/libd
>>> > ovecot-storage.so.0(index_storage_mailbox_open+0xab) [0xb76a808b] -> 
>>> > /usr/lib/do
>>> > vecot/libdovecot-storage.so.0(+0x5a481) [0xb765a481] -> 
>>> > /usr/lib/dovecot/libdove
>>> > cot-storage.so.0(+0x5a6f2) [0xb765a6f2] -> 
>>> > /usr/lib/dovecot/libdovecot-storage.s
>>> > o.0(+0x7a017) [0xb767a017] -> 
>>> > /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_o
>>> > pen+0x26) [0xb767a1d6] -> dovecot/imap(client_open_save_dest_box+0x79) 
>>> > [0x805dca
>>> > 9] -> dovecot/imap() [0x8052678] -> dovecot/imap(command_exec+0x32) 
>>> > [0x805d7a2]
>>> > -> dovecot/imap() [0x805c746] -> dovecot/imap() [0x805c820] -> 
>>> > dovecot/imap(clie
>>> > nt_handle_input+0x125) [0x805cad5] -> dovecot/imap(client_input+0x71) 
>>> > [0x805ce91
>>> > ] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x42) [0xb75c1292] 
>>> > -> /usr
>>> > /lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xdb) [0xb75c22cb] -> 
>>> > /usr/lib/
>>> > dovecot/libdovecot.so.0(io_loop_run+0x48) [0xb75c0cd8] -> 
>>> > /usr/lib/dovecot/libdo
>>> > vecot.so.0(master_service_run+0x2d) [0xb756728d] -> 
>>> > dovecot/imap(main+0x2bf) [0x
>>> > 8066fef] -> /lib/libc.so.6(__libc_start_main+0xe6) [0xb73cfdb6]
>>> > 
>>> > Nov 28 13:36:20 imap(xyz): Fatal: master: service(imap): child 29245 
>>> > killed with
>>> >  signal 6 (core dumps disabled)
>>> > 
>>> > Nov 28 13:36:20 imap-login: Info: Login: user=, method=PLAIN, 
>>> > rip=xxx.yyy.z
>>> > zz.154, lip=aaa.bbb.ccc.7, mpid=29247, TLS, session=
>>> > 
>>> > Nov 28 13:36:21 

Re: Dovecot crash

[JCA]

Actually, I was wrong - that did indeed fix the problem. Thanks.

On Fri, Nov 30, 2018 at 1:33 PM JCA <1.41...@gmail.com> wrote:

> Thanks. Unfortunately, that made no difference.
>
>
> On Fri, Nov 30, 2018 at 1:20 PM Thomas Durand  wrote:
>
>> Exactly - I removed then with
>> *find* . -name "dovecot.index*" -type f -delete
>>
>> There is no need to restart dovecot. IMAP client will be forced to resync
>> all the emails from the server.
>>
>>
>> Le 28 nov. 2018 à 23:20, JCA <1.41...@gmail.com> a écrit :
>>
>> Thanks. Assuming that the IMAP mail directory for the account affected is
>> under /home/xyz/mail, are you talking about the contents of the index
>> directory, excluding the log file therein?
>>
>> On Wed, Nov 28, 2018 at 2:29 PM Thomas Durand  wrote:
>>
>>> Hi,
>>>
>>> I had the similar messages after an upgrade then downgrade. I was able
>>> to fix by removing all indexes files.
>>>
>>> Thomas
>>>
>>> > Le 28 nov. 2018 à 22:02, JCA <1.41...@gmail.com> a écrit :
>>> >
>>> >   This happening when my Thunderbird client is trying to establish a
>>> connection with a Dovecot server. Some background first:
>>> >
>>> >   1) I am running Thunderbird 6.20.1 from a Linux client.
>>> >   2) Other clients (e.g. Maildroid in my Android phone) do not have
>>> any  issues.
>>> >   3) The Dovecot software is version 2.2.9, running in a Linux server.
>>> >   4) This may be the root of the problem: at some point, the Dovecot
>>> software  was changed to  version 2.3.1, and the reverted to 2.2.9. The
>>> crash started to appear when this reversion took place.
>>> >
>>> >   My guess is that upgrading to 2.3.1 will eliminate this problem.
>>> However, in  case that does not solve the problem, I would be grateful if
>>> anybody could throw some light into exactly what is going on here, and
>>> whether it can be fixed even without the need of upgrading to 2.3.1.
>>> >
>>> >   What follows are the traces generated by Dovecot  2.2.9 when a
>>> connection is attempted from Thunderbird, with usernames and IP addresses
>>> disguised for privacy, and some blank lines inserted for readability:
>>> >
>>> > Nov 28 13:36:20 imap-login: Info: Login: user=, method=PLAIN,
>>> rip=xxx.yyy.z
>>> > zz.154, lip=aaa.bbb.ccc.7, mpid=29245, TLS, session=
>>> >
>>> > Nov 28 13:36:20 imap(xyz): Panic: file mail-index-sync-keywords.c:
>>> line 227 (key
>>> > words_update_records): assertion failed: (data_offset >= sizeof(struct
>>> mail_index_record))
>>> >
>>> > Nov 28 13:36:20 imap(xyz): Error: Raw backtrace:
>>> /usr/lib/dovecot/libdovecot.so.
>>> > 0(+0x65626) [0xb75ae626] -> /usr/lib/dovecot/libdovecot.so.0(+0x6569f)
>>> [0xb75ae6
>>> > 9f] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0xb756180e] ->
>>> /usr/lib/dove
>>> > cot/libdovecot-storage.so.0(mail_index_sync_keywords+0x707)
>>> [0xb76cb6b7] -> /usr
>>> > /lib/dovecot/libdovecot-storage.so.0(mail_index_sync_record+0xf7)
>>> [0xb76cc167] -
>>> > > /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x2a4)
>>> [0xb76cd22
>>> > 4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_map+0x57c)
>>> [0xb76bcb9c
>>> > ] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xb7c2a) [0xb76b7c2a]
>>> -> /usr/lib
>>> > /dovecot/libdovecot-storage.so.0(+0xb7daa) [0xb76b7daa] ->
>>> /usr/lib/dovecot/libd
>>> > ovecot-storage.so.0(mail_index_open+0x114) [0xb76b7f54] ->
>>> /usr/lib/dovecot/libd
>>> > ovecot-storage.so.0(index_storage_mailbox_open+0xab) [0xb76a808b] ->
>>> /usr/lib/do
>>> > vecot/libdovecot-storage.so.0(+0x5a481) [0xb765a481] ->
>>> /usr/lib/dovecot/libdove
>>> > cot-storage.so.0(+0x5a6f2) [0xb765a6f2] ->
>>> /usr/lib/dovecot/libdovecot-storage.s
>>> > o.0(+0x7a017) [0xb767a017] ->
>>> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_o
>>> > pen+0x26) [0xb767a1d6] -> dovecot/imap(client_open_save_dest_box+0x79)
>>> [0x805dca
>>> > 9] -> dovecot/imap() [0x8052678] -> dovecot/imap(command_exec+0x32)
>>> [0x805d7a2]
>>> > -> dovecot/imap() [0x805c746] -> dovecot/imap() [0x805c820] ->
>>> dovecot/imap(clie
>>> > nt_handle_input+0x125) [0x805cad5] -> dovecot/imap(client_input+0x71)
>>> [0x805ce91
>>> > ] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x42)
>>> [0xb75c1292] -> /usr
>>> > /lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xdb) [0xb75c22cb] ->
>>> /usr/lib/
>>> > dovecot/libdovecot.so.0(io_loop_run+0x48) [0xb75c0cd8] ->
>>> /usr/lib/dovecot/libdo
>>> > vecot.so.0(master_service_run+0x2d) [0xb756728d] ->
>>> dovecot/imap(main+0x2bf) [0x
>>> > 8066fef] -> /lib/libc.so.6(__libc_start_main+0xe6) [0xb73cfdb6]
>>> >
>>> > Nov 28 13:36:20 imap(xyz): Fatal: master: service(imap): child 29245
>>> killed with
>>> >  signal 6 (core dumps disabled)
>>> >
>>> > Nov 28 13:36:20 imap-login: Info: Login: user=, method=PLAIN,
>>> rip=xxx.yyy.z
>>> > zz.154, lip=aaa.bbb.ccc.7, mpid=29247, TLS, session=
>>> >
>>> > Nov 28 13:36:21 imap(xyz): Panic: file mail-index-sync-keywords.c:
>>> line 227 (key
>>> > words_update_records): assertion failed: (data_offset >= sizeof(struct

Re: Dovecot crash

[JCA]

Thanks. Unfortunately, that made no difference.


On Fri, Nov 30, 2018 at 1:20 PM Thomas Durand  wrote:

> Exactly - I removed then with
> *find* . -name "dovecot.index*" -type f -delete
>
> There is no need to restart dovecot. IMAP client will be forced to resync
> all the emails from the server.
>
>
> Le 28 nov. 2018 à 23:20, JCA <1.41...@gmail.com> a écrit :
>
> Thanks. Assuming that the IMAP mail directory for the account affected is
> under /home/xyz/mail, are you talking about the contents of the index
> directory, excluding the log file therein?
>
> On Wed, Nov 28, 2018 at 2:29 PM Thomas Durand  wrote:
>
>> Hi,
>>
>> I had the similar messages after an upgrade then downgrade. I was able to
>> fix by removing all indexes files.
>>
>> Thomas
>>
>> > Le 28 nov. 2018 à 22:02, JCA <1.41...@gmail.com> a écrit :
>> >
>> >   This happening when my Thunderbird client is trying to establish a
>> connection with a Dovecot server. Some background first:
>> >
>> >   1) I am running Thunderbird 6.20.1 from a Linux client.
>> >   2) Other clients (e.g. Maildroid in my Android phone) do not have
>> any  issues.
>> >   3) The Dovecot software is version 2.2.9, running in a Linux server.
>> >   4) This may be the root of the problem: at some point, the Dovecot
>> software  was changed to  version 2.3.1, and the reverted to 2.2.9. The
>> crash started to appear when this reversion took place.
>> >
>> >   My guess is that upgrading to 2.3.1 will eliminate this problem.
>> However, in  case that does not solve the problem, I would be grateful if
>> anybody could throw some light into exactly what is going on here, and
>> whether it can be fixed even without the need of upgrading to 2.3.1.
>> >
>> >   What follows are the traces generated by Dovecot  2.2.9 when a
>> connection is attempted from Thunderbird, with usernames and IP addresses
>> disguised for privacy, and some blank lines inserted for readability:
>> >
>> > Nov 28 13:36:20 imap-login: Info: Login: user=, method=PLAIN,
>> rip=xxx.yyy.z
>> > zz.154, lip=aaa.bbb.ccc.7, mpid=29245, TLS, session=
>> >
>> > Nov 28 13:36:20 imap(xyz): Panic: file mail-index-sync-keywords.c: line
>> 227 (key
>> > words_update_records): assertion failed: (data_offset >= sizeof(struct
>> mail_index_record))
>> >
>> > Nov 28 13:36:20 imap(xyz): Error: Raw backtrace:
>> /usr/lib/dovecot/libdovecot.so.
>> > 0(+0x65626) [0xb75ae626] -> /usr/lib/dovecot/libdovecot.so.0(+0x6569f)
>> [0xb75ae6
>> > 9f] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0xb756180e] ->
>> /usr/lib/dove
>> > cot/libdovecot-storage.so.0(mail_index_sync_keywords+0x707)
>> [0xb76cb6b7] -> /usr
>> > /lib/dovecot/libdovecot-storage.so.0(mail_index_sync_record+0xf7)
>> [0xb76cc167] -
>> > > /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x2a4)
>> [0xb76cd22
>> > 4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_map+0x57c)
>> [0xb76bcb9c
>> > ] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xb7c2a) [0xb76b7c2a] ->
>> /usr/lib
>> > /dovecot/libdovecot-storage.so.0(+0xb7daa) [0xb76b7daa] ->
>> /usr/lib/dovecot/libd
>> > ovecot-storage.so.0(mail_index_open+0x114) [0xb76b7f54] ->
>> /usr/lib/dovecot/libd
>> > ovecot-storage.so.0(index_storage_mailbox_open+0xab) [0xb76a808b] ->
>> /usr/lib/do
>> > vecot/libdovecot-storage.so.0(+0x5a481) [0xb765a481] ->
>> /usr/lib/dovecot/libdove
>> > cot-storage.so.0(+0x5a6f2) [0xb765a6f2] ->
>> /usr/lib/dovecot/libdovecot-storage.s
>> > o.0(+0x7a017) [0xb767a017] ->
>> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_o
>> > pen+0x26) [0xb767a1d6] -> dovecot/imap(client_open_save_dest_box+0x79)
>> [0x805dca
>> > 9] -> dovecot/imap() [0x8052678] -> dovecot/imap(command_exec+0x32)
>> [0x805d7a2]
>> > -> dovecot/imap() [0x805c746] -> dovecot/imap() [0x805c820] ->
>> dovecot/imap(clie
>> > nt_handle_input+0x125) [0x805cad5] -> dovecot/imap(client_input+0x71)
>> [0x805ce91
>> > ] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x42)
>> [0xb75c1292] -> /usr
>> > /lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xdb) [0xb75c22cb] ->
>> /usr/lib/
>> > dovecot/libdovecot.so.0(io_loop_run+0x48) [0xb75c0cd8] ->
>> /usr/lib/dovecot/libdo
>> > vecot.so.0(master_service_run+0x2d) [0xb756728d] ->
>> dovecot/imap(main+0x2bf) [0x
>> > 8066fef] -> /lib/libc.so.6(__libc_start_main+0xe6) [0xb73cfdb6]
>> >
>> > Nov 28 13:36:20 imap(xyz): Fatal: master: service(imap): child 29245
>> killed with
>> >  signal 6 (core dumps disabled)
>> >
>> > Nov 28 13:36:20 imap-login: Info: Login: user=, method=PLAIN,
>> rip=xxx.yyy.z
>> > zz.154, lip=aaa.bbb.ccc.7, mpid=29247, TLS, session=
>> >
>> > Nov 28 13:36:21 imap(xyz): Panic: file mail-index-sync-keywords.c: line
>> 227 (key
>> > words_update_records): assertion failed: (data_offset >= sizeof(struct
>> mail_inde
>> > x_record))
>> >
>> > Nov 28 13:36:21 imap(xyz): Error: Raw backtrace:
>> /usr/lib/dovecot/libdovecot.so.
>> > 0(+0x65626) [0xb7757626] -> /usr/lib/dovecot/libdovecot.so.0(+0x6569f)
>> [0xb77576
>> > 9f] -> 

Re: Dovecot crash

[Thomas Durand]

Exactly - I removed then with 
find . -name "dovecot.index*" -type f -delete

There is no need to restart dovecot. IMAP client will be forced to resync all 
the emails from the server.


> Le 28 nov. 2018 à 23:20, JCA <1.41...@gmail.com > a 
> écrit :
> 
> Thanks. Assuming that the IMAP mail directory for the account affected is 
> under /home/xyz/mail, are you talking about the contents of the index 
> directory, excluding the log file therein?
> 
> On Wed, Nov 28, 2018 at 2:29 PM Thomas Durand  > wrote:
> Hi,
> 
> I had the similar messages after an upgrade then downgrade. I was able to fix 
> by removing all indexes files. 
> 
> Thomas 
> 
> > Le 28 nov. 2018 à 22:02, JCA <1.41...@gmail.com > 
> > a écrit :
> > 
> >   This happening when my Thunderbird client is trying to establish a 
> > connection with a Dovecot server. Some background first:
> > 
> >   1) I am running Thunderbird 6.20.1 from a Linux client.
> >   2) Other clients (e.g. Maildroid in my Android phone) do not have any  
> > issues.
> >   3) The Dovecot software is version 2.2.9, running in a Linux server.
> >   4) This may be the root of the problem: at some point, the Dovecot 
> > software  was changed to  version 2.3.1, and the reverted to 2.2.9. The 
> > crash started to appear when this reversion took place.
> > 
> >   My guess is that upgrading to 2.3.1 will eliminate this problem. However, 
> > in  case that does not solve the problem, I would be grateful if anybody 
> > could throw some light into exactly what is going on here, and whether it 
> > can be fixed even without the need of upgrading to 2.3.1.
> > 
> >   What follows are the traces generated by Dovecot  2.2.9 when a connection 
> > is attempted from Thunderbird, with usernames and IP addresses disguised 
> > for privacy, and some blank lines inserted for readability:
> > 
> > Nov 28 13:36:20 imap-login: Info: Login: user=, method=PLAIN, 
> > rip=xxx.yyy.z
> > zz.154, lip=aaa.bbb.ccc.7, mpid=29245, TLS, session=
> > 
> > Nov 28 13:36:20 imap(xyz): Panic: file mail-index-sync-keywords.c: line 227 
> > (key
> > words_update_records): assertion failed: (data_offset >= sizeof(struct 
> > mail_index_record))
> > 
> > Nov 28 13:36:20 imap(xyz): Error: Raw backtrace: 
> > /usr/lib/dovecot/libdovecot.so.
> > 0(+0x65626) [0xb75ae626] -> /usr/lib/dovecot/libdovecot.so.0(+0x6569f) 
> > [0xb75ae6
> > 9f] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0xb756180e] -> 
> > /usr/lib/dove
> > cot/libdovecot-storage.so.0(mail_index_sync_keywords+0x707) [0xb76cb6b7] -> 
> > /usr
> > /lib/dovecot/libdovecot-storage.so.0(mail_index_sync_record+0xf7) 
> > [0xb76cc167] -
> > > /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x2a4) 
> > > [0xb76cd22
> > 4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_map+0x57c) 
> > [0xb76bcb9c
> > ] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xb7c2a) [0xb76b7c2a] -> 
> > /usr/lib
> > /dovecot/libdovecot-storage.so.0(+0xb7daa) [0xb76b7daa] -> 
> > /usr/lib/dovecot/libd
> > ovecot-storage.so.0(mail_index_open+0x114) [0xb76b7f54] -> 
> > /usr/lib/dovecot/libd
> > ovecot-storage.so.0(index_storage_mailbox_open+0xab) [0xb76a808b] -> 
> > /usr/lib/do
> > vecot/libdovecot-storage.so.0(+0x5a481) [0xb765a481] -> 
> > /usr/lib/dovecot/libdove
> > cot-storage.so.0(+0x5a6f2) [0xb765a6f2] -> 
> > /usr/lib/dovecot/libdovecot-storage.s
> > o.0(+0x7a017) [0xb767a017] -> 
> > /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_o
> > pen+0x26) [0xb767a1d6] -> dovecot/imap(client_open_save_dest_box+0x79) 
> > [0x805dca
> > 9] -> dovecot/imap() [0x8052678] -> dovecot/imap(command_exec+0x32) 
> > [0x805d7a2]
> > -> dovecot/imap() [0x805c746] -> dovecot/imap() [0x805c820] -> 
> > dovecot/imap(clie
> > nt_handle_input+0x125) [0x805cad5] -> dovecot/imap(client_input+0x71) 
> > [0x805ce91
> > ] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x42) [0xb75c1292] -> 
> > /usr
> > /lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xdb) [0xb75c22cb] -> 
> > /usr/lib/
> > dovecot/libdovecot.so.0(io_loop_run+0x48) [0xb75c0cd8] -> 
> > /usr/lib/dovecot/libdo
> > vecot.so.0(master_service_run+0x2d) [0xb756728d] -> 
> > dovecot/imap(main+0x2bf) [0x
> > 8066fef] -> /lib/libc.so.6(__libc_start_main+0xe6) [0xb73cfdb6]
> > 
> > Nov 28 13:36:20 imap(xyz): Fatal: master: service(imap): child 29245 killed 
> > with
> >  signal 6 (core dumps disabled)
> > 
> > Nov 28 13:36:20 imap-login: Info: Login: user=, method=PLAIN, 
> > rip=xxx.yyy.z
> > zz.154, lip=aaa.bbb.ccc.7, mpid=29247, TLS, session=
> > 
> > Nov 28 13:36:21 imap(xyz): Panic: file mail-index-sync-keywords.c: line 227 
> > (key
> > words_update_records): assertion failed: (data_offset >= sizeof(struct 
> > mail_inde
> > x_record))
> > 
> > Nov 28 13:36:21 imap(xyz): Error: Raw backtrace: 
> > /usr/lib/dovecot/libdovecot.so.
> > 0(+0x65626) [0xb7757626] -> /usr/lib/dovecot/libdovecot.so.0(+0x6569f) 
> > [0xb77576
> > 9f] -> 

Re: Dovecot crash

[JCA]

Thanks. Assuming that the IMAP mail directory for the account affected is
under /home/xyz/mail, are you talking about the contents of the index
directory, excluding the log file therein?

On Wed, Nov 28, 2018 at 2:29 PM Thomas Durand  wrote:

> Hi,
>
> I had the similar messages after an upgrade then downgrade. I was able to
> fix by removing all indexes files.
>
> Thomas
>
> > Le 28 nov. 2018 à 22:02, JCA <1.41...@gmail.com> a écrit :
> >
> >   This happening when my Thunderbird client is trying to establish a
> connection with a Dovecot server. Some background first:
> >
> >   1) I am running Thunderbird 6.20.1 from a Linux client.
> >   2) Other clients (e.g. Maildroid in my Android phone) do not have any
> issues.
> >   3) The Dovecot software is version 2.2.9, running in a Linux server.
> >   4) This may be the root of the problem: at some point, the Dovecot
> software  was changed to  version 2.3.1, and the reverted to 2.2.9. The
> crash started to appear when this reversion took place.
> >
> >   My guess is that upgrading to 2.3.1 will eliminate this problem.
> However, in  case that does not solve the problem, I would be grateful if
> anybody could throw some light into exactly what is going on here, and
> whether it can be fixed even without the need of upgrading to 2.3.1.
> >
> >   What follows are the traces generated by Dovecot  2.2.9 when a
> connection is attempted from Thunderbird, with usernames and IP addresses
> disguised for privacy, and some blank lines inserted for readability:
> >
> > Nov 28 13:36:20 imap-login: Info: Login: user=, method=PLAIN,
> rip=xxx.yyy.z
> > zz.154, lip=aaa.bbb.ccc.7, mpid=29245, TLS, session=
> >
> > Nov 28 13:36:20 imap(xyz): Panic: file mail-index-sync-keywords.c: line
> 227 (key
> > words_update_records): assertion failed: (data_offset >= sizeof(struct
> mail_index_record))
> >
> > Nov 28 13:36:20 imap(xyz): Error: Raw backtrace:
> /usr/lib/dovecot/libdovecot.so.
> > 0(+0x65626) [0xb75ae626] -> /usr/lib/dovecot/libdovecot.so.0(+0x6569f)
> [0xb75ae6
> > 9f] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0xb756180e] ->
> /usr/lib/dove
> > cot/libdovecot-storage.so.0(mail_index_sync_keywords+0x707) [0xb76cb6b7]
> -> /usr
> > /lib/dovecot/libdovecot-storage.so.0(mail_index_sync_record+0xf7)
> [0xb76cc167] -
> > > /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x2a4)
> [0xb76cd22
> > 4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_map+0x57c)
> [0xb76bcb9c
> > ] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xb7c2a) [0xb76b7c2a] ->
> /usr/lib
> > /dovecot/libdovecot-storage.so.0(+0xb7daa) [0xb76b7daa] ->
> /usr/lib/dovecot/libd
> > ovecot-storage.so.0(mail_index_open+0x114) [0xb76b7f54] ->
> /usr/lib/dovecot/libd
> > ovecot-storage.so.0(index_storage_mailbox_open+0xab) [0xb76a808b] ->
> /usr/lib/do
> > vecot/libdovecot-storage.so.0(+0x5a481) [0xb765a481] ->
> /usr/lib/dovecot/libdove
> > cot-storage.so.0(+0x5a6f2) [0xb765a6f2] ->
> /usr/lib/dovecot/libdovecot-storage.s
> > o.0(+0x7a017) [0xb767a017] ->
> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_o
> > pen+0x26) [0xb767a1d6] -> dovecot/imap(client_open_save_dest_box+0x79)
> [0x805dca
> > 9] -> dovecot/imap() [0x8052678] -> dovecot/imap(command_exec+0x32)
> [0x805d7a2]
> > -> dovecot/imap() [0x805c746] -> dovecot/imap() [0x805c820] ->
> dovecot/imap(clie
> > nt_handle_input+0x125) [0x805cad5] -> dovecot/imap(client_input+0x71)
> [0x805ce91
> > ] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x42) [0xb75c1292]
> -> /usr
> > /lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xdb) [0xb75c22cb] ->
> /usr/lib/
> > dovecot/libdovecot.so.0(io_loop_run+0x48) [0xb75c0cd8] ->
> /usr/lib/dovecot/libdo
> > vecot.so.0(master_service_run+0x2d) [0xb756728d] ->
> dovecot/imap(main+0x2bf) [0x
> > 8066fef] -> /lib/libc.so.6(__libc_start_main+0xe6) [0xb73cfdb6]
> >
> > Nov 28 13:36:20 imap(xyz): Fatal: master: service(imap): child 29245
> killed with
> >  signal 6 (core dumps disabled)
> >
> > Nov 28 13:36:20 imap-login: Info: Login: user=, method=PLAIN,
> rip=xxx.yyy.z
> > zz.154, lip=aaa.bbb.ccc.7, mpid=29247, TLS, session=
> >
> > Nov 28 13:36:21 imap(xyz): Panic: file mail-index-sync-keywords.c: line
> 227 (key
> > words_update_records): assertion failed: (data_offset >= sizeof(struct
> mail_inde
> > x_record))
> >
> > Nov 28 13:36:21 imap(xyz): Error: Raw backtrace:
> /usr/lib/dovecot/libdovecot.so.
> > 0(+0x65626) [0xb7757626] -> /usr/lib/dovecot/libdovecot.so.0(+0x6569f)
> [0xb77576
> > 9f] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0xb770a80e] ->
> /usr/lib/dove
> > cot/libdovecot-storage.so.0(mail_index_sync_keywords+0x707) [0xb78746b7]
> -> /usr
> > /lib/dovecot/libdovecot-storage.so.0(mail_index_sync_record+0xf7)
> [0xb7875167] -
> > > /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x2a4)
> [0xb787622
> > 4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_map+0x57c)
> [0xb7865b9c
> > ] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xb7c2a) [0xb7860c2a] ->
> 

Re: Dovecot crash

[Thomas Durand]

Hi,

I had the similar messages after an upgrade then downgrade. I was able to fix 
by removing all indexes files. 

Thomas 

> Le 28 nov. 2018 à 22:02, JCA <1.41...@gmail.com> a écrit :
> 
>   This happening when my Thunderbird client is trying to establish a 
> connection with a Dovecot server. Some background first:
> 
>   1) I am running Thunderbird 6.20.1 from a Linux client.
>   2) Other clients (e.g. Maildroid in my Android phone) do not have any  
> issues.
>   3) The Dovecot software is version 2.2.9, running in a Linux server.
>   4) This may be the root of the problem: at some point, the Dovecot software 
>  was changed to  version 2.3.1, and the reverted to 2.2.9. The crash 
> started to appear when this reversion took place.
> 
>   My guess is that upgrading to 2.3.1 will eliminate this problem. However, 
> in  case that does not solve the problem, I would be grateful if anybody 
> could throw some light into exactly what is going on here, and whether it can 
> be fixed even without the need of upgrading to 2.3.1.
> 
>   What follows are the traces generated by Dovecot  2.2.9 when a connection 
> is attempted from Thunderbird, with usernames and IP addresses disguised for 
> privacy, and some blank lines inserted for readability:
> 
> Nov 28 13:36:20 imap-login: Info: Login: user=, method=PLAIN, 
> rip=xxx.yyy.z
> zz.154, lip=aaa.bbb.ccc.7, mpid=29245, TLS, session=
> 
> Nov 28 13:36:20 imap(xyz): Panic: file mail-index-sync-keywords.c: line 227 
> (key
> words_update_records): assertion failed: (data_offset >= sizeof(struct 
> mail_index_record))
> 
> Nov 28 13:36:20 imap(xyz): Error: Raw backtrace: 
> /usr/lib/dovecot/libdovecot.so.
> 0(+0x65626) [0xb75ae626] -> /usr/lib/dovecot/libdovecot.so.0(+0x6569f) 
> [0xb75ae6
> 9f] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0xb756180e] -> 
> /usr/lib/dove
> cot/libdovecot-storage.so.0(mail_index_sync_keywords+0x707) [0xb76cb6b7] -> 
> /usr
> /lib/dovecot/libdovecot-storage.so.0(mail_index_sync_record+0xf7) 
> [0xb76cc167] -
> > /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x2a4) 
> > [0xb76cd22
> 4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_map+0x57c) 
> [0xb76bcb9c
> ] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xb7c2a) [0xb76b7c2a] -> 
> /usr/lib
> /dovecot/libdovecot-storage.so.0(+0xb7daa) [0xb76b7daa] -> 
> /usr/lib/dovecot/libd
> ovecot-storage.so.0(mail_index_open+0x114) [0xb76b7f54] -> 
> /usr/lib/dovecot/libd
> ovecot-storage.so.0(index_storage_mailbox_open+0xab) [0xb76a808b] -> 
> /usr/lib/do
> vecot/libdovecot-storage.so.0(+0x5a481) [0xb765a481] -> 
> /usr/lib/dovecot/libdove
> cot-storage.so.0(+0x5a6f2) [0xb765a6f2] -> 
> /usr/lib/dovecot/libdovecot-storage.s
> o.0(+0x7a017) [0xb767a017] -> 
> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_o
> pen+0x26) [0xb767a1d6] -> dovecot/imap(client_open_save_dest_box+0x79) 
> [0x805dca
> 9] -> dovecot/imap() [0x8052678] -> dovecot/imap(command_exec+0x32) 
> [0x805d7a2]
> -> dovecot/imap() [0x805c746] -> dovecot/imap() [0x805c820] -> 
> dovecot/imap(clie
> nt_handle_input+0x125) [0x805cad5] -> dovecot/imap(client_input+0x71) 
> [0x805ce91
> ] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x42) [0xb75c1292] -> 
> /usr
> /lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xdb) [0xb75c22cb] -> 
> /usr/lib/
> dovecot/libdovecot.so.0(io_loop_run+0x48) [0xb75c0cd8] -> 
> /usr/lib/dovecot/libdo
> vecot.so.0(master_service_run+0x2d) [0xb756728d] -> dovecot/imap(main+0x2bf) 
> [0x
> 8066fef] -> /lib/libc.so.6(__libc_start_main+0xe6) [0xb73cfdb6]
> 
> Nov 28 13:36:20 imap(xyz): Fatal: master: service(imap): child 29245 killed 
> with
>  signal 6 (core dumps disabled)
> 
> Nov 28 13:36:20 imap-login: Info: Login: user=, method=PLAIN, 
> rip=xxx.yyy.z
> zz.154, lip=aaa.bbb.ccc.7, mpid=29247, TLS, session=
> 
> Nov 28 13:36:21 imap(xyz): Panic: file mail-index-sync-keywords.c: line 227 
> (key
> words_update_records): assertion failed: (data_offset >= sizeof(struct 
> mail_inde
> x_record))
> 
> Nov 28 13:36:21 imap(xyz): Error: Raw backtrace: 
> /usr/lib/dovecot/libdovecot.so.
> 0(+0x65626) [0xb7757626] -> /usr/lib/dovecot/libdovecot.so.0(+0x6569f) 
> [0xb77576
> 9f] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0xb770a80e] -> 
> /usr/lib/dove
> cot/libdovecot-storage.so.0(mail_index_sync_keywords+0x707) [0xb78746b7] -> 
> /usr
> /lib/dovecot/libdovecot-storage.so.0(mail_index_sync_record+0xf7) 
> [0xb7875167] -
> > /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x2a4) 
> > [0xb787622
> 4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_map+0x57c) 
> [0xb7865b9c
> ] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xb7c2a) [0xb7860c2a] -> 
> /usr/lib
> /dovecot/libdovecot-storage.so.0(+0xb7daa) [0xb7860daa] -> 
> /usr/lib/dovecot/libd
> ovecot-storage.so.0(mail_index_open+0x114) [0xb7860f54] -> 
> /usr/lib/dovecot/libd
> ovecot-storage.so.0(index_storage_mailbox_open+0xab) [0xb785108b] -> 
> /usr/lib/do
> vecot/libdovecot-storage.so.0(+0x5a481) 

Dovecot crash

[JCA]

  This happening when my Thunderbird client is trying to establish a
connection with a Dovecot server. Some background first:

  1) I am running Thunderbird 6.20.1 from a Linux client.
  2) Other clients (e.g. Maildroid in my Android phone) do not have any
issues.
  3) The Dovecot software is version 2.2.9, running in a Linux server.
  4) This may be the root of the problem: at some point, the Dovecot
software  was changed to  version 2.3.1, and the reverted to 2.2.9. The
crash started to appear when this reversion took place.

  My guess is that upgrading to 2.3.1 will eliminate this problem. However,
in  case that does not solve the problem, I would be grateful if anybody
could throw some light into exactly what is going on here, and whether it
can be fixed even without the need of upgrading to 2.3.1.

  What follows are the traces generated by Dovecot  2.2.9 when a connection
is attempted from Thunderbird, with usernames and IP addresses disguised
for privacy, and some blank lines inserted for readability:

Nov 28 13:36:20 imap-login: Info: Login: user=, method=PLAIN,
rip=xxx.yyy.z
zz.154, lip=aaa.bbb.ccc.7, mpid=29245, TLS, session=

Nov 28 13:36:20 imap(xyz): Panic: file mail-index-sync-keywords.c: line 227
(key
words_update_records): assertion failed: (data_offset >= sizeof(struct
mail_index_record))

Nov 28 13:36:20 imap(xyz): Error: Raw backtrace:
/usr/lib/dovecot/libdovecot.so.
0(+0x65626) [0xb75ae626] -> /usr/lib/dovecot/libdovecot.so.0(+0x6569f)
[0xb75ae6
9f] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0xb756180e] ->
/usr/lib/dove
cot/libdovecot-storage.so.0(mail_index_sync_keywords+0x707) [0xb76cb6b7] ->
/usr
/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_record+0xf7)
[0xb76cc167] -
> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x2a4)
[0xb76cd22
4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_map+0x57c)
[0xb76bcb9c
] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xb7c2a) [0xb76b7c2a] ->
/usr/lib
/dovecot/libdovecot-storage.so.0(+0xb7daa) [0xb76b7daa] ->
/usr/lib/dovecot/libd
ovecot-storage.so.0(mail_index_open+0x114) [0xb76b7f54] ->
/usr/lib/dovecot/libd
ovecot-storage.so.0(index_storage_mailbox_open+0xab) [0xb76a808b] ->
/usr/lib/do
vecot/libdovecot-storage.so.0(+0x5a481) [0xb765a481] ->
/usr/lib/dovecot/libdove
cot-storage.so.0(+0x5a6f2) [0xb765a6f2] ->
/usr/lib/dovecot/libdovecot-storage.s
o.0(+0x7a017) [0xb767a017] ->
/usr/lib/dovecot/libdovecot-storage.so.0(mailbox_o
pen+0x26) [0xb767a1d6] -> dovecot/imap(client_open_save_dest_box+0x79)
[0x805dca
9] -> dovecot/imap() [0x8052678] -> dovecot/imap(command_exec+0x32)
[0x805d7a2]
-> dovecot/imap() [0x805c746] -> dovecot/imap() [0x805c820] ->
dovecot/imap(clie
nt_handle_input+0x125) [0x805cad5] -> dovecot/imap(client_input+0x71)
[0x805ce91
] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x42) [0xb75c1292] ->
/usr
/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xdb) [0xb75c22cb] ->
/usr/lib/
dovecot/libdovecot.so.0(io_loop_run+0x48) [0xb75c0cd8] ->
/usr/lib/dovecot/libdo
vecot.so.0(master_service_run+0x2d) [0xb756728d] ->
dovecot/imap(main+0x2bf) [0x
8066fef] -> /lib/libc.so.6(__libc_start_main+0xe6) [0xb73cfdb6]

Nov 28 13:36:20 imap(xyz): Fatal: master: service(imap): child 29245 killed
with
 signal 6 (core dumps disabled)

Nov 28 13:36:20 imap-login: Info: Login: user=, method=PLAIN,
rip=xxx.yyy.z
zz.154, lip=aaa.bbb.ccc.7, mpid=29247, TLS, session=

Nov 28 13:36:21 imap(xyz): Panic: file mail-index-sync-keywords.c: line 227
(key
words_update_records): assertion failed: (data_offset >= sizeof(struct
mail_inde
x_record))

Nov 28 13:36:21 imap(xyz): Error: Raw backtrace:
/usr/lib/dovecot/libdovecot.so.
0(+0x65626) [0xb7757626] -> /usr/lib/dovecot/libdovecot.so.0(+0x6569f)
[0xb77576
9f] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0xb770a80e] ->
/usr/lib/dove
cot/libdovecot-storage.so.0(mail_index_sync_keywords+0x707) [0xb78746b7] ->
/usr
/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_record+0xf7)
[0xb7875167] -
> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x2a4)
[0xb787622
4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_map+0x57c)
[0xb7865b9c
] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xb7c2a) [0xb7860c2a] ->
/usr/lib
/dovecot/libdovecot-storage.so.0(+0xb7daa) [0xb7860daa] ->
/usr/lib/dovecot/libd
ovecot-storage.so.0(mail_index_open+0x114) [0xb7860f54] ->
/usr/lib/dovecot/libd
ovecot-storage.so.0(index_storage_mailbox_open+0xab) [0xb785108b] ->
/usr/lib/do
vecot/libdovecot-storage.so.0(+0x5a481) [0xb7803481] ->
/usr/lib/dovecot/libdove
cot-storage.so.0(+0x5a6f2) [0xb78036f2] ->
/usr/lib/dovecot/libdovecot-storage.s
o.0(+0x7a017) [0xb7823017] ->
/usr/lib/dovecot/libdovecot-storage.so.0(mailbox_o
pen+0x26) [0xb78231d6] -> dovecot/imap(client_open_save_dest_box+0x79)
[0x805dca
9] -> dovecot/imap() [0x8052678] -> dovecot/imap(command_exec+0x32)
[0x805d7a2]
-> dovecot/imap() [0x805c746] -> dovecot/imap() [0x805c820] ->
dovecot/imap(clie
nt_handle_input+0x125) 

dovecot crash with virtual folders (debian testing version 2.2.13-11)

[James Bottomley]

The virtual folder triggering the crash has the configuration

namespace {
  prefix = virtual/
  separator = /
  location = virtual:~/Maildir/virtual
}

And the actual virtual/openstack/dovecot-virtual file is

Lists/openstack-dev
  inthread refs or from james bottomley keyword thread

It's a standard search for threads I've either replied to or marked with
an imap keyword 'thread'

The imap command

0 status virtual/openstack (MESSAGES UNSEEN RECENT)

Is crashing most of the time with

gdb /usr/lib/dovecot/imap
GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show
copying
and show warranty for details.
This GDB was configured as i586-linux-gnu.
Type show configuration for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type help.
Type apropos word to search for commands related to word...
Reading symbols from /usr/lib/dovecot/imap...Reading symbols
from /usr/lib/debug//usr/lib/dovecot/imap...done.
done.
(gdb) r
Starting program: /usr/lib/dovecot/imap 
process 7868 is executing new program: /usr/bin/doveconf
process 7868 is executing new program: /usr/lib/dovecot/imap
* PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID
ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS
THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN
NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH
ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE BINARY
MOVE] Logged in as jejb
0 status virtual/openstack (MESSAGES UNSEEN RECENT)

Program received signal SIGSEGV, Segmentation fault.
0xb7f0814b in mail_search_args_deinit_sub (args=args@entry=0x8005caf0, 
arg=0x8005cb08) at mail-search.c:169
169 mail-search.c: No such file or directory.
(gdb) bt
#0  0xb7f0814b in mail_search_args_deinit_sub
(args=args@entry=0x8005caf0, 
arg=0x8005cb08) at mail-search.c:169
#1  0xb7f08aea in mail_search_args_deinit (args=0x8005caf0)
at mail-search.c:193
#2  0xb7d9ecf1 in virtual_mailbox_close_internal
(mbox=mbox@entry=0x800585d0)
at virtual-storage.c:253
#3  0xb7d9ed7b in virtual_mailbox_close (box=0x800585d0)
at virtual-storage.c:307
#4  0xb7f403ff in mail_thread_mailbox_close (box=0x800585d0)
at index-thread.c:628
#5  0xb7f0d3fe in mailbox_close (box=0x800585d0) at mail-storage.c:1182
#6  0xb7f0d472 in mailbox_free (_box=0xb878) at mail-storage.c:1197
#7  0x8001e0ae in imap_status_get (cmd=0x80053948, ns=0x80052220, 
mailbox=0x8003a250 virtual/openstack, items=0xb8f8, 
result_r=0xb900) at imap-status.c:96
#8  0x80011f64 in cmd_status (cmd=0x80053948) at cmd-status.c:40
#9  0x80016847 in command_exec (cmd=0x80053948) at imap-commands.c:158
#10 0x800155cb in client_command_input (cmd=0x80053948) at
imap-client.c:778
#11 0x80015719 in client_command_input (cmd=0x80053948) at
imap-client.c:839
#12 0x800159cd in client_handle_next_command (remove_io_r=synthetic
pointer, 
client=0x80052ee0) at imap-client.c:877
#13 client_handle_input (client=0x80052ee0) at imap-client.c:889
#14 0x80015dd5 in client_input (client=0x80052ee0) at imap-client.c:931
---Type return to continue, or q return to quit---
#15 0xb7e202e3 in io_loop_call_io (io=0x800538c8) at ioloop.c:441
#16 0xb7e214be in io_loop_handler_run_internal (ioloop=0x80042458)
at ioloop-epoll.c:220
#17 0xb7e2036a in io_loop_handler_run (ioloop=0x80042458) at
ioloop.c:488
#18 0xb7e203f9 in io_loop_run (ioloop=0x80042458) at ioloop.c:465
#19 0xb7dc6985 in master_service_run (service=0x80042380, 
callback=0x800200b0 client_connected) at master-service.c:566
#20 0x80008b44 in main (argc=1, argv=0xbd84) at main.c:400

I thought it might be this patch

http://hg.dovecot.org/dovecot-2.2/rev/5c6f49e2d8d9

But after applying I still get the same segfault.

James

Re: [Dovecot] crash while fts searching a virtual folder

[Matthias Rieber]

On Fri, 2 May 2014, Timo Sirainen wrote:


On 25.4.2014, at 15.24, Matthias Rieber ml-dove...@zu-con.org wrote:


searching a virtual folder crashes dovecot quite often. I'm using dovecot 
2.2.12. Here's the backtrace:

#5  0x7fc1d6774ed9 in level_scores_add_vuids (br=0x2413ab8, 
level=0x1c0c2e0, vbox=0x170c950) at fts-search.c:81


http://hg.dovecot.org/dovecot-2.2/rev/d63b209737be should fix this.


after a few searches I get the following crash:

[New LWP 4218]
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
Core was generated by `dovecot/imap'.
Program terminated with signal 6, Aborted.
#0  0x7fbfff6d9425 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#0  0x7fbfff6d9425 in raise () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#1  0x7fbfff6dcb8b in abort () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#2  0x7fbfffacc935 in default_fatal_finish (type=optimized out, status=0) 
at failures.c:193
backtrace = 0x1240598 /usr/local/lib/dovecot/libdovecot.so.0(+0x6993f) 
[0x7fbfffacc93f] - /usr/local/lib/dovecot/libdovecot.so.0(+0x6999e) [0x7fbfffacc99e] - 
/usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fbfffa85...
#3  0x7fbfffacc99e in i_internal_fatal_handler (ctx=0x7fffe578e2f0, 
format=optimized out, args=optimized out) at failures.c:657
status = 0
#4  0x7fbfffa85969 in i_panic (format=optimized out) at failures.c:267
ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp = 0x0}
args = {{gp_offset = 40, fp_offset = 48, overflow_arg_area = 
0x7fffe578e3c0, reg_save_area = 0x7fffe578e300}}
#5  0x7fbffea5a007 in fts_search_deserialize_add_idx (args=optimized out, buf=optimized 
out, idx=optimized out, matches=optimized out) at fts-search-serialize.c:63
No locals.
#6  fts_search_deserialize_add_idx (args=0x1622db0, buf=0x16a5ac8, 
idx=0x7fffe578e40c, matches=false) at fts-search-serialize.c:56
data = 0x16a5b00 
#7  0x7fbffea5a15c in fts_search_deserialize_add_nonmatches (args=optimized 
out, buf=0x16a5ac8) at fts-search-serialize.c:97
idx = 0
__FUNCTION__ = fts_search_deserialize_add_nonmatches
#8  0x7fbffea5ab7f in fts_search_apply_results_level (ctx=0x134e850, 
args=0x1622db0, idx=0x7fffe578e46c) at fts-storage.c:277
fctx = optimized out
level = 0x16257e0
#9  0x7fbffea5ad12 in fts_mailbox_search_next_update_seq (ctx=0x134e850) at 
fts-storage.c:314
fbox = 0x12769a0
fctx = 0x16256a0
idx = 0
#10 0x7fbfffddbb1c in search_more_with_mail (mail=0x16b62b0, ctx=0x134e850) 
at index-search.c:1509
_ctx = 0x134e850
box = 0x12759a0
match = 0
ret = -1
imail = 0x16b62b0
cost1 = 0
#11 search_more_with_prefetching (mail_r=optimized out, ctx=optimized out) 
at index-search.c:1582
_data_stack_cur_id = 4
ret = optimized out
mail = 0x16b62b0
#12 search_more (ctx=0x134e850, mail_r=0x7fffe578e500) at index-search.c:1653
imail = optimized out
ret = 0
#13 0x7fbfffddc1b8 in index_storage_search_next_nonblock (_ctx=0x134e850, 
mail_r=0x7fffe578e600, tryagain_r=0x7fffe578e60f) at index-search.c:1689
ctx = 0x134e850
mail = 0x62e8f0
seq = optimized out
ret = optimized out
#14 0x7fbffe846106 in virtual_search_next_nonblock (ctx=0x134e850, 
mail_r=0x7fffe578e600, tryagain_r=0x7fffe578e60f) at virtual-search.c:150
vctx = 0x16253c0
ictx = 0x134e850
seq = optimized out
__FUNCTION__ = virtual_search_next_nonblock
#15 0x7fbffe84601e in virtual_search_next_nonblock (ctx=0x134e850, 
mail_r=0x7fffe578e600, tryagain_r=0x7fffe578e60f) at virtual-search.c:148
vctx = 0x16253c0
ictx = 0x134e850
seq = optimized out
__FUNCTION__ = virtual_search_next_nonblock
#16 0x7fbfffdb5ac7 in mailbox_search_next_nonblock (ctx=0x134e850, 
mail_r=0x7fffe578e600, tryagain_r=optimized out) at mail-storage.c:1796
box = optimized out
#17 0x0041c6e7 in cmd_search_more (cmd=0x1273180) at imap-search.c:443
ctx = 0x12732a0
opts = SEARCH_RETURN_ALL
mail = 0x0
sync_flags = optimized out
end_time = {tv_sec = 23813664, tv_usec = 1024}
range = 0x6
count = optimized out
id = optimized out
id_min = 0
id_max = 0
ok_reply = optimized out
time_msecs = optimized out
tryagain = optimized out
lost_data = optimized out
__FUNCTION__ = cmd_search_more
#18 0x0041cb69 in imap_search_start (ctx=0x12732a0, sargs=optimized out, 
sort_program=optimized out) at imap-search.c:610
cmd = 0x1273180
__FUNCTION__ = imap_search_start
#19 0x00412f49 in cmd_sort (cmd=0x1273180) at cmd-sort.c:141
ctx = 0x12732a0
sargs = 0x1622ce0
sort_program = 

Re: [Dovecot] crash while fts searching a virtual folder

[Timo Sirainen]

On 25.4.2014, at 15.24, Matthias Rieber ml-dove...@zu-con.org wrote:

 searching a virtual folder crashes dovecot quite often. I'm using dovecot 
 2.2.12. Here's the backtrace:
 
 #5  0x7fc1d6774ed9 in level_scores_add_vuids (br=0x2413ab8, 
 level=0x1c0c2e0, vbox=0x170c950) at fts-search.c:81

http://hg.dovecot.org/dovecot-2.2/rev/d63b209737be should fix this.

[Dovecot] crash while fts searching a virtual folder

[Matthias Rieber]

Hi,

searching a virtual folder crashes dovecot quite often. I'm using 
dovecot 2.2.12. Here's the backtrace:


[New LWP 28245]
[Thread debugging using libthread_db enabled]
Using host libthread_db library 
/lib/x86_64-linux-gnu/libthread_db.so.1.

Core was generated by `dovecot/imap'.
Program terminated with signal 6, Aborted.
#0  0x7fc1d73f4425 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#0  0x7fc1d73f4425 in raise () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#1  0x7fc1d73f7b8b in abort () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#2  0x7fc1d77e6d45 in default_fatal_finish (type=optimized out, 
status=0) at failures.c:193
backtrace = 0x1cdc318 
/usr/local/lib/dovecot/libdovecot.so.0(+0x68d4f) [0x7fc1d77e6d4f] - 
/usr/local/lib/dovecot/libdovecot.so.0(+0x68dae) [0x7fc1d77e6dae] - 
/usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fc1d77a0...
#3  0x7fc1d77e6dae in i_internal_fatal_handler (ctx=0x7fff86d4b2d0, 
format=optimized out, args=optimized out) at failures.c:657

status = 0
#4  0x7fc1d77a03b9 in i_panic (format=optimized out) at 
failures.c:267

ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp = 0x0}
args = {{gp_offset = 40, fp_offset = 48, overflow_arg_area = 
0x7fff86d4b3a0, reg_save_area = 0x7fff86d4b2e0}}
#5  0x7fc1d6774ed9 in level_scores_add_vuids (br=0x2413ab8, 
level=0x1c0c2e0, vbox=0x170c950) at fts-search.c:81

i = optimized out
count = 234
backend_uids = {arr = {buffer = 0x1cdbe90, element_size = 8}, v 
= 0x1cdbe90, v_modifiable = 0x1cdbe90}
vuids_arr = {arr = {buffer = 0x1cdba98, element_size = 4}, v = 
0x1cdba98, v_modifiable = 0x1cdba98}

vuids = 0xea
scores = 0x23c8f50
score = 0xea
#6  multi_add_lookup_result (args=0x1bbb220, level=0x1c0c2e0, 
fctx=0x18c2240, result=optimized out) at fts-search.c:146

br = 0x2413ab8
vbox = 0x170c950
vuids = {arr = {buffer = 0x16dbe70, element_size = 8}, v = 
0x16dbe70, v_modifiable = 0x16dbe70}

orig_size = optimized out
i = optimized out
#7  fts_search_lookup_level_multi (and_args=true, args=0x1bbb220, 
fctx=0x18c2240) at fts-search.c:194
mailboxes_arr = {arr = {buffer = 0x1e0a580, element_size = 8}, v 
= 0x1e0a580, v_modifiable = 0x1e0a580}

backend = optimized out
j = 60
vbox = optimized out
mailboxes = 0x1e0a5b8
level = 0x1c0c2e0
result = {pool = 0x1e0a560, box_results = 0x2413838}
i = optimized out
mailbox_count = 60
#8  fts_search_lookup_level (fctx=0x18c2240, args=0x1bbb220, 
and_args=true) at fts-search.c:208

_data_stack_cur_id = 4
ret = optimized out
#9  0x7fc1d6774f86 in fts_search_lookup (fctx=optimized out) at 
fts-search.c:354

last_uid = 32653
seq1 = 0
seq2 = 0
__FUNCTION__ = fts_search_lookup
#10 0x7fc1d6776388 in fts_mailbox_search_init (t=optimized out, 
args=0x1bbb160, sort_program=optimized out, wanted_fields=0, 
wanted_headers=0x0) at fts-storage.c:207

ft = 0x1d4be20
fbox = optimized out
flist = 0x1706610
ctx = 0x192f540
fctx = 0x18c2240
#11 0x0041caa0 in imap_search_start (ctx=0x170a238, 
sargs=0x1bbb160, sort_program=0x0) at imap-search.c:576

cmd = 0x170a130
__FUNCTION__ = imap_search_start
#12 0x004117b6 in cmd_search (cmd=0x170a130) at cmd-search.c:48
ctx = 0x170a238
sargs = 0x1bbb160
args = 0x16e2a38
charset = 0x424d0b UTF-8
ret = optimized out
#13 0x0041734d in command_exec (cmd=0x170a130) at 
imap-commands.c:158

hook = 0x16e00f0
ret = optimized out
#14 0x004163e0 in client_command_input (cmd=0x170a130) at 
imap-client.c:780

client = 0x17095e0
command = optimized out
__FUNCTION__ = client_command_input
#15 0x004164c5 in client_command_input (cmd=0x170a130) at 
imap-client.c:841

client = 0x17095e0
command = optimized out
__FUNCTION__ = client_command_input
#16 0x0041676d in client_handle_next_command 
(remove_io_r=synthetic pointer, client=0x17095e0) at imap-client.c:879

No locals.
#17 client_handle_input (client=0x17095e0) at imap-client.c:891
_data_stack_cur_id = 3
ret = 48
remove_io = false
handled_commands = false
__FUNCTION__ = client_handle_input
#18 0x00416ae2 in client_input (client=0x17095e0) at 
imap-client.c:933

cmd = optimized out
output = 0x1709ff0
bytes = 26
__FUNCTION__ = client_input
#19 0x7fc1d77f7616 in io_loop_call_io (io=0x17071a0) at ioloop.c:388
ioloop = 0x16df730
t_id = 2
#20 0x7fc1d77f84cf in io_loop_handler_run (ioloop=optimized out) 
at ioloop-epoll.c:220

ctx = 0x16e03d0
events = 0x0
event = 0x16e1230

Re: [Dovecot] Crash in pop3 with version 2.2.12

[Axel Luttgens]

Le 28 mars 2014 à 17:12, Urban Loesch a écrit :

 Hi,
 
 thanks for your fast help.
 Now pop3 works again without error.
 
 Thanks
 Urban
 
 
 Am 28.03.2014 15:03, schrieb Teemu Huovila:
 Thats my bad. This commit should fix it 
 http://hg.dovecot.org/dovecot-2.2/rev/b0359910ec96. Thanks for reporting it.
 
 Teemu Huovila


Hello,

I'm still wondering... under which circumstances could the crash occur?

Trying here to reproduce it with an unpatched 2.2.12, without success: LIST 
and UIDL always return consistent results, without crashes, and behave that way 
on several mailboxes.

I'm asking, because the problem could thus be tied to some 
configurations/settings only (as Urban wrote: I saw some people on the list 
[...]); but the correction brought by b0359910ec96 is an unconditional one.

On the other hand, the problem might be raised because of some particular 
combination of circumstances, which I can't reproduce now, but which I could 
face one day or another...

Hence the question: to patch or not to patch?

Many thanks in advance,
Axel

Re: [Dovecot] Crash in pop3 with version 2.2.12

[Nikolaos Milas]

On 4/4/2014 11:18 πμ, Axel Luttgens wrote:


I'm still wondering... under which circumstances could the crash occur?


I was wondering the same thing. We are now running 2.2.12 in production 
for two weeks (unpatched) and we have not seen such an error (despite 
extensive use of POP3).


Regards,
Nick

Re: [Dovecot] Crash in pop3 with version 2.2.12

[Teemu Huovila]

Hello

On 04/04/2014 11:18 AM, Axel Luttgens wrote:
 I'm still wondering... under which circumstances could the crash occur?
This issue occurs whenever the function 
src/pop3/pop3-commands.c:client_uidls_save() is called.
The function is called when:

The pop3 internal structure client-message_uidls_save is 1. This in turn 
happens when any of these is true:
1. pop3 logoutformat has %u
2. config setting pop3_uidl_duplicates is not the default allow
3. config setting pop3_save_uidl=yes

The problem manifests in two different ways.
1) When the zlib plugin is active the executable crashed due to a segmentation 
fault.
2) If there is no zlib, the data returned by the UIDL command is off-by-one 
and the last data item is null.

Without zlib the error might look something like this:
C:uidl
S:+OK
S:1 0002533553b6
S:2 0003533553b6
S:3 0004533553b6
S:4 0005533553b6
S:5 0006533553b6
S:6 (null)
S:.

 Hence the question: to patch or not to patch?
Patch, if your setup will need to meet any of the three criteria triggering the 
issue, before 2.2.13 is released.

br,
Teemu Huovila

Re: [Dovecot] Crash in pop3 with version 2.2.12

[Axel Luttgens]

Le 4 avr. 2014 à 10:37, Teemu Huovila a écrit :

 Hello
 
 On 04/04/2014 11:18 AM, Axel Luttgens wrote:
 I'm still wondering... under which circumstances could the crash occur?
 This issue occurs whenever the function 
 src/pop3/pop3-commands.c:client_uidls_save() is called.
 The function is called when:
 
 The pop3 internal structure client-message_uidls_save is 1. This in turn 
 happens when any of these is true:
 1. pop3 logoutformat has %u
 2. config setting pop3_uidl_duplicates is not the default allow
 3. config setting pop3_save_uidl=yes
 
 The problem manifests in two different ways.
 1) When the zlib plugin is active the executable crashed due to a 
 segmentation fault.
 2) If there is no zlib, the data returned by the UIDL command is off-by-one 
 and the last data item is null.
 
 Without zlib the error might look something like this:
 C:uidl
 S:+OK
 S:1 0002533553b6
 S:2 0003533553b6
 S:3 0004533553b6
 S:4 0005533553b6
 S:5 0006533553b6
 S:6 (null)
 S:.
 
 Hence the question: to patch or not to patch?
 Patch, if your setup will need to meet any of the three criteria triggering 
 the issue, before 2.2.13 is released.

Hello Teemu,

Thank you very much for your kind and very detailed explanation.

None of 1. to 3. apply here, so I guess I've just been lucky.
On the other hand, I didn't notice that the patch applies to a very precise 
context (the client_uidls_save function); it should thus be safe to apply it in 
all cases (even if un-needed with some *current* configuration).

Sincerely,
Axel

[Dovecot] Crash in pop3 with version 2.2.12

[Urban Loesch]

Hi,

today I upgraded to version 2.2.12 under Debian Squeeze.
I saw some people on the list they had the same problems with version 2.2.11, 
but which should have been fixed in version 2.2.12.

My logfile shows:

..
Mar 28 08:25:01 mailstore dovecot: pop3-login: Login: user=u...@domain.net, 
method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=34568, secured,
session=Jp6RmaX1YAB/AAAB
Mar 28 08:25:06 mailstore dovecot: pop3(u...@domain.net pid:34568 
session:Jp6RmaX1YAB/AAAB): Fatal: master: service(pop3): child 34568 killed 
with
signal 11 (core dumped)
...

I made some more dubugging and I found that the pop3 process crashed on the 
uidl command.
Here my output from telnet session:

..
root@mailstore: #  telnet localhost 110
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
+OK Dovecot ready.
user u...@domain.net
+OK
pass PASS
+OK Logged in.
list
+OK 5 messages:
1 3492
2 21924
3 3525
4 3472
5 3273
.
uidl
Connection closed by foreign host.
...

Listing massages or retrieving messages works normally. Only on uidl command 
the services crashes.

I made a backtrace.

- start backtrace -
Core was generated by `dovecot/pop3'.
Program terminated with signal 11, Segmentation fault.
#0  0x7f9dd8ca488d in vfprintf () from /lib/libc.so.6
(gdb) bt full
#0  0x7f9dd8ca488d in vfprintf () from /lib/libc.so.6
No symbol table info available.
#1  0x7f9dd8cc6732 in vsnprintf () from /lib/libc.so.6
No symbol table info available.
#2  0x7f9dd904d0db in str_vprintfa (str=0x11aa4f8, fmt=0x409184 %u %s, 
args=0x7ab4fff0) at str.c:155
args2 = {{gp_offset = 16, fp_offset = 48, overflow_arg_area = 
0x7ab500e0, reg_save_area = 0x7ab50010}}
init_size = 4231558
pos = 0
ret = value optimized out
ret2 = value optimized out
__FUNCTION__ = str_vprintfa
#3  0x004055ff in client_send_line (client=0x11d1e50, fmt=value 
optimized out) at pop3-client.c:678
str = 0x11aa4f8
_data_stack_cur_id = 4
va = {{gp_offset = 32, fp_offset = 48, overflow_arg_area = 
0x7ab500e0, reg_save_area = 0x7ab50010}}
ret = value optimized out
__FUNCTION__ = client_send_line
#4  0x004073cd in list_uidls_saved_iter (client=0x11d1e50, 
ctx=0x11da3c0) at pop3-commands.c:666
found = true
#5  list_uids_iter (client=0x11d1e50, ctx=0x11da3c0) at pop3-commands.c:693
str = value optimized out
permanent_uidl = value optimized out
found = value optimized out
failed = value optimized out
#6  0x00407d88 in cmd_uidl (client=0x11d1e50, name=value optimized 
out, args=0x408880 ) at pop3-commands.c:874
ctx = 0x0
seq = value optimized out
#7  client_command_execute (client=0x11d1e50, name=value optimized out, 
args=0x408880 ) at pop3-commands.c:938
No locals.
#8  0x00405870 in client_handle_input (client=0x11d1e50) at 
pop3-client.c:739
_data_stack_cur_id = 3
line = value optimized out
args = 0x408880 
ret = value optimized out
#9  0x7f9dd903c3d6 in io_loop_call_io (io=0x11d2760) at ioloop.c:388
ioloop = 0x11b2740
t_id = 2
#10 0x7f9dd903d45f in io_loop_handler_run (ioloop=value optimized out) at 
ioloop-epoll.c:220
ctx = 0x11b2aa0
event = 0x11b3900
list = 0x11b44d0
io = 0x51
tv = {tv_sec = 9, tv_usec = 999326}
msecs = value optimized out
ret = 1
i = 0
call = false
__FUNCTION__ = io_loop_handler_run
#11 0x7f9dd903c348 in io_loop_run (ioloop=0x11b2740) at ioloop.c:412
__FUNCTION__ = io_loop_run
#12 0x7f9dd8fea953 in master_service_run (service=0x11b25d0, 
callback=0x409186) at master-service.c:566
No locals.
#13 0x00404ac7 in main (argc=1, argv=0x11b2390) at main.c:277
set_roots = {0x4094e0, 0x0}
login_set = {auth_socket_path = 0x11aa050 
/var/run/dovecot/auth-master, postlogin_socket_path = 0x0, 
postlogin_timeout_secs = 60, callback =
0x404ca0 login_client_connected,
  failure_callback = 0x404c50 login_client_failed, request_auth_token 
= 0}
service_flags = value optimized out
storage_service_flags = MAIL_STORAGE_SERVICE_FLAG_DISALLOW_ROOT
username = 0x0
c = value optimized out
(gdb) quit
- end backtrace -

And at least my pop3 configuration part:

- start config -
protocol pop3 {
  mail_plugins =  quota mail_log notify acl zlib stats
  pop3_client_workarounds = outlook-no-nuls oe-ns-eoh
  pop3_lock_session = yes
  pop3_logout_format = bytes_sent=%o top=%t/%p, retr=%r/%b, del=%d/%m, size=%s 
uidl_hash=%u session=%{session}
  pop3_reuse_xuidl = yes
}
- end config -

Setting pop3_reuse_xuidl = no has noe effect. Always the same crash.

Thanks and regards
Urban Loesch

Re: [Dovecot] Crash in pop3 with version 2.2.12

[Teemu Huovila]

Thats my bad. This commit should fix it 
http://hg.dovecot.org/dovecot-2.2/rev/b0359910ec96. Thanks for reporting it.

Teemu Huovila

Re: [Dovecot] Crash in pop3 with version 2.2.12

[Urban Loesch]

Hi,

thanks for your fast help.
Now pop3 works again without error.

Thanks
Urban


Am 28.03.2014 15:03, schrieb Teemu Huovila:
 Thats my bad. This commit should fix it 
 http://hg.dovecot.org/dovecot-2.2/rev/b0359910ec96. Thanks for reporting it.
 
 Teemu Huovila
 

Re: [Dovecot] Crash in pop3 with recent dovecot, backtrace

[Leo]

Sorry - my fault!
 
I downloaded it on thursday (version 2.2.11 was released the day before
and it was the latest version at this time) but installed it on friday.
Then I had the problems and found this thread on Google. Unfortunately I
did not double check the download page and even did not notice the
announcement of 2.2.12 here on the list. I very much apologize ...
 
However many thanks for your quick replies!
 
Regards,
Leo


On 02/14/2014 09:38 PM, Reindl Harald wrote:

 Am 14.02.2014 18:22, schrieb Leo:
 I have the same crashes in pop3 with the recent dovecot release 2.2.11
 it is not the recent and because the pop3 problems 2.2.12 was already released

 as always:
 look on the download page for the current version before
 report problems possibly already solved

Re: [Dovecot] Crash in pop3 with recent dovecot, backtrace

[Leo]

Hi,

I have the same crashes in pop3 with the recent dovecot release 2.2.11
on Fedora 16 x86_64. The log file shows:

dovecot: pop3(usern...@example.com): Fatal: master: service(pop3): child
26735 killed with signal 11 (core dumped)

New mails will be successfully fetched by the client but all the dovecot
files in the users maildir (dovecot.index.log, dovecot.index.cache, ...)
are not being updated anymore.

Here is my backtrace:

- start backtrace -

Reading symbols from /usr/local/libexec/dovecot/pop3...done.
[New LWP 26735]
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib64/libthread_db.so.1.
Core was generated by `dovecot/pop3'.
Program terminated with signal 11, Segmentation fault.
#0  client_update_mails (client=0x2388560) at pop3-commands.c:256
256
seq_range_array_add(deleted_msgs, client-msgnum_to_seq_map[msgnum]);
(gdb) bt full
#0  client_update_mails (client=0x2388560) at pop3-commands.c:256
search_args = optimized out
ctx = optimized out
mail = 0x7fb36483ac5d
deleted_msgs = {arr = {buffer = 0x236c088, element_size = 8}, v
= 0x236c088, v_modifiable = 0x236c088}
seen_msgs = {arr = {buffer = 0x237765a, element_size =
140408462221679}, v = 0x237765a,
  v_modifiable = 0x237765a}
msgnum = optimized out
bit = 1
#1  0x00407800 in cmd_quit (args=optimized out,
client=0x2388560) at pop3-commands.c:289
No locals.
#2  client_command_execute (client=0x2388560, name=optimized out,
args=0x408200 ) at pop3-commands.c:920
No locals.
#3  0x00405fb8 in client_handle_input (client=0x2388560) at
pop3-client.c:739
_data_stack_cur_id = 3
line = 0x237765a QUIT
args = optimized out
ret = optimized out
#4  0x7fb364828e06 in io_loop_call_io (io=0x2388d10) at ioloop.c:388
ioloop = 0x2374730
t_id = 2
#5  0x7fb364829c9f in io_loop_handler_run (ioloop=optimized out)
at ioloop-epoll.c:220
ctx = 0x2374a90
events = 0x0
event = 0x23758f0
list = 0x23764c0
io = optimized out
tv = {tv_sec = 9, tv_usec = 999836}
events_count = optimized out
msecs = optimized out
ret = 1
i = optimized out
call = optimized out
__FUNCTION__ = io_loop_handler_run
#6  0x7fb364828918 in io_loop_run (ioloop=0x2374730) at ioloop.c:412
__FUNCTION__ = io_loop_run
#7  0x7fb3647d7533 in master_service_run (service=0x23745c0,
callback=optimized out) at master-service.c:566
No locals.
#8  0x004041f7 in main (argc=1, argv=0x2374390) at main.c:277
set_roots = {0x408e60, 0x0}
login_set = {auth_socket_path = 0x236c048
/run/dovecot/auth-master, postlogin_socket_path = 0x0,
  postlogin_timeout_secs = 60, callback = 0x4045e0
login_client_connected,
  failure_callback = 0x404590 login_client_failed,
request_auth_token = 0}
service_flags = optimized out
storage_service_flags = optimized out
username = optimized out
c = optimized out
(gdb)

- end backtrace -

Kind regards,
Leo

Re: [Dovecot] Crash in pop3 with recent dovecot, backtrace

[Robert Schetterer]

Am 14.02.2014 18:22, schrieb Leo:
 I have the same crashes in pop3 with the recent dovecot release 2.2.11

go vers 2.2.12


Best Regards
MfG Robert Schetterer

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein

Re: [Dovecot] Crash in pop3 with recent dovecot, backtrace

[Reindl Harald]

Am 14.02.2014 18:22, schrieb Leo:
 I have the same crashes in pop3 with the recent dovecot release 2.2.11

it is not the recent and because the pop3 problems 2.2.12 was already released

as always:
look on the download page for the current version before
report problems possibly already solved



signature.asc
Description: OpenPGP digital signature

[Dovecot] Crash in pop3 with recent dovecot, backtrace

[Ralf Hildebrandt]

Core was generated by `dovecot/pop3'.
Program terminated with signal 11, Segmentation fault.
#0  0x0804eb6a in client_update_mails (client=client@entry=0x8afd7a8)
at pop3-commands.c:256
256 seq_range_array_add(deleted_msgs, 
client-msgnum_to_seq_map[msgnum]);
#0  0x0804eb6a in client_update_mails (client=client@entry=0x8afd7a8)
at pop3-commands.c:256
search_args = optimized out
ctx = optimized out
mail = 0xb762d797
deleted_msgs = {arr = {buffer = 0x8ade098, element_size = 8}, 
  v = 0x8ade098, v_modifiable = 0x8ade098}
seen_msgs = {arr = {buffer = 0xb7671224, element_size = 3076604219}, 
  v = 0xb7671224, v_modifiable = 0xb7671224}
msgnum = optimized out
bit = 1
#1  0x0804ee80 in cmd_quit (client=0x8afd7a8, args=optimized out)
at pop3-commands.c:289
No locals.
#2  client_command_execute (client=client@entry=0x8afd7a8, 
name=optimized out, name@entry=0x8b3e194 QUIT, 
args=args@entry=0x804f839 ) at pop3-commands.c:920
No locals.
#3  0x0804d5f1 in client_handle_input (client=0x8afd7a8) at pop3-client.c:739
_data_stack_cur_id = 3
line = 0x8b3e194 QUIT
args = optimized out
ret = optimized out
#4  0xb7618d44 in io_loop_call_io (io=0x8afca88) at ioloop.c:388
ioloop = 0x8ae6498
t_id = 2
#5  0xb7619e0e in io_loop_handler_run (ioloop=ioloop@entry=0x8ae6498)
at ioloop-epoll.c:220
ctx = 0x8ae7180
events = 0x0
event = 0x8ae71c0
list = 0x8ae7aa8
io = optimized out
tv = {tv_sec = 9, tv_usec = 999871}
events_count = 0
msecs = optimized out
ret = 1
i = optimized out
j = optimized out
call = optimized out
__FUNCTION__ = io_loop_handler_run
#6  0xb76187d8 in io_loop_run (ioloop=0x8ae6498) at ioloop.c:412
__FUNCTION__ = io_loop_run
#7  0xb75bdd7e in master_service_run (service=0x8ae63c0, 
callback=callback@entry=0x804b940 client_connected)
at master-service.c:566
No locals.
#8  0x0804bd05 in main (argc=1, argv=0x8ae61e0) at main.c:277
set_roots = {0x80504c0, 0x0}
login_set = {
  auth_socket_path = 0x8ade048 
/usr/local/dovecot-2.2/var/run/dovecot/auth-master, postlogin_socket_path = 
0x0, postlogin_timeout_secs = 60, 
  callback = 0x804b800 login_client_connected, 
  failure_callback = 0x804b7c0 login_client_failed, 
  request_auth_token = 0}
service_flags = optimized out
storage_service_flags = optimized out
username = 0x0
c = optimized out

-- 
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

[Dovecot] Crash in recent dovecot, different line (with Backtrace:dovecot/pop3)

[Ralf Hildebrandt]

Reading symbols from /usr/local/dovecot-2.2/libexec/dovecot/pop3...done.
[New LWP 17294]
[Thread debugging using libthread_db enabled]
Using host libthread_db library 
/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1.
Core was generated by `dovecot/pop3'.
Program terminated with signal 11, Segmentation fault.
#0  0x0804eb6a in client_update_mails (client=client@entry=0x82017a0)
at pop3-commands.c:256
256 ret = FALSE;
#0  0x0804eb6a in client_update_mails (client=client@entry=0x82017a0)
at pop3-commands.c:256
search_args = optimized out
ctx = optimized out
mail = 0xb759a797
deleted_msgs = {arr = {buffer = 0x81e2098, element_size = 8}, 
  v = 0x81e2098, v_modifiable = 0x81e2098}
seen_msgs = {arr = {buffer = 0xb75de224, element_size = 3076002107}, 
  v = 0xb75de224, v_modifiable = 0xb75de224}
msgnum = optimized out
bit = 1
#1  0x0804ee80 in cmd_quit (client=0x82017a0, args=optimized out)
at pop3-commands.c:289
No locals.
#2  client_command_execute (client=client@entry=0x82017a0, 
name=optimized out, name@entry=0x823e08c QUIT, 
args=args@entry=0x804f839 ) at pop3-commands.c:920
No locals.
#3  0x0804d5f1 in client_handle_input (client=0x82017a0) at pop3-client.c:739
_data_stack_cur_id = 3
line = 0x823e08c QUIT
args = optimized out
ret = optimized out
#4  0xb7585d44 in io_loop_call_io (io=0x8200a80) at ioloop.c:388
ioloop = 0x81ea490
t_id = 2
#5  0xb7586e0e in io_loop_handler_run (ioloop=ioloop@entry=0x81ea490)
at ioloop-epoll.c:220
ctx = 0x81eb178
events = 0x0
event = 0x81eb1b8
list = 0x81ebaa0
io = optimized out
tv = {tv_sec = 9, tv_usec = 999652}
events_count = 0
msecs = optimized out
ret = 1
i = optimized out
j = optimized out
call = optimized out
__FUNCTION__ = io_loop_handler_run
#6  0xb75857d8 in io_loop_run (ioloop=0x81ea490) at ioloop.c:412
__FUNCTION__ = io_loop_run
#7  0xb752ad7e in master_service_run (service=0x81ea3b8, 
callback=callback@entry=0x804b940 client_connected)
at master-service.c:566
No locals.
#8  0x0804bd05 in main (argc=1, argv=0x81ea1e0) at main.c:277
set_roots = {0x80504c0, 0x0}
login_set = {
  auth_socket_path = 0x81e2048 
/usr/local/dovecot-2.2/var/run/dovecot/auth-master, postlogin_socket_path = 
0x0, postlogin_timeout_secs = 60, 
  callback = 0x804b800 login_client_connected, 
  failure_callback = 0x804b7c0 login_client_failed, 
  request_auth_token = 0}
service_flags = optimized out
storage_service_flags = optimized out
username = 0x0
c = optimized out

-- 
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] Crash in recent dovecot, different line (with Backtrace:dovecot/pop3)

[Birta Levente]

On 12/02/2014 11:26, Ralf Hildebrandt wrote:
 


Sorry, I didn't do this before. Hope is ok. Here is mine:

Reading symbols from /usr/libexec/dovecot/pop3...Reading symbols from
/usr/lib/debug/usr/libexec/dovecot/pop3.debug...done.
done.
[New Thread 19189]
Missing separate debuginfo for
Try: yum --disablerepo='*' --enablerepo='*-debug*' install
/usr/lib/debug/.build-id/8a/367167daa883546ca1ffeda543ce1ce919519b
Reading symbols from
/usr/lib64/dovecot/libdovecot-storage.so.0.0.0...Reading symbols from
/usr/lib/debug/usr/lib64/dovecot/libdovecot-storage.so.0.0.0.debug...done.
done.
Loaded symbols for /usr/lib64/dovecot/libdovecot-storage.so.0.0.0
Reading symbols from /usr/lib64/dovecot/libdovecot.so.0.0.0...Reading
symbols from
/usr/lib/debug/usr/lib64/dovecot/libdovecot.so.0.0.0.debug...done.
done.
Loaded symbols for /usr/lib64/dovecot/libdovecot.so.0.0.0
Reading symbols from /lib64/libc-2.12.so...Reading symbols from
/usr/lib/debug/lib64/libc-2.12.so.debug...done.
done.
Loaded symbols for /lib64/libc-2.12.so
Reading symbols from /lib64/librt-2.12.so...Reading symbols from
/usr/lib/debug/lib64/librt-2.12.so.debug...done.
done.
Loaded symbols for /lib64/librt-2.12.so
Reading symbols from /lib64/libdl-2.12.so...Reading symbols from
/usr/lib/debug/lib64/libdl-2.12.so.debug...done.
done.
Loaded symbols for /lib64/libdl-2.12.so
Reading symbols from /lib64/ld-2.12.so...Reading symbols from
/usr/lib/debug/lib64/ld-2.12.so.debug...done.
done.
Loaded symbols for /lib64/ld-2.12.so
Reading symbols from /lib64/libpthread-2.12.so...Reading symbols from
/usr/lib/debug/lib64/libpthread-2.12.so.debug...done.
[Thread debugging using libthread_db enabled]
done.
Loaded symbols for /lib64/libpthread-2.12.so
Core was generated by `dovecot/pop3'.
Program terminated with signal 11, Segmentation fault.
#0  client_update_mails (client=0x157b2b0) at pop3-commands.c:264
264 seq_range_array_add(seen_msgs,
client-msgnum_to_seq_map[msgnum]);
(gdb) bt full
#0  client_update_mails (client=0x157b2b0) at pop3-commands.c:264
search_args = value optimized out
ctx = value optimized out
mail = 0x156a66a
deleted_msgs = {arr = {buffer = 0x155f090, element_size = 8}, v
= 0x155f090, v_modifiable = 0x155f090}
seen_msgs = {arr = {buffer = 0x155f120, element_size = 8}, v =
0x155f120, v_modifiable = 0x155f120}
msgnum = value optimized out
bit = 2
#1  0x004079af in cmd_quit (client=0x157b2b0, name=value
optimized out, args=0x408340 ) at pop3-commands.c:289
No locals.
#2  client_command_execute (client=0x157b2b0, name=value optimized
out, args=0x408340 ) at pop3-commands.c:920
No locals.
#3  0x00405300 in client_handle_input (client=0x157b2b0) at
pop3-client.c:739
_data_stack_cur_id = 3
line = 0x156a66a QUIT
args = value optimized out
ret = value optimized out
#4  0x7f1cc2c67d56 in io_loop_call_io (io=0x157bbc0) at ioloop.c:388
ioloop = 0x1567740
t_id = 2
#5  0x7f1cc2c68e27 in io_loop_handler_run (ioloop=value optimized
out) at ioloop-epoll.c:220
ctx = 0x1567aa0
events = value optimized out
event = 0x1568900
list = 0x15694d0
io = value optimized out
tv = {tv_sec = 9, tv_usec = 999595}
msecs = value optimized out
ret = 1
i = value optimized out
call = value optimized out
__FUNCTION__ = io_loop_handler_run
#6  0x7f1cc2c67cc8 in io_loop_run (ioloop=0x1567740) at ioloop.c:412
__FUNCTION__ = io_loop_run
#7  0x7f1cc2c16023 in master_service_run (service=0x15675d0,
callback=value optimized out) at master-service.c:566
No locals.
#8  0x004046bb in main (argc=1, argv=0x1567390) at main.c:277
set_roots = {0x408fa0, 0x0}
login_set = {auth_socket_path = 0x155f050
/var/run/dovecot/auth-master, postlogin_socket_path = 0x0,
postlogin_timeout_secs = 60, callback = 0x4047f0
login_client_connected, failure_callback = 0x404310
login_client_failed, request_auth_token = 0}
service_flags = value optimized out
storage_service_flags = value optimized out
username = value optimized out
c = value optimized out







signature.asc
Description: OpenPGP digital signature

Re: [Dovecot] Crash in dovecot 2.2.6

[Timo Sirainen]

On 5.11.2013, at 10.26, Ed W li...@wildgooses.com wrote:

 Hi, I recently upgraded from a dovecot 2.1 version to 2.2.6.  I now have a 
 single user who occasionally triggers a crash (just this one user it 
 seems?).  The user connects via LiveMail (v14.0.8117.) and IMAP.
..
 Nov  5 06:08:43 mail1 dovecot: imap(u...@example.com): Panic: file 
 mail-index-transaction-export.c: line 203 (log_append_ext_hdr_update): 
 assertion failed: (u32.offset + u32.size = ext_hdr_size)

Is this still happening? The index file seems to be somehow corrupted. Is this 
still happening / did you already delete it? Would be useful to look at the 
index (and/or make it write core dump and gdb it).

Re: [Dovecot] Crash in dovecot 2.2.6

[Ed W]

On 02/11/2013 11:18, Timo Sirainen wrote:

On 29.10.2013, at 10.26, Ed W li...@wildgooses.com wrote:


Hi, I recently upgraded from a dovecot 2.1 version to 2.2.6.  I now have a 
single user who occasionally triggers a crash (just this one user it seems?).  
The user connects via LiveMail (v14.0.8117.) and IMAP.

Oct 29 08:05:26 mail1 dovecot: imap(custo...@example.org): Error: Raw backtrace: 
/usr/lib/dovecot/libdovecot.so.0(+0x6575a) [0xd94cc75a] - 
/usr/lib/dovecot/libdovecot.so.0(+0x657cb) [0xd94cc7cb] - 
/usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0xd9481991] - 
/usr/lib/dovecot/libdovecot

There was an assert error message logged before this raw backtrace. What is it?



I'm sorry, yes of course there is.  Sorry, tunnel vision:

Samples:

Nov  5 06:08:43 mail1 dovecot: imap(u...@example.com): Panic: file 
mail-index-transaction-export.c: line 203 (log_append_ext_hdr_update): 
assertion failed: (u32.offset + u32.size = ext_hdr_size)
Nov  5 06:13:21 mail1 dovecot: imap(u...@example.com): Panic: file 
mail-index-transaction-export.c: line 203 (log_append_ext_hdr_update): 
assertion failed: (u32.offset + u32.size = ext_hdr_size)
Nov  5 07:50:59 mail1 dovecot: imap(u...@example.com): Panic: file 
mail-index-transaction-export.c: line 203 (log_append_ext_hdr_update): 
assertion failed: (u32.offset + u32.size = ext_hdr_size)
Nov  5 07:55:23 mail1 dovecot: imap(u...@example.com): Panic: file 
mail-index-transaction-export.c: line 203 (log_append_ext_hdr_update): 
assertion failed: (u32.offset + u32.size = ext_hdr_size)


Thanks

Ed W

Re: [Dovecot] Crash in dovecot 2.2.6

[Timo Sirainen]

On 29.10.2013, at 10.26, Ed W li...@wildgooses.com wrote:

 Hi, I recently upgraded from a dovecot 2.1 version to 2.2.6.  I now have a 
 single user who occasionally triggers a crash (just this one user it seems?). 
  The user connects via LiveMail (v14.0.8117.) and IMAP.
 
 Oct 29 08:05:26 mail1 dovecot: imap(custo...@example.org): Error: Raw 
 backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x6575a) [0xd94cc75a] - 
 /usr/lib/dovecot/libdovecot.so.0(+0x657cb) [0xd94cc7cb] - 
 /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0xd9481991] - 
 /usr/lib/dovecot/libdovecot

There was an assert error message logged before this raw backtrace. What is it?

Re: [Dovecot] crash/mem violation in auth_worker + 50G logs in 2.1.7

[Mrten]

On 13/6/2013 05:11 , Timo Sirainen wrote:

 Looks like there was a generic problem with how crash during
 initialization was handled. This should fix all of them:
 http://hg.dovecot.org/dovecot-2.2/rev/754d244b8249

OK, thanks for the fix!

M.

Re: [Dovecot] crash/mem violation in auth_worker + 50G logs in 2.1.7

[Timo Sirainen]

On Sat, 2013-06-08 at 13:27 +0200, Mrten wrote:
 Hi,
 
 This morning I discovered what seemed to be a deliberate crash in
 auth_worker:
 
 Jun  7 23:02:09 localhost dovecot: auth-worker: Error: #007Can't read
 dir of '/etc/mysql/conf.d/' (Errcode: 2)
 Jun  7 23:02:09 localhost dovecot: auth-worker: Error: Fatal error in
 defaults handling. Program aborted
 Jun  7 23:02:09 localhost dovecot: auth-worker: Error: *** glibc
 detected *** dovecot/auth worker: waiting for connection: free():
 invalid pointer: 0x7fffa0863160 ***
..
 /usr/lib/libmysqlclient.so.18(free_defaults+0x4b)[0x7f22d3796e6b]
 Jun  7 23:02:09 localhost dovecot: auth-worker: Error:
 /usr/lib/libmysqlclient.so.18(mysql_read_default_options+0x13c)[0x7f22d377d00c]
 Jun  7 23:02:09 localhost dovecot: auth-worker: Error:
 /usr/lib/libmysqlclient.so.18(mysql_real_connect+0x8e)[0x7f22d377eb4e]

It crashes in mysql_real_connect() internally, which also starts the
whole mysql session. So this is a bug in MySQL library.

 This repeated until I killed dovecot (12 hours later), by then 54GB of
 logs had accumulated. Besides leaving me impressed with the logserver
 :), I was wondering if this is a known problem.
 
 Shouldn't dovecot recognize that the auth worker is crashing?

Looks like there was a generic problem with how crash during
initialization was handled. This should fix all of them:
http://hg.dovecot.org/dovecot-2.2/rev/754d244b8249

 One more thing, this is (one line from many) from audit.log (I have
 auditd logging audit records)
 
 type=ANOM_ABEND msg=audit(1370682566.377:3499876): auid=4294967295
 uid=108 gid=115 ses=4294967295 pid=23187 comm=auth reason=memory
 violation sig=6
 
 108 is the dovecot user, so it probably is related.

Yeah, that's the same abort() crash.

[Dovecot] crash/mem violation in auth_worker + 50G logs in 2.1.7

[Mrten]

Hi,

This morning I discovered what seemed to be a deliberate crash in
auth_worker:

Jun  7 23:02:09 localhost dovecot: auth-worker: Error: #007Can't read
dir of '/etc/mysql/conf.d/' (Errcode: 2)
Jun  7 23:02:09 localhost dovecot: auth-worker: Error: Fatal error in
defaults handling. Program aborted
Jun  7 23:02:09 localhost dovecot: auth-worker: Error: *** glibc
detected *** dovecot/auth worker: waiting for connection: free():
invalid pointer: 0x7fffa0863160 ***
Jun  7 23:02:09 localhost dovecot: auth-worker: Error: ===
Backtrace: =
Jun  7 23:02:09 localhost dovecot: auth-worker: Error:
/lib/x86_64-linux-gnu/libc.so.6(+0x7eb96)[0x7f22d42f9b96]
Jun  7 23:02:09 localhost dovecot: auth-worker: Error:
/usr/lib/libmysqlclient.so.18(free_root+0x90)[0x7f22d37988c0]
Jun  7 23:02:09 localhost dovecot: auth-worker: Error:
/usr/lib/libmysqlclient.so.18(free_defaults+0x4b)[0x7f22d3796e6b]
Jun  7 23:02:09 localhost dovecot: auth-worker: Error:
/usr/lib/libmysqlclient.so.18(mysql_read_default_options+0x13c)[0x7f22d377d00c]
Jun  7 23:02:09 localhost dovecot: auth-worker: Error:
/usr/lib/libmysqlclient.so.18(mysql_real_connect+0x8e)[0x7f22d377eb4e]
Jun  7 23:02:09 localhost dovecot: auth-worker: Error:
/usr/lib/dovecot/modules/auth/libdriver_mysql.so(+0x1fc6)[0x7f22d3c52fc6]
Jun  7 23:02:09 localhost dovecot: auth-worker: Error: dovecot/auth
worker: waiting for connection(+0x2be1d)[0x7f22d515be1d]
Jun  7 23:02:09 localhost dovecot: auth-worker: Error: dovecot/auth
worker: waiting for connection(db_sql_connect+0xd)[0x7f22d514aedd]
Jun  7 23:02:09 localhost dovecot: auth-worker: Error: dovecot/auth
worker: waiting for connection(+0x23d70)[0x7f22d5153d70]
Jun  7 23:02:09 localhost dovecot: auth-worker: Error: dovecot/auth
worker: waiting for connection(passdb_init+0x2a)[0x7f22d515158a]
Jun  7 23:02:09 localhost dovecot: auth-worker: Error: dovecot/auth
worker: waiting for connection(auths_init+0x59)[0x7f22d513dfe9]
Jun  7 23:02:09 localhost dovecot: auth-worker: Error: dovecot/auth
worker: waiting for connection(main+0x345)[0x7f22d513d5f5]
Jun  7 23:02:09 localhost dovecot: auth-worker: Error:
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7f22d429c76d]
Jun  7 23:02:09 localhost dovecot: auth-worker: Error: dovecot/auth
worker: waiting for connection(+0xd7d9)[0x7f22d513d7d9]

There follows a memory map but I snipped that.

This repeated until I killed dovecot (12 hours later), by then 54GB of
logs had accumulated. Besides leaving me impressed with the logserver
:), I was wondering if this is a known problem.



I don't know what triggered this at 23:02 (shown above is the first set
of problem logentries). Can't really have been an upgrade, since I
backported the raring dovecot Ubuntu package for my precise server, no
automated upgrades there.

I did go look for the /etc/mysql/conf.d directory mentioned, it wasn't
there, but there was a /etc/mysql/my.cnf trying to !includedir it. Since
there is no mysql on the server besides libmysqlclient I removed the
directory and haven't seen the problem return yet. Sounds like the
reason for happening, however, the memory error after that probably
warrants research?

If it is in libmysqlclient, that's another non-default snag because
that's the lib I get from Percona, not the Ubuntu default one.

Shouldn't dovecot recognize that the auth worker is crashing?


One more thing, this is (one line from many) from audit.log (I have
auditd logging audit records)

type=ANOM_ABEND msg=audit(1370682566.377:3499876): auid=4294967295
uid=108 gid=115 ses=4294967295 pid=23187 comm=auth reason=memory
violation sig=6

108 is the dovecot user, so it probably is related.

I realise I'm way off defaults here but I wanted to report anyway.


(dovecot -n attached)

thanks for any insight,
Maarten.
# 2.1.7: /etc/dovecot/dovecot.conf
# OS: Linux 3.2.0-43-virtual x86_64 Ubuntu 12.04.2 LTS
auth_cache_negative_ttl = 0
auth_cache_size = 10 M
auth_cache_ttl = 5 mins
auth_failure_delay = 3 secs
auth_username_chars = 
abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-@
disable_plaintext_auth = no
log_timestamp = %Y-%m-%d %H:%M:%S 
mail_save_crlf = yes
maildir_stat_dirs = yes
namespace inbox {
  inbox = yes
  location =
  mailbox Drafts {
special_use = \Drafts
  }
  mailbox Junk {
special_use = \Junk
  }
  mailbox Sent {
special_use = \Sent
  }
  mailbox Sent Messages {
special_use = \Sent
  }
  mailbox Trash {
special_use = \Trash
  }
  prefix =
}
passdb {
  args = /etc/dovecot/extra/dovecot-sql.conf.ext
  driver = sql
}
plugin {
  fts = squat
  quota = maildir:User quota
  quota_rule = *:bytes=10G
  quota_rule2 = Trash:bytes=+100M
  trash = /etc/dovecot/conf.d/trash
  var_domainpart = %d
  var_remote = %r
  var_service = %Ls
  var_user = %u
  var_userpart = %n
}
protocols = imap pop3
service auth-worker {
  user = $default_internal_user
}
service auth {
  unix_listener /var/spool/exim4/private/auth {
mode = 0660
  }
  unix_listener auth-userdb {

[Dovecot] Crash dovecot 1.2.15

[ib]

inline: logo-ice-dev.gif

Re: [Dovecot] Crash dovecot 1.2.15

[Benny Pedersen]

ib skrev den 2013-06-05 10:38:

Jun 05 06:26:01 dovecot: Warning: SIGHUP received - reloading 
configuration

Jun 05 06:26:02 dovecot: Error: Raw backtrace: /usr/sbin/dovecot()
[0x41348a] - /usr/sbin/dovecot() [0x413584] - /usr/sbin/dovecot()
[0x40b290] - /usr/sbin/dovecot() [0x412bf6] - /usr/sbin/dovecot()
[0x405c9a] - /usr/sbin/dovecot() [0x416f3d] - /usr/sbin/dovecot()
[0x4163b8] - /usr/sbin/dovecot() [0x40bb39] -
/lib/libc.so.6(__libc_start_main+0xfd) [0x7f2bad861c8d] -
/usr/sbin/dovecot() [0x403859]
Jun 05 07:58:09 dovecot: Info: Dovecot v1.2.15 starting up (core 
dumps disabled)


recompile dovecot, or update to later stable ?, 1.2.15 is not the 
latest in 1.x, and its more or less a flame war on dovecot maillist to 
keep 1.x running :(


as i read it you have upgraded gcc/glibc, if its gentoo/funtoo, 
revdep-rebuild will fix it


i have 1.2.16

--
senders that put my email into body content will deliver it to my own 
trashcan, so if you like to get reply, dont do it

Re: [Dovecot] crash with dovecot 2.2: Panic: Buffer full

[Tonio]

Le 9 avr. 2013 à 22:56, Timo Sirainen t...@iki.fi a écrit :

 On 8.4.2013, at 23.26, to...@starbridge.org wrote:
 
 imap(clean-quarant...@spamguard.fr): Panic: file istream.c: line 153
 (i_stream_read): assertion failed: (_stream-skip != _stream-pos)
 
 http://hg.dovecot.org/dovecot-2.2/rev/fbef40826602 should fix this.
 

Thanks Timo
Its ok now

Regards
Tonio

Re: [Dovecot] crash with dovecot 2.2: Panic: Buffer full

[Timo Sirainen]

On 8.4.2013, at 23.26, to...@starbridge.org wrote:

 imap(clean-quarant...@spamguard.fr): Panic: file istream.c: line 153
 (i_stream_read): assertion failed: (_stream-skip != _stream-pos)

http://hg.dovecot.org/dovecot-2.2/rev/fbef40826602 should fix this.

Re: [Dovecot] crash with dovecot 2.2: Panic: Buffer full

[to...@starbridge.org]

Le 07/04/2013 22:56, Timo Sirainen a écrit :
 On Sun, 2013-04-07 at 21:47 +0200, to...@starbridge.org wrote:
 since I've upgraded to 2.2.rc5 (c24783148d78), I've got the previous
 error again:
 It's happening on a large mailbox on almost every emails, with Horde 5
 webmail client (works fine with thunderbird so far)
  Thanks for your help

 Apr  7 21:30:58 mx2 dovecot: imap(clean-quarant...@spamguard.fr): Panic:
 Buffer full (8206  8192, pool none)
 Thanks, this should fix it:
 http://hg.dovecot.org/dovecot-2.2/rev/bb25fa35d887


Hi Timo,
It's ok for this error, but now, on a few email, I've got this:
dovecot --version
2.2.rc6 (548e59794f2e)


imap(clean-quarant...@spamguard.fr): Panic: file istream.c: line 153
(i_stream_read): assertion failed: (_stream-skip != _stream-pos)
Apr  8 22:19:26 mx2 dovecot: imap(clean-quarant...@spamguard.fr): Error:
Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x60ada)
[0x7f692abe1ada] - /usr/lib/dovecot/libdovecot.so.0(+0x60b1e)
[0x7f692abe1b1e] - /usr/lib/dovecot/libdovecot.so.0(i_fatal+0)
[0x7f692aba3415] -
/usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x1b9) [0x7f692abea2a9]
- /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3d)
[0x7f692abea9dd] - /usr/lib/dovecot/libdovecot-storage.so.0(+0x9b624)
[0x7f692aed8624] -
/usr/lib/dovecot/libdovecot-storage.so.0(index_mail_get_binary_stream+0x77)
[0x7f692aed8ab7] -
/usr/lib/dovecot/libdovecot-storage.so.0(mail_get_binary_stream+0x60)
[0x7f692aeb1640] -
/usr/lib/dovecot/libdovecot-storage.so.0(imap_msgpart_open+0x9f)
[0x7f692af0db4f] - dovecot/imap() [0x418f35] - dovecot/imap()
[0x4175dd] - dovecot/imap(imap_fetch_more+0x34) [0x418534] -
dovecot/imap(cmd_fetch+0x309) [0x40e2c9] -
dovecot/imap(command_exec+0x3c) [0x41621c] - dovecot/imap() [0x415280]
- dovecot/imap() [0x41533a] - dovecot/imap(client_handle_input+0x115)
[0x4155f5] - dovecot/imap(client_input+0x72) [0x4159a2] -
/usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x7f692abf14a6]
- /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xd7)
[0x7f692abf22f7] - /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x28)
[0x7f692abf0fe8] -
/usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13)
[0x7f692aba85a3] - dovecot/imap(main+0x270) [0x40b940] -
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7f692a815ead]
- dovecot/imap() [0x40ba9d]
Apr  8 22:19:26 mx2 dovecot: imap(clean-quarant...@spamguard.fr): Fatal:
master: service(imap): child 4369 killed with signal 6 (core dumped)


#0  0x7f692a829475 in raise () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#1  0x7f692a82c6f0 in abort () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#2  0x7f692abe1ae8 in default_fatal_finish (type=optimized out,
status=status@entry=0) at failures.c:191
backtrace = 0x62d818 /usr/lib/dovecot/libdovecot.so.0(+0x60ada)
[0x7f692abe1ada] - /usr/lib/dovecot/libdovecot.so.0(+0x60b1e)
[0x7f692abe1b1e] - /usr/lib/dovecot/libdovecot.so.0(i_fatal+0)
[0x7f692aba3415] - /usr/lib/d...
#3  0x7f692abe1b1e in i_internal_fatal_handler (ctx=0x7fff605d4680,
format=optimized out, args=optimized out) at failures.c:652
status = 0
#4  0x7f692aba3415 in i_panic (format=format@entry=0x7f692ac06e68
file %s: line %d (%s): assertion failed: (%s)) at failures.c:263
ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp = 0x0}
args = {{gp_offset = 40, fp_offset = 48, overflow_arg_area =
0x7fff605d4770, reg_save_area = 0x7fff605d46b0}}
#5  0x7f692abea2a9 in i_stream_read (stream=stream@entry=0x9fa6a0)
at istream.c:153
_stream = 0x9fa640
old_size = 0
ret = -2
__FUNCTION__ = i_stream_read
#6  0x7f692abea9dd in i_stream_read_data
(stream=stream@entry=0x9fa6a0, data_r=data_r@entry=0x7fff605d4820,
size_r=size_r@entry=0x7fff605d4828, threshold=threshold@entry=0) at
istream.c:479
ret = optimized out
read_more = false
__FUNCTION__ = i_stream_read_data
#7  0x7f692aed8624 in blocks_count_lines (full_input=0x9fa6a0,
ctx=0x7fff605d4830) at index-mail-binary.c:319
block_idx = 5
p = optimized out
size = 0
data = 0x0
ret = optimized out
cur_block = 0x62d488
block_count = 7
cur_offset = 2755
skip = optimized out
#8  index_mail_read_binary_to_cache (_mail=_mail@entry=0x66d630,
part=part@entry=0x672190, include_hdr=include_hdr@entry=false,
binary_r=binary_r@entry=0x7fff605d48e6,
converted_r=converted_r@entry=0x7fff605d48e7) at index-mail-binary.c:393
mail = 0x66d630
cache = 0x657b30
ctx = {mail = 0x66d630, input = 0x685c00, has_nuls = false,
converted = true, blocks = {arr = {buffer = 0x62d3d8, element_size =
24}, v = 0x62d3d8, v_modifiable = 0x62d3d8}, copy_start_offset = 113072}
__FUNCTION__ = index_mail_read_binary_to_cache
#9  0x7f692aed8ab7 in index_mail_get_binary_stream (_mail=0x66d630,
part=0x672190, include_hdr=false, size_r=0x7fff605d49a8,

Re: [Dovecot] crash with dovecot 2.2: Panic: Buffer full

[to...@starbridge.org]

Le 19/03/2013 07:24, Tonio a écrit :



 Le 18 mars 2013 à 14:47, Timo Sirainen t...@iki.fi a écrit :

 On Sat, 2013-03-16 at 13:51 +0100, to...@starbridge.org wrote:
 Hi Timo,
 I've got a crash with  dovecot 2.2

 dovecot --version
 2.2.rc2 (69c26a9e3be5)

 It's occured when accessing with imap on a large mailbox (around 50k
 messages)

 imap(clean-quarant...@spamguard.fr): Panic: Buffer full (4254  4248,
 pool none)
 These should fix it: http://hg.dovecot.org/dovecot-2.2/rev/689dbeadf168
 http://hg.dovecot.org/dovecot-2.2/rev/ee7352f46d1e



 Thx Timo
 It's ok now

 Regards 
 Tonio 


Hi Timo,
since I've upgraded to 2.2.rc5 (c24783148d78), I've got the previous
error again:
It's happening on a large mailbox on almost every emails, with Horde 5
webmail client (works fine with thunderbird so far)
 Thanks for your help

Apr  7 21:30:58 mx2 dovecot: imap(clean-quarant...@spamguard.fr): Panic:
Buffer full (8206  8192, pool none)
Apr  7 21:30:58 mx2 dovecot: imap(clean-quarant...@spamguard.fr): Error:
Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x608ea)
[0x7f29866848ea] - /usr/lib/dovecot/libdovecot.so.0(+0x6092e)
[0x7f298668492e] - /usr/lib/dovecot/libdovecot.so.0(i_fatal+0)
[0x7f2986646385] - /usr/lib/dovecot/libdovecot.so.0(+0x5d198)
[0x7f2986681198] - /usr/lib/dovecot/libdovecot.so.0(+0x56d90)
[0x7f298667ad90] - /usr/lib/dovecot/libdovecot.so.0(+0x4fc1f)
[0x7f2986673c1f] - /usr/lib/dovecot/libdovecot.so.0(+0x4fc92)
[0x7f2986673c92] - /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x69)
[0x7f298668ce39] - /usr/lib/dovecot/libdovecot.so.0(+0x6ddac)
[0x7f2986691dac] - /usr/lib/dovecot/libdovecot.so.0(+0x6df59)
[0x7f2986691f59] - /usr/lib/dovecot/libdovecot.so.0(+0x6e04b)
[0x7f298669204b] - /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x69)
[0x7f298668ce39] -
/usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3d)
[0x7f298668d6bd] - /usr/lib/dovecot/libdovecot-storage.so.0(+0x9b524)
[0x7f298697b524] -
/usr/lib/dovecot/libdovecot-storage.so.0(index_mail_get_binary_stream+0x77)
[0x7f298697b9b7] -
/usr/lib/dovecot/libdovecot-storage.so.0(mail_get_binary_stream+0x60)
[0x7f2986954590] -
/usr/lib/dovecot/libdovecot-storage.so.0(imap_msgpart_open+0x9f)
[0x7f29869b0a3f] - dovecot/imap() [0x418f35] - dovecot/imap()
[0x4175dd] - dovecot/imap(imap_fetch_more+0x34) [0x418534] -
dovecot/imap(cmd_fetch+0x309) [0x40e2c9] -
dovecot/imap(command_exec+0x3c) [0x41621c] - dovecot/imap() [0x415280]
- dovecot/imap() [0x41533a] - dovecot/imap(client_handle_input+0x115)
[0x4155f5] - dovecot/imap(client_input+0x72) [0x4159a2] -
/usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x7f2986694186]
- /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xd7)
[0x7f2986694fd7]
Apr  7 21:30:58 mx2 dovecot: imap(clean-quarant...@spamguard.fr): Fatal:
master: service(imap): child 23573 killed with signal 6 (core dumped)


#0  0x7f29862cc475 in raise () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt full
#0  0x7f29862cc475 in raise () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#1  0x7f29862cf6f0 in abort () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#2  0x7f29866848f8 in default_fatal_finish (type=optimized out,
status=status@entry=0) at failures.c:191
backtrace = 0x62d6b0 /usr/lib/dovecot/libdovecot.so.0(+0x608ea)
[0x7f29866848ea] - /usr/lib/dovecot/libdovecot.so.0(+0x6092e)
[0x7f298668492e] - /usr/lib/dovecot/libdovecot.so.0(i_fatal+0)
[0x7f2986646385] - /usr/lib/d...
#3  0x7f298668492e in i_internal_fatal_handler (ctx=0x7fffe230f150,
format=optimized out, args=optimized out) at failures.c:652
status = 0
#4  0x7f2986646385 in i_panic (format=format@entry=0x7f29866b3890
Buffer full (%lu  %lu, pool %s)) at failures.c:263
ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp = 0x0}
args = {{gp_offset = 32, fp_offset = 48, overflow_arg_area =
0x7fffe230f240, reg_save_area = 0x7fffe230f180}}
#5  0x7f2986681198 in buffer_check_limits (data_size=38, pos=8168,
buf=optimized out) at buffer.c:65
extra = optimized out
new_size = 8206
#6  buffer_write (_buf=0x7fffe230f300, pos=8168, data=0x688beb,
data_size=38) at buffer.c:178
buf = optimized out
#7  0x7f298667ad90 in quoted_printable_decode_full (
src=src@entry=0x686c20 ' ' repeats 24 times, br\n, ' '
repeats 20 times, /strong\n, ' ' repeats 16 times, /td\n, '
' repeats 12 times, /tr\n, ' ' repeats 12 times, tr
height=3D\36\ align=3D\center\\n, ' ' repeats 16 times, td
width=3D\62%\ \n, ' ' repeats 17 times..., src_size=8192,
src_pos_r=src_pos_r@entry=0x7fffe230f2f8,
dest=dest@entry=0x7fffe230f300, eof=eof@entry=false) at
quoted-printable.c:61
hexbuf = 3D
src_pos = optimized out
pos = optimized out
next = optimized out
errors = optimized out
#8  0x7f298667af28 in quoted_printable_decode (
src=src@entry=0x686c20 ' ' repeats 24 times, br\n, ' '
repeats 20 times, /strong\n, ' ' repeats 16 times, /td\n, 

Re: [Dovecot] crash with dovecot 2.2: Panic: Buffer full

[Timo Sirainen]

On Sun, 2013-04-07 at 21:47 +0200, to...@starbridge.org wrote:
 since I've upgraded to 2.2.rc5 (c24783148d78), I've got the previous
 error again:
 It's happening on a large mailbox on almost every emails, with Horde 5
 webmail client (works fine with thunderbird so far)
  Thanks for your help
 
 Apr  7 21:30:58 mx2 dovecot: imap(clean-quarant...@spamguard.fr): Panic:
 Buffer full (8206  8192, pool none)

Thanks, this should fix it:
http://hg.dovecot.org/dovecot-2.2/rev/bb25fa35d887

Re: [Dovecot] Crash while moving mail between private folder and shared folder

[kadafax]

Le 31/03/13 16:26, Timo Sirainen a écrit :

On 27.3.2013, at 18.01, kada...@gmail.com wrote:


Just to bump the OP message as I experience the exact same symptom with the 
same configuration. That is: when moving an email to a virtual mailboxes, 
dovecot crash (and sometime the email disappears from the real mailbox).

I'm guessing your error was different though. These should fix them:

http://hg.dovecot.org/dovecot-2.2/rev/12136db6e31f
http://hg.dovecot.org/dovecot-2.2/rev/9a8119326bd0

(not sure if http://hg.dovecot.org/dovecot-2.2/rev/f31d241d5371 is also 
required)
Thanks Timo, this fixed my issue (yesterday's pull of the mercurial 
repo). You are the internet IMAP Hero.


Have a nice day,
kfx

Re: [Dovecot] Crash while moving mail between private folder and shared folder

[Timo Sirainen]

On 23.3.2013, at 11.03, Christian Felsing hostmas...@taunusstein.net wrote:

 while moving a mail from a private folder (inbox) to a shared folder and
 back to private folder Dovecot 2.2rc3 crashes:
 
 ---cut here---
 Mar 23 09:57:44 dovecot dovecot: imap-login: Login:
 user=john@example.net, method=PLAIN, rip=192.168.200.6,
 lip=192.168.200.22, mpid=19423, TLS
 Mar 23 09:57:44 dovecot dovecot: imap(john@example.net): Panic: file
 mail-namespace.c: line 654 (mail_namespace_find): assertion failed: (ns
 != NULL)

Fixed: http://hg.dovecot.org/dovecot-2.2/rev/f617e2fcce66

Re: [Dovecot] Crash while moving mail between private folder and shared folder

[Timo Sirainen]

On 27.3.2013, at 18.01, kada...@gmail.com wrote:

 Just to bump the OP message as I experience the exact same symptom with the 
 same configuration. That is: when moving an email to a virtual mailboxes, 
 dovecot crash (and sometime the email disappears from the real mailbox).

I'm guessing your error was different though. These should fix them:

http://hg.dovecot.org/dovecot-2.2/rev/12136db6e31f
http://hg.dovecot.org/dovecot-2.2/rev/9a8119326bd0

(not sure if http://hg.dovecot.org/dovecot-2.2/rev/f31d241d5371 is also 
required)

 
 Thx
 
 Le 23/03/13 10:03, Christian Felsing a écrit :
 Hello,
 
 while moving a mail from a private folder (inbox) to a shared folder and
 back to private folder Dovecot 2.2rc3 crashes:
 
 ---cut here---
 Mar 23 09:57:44 dovecot dovecot: imap-login: Login:
 user=john@example.net, method=PLAIN, rip=192.168.200.6,
 lip=192.168.200.22, mpid=19423, TLS
 Mar 23 09:57:44 dovecot dovecot: imap(john@example.net): Panic: file
 mail-namespace.c: line 654 (mail_namespace_find): assertion failed: (ns
 != NULL)
 Mar 23 09:57:44 dovecot dovecot: imap(john@example.net): Error: Raw
 backtrace: /opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(+0x608fa)
 [0x7f82f65b28fa] -
 /opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(+0x6093e)
 [0x7f82f65b293e] -
 /opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(i_fatal+0)
 [0x7f82f657435b] -
 /opt/dovecot-2.2.rc3/lib/dovecot/libdovecot-storage.so.0(mail_namespace_find_unalias+0)
 [0x7f82f686b590] -
 /opt/dovecot-2.2.rc3/lib/dovecot/libdovecot-storage.so.0(mail_namespace_find_unalias+0x19)
 [0x7f82f686b5a9] -
 /opt/dovecot-2.2.rc3/lib/dovecot/lib10_quota_plugin.so(+0x57bd)
 [0x7f82f51127bd] -
 /opt/dovecot-2.2.rc3/lib/dovecot/lib10_quota_plugin.so(quota_test_alloc+0xcb)
 [0x7f82f511424b] -
 /opt/dovecot-2.2.rc3/lib/dovecot/lib10_quota_plugin.so(quota_try_alloc+0x3d)
 [0x7f82f511445d] -
 /opt/dovecot-2.2.rc3/lib/dovecot/lib10_quota_plugin.so(+0xb00b)
 [0x7f82f511800b] -
 /opt/dovecot-2.2.rc3/lib/dovecot/lib01_acl_plugin.so(+0xc7cb)
 [0x7f82f552d7cb] -
 /opt/dovecot-2.2.rc3/lib/dovecot/libdovecot-storage.so.0(mailbox_copy+0x5f)
 [0x7f82f687274f] -
 /opt/dovecot-2.2.rc3/lib/dovecot/libdovecot-storage.so.0(mailbox_move+0x10)
 [0x7f82f6872810] - dovecot-01/imap() [0x40d29d] -
 dovecot-01/imap(command_exec+0x3c) [0x4161ec] - dovecot-01/imap()
 [0x415250] - dovecot-01/imap() [0x41530a] -
 dovecot-01/imap(client_handle_input+0x115) [0x4155c5] -
 dovecot-01/imap(client_input+0x72) [0x415972] -
 /opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36)
 [0x7f82f65c20e6] -
 /opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xd7)
 [0x7f82f65c2f37] -
 /opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(io_loop_run+0x28)
 [0x7f82f65c1c28] -
 /opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(master_service_run+0x13) 
 [0x7f82f6579473]
 - dovecot-01/imap(main+0x270) [0x40b950] -
 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7f82f61e6ead]
 - dovecot-01/imap() [0x40baad]
 Mar 23 09:57:44 dovecot dovecot: imap(john@example.net): Fatal:
 master: service(imap): child 19423 killed with signal 6 (core dumps
 disabled)
 Mar 23 09:57:44 dovecot dovecot: imap-login: Login:
 user=john@example.net, method=PLAIN, rip=192.168.200.6,
 lip=192.168.200.22, mpid=19425, TLS
 Mar 23 09:57:44 dovecot dovecot: imap(john@example.net): Panic: file
 mail-namespace.c: line 654 (mail_namespace_find): assertion failed: (ns
 != NULL)
 Mar 23 09:57:44 dovecot dovecot: imap(john@example.net): Error: Raw
 backtrace: /opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(+0x608fa)
 [0x7f66ed9a58fa] -
 /opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(+0x6093e)
 [0x7f66ed9a593e] -
 /opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(i_fatal+0)
 [0x7f66ed96735b] -
 /opt/dovecot-2.2.rc3/lib/dovecot/libdovecot-storage.so.0(mail_namespace_find_unalias+0)
 [0x7f66edc5e590] -
 /opt/dovecot-2.2.rc3/lib/dovecot/libdovecot-storage.so.0(mail_namespace_find_unalias+0x19)
 [0x7f66edc5e5a9] -
 /opt/dovecot-2.2.rc3/lib/dovecot/lib10_quota_plugin.so(+0x57bd)
 [0x7f66ec5057bd] -
 /opt/dovecot-2.2.rc3/lib/dovecot/lib10_quota_plugin.so(quota_test_alloc+0xcb)
 [0x7f66ec50724b] -
 /opt/dovecot-2.2.rc3/lib/dovecot/lib10_quota_plugin.so(quota_try_alloc+0x3d)
 [0x7f66ec50745d] -
 /opt/dovecot-2.2.rc3/lib/dovecot/lib10_quota_plugin.so(+0xb00b)
 [0x7f66ec50b00b] -
 /opt/dovecot-2.2.rc3/lib/dovecot/lib01_acl_plugin.so(+0xc7cb)
 [0x7f66ec9207cb] -
 /opt/dovecot-2.2.rc3/lib/dovecot/libdovecot-storage.so.0(mailbox_copy+0x5f)
 [0x7f66edc6574f] -
 /opt/dovecot-2.2.rc3/lib/dovecot/libdovecot-storage.so.0(mailbox_move+0x10)
 [0x7f66edc65810] - dovecot-01/imap() [0x40d29d] -
 dovecot-01/imap(command_exec+0x3c) [0x4161ec] - dovecot-01/imap()
 [0x415250] - dovecot-01/imap() [0x41530a] -
 dovecot-01/imap(client_handle_input+0x115) [0x4155c5] -
 dovecot-01/imap(client_input+0x72) [0x415972] -
 /opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36)
 [0x7f66ed9b50e6

Re: [Dovecot] Crash while moving mail between private folder and shared folder

[kadafax]

Hi,

Just to bump the OP message as I experience the exact same symptom with 
the same configuration. That is: when moving an email to a virtual 
mailboxes, dovecot crash (and sometime the email disappears from the 
real mailbox).


Thx

Le 23/03/13 10:03, Christian Felsing a écrit :

Hello,

while moving a mail from a private folder (inbox) to a shared folder and
back to private folder Dovecot 2.2rc3 crashes:

---cut here---
Mar 23 09:57:44 dovecot dovecot: imap-login: Login:
user=john@example.net, method=PLAIN, rip=192.168.200.6,
lip=192.168.200.22, mpid=19423, TLS
Mar 23 09:57:44 dovecot dovecot: imap(john@example.net): Panic: file
mail-namespace.c: line 654 (mail_namespace_find): assertion failed: (ns
!= NULL)
Mar 23 09:57:44 dovecot dovecot: imap(john@example.net): Error: Raw
backtrace: /opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(+0x608fa)
[0x7f82f65b28fa] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(+0x6093e)
[0x7f82f65b293e] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(i_fatal+0)
[0x7f82f657435b] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot-storage.so.0(mail_namespace_find_unalias+0)
[0x7f82f686b590] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot-storage.so.0(mail_namespace_find_unalias+0x19)
[0x7f82f686b5a9] -
/opt/dovecot-2.2.rc3/lib/dovecot/lib10_quota_plugin.so(+0x57bd)
[0x7f82f51127bd] -
/opt/dovecot-2.2.rc3/lib/dovecot/lib10_quota_plugin.so(quota_test_alloc+0xcb)
[0x7f82f511424b] -
/opt/dovecot-2.2.rc3/lib/dovecot/lib10_quota_plugin.so(quota_try_alloc+0x3d)
[0x7f82f511445d] -
/opt/dovecot-2.2.rc3/lib/dovecot/lib10_quota_plugin.so(+0xb00b)
[0x7f82f511800b] -
/opt/dovecot-2.2.rc3/lib/dovecot/lib01_acl_plugin.so(+0xc7cb)
[0x7f82f552d7cb] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot-storage.so.0(mailbox_copy+0x5f)
[0x7f82f687274f] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot-storage.so.0(mailbox_move+0x10)
[0x7f82f6872810] - dovecot-01/imap() [0x40d29d] -
dovecot-01/imap(command_exec+0x3c) [0x4161ec] - dovecot-01/imap()
[0x415250] - dovecot-01/imap() [0x41530a] -
dovecot-01/imap(client_handle_input+0x115) [0x4155c5] -
dovecot-01/imap(client_input+0x72) [0x415972] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36)
[0x7f82f65c20e6] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xd7)
[0x7f82f65c2f37] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(io_loop_run+0x28)
[0x7f82f65c1c28] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(master_service_run+0x13) 
[0x7f82f6579473]
- dovecot-01/imap(main+0x270) [0x40b950] -
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7f82f61e6ead]
- dovecot-01/imap() [0x40baad]
Mar 23 09:57:44 dovecot dovecot: imap(john@example.net): Fatal:
master: service(imap): child 19423 killed with signal 6 (core dumps
disabled)
Mar 23 09:57:44 dovecot dovecot: imap-login: Login:
user=john@example.net, method=PLAIN, rip=192.168.200.6,
lip=192.168.200.22, mpid=19425, TLS
Mar 23 09:57:44 dovecot dovecot: imap(john@example.net): Panic: file
mail-namespace.c: line 654 (mail_namespace_find): assertion failed: (ns
!= NULL)
Mar 23 09:57:44 dovecot dovecot: imap(john@example.net): Error: Raw
backtrace: /opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(+0x608fa)
[0x7f66ed9a58fa] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(+0x6093e)
[0x7f66ed9a593e] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(i_fatal+0)
[0x7f66ed96735b] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot-storage.so.0(mail_namespace_find_unalias+0)
[0x7f66edc5e590] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot-storage.so.0(mail_namespace_find_unalias+0x19)
[0x7f66edc5e5a9] -
/opt/dovecot-2.2.rc3/lib/dovecot/lib10_quota_plugin.so(+0x57bd)
[0x7f66ec5057bd] -
/opt/dovecot-2.2.rc3/lib/dovecot/lib10_quota_plugin.so(quota_test_alloc+0xcb)
[0x7f66ec50724b] -
/opt/dovecot-2.2.rc3/lib/dovecot/lib10_quota_plugin.so(quota_try_alloc+0x3d)
[0x7f66ec50745d] -
/opt/dovecot-2.2.rc3/lib/dovecot/lib10_quota_plugin.so(+0xb00b)
[0x7f66ec50b00b] -
/opt/dovecot-2.2.rc3/lib/dovecot/lib01_acl_plugin.so(+0xc7cb)
[0x7f66ec9207cb] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot-storage.so.0(mailbox_copy+0x5f)
[0x7f66edc6574f] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot-storage.so.0(mailbox_move+0x10)
[0x7f66edc65810] - dovecot-01/imap() [0x40d29d] -
dovecot-01/imap(command_exec+0x3c) [0x4161ec] - dovecot-01/imap()
[0x415250] - dovecot-01/imap() [0x41530a] -
dovecot-01/imap(client_handle_input+0x115) [0x4155c5] -
dovecot-01/imap(client_input+0x72) [0x415972] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36)
[0x7f66ed9b50e6] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xd7)
[0x7f66ed9b5f37] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(io_loop_run+0x28)
[0x7f66ed9b4c28] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(master_service_run+0x13) 
[0x7f66ed96c473]
- dovecot-01/imap(main+0x270) [0x40b950] -
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7f66ed5d9ead]
- dovecot

[Dovecot] Crash while moving mail between private folder and shared folder

[Christian Felsing]

Hello,

while moving a mail from a private folder (inbox) to a shared folder and
back to private folder Dovecot 2.2rc3 crashes:

---cut here---
Mar 23 09:57:44 dovecot dovecot: imap-login: Login:
user=john@example.net, method=PLAIN, rip=192.168.200.6,
lip=192.168.200.22, mpid=19423, TLS
Mar 23 09:57:44 dovecot dovecot: imap(john@example.net): Panic: file
mail-namespace.c: line 654 (mail_namespace_find): assertion failed: (ns
!= NULL)
Mar 23 09:57:44 dovecot dovecot: imap(john@example.net): Error: Raw
backtrace: /opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(+0x608fa)
[0x7f82f65b28fa] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(+0x6093e)
[0x7f82f65b293e] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(i_fatal+0)
[0x7f82f657435b] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot-storage.so.0(mail_namespace_find_unalias+0)
[0x7f82f686b590] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot-storage.so.0(mail_namespace_find_unalias+0x19)
[0x7f82f686b5a9] -
/opt/dovecot-2.2.rc3/lib/dovecot/lib10_quota_plugin.so(+0x57bd)
[0x7f82f51127bd] -
/opt/dovecot-2.2.rc3/lib/dovecot/lib10_quota_plugin.so(quota_test_alloc+0xcb)
[0x7f82f511424b] -
/opt/dovecot-2.2.rc3/lib/dovecot/lib10_quota_plugin.so(quota_try_alloc+0x3d)
[0x7f82f511445d] -
/opt/dovecot-2.2.rc3/lib/dovecot/lib10_quota_plugin.so(+0xb00b)
[0x7f82f511800b] -
/opt/dovecot-2.2.rc3/lib/dovecot/lib01_acl_plugin.so(+0xc7cb)
[0x7f82f552d7cb] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot-storage.so.0(mailbox_copy+0x5f)
[0x7f82f687274f] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot-storage.so.0(mailbox_move+0x10)
[0x7f82f6872810] - dovecot-01/imap() [0x40d29d] -
dovecot-01/imap(command_exec+0x3c) [0x4161ec] - dovecot-01/imap()
[0x415250] - dovecot-01/imap() [0x41530a] -
dovecot-01/imap(client_handle_input+0x115) [0x4155c5] -
dovecot-01/imap(client_input+0x72) [0x415972] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36)
[0x7f82f65c20e6] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xd7)
[0x7f82f65c2f37] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(io_loop_run+0x28)
[0x7f82f65c1c28] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(master_service_run+0x13) 
[0x7f82f6579473]
- dovecot-01/imap(main+0x270) [0x40b950] -
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7f82f61e6ead]
- dovecot-01/imap() [0x40baad]
Mar 23 09:57:44 dovecot dovecot: imap(john@example.net): Fatal:
master: service(imap): child 19423 killed with signal 6 (core dumps
disabled)
Mar 23 09:57:44 dovecot dovecot: imap-login: Login:
user=john@example.net, method=PLAIN, rip=192.168.200.6,
lip=192.168.200.22, mpid=19425, TLS
Mar 23 09:57:44 dovecot dovecot: imap(john@example.net): Panic: file
mail-namespace.c: line 654 (mail_namespace_find): assertion failed: (ns
!= NULL)
Mar 23 09:57:44 dovecot dovecot: imap(john@example.net): Error: Raw
backtrace: /opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(+0x608fa)
[0x7f66ed9a58fa] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(+0x6093e)
[0x7f66ed9a593e] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(i_fatal+0)
[0x7f66ed96735b] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot-storage.so.0(mail_namespace_find_unalias+0)
[0x7f66edc5e590] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot-storage.so.0(mail_namespace_find_unalias+0x19)
[0x7f66edc5e5a9] -
/opt/dovecot-2.2.rc3/lib/dovecot/lib10_quota_plugin.so(+0x57bd)
[0x7f66ec5057bd] -
/opt/dovecot-2.2.rc3/lib/dovecot/lib10_quota_plugin.so(quota_test_alloc+0xcb)
[0x7f66ec50724b] -
/opt/dovecot-2.2.rc3/lib/dovecot/lib10_quota_plugin.so(quota_try_alloc+0x3d)
[0x7f66ec50745d] -
/opt/dovecot-2.2.rc3/lib/dovecot/lib10_quota_plugin.so(+0xb00b)
[0x7f66ec50b00b] -
/opt/dovecot-2.2.rc3/lib/dovecot/lib01_acl_plugin.so(+0xc7cb)
[0x7f66ec9207cb] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot-storage.so.0(mailbox_copy+0x5f)
[0x7f66edc6574f] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot-storage.so.0(mailbox_move+0x10)
[0x7f66edc65810] - dovecot-01/imap() [0x40d29d] -
dovecot-01/imap(command_exec+0x3c) [0x4161ec] - dovecot-01/imap()
[0x415250] - dovecot-01/imap() [0x41530a] -
dovecot-01/imap(client_handle_input+0x115) [0x4155c5] -
dovecot-01/imap(client_input+0x72) [0x415972] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36)
[0x7f66ed9b50e6] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xd7)
[0x7f66ed9b5f37] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(io_loop_run+0x28)
[0x7f66ed9b4c28] -
/opt/dovecot-2.2.rc3/lib/dovecot/libdovecot.so.0(master_service_run+0x13) 
[0x7f66ed96c473]
- dovecot-01/imap(main+0x270) [0x40b950] -
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7f66ed5d9ead]
- dovecot-01/imap() [0x40baad]
Mar 23 09:57:44 dovecot dovecot: imap(john@example.net): Fatal:
master: service(imap): child 19425 killed with signal 6 (core dumps
disabled)
Mar 23 09:57:46 dovecot dovecot: imap(john@example.net):
Disconnected: Logged out in=192 out=1118
---cut here---

Re: [Dovecot] crash with dovecot 2.2: Panic: Buffer full

[Tonio]

Le 18 mars 2013 à 14:47, Timo Sirainen t...@iki.fi a écrit :

 On Sat, 2013-03-16 at 13:51 +0100, to...@starbridge.org wrote:
 Hi Timo,
 I've got a crash with  dovecot 2.2
 
 dovecot --version
 2.2.rc2 (69c26a9e3be5)
 
 It's occured when accessing with imap on a large mailbox (around 50k
 messages)
 
 imap(clean-quarant...@spamguard.fr): Panic: Buffer full (4254  4248,
 pool none)
 
 These should fix it: http://hg.dovecot.org/dovecot-2.2/rev/689dbeadf168
 http://hg.dovecot.org/dovecot-2.2/rev/ee7352f46d1e
 
 
 

Thx Timo
It's ok now

Regards 
Tonio 

Re: [Dovecot] crash with dovecot 2.2: Panic: Buffer full

[Timo Sirainen]

On Sat, 2013-03-16 at 13:51 +0100, to...@starbridge.org wrote:
 Hi Timo,
 I've got a crash with  dovecot 2.2
 
 dovecot --version
 2.2.rc2 (69c26a9e3be5)
 
 It's occured when accessing with imap on a large mailbox (around 50k
 messages)
 
 imap(clean-quarant...@spamguard.fr): Panic: Buffer full (4254  4248,
 pool none)

These should fix it: http://hg.dovecot.org/dovecot-2.2/rev/689dbeadf168
http://hg.dovecot.org/dovecot-2.2/rev/ee7352f46d1e

[Dovecot] crash with dovecot 2.2: Panic: Buffer full

[to...@starbridge.org]

Hi Timo,
I've got a crash with  dovecot 2.2

dovecot --version
2.2.rc2 (69c26a9e3be5)

It's occured when accessing with imap on a large mailbox (around 50k
messages)

imap(clean-quarant...@spamguard.fr): Panic: Buffer full (4254  4248,
pool none)
Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x6089a)
[0x7f9d1bcde89a] - /usr/lib/dovecot/libdovecot.so.0(+0x608de)
[0x7f9d1bcde8de] - /usr/lib/dovecot/libdovecot.so.0(i_fatal+0)
[0x7f9d1bca039b] - /usr/lib/dovecot/libdovecot.so.0(+0x5d148)
[0x7f9d1bcdb148] - /usr/lib/dovecot/libdovecot.so.0(+0x56ba8)
[0x7f9d1bcd4ba8] - /usr/lib/dovecot/libdovecot.so.0(+0x4fa77)
[0x7f9d1bccda77] - /usr/lib/dovecot/libdovecot.so.0(+0x4faf2)
[0x7f9d1bccdaf2] - /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x69)
[0x7f9d1bce6de9] - /usr/lib/dovecot/libdovecot.so.0(+0x6dcac)
[0x7f9d1bcebcac] - /usr/lib/dovecot/libdovecot.so.0(+0x6de59)
[0x7f9d1bcebe59] - /usr/lib/dovecot/libdovecot.so.0(+0x6df4b)
[0x7f9d1bcebf4b] - /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x69)
[0x7f9d1bce6de9] -
/usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3d)
[0x7f9d1bce765d] - /usr/lib/dovecot/libdovecot-storage.so.0(+0x9af84)
[0x7f9d1bfd4f84] -
/usr/lib/dovecot/libdovecot-storage.so.0(index_mail_get_binary_stream+0x77)
[0x7f9d1bfd5417] -
/usr/lib/dovecot/libdovecot-storage.so.0(mail_get_binary_stream+0x60)
[0x7f9d1bfae5c0] -
/usr/lib/dovecot/libdovecot-storage.so.0(imap_msgpart_open+0x9f)
[0x7f9d1c00a3df] - dovecot/imap() [0x418f55] - dovecot/imap()
[0x4175fd] - dovecot/imap(imap_fetch_more+0x34) [0x418554] -
dovecot/imap(cmd_fetch+0x309) [0x40e2c9] -
dovecot/imap(command_exec+0x3c) [0x41623c] - dovecot/imap() [0x4152a0]
- dovecot/imap() [0x41535a] - dovecot/imap(client_handle_input+0x115)
[0x415615] - dovecot/imap(client_input+0x72) [0x4159c2] -
/usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x7f9d1bcee086]
- /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xd7)
[0x7f9d1bceeed7]
Mar 16 13:37:19 mx2 dovecot: imap(clean-quarant...@spamguard.fr): Fatal:
master: service(imap): child 9983 killed with signal 6 (core dumped)

backtrace:

#0  0x7f9d1b926475 in raise () from
/lib/x86_64-linux-gnu/libc.so.6 

  

No symbol table info
available.  


 

#1  0x7f9d1b9296f0 in abort () from
/lib/x86_64-linux-gnu/libc.so.6 

  

No symbol table info
available.  


 

#2  0x7f9d1bcde8a8 in default_fatal_finish (type=optimized out,
status=status@entry=0) at
failures.c:191  

  

backtrace = 0x62d5f0 /usr/lib/dovecot/libdovecot.so.0(+0x6089a)
[0x7f9d1bcde89a] - /usr/lib/dovecot/libdovecot.so.0(+0x608de)
[0x7f9d1bcde8de] - /usr/lib/dovecot/libdovecot.so.0(i_fatal+0)
[0x7f9d1bca039b] - /usr/lib/d...
#3  0x7f9d1bcde8de in i_internal_fatal_handler (ctx=0x7fff68422000,
format=optimized out, args=optimized out) at
failures.c:652  
 

status =
0   


 

#4  0x7f9d1bca039b in i_panic (format=format@entry=0x7f9d1bd0d510
Buffer full (%lu  %lu, pool %s)) at
failures.c:263  

 

ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp =
0x0}

   

args = {{gp_offset = 32, fp_offset = 48, overflow_arg_area =
0x7fff684220f0, reg_save_area =
0x7fff68422030}} 

Re: [Dovecot] crash with dovecot 2.2: Panic: Buffer full

[Timo Sirainen]

On 16.3.2013, at 13.51, to...@starbridge.org wrote:

 It's occured when accessing with imap on a large mailbox (around 50k
 messages)
 
 imap(clean-quarant...@spamguard.fr): Panic: Buffer full (4254  4248,
 pool none)
..
 #7  0x7f9d1bcd4ba8 in quoted_printable_decode_full
 ( 
   

 
src=src@entry=0x677eb0 enter\ bgcolor=3D\#ff\
 width=3D\560\\n  table cellspacing=3D\0\ border=3D\0\
 align=3D\center\ style=3D\margin: 0=\n auto;\ cellpadding=3D\0\
 width=3D\520\tr\ntd align=3D\left\ width=3D\520\\n 
 ...,
src_size=5570, src_pos_r=src_pos_r@entry=0x7fff684221a8,
 dest=dest@entry=0x7fff684221b0, eof=eof@entry=false) at
 quoted-printable.c:60 


The problem is with a specific mail and trying to decode its quoted-printable 
data. I can maybe figure out the bug with this info already, but it would be 
helpful if you could send the specific mail that causes the crash. You can 
probably cause the crash easiest by doing:

telnet localhost 143
a login user pass
b select inbox
c search text testing

Re: [Dovecot] Crash in dsync [dovecot 2.1.7]

[Timo Sirainen]

On 22.2.2013, at 0.54, Joe Beaubien joe.beaub...@gmail.com wrote:

 dsync(document): Error: Mailbox INBOX/Julie: Corrupted index, uidvalidity=0
 dsync(document): Warning: mdbox
 /backup_hdd/current/emails/document/storage: rebuilding indexes
 dsync(document): Panic: file mdbox-storage-rebuild.c: line 66
 (mdbox_storage_rebuild_init): assertion failed:
 (!storage-rebuilding_storage)

Fixed: http://hg.dovecot.org/dovecot-2.1/rev/9cb64709dd8c

Re: [Dovecot] Crash on force-resync if / is given as mailbox name

[Timo Sirainen]

On Sat, 2012-05-26 at 15:30 +0200, Daniel Parthey wrote:

 when I specify a slash a mailbox name on the command line
 of doveadm force-resync, it throws a panic. I'm not sure
 this is considered a bug.

It's a bug.

 # 2.0.20: /etc/dovecot/dovecot.conf

But it's already been fixed in v2.1 and the fix for v2.0 would be too
difficult.

[Dovecot] Crash on force-resync if / is given as mailbox name

[Daniel Parthey]

Hi,

when I specify a slash a mailbox name on the command line
of doveadm force-resync, it throws a panic. I'm not sure
this is considered a bug.

mail01:~# doveadm force-resync -u us...@example.org /
doveadm(us...@example.org): Panic: file mailbox-list-fs.c: line 150 
(fs_list_get_path): assertion failed: (mailbox_list_is_valid_pattern(_list, 
name))
doveadm(us...@example.org): Error: Raw backtrace: 
/usr/lib/dovecot/libdovecot.so.0(+0x3a7ca) [0x7f1250b797ca] - 
/usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x32) [0x7f1250b798b2] 
- /usr/lib/dovecot/libdovecot.so.0(+0x13e4a) [0x7f1250b52e4a] - 
/usr/lib/dovecot/libdovecot-storage.so.0(+0x364a7) [0x7f12512384a7] - 
/usr/lib/dovecot/libdovecot-storage.so.0(index_storage_mailbox_alloc+0x13c) 
[0x7f125124a89c] - 
/usr/lib/dovecot/libdovecot-storage.so.0(mdbox_mailbox_alloc+0x9a) 
[0x7f1251258eaa] - 
/usr/lib/dovecot/libdovecot-storage.so.0(mailbox_alloc+0x5d) [0x7f125122c8bd] 
- doveadm() [0x40a1fb] - doveadm() [0x40a2c2] - doveadm() [0x40a753] - 
doveadm(doveadm_mail_single_user+0x61) [0x40a811] - doveadm() [0x40ac4d] - 
doveadm(doveadm_mail_try_run+0x141) [0x40b081] - doveadm(main+0x3b1) 
[0x410b11] - /lib/libc.so.6(__libc_start_main+0xfd) [0x7f12503cec4d] - 
doveadm() [0x40a009]
Aborted

mail01:~# echo $?
134

# 2.0.20: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-40-server x86_64 Ubuntu 10.04.4 LTS

Regards
Daniel

Re: [Dovecot] Crash in settings parser (assertion failed: (src_count == ccount))

[Timo Sirainen]

On Sat, 2012-05-12 at 21:34 -0400, Michael Orlitzky wrote:
 Lutz Schildt posted this to the Gentoo bugzilla recently:
 
   http://bugs.gentoo.org/show_bug.cgi?id=415571
 
 There's a backtrace and conf files attached. I was able to find this
 possibly-related post from a while ago:
 
   http://dovecot.org/list/dovecot/2010-September/052963.html

Since the problem is related to config parsing, having the original
config files instead of only doveconf output would be helpful.

Also, there are several fixes in v2.1's settings-parser.c so this bug
may have already been fixed there.

[Dovecot] Crash in settings parser (assertion failed: (src_count == ccount))

[Michael Orlitzky]

Lutz Schildt posted this to the Gentoo bugzilla recently:

  http://bugs.gentoo.org/show_bug.cgi?id=415571

There's a backtrace and conf files attached. I was able to find this
possibly-related post from a while ago:

  http://dovecot.org/list/dovecot/2010-September/052963.html

Re: [Dovecot] Crash on mail folder delete

[Timo Sirainen]

On Wed, 2012-01-25 at 16:04 -0800, Daniel L. Miller wrote:
 On 1/25/2012 3:43 PM, Daniel L. Miller wrote:
  On 1/25/2012 3:42 PM, Timo Sirainen wrote:
  On 26.1.2012, at 1.37, Daniel L. Miller wrote:
 
  Attempting to delete a folder from within the trash folder using 
  Thunderbird.  I see the following in the log:
  Dovecot version?
 
  2.1.rc3.  I'm compiling rc5 now...
 
 Error still there on rc5.
 
 Jan 25 16:03:47 bubba dovecot: imap(dmil...@amfes.com): Panic: file 
 mailbox-list-fs.c: line 156 (fs_list_get_path): assertion failed: 
 (mailbox_list_is_valid_pattern(_list, name))

Fixed: http://hg.dovecot.org/dovecot-2.1/rev/95a9428fe68b

Re: [Dovecot] crash on shared folders if remote user has empty $home

[Timo Sirainen]

On 22.12.2011, at 23.01, Peer Heinlein wrote:

 d) If foo logs in, dovecot's exploring the shared folders given from the 
 non-existing user bar. But bar's entry in LDAP doesn't have $home any 
 more. imap crashes and closes the TCP-connection immediately.

Fixed: http://hg.dovecot.org/dovecot-2.0/rev/09f964850245

Re: [Dovecot] Crash on mail folder delete

[Timo Sirainen]

On 28.1.2012, at 9.15, Daniel L. Miller wrote:

 Can I do anything to help find this?  Folders are still shown in Trash - 
 unable to delete.

gdb backtrace would be helpful: http://dovecot.org/bugreport.html

and doveconf -n and the folder name.

Re: [Dovecot] Crash on mail folder delete

[Daniel L. Miller]

On 1/25/2012 4:04 PM, Daniel L. Miller wrote:

On 1/25/2012 3:43 PM, Daniel L. Miller wrote:

On 1/25/2012 3:42 PM, Timo Sirainen wrote:

On 26.1.2012, at 1.37, Daniel L. Miller wrote:

Attempting to delete a folder from within the trash folder using 
Thunderbird.  I see the following in the log:

Dovecot version?


2.1.rc3.  I'm compiling rc5 now...


Error still there on rc5.



Can I do anything to help find this?  Folders are still shown in Trash - 
unable to delete.


--
Daniel

[Dovecot] Crash on mail folder delete

[Daniel L. Miller]

Attempting to delete a folder from within the trash folder using 
Thunderbird.  I see the following in the log:


Jan 25 15:36:22 bubba dovecot: imap(dmil...@amfes.com): Panic: file 
mailbox-list-fs.c: line 156 (fs_list_get_path): assertion failed: 
(mailbox_list_is_valid_pattern(_list, name))
Jan 25 15:36:22 bubba dovecot: imap(dmil...@amfes.com): Error: Raw 
backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x3efba) 
[0x7f5fe9f86fba] - /usr/local/lib/dovecot/libdovecot.so.0(+0x3f006) 
[0x7f5fe9f87006] - /usr/local/lib/dovecot/libdovecot.so.0(+0x17f5a) 
[0x7f5fe9f5ff5a] - 
/usr/local/lib/dovecot/libdovecot-storage.so.0(+0x47287) 
[0x7f5fea214287] - /usr/local/lib/dovecot/lib01_acl_plugin.so(+0x6c71) 
[0x7f5fe8b9cc71] - /usr/local/lib/dovecot/lib01_acl_plugin.so(+0x6d47) 
[0x7f5fe8b9cd47] - 
/usr/local/lib/dovecot/lib01_acl_plugin.so(acl_mailbox_allocated+0x9e) 
[0x7f5fe8ba061e] - 
/usr/local/lib/dovecot/libdovecot-storage.so.0(hook_mailbox_allocated+0x62) 
[0x7f5fea2085b2] - 
/usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_alloc+0xb2) 
[0x7f5fea2073d2] - dovecot/imap [dmil...@amfes.com 192.168.0.91 
delete](cmd_delete+0x72) [0x409922] - dovecot/imap [dmil...@amfes.com 
192.168.0.91 delete](command_exec+0x3d) [0x4109ad] - dovecot/imap 
[dmil...@amfes.com 192.168.0.91 delete]() [0x40f97e] - dovecot/imap 
[dmil...@amfes.com 192.168.0.91 delete]() [0x40fa5d] - dovecot/imap 
[dmil...@amfes.com 192.168.0.91 delete](client_handle_input+0x135) 
[0x40fc85] - dovecot/imap [dmil...@amfes.com 192.168.0.91 
delete](client_input+0x5f) [0x4105af] - 
/usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36) 
[0x7f5fe9f93406] - 
/usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x9f) 
[0x7f5fe9f9448f] - 
/usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x28) 
[0x7f5fe9f933a8] - 
/usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) 
[0x7f5fe9f803b3] - dovecot/imap [dmil...@amfes.com 192.168.0.91 
delete](main+0x301) [0x418a61] - /lib/libc.so.6(__libc_start_main+0xfe) 
[0x7f5fe9be3d8e] - dovecot/imap [dmil...@amfes.com 192.168.0.91 
delete]() [0x4083f9]
Jan 25 15:36:23 bubba dovecot: imap(dmil...@amfes.com): Panic: file 
mailbox-list-fs.c: line 156 (fs_list_get_path): assertion failed: 
(mailbox_list_is_valid_pattern(_list, name))
Jan 25 15:36:23 bubba dovecot: imap(dmil...@amfes.com): Error: Raw 
backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x3efba) 
[0x7f33673dafba] - /usr/local/lib/dovecot/libdovecot.so.0(+0x3f006) 
[0x7f33673db006] - /usr/local/lib/dovecot/libdovecot.so.0(+0x17f5a) 
[0x7f33673b3f5a] - 
/usr/local/lib/dovecot/libdovecot-storage.so.0(+0x47287) 
[0x7f3367668287] - /usr/local/lib/dovecot/lib01_acl_plugin.so(+0x6c71) 
[0x7f3365ff0c71] - /usr/local/lib/dovecot/lib01_acl_plugin.so(+0x6d47) 
[0x7f3365ff0d47] - 
/usr/local/lib/dovecot/lib01_acl_plugin.so(acl_mailbox_allocated+0x9e) 
[0x7f3365ff461e] - 
/usr/local/lib/dovecot/libdovecot-storage.so.0(hook_mailbox_allocated+0x62) 
[0x7f336765c5b2] - 
/usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_alloc+0xb2) 
[0x7f336765b3d2] - dovecot/imap [dmil...@amfes.com 192.168.0.91 
delete](cmd_delete+0x72) [0x409922] - dovecot/imap [dmil...@amfes.com 
192.168.0.91 delete](command_exec+0x3d) [0x4109ad] - dovecot/imap 
[dmil...@amfes.com 192.168.0.91 delete]() [0x40f97e] - dovecot/imap 
[dmil...@amfes.com 192.168.0.91 delete]() [0x40fa5d] - dovecot/imap 
[dmil...@amfes.com 192.168.0.91 delete](client_handle_input+0x135) 
[0x40fc85] - dovecot/imap [dmil...@amfes.com 192.168.0.91 
delete](client_input+0x5f) [0x4105af] - 
/usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36) 
[0x7f33673e7406] - 
/usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x9f) 
[0x7f33673e848f] - 
/usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x28) 
[0x7f33673e73a8] - 
/usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) 
[0x7f33673d43b3] - dovecot/imap [dmil...@amfes.com 192.168.0.91 
delete](main+0x301) [0x418a61] - /lib/libc.so.6(__libc_start_main+0xfe) 
[0x7f3367037d8e] - dovecot/imap [dmil...@amfes.com 192.168.0.91 
delete]() [0x4083f9]
Jan 25 15:36:23 bubba dovecot: imap(dmil...@amfes.com): Fatal: master: 
service(imap): child 6074 killed with signal 6 (core dumps disabled)
Jan 25 15:36:23 bubba dovecot: imap(dmil...@amfes.com): Fatal: master: 
service(imap): child 6589 killed with signal 6 (core dumps disabled)


--
Daniel

Re: [Dovecot] Crash on mail folder delete

[Timo Sirainen]

On 26.1.2012, at 1.37, Daniel L. Miller wrote:

 Attempting to delete a folder from within the trash folder using Thunderbird. 
  I see the following in the log:

Dovecot version?

Re: [Dovecot] Crash on mail folder delete

[Daniel L. Miller]

On 1/25/2012 3:42 PM, Timo Sirainen wrote:

On 26.1.2012, at 1.37, Daniel L. Miller wrote:


Attempting to delete a folder from within the trash folder using Thunderbird.  
I see the following in the log:

Dovecot version?


2.1.rc3.  I'm compiling rc5 now...

--
Daniel

Re: [Dovecot] Crash on mail folder delete

[Daniel L. Miller]

On 1/25/2012 3:43 PM, Daniel L. Miller wrote:

On 1/25/2012 3:42 PM, Timo Sirainen wrote:

On 26.1.2012, at 1.37, Daniel L. Miller wrote:

Attempting to delete a folder from within the trash folder using 
Thunderbird.  I see the following in the log:

Dovecot version?


2.1.rc3.  I'm compiling rc5 now...


Error still there on rc5.

Jan 25 16:03:47 bubba dovecot: imap(dmil...@amfes.com): Panic: file 
mailbox-list-fs.c: line 156 (fs_list_get_path): assertion failed: 
(mailbox_list_is_valid_pattern(_list, name))
Jan 25 16:03:47 bubba dovecot: imap(dmil...@amfes.com): Error: Raw 
backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x3f1ba) 
[0x7f7c3f0331ba] - /usr/local/lib/dovecot/libdovecot.so.0(+0x3f206) 
[0x7f7c3f033206] - /usr/local/lib/dovecot/libdovecot.so.0(+0x1804a) 
[0x7f7c3f00c04a] - 
/usr/local/lib/dovecot/libdovecot-storage.so.0(+0x47317) 
[0x7f7c3f2c0317] - /usr/local/lib/dovecot/lib01_acl_plugin.so(+0x6c71) 
[0x7f7c3dc48c71] - /usr/local/lib/dovecot/lib01_acl_plugin.so(+0x6d47) 
[0x7f7c3dc48d47] - 
/usr/local/lib/dovecot/lib01_acl_plugin.so(acl_mailbox_allocated+0x9e) 
[0x7f7c3dc4c61e] - 
/usr/local/lib/dovecot/libdovecot-storage.so.0(hook_mailbox_allocated+0x62) 
[0x7f7c3f2b4662] - 
/usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_alloc+0xb2) 
[0x7f7c3f2b3482] - dovecot/imap [dmil...@amfes.com 192.168.0.91 
delete](cmd_delete+0x72) [0x409972] - dovecot/imap [dmil...@amfes.com 
192.168.0.91 delete](command_exec+0x3d) [0x4109fd] - dovecot/imap 
[dmil...@amfes.com 192.168.0.91 delete]() [0x40f9ce] - dovecot/imap 
[dmil...@amfes.com 192.168.0.91 delete]() [0x40faad] - dovecot/imap 
[dmil...@amfes.com 192.168.0.91 delete](client_handle_input+0x135) 
[0x40fcd5] - dovecot/imap [dmil...@amfes.com 192.168.0.91 
delete](client_input+0x5f) [0x4105ff] - 
/usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36) 
[0x7f7c3f03f5d6] - 
/usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x9f) 
[0x7f7c3f04065f] - 
/usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x28) 
[0x7f7c3f03f578] - 
/usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) 
[0x7f7c3f02c593] - dovecot/imap [dmil...@amfes.com 192.168.0.91 
delete](main+0x2a5) [0x418a55] - /lib/libc.so.6(__libc_start_main+0xfe) 
[0x7f7c3ec8fd8e] - dovecot/imap [dmil...@amfes.com 192.168.0.91 
delete]() [0x408449]
Jan 25 16:03:48 bubba dovecot: imap(dmil...@amfes.com): Panic: file 
mailbox-list-fs.c: line 156 (fs_list_get_path): assertion failed: 
(mailbox_list_is_valid_pattern(_list, name))
Jan 25 16:03:48 bubba dovecot: imap(dmil...@amfes.com): Error: Raw 
backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x3f1ba) 
[0x7f9e52e211ba] - /usr/local/lib/dovecot/libdovecot.so.0(+0x3f206) 
[0x7f9e52e21206] - /usr/local/lib/dovecot/libdovecot.so.0(+0x1804a) 
[0x7f9e52dfa04a] - 
/usr/local/lib/dovecot/libdovecot-storage.so.0(+0x47317) 
[0x7f9e530ae317] - /usr/local/lib/dovecot/lib01_acl_plugin.so(+0x6c71) 
[0x7f9e51a36c71] - /usr/local/lib/dovecot/lib01_acl_plugin.so(+0x6d47) 
[0x7f9e51a36d47] - 
/usr/local/lib/dovecot/lib01_acl_plugin.so(acl_mailbox_allocated+0x9e) 
[0x7f9e51a3a61e] - 
/usr/local/lib/dovecot/libdovecot-storage.so.0(hook_mailbox_allocated+0x62) 
[0x7f9e530a2662] - 
/usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_alloc+0xb2) 
[0x7f9e530a1482] - dovecot/imap [dmil...@amfes.com 192.168.0.91 
delete](cmd_delete+0x72) [0x409972] - dovecot/imap [dmil...@amfes.com 
192.168.0.91 delete](command_exec+0x3d) [0x4109fd] - dovecot/imap 
[dmil...@amfes.com 192.168.0.91 delete]() [0x40f9ce] - dovecot/imap 
[dmil...@amfes.com 192.168.0.91 delete]() [0x40faad] - dovecot/imap 
[dmil...@amfes.com 192.168.0.91 delete](client_handle_input+0x135) 
[0x40fcd5] - dovecot/imap [dmil...@amfes.com 192.168.0.91 
delete](client_input+0x5f) [0x4105ff] - 
/usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36) 
[0x7f9e52e2d5d6] - 
/usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x9f) 
[0x7f9e52e2e65f] - 
/usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x28) 
[0x7f9e52e2d578] - 
/usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) 
[0x7f9e52e1a593] - dovecot/imap [dmil...@amfes.com 192.168.0.91 
delete](main+0x2a5) [0x418a55] - /lib/libc.so.6(__libc_start_main+0xfe) 
[0x7f9e52a7dd8e] - dovecot/imap [dmil...@amfes.com 192.168.0.91 
delete]() [0x408449]
Jan 25 16:03:48 bubba dovecot: imap(dmil...@amfes.com): Fatal: master: 
service(imap): child 3300 killed with signal 6 (core dumps disabled)
Jan 25 16:03:48 bubba dovecot: imap(dmil...@amfes.com): Fatal: master: 
service(imap): child 3267 killed with signal 6 (core dumps disabled)

--
Daniel

[Dovecot] crash on shared folders if remote user has empty $home

[Peer Heinlein]

Hi,

in seldom cirumstances it's possible that the imap-process is crashing 
without write something usefule into the logfile.

a) User foo exists, is happy and everything's alright

b) He had a shared folder given from bar

c) In our setup we have mailforwarding adresses without a valid $home in 
LDAP

c) if user bar is changed from a user with into a mailforwarding adress, 
the user foo won't have an entry for $home any more, but still exists in 
LDAP.

d) If foo logs in, dovecot's exploring the shared folders given from the 
non-existing user bar. But bar's entry in LDAP doesn't have $home any 
more. imap crashes and closes the TCP-connection immediately.

root@dobby2:/etc/dovecot# telnet  143
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE 
IDLE ACL UIDPLUS STARTTLS AUTH=PLAIN AUTH=LOGIN AUTH=CRAM-MD5 
AUTH=DIGEST-MD5] Dovecot ready. Testing.
a LOGIN foo x
a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE 
IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND 
UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE 
QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS ACL 
UIDPLUS QUOTA ACL RIGHTS=texk] Logged in
a LIST  *
* BYE Internal error occurred. Refer to server log for more information.
Connection closed by foreign host.

Dec 22 21:57:41 dobby2 dovecot: master: Error: service(imap): child 
18095 killed with signal 11 (core dumps disabled)


e) This happens if mail_location=mdbox:%%h/mdbox is set in the shared 
folder namespace. If I set mail_location=auto: then Dovecot logs an 
error message, but is still possible to continue without any problems.

Dec 22 21:33:59 dobby2 dovecot: imap(bar): Error: Namespace 
'shared/bar/': Autodetection failed for auto: (home=/mail/foo/)

-- 

Heinlein Professional Linux Support GmbH
Linux: Akademie - Support - Hosting

http://www.heinlein-support.de
Tel: 030 / 40 50 51 - 0
Fax: 030 / 40 50 51 - 19

Zwangsangaben lt. §35a GmbHG:
HRB 93818 B / Amtsgericht Berlin-Charlottenburg,
Geschäftsführer: Peer Heinlein  -- Sitz: Berlin

Re: [Dovecot] crash on shared folders if remote user has empty $home

[Peer Heinlein]

Am Donnerstag, 22. Dezember 2011, 22:01:41 schrieb Peer Heinlein:


Hi,

 e) This happens if mail_location=mdbox:%%h/mdbox is set in the shared
 folder namespace. If I set mail_location=auto: then Dovecot logs an

Sorry, it's

 mail=
and not
 mail_location=

in the shared namespace area.

Peer



-- 

Heinlein Professional Linux Support GmbH
Linux: Akademie - Support - Hosting

http://www.heinlein-support.de
Tel: 030 / 40 50 51 - 0
Fax: 030 / 40 50 51 - 19

Zwangsangaben lt. §35a GmbHG:
HRB 93818 B / Amtsgericht Berlin-Charlottenburg,
Geschäftsführer: Peer Heinlein  -- Sitz: Berlin

[Dovecot] Crash in director/lmtp-proxy (lmtp_proxy_output_timeout)

[Jan-Frode Myklebust]

FYI, we saw one panic on our director/lmtp-proxy yesterday. It's running 
dovecot v2.0.13, so it very well might have been fixed already.., but here
it is anyway:


Aug 31 11:33:31 loadbalancer1 dovecot::  lmtp(4119): Panic: file lmtp-proxy.c: 
line 370 (lmtp_proxy_output_timeout): assertion failed: (proxy-data_input-eof)
Aug 31 11:33:31 loadbalancer1 dovecot::  lmtp(4119): Error: Raw backtrace: 
/usr/lib64/dovecot/libdovecot.so.0 [0x3aabc3bb70] - 
/usr/lib64/dovecot/libdovecot.so.0 [0x3aabc3bbc6] - 
/usr/lib64/dovecot/libdovecot.so.0 [0x3aabc3b083] - dovecot/lmtp [0x406c90] - 
/usr/lib64/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0xcd) [0x3aabc46a8d] 
- /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x68) [0x3aabc47a48] 
- /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x2d) [0x3aabc466fd] - 
/usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x3aabc34fe3] - 
dovecot/lmtp(main+0x144) [0x404034] - /lib64/libc.so.6(__libc_start_main+0xf4) 
[0x32ae81d994] - dovecot/lmtp [0x403e39]
Aug 31 11:33:31 loadbalancer1 dovecot::  master: Error: service(lmtp): child 
4119 killed with signal 6 (core dumps disabled)

On postfix side at the same time, we saw a few different messages about:

postfix/lmtp[5178]::  849FD1C024: lost connection with 
loadbalancers.example.com[192.168.42.15] while sending end of data -- message 
may be sent more than once

so I suspect this crash took down all active lmtp-proxyed connections.


  -jf

Re: [Dovecot] occasional dovecot crash, core captured but no symbol table info?

[John Clements]

On Aug 26, 2011, at 10:30 PM, mail...@securitylabs.it wrote:

 Il 26/08/2011 20:38, John Clements ha scritto:
 Dovecot is crashing occasionally for me.  Today it crashed six times in 
 quick succession, as I fired up a computer (Mac) I hadn't used in a while, 
 and my mail application (Apple Mail) tried to synchronize many large 
 mailboxes.
 
 The log entries look like this:
 
 Aug 26 10:26:15 computer dovecot: dovecot: child 23223 (imap) killed with 
 signal 6 (core dumped)
 Aug 26 10:26:30 computer dovecot: IMAP(granitemon): Panic: file 
 istream-raw-mbox.c: line 583 (istream_raw_mbox_get_body_size): assertion 
 failed: (rstream-body_offset != (uoff_t)-1)
 
 Hello,
 
 http://www.dovecot.org/list/dovecot/2010-March/047426.html
 
 dunno if it has been fixed in 1.2.16 or 1.2.17, you may try to upgrade to 
 1.2.17 or apply the above patch.

Thanks for googling that for me... :)

The tone of that message suggests that this core dump is probably not 
associated with data loss; any idea if that's true?

Thanks and apologies for not doing enough homework,

John Clements

[Dovecot] occasional dovecot crash, core captured but no symbol table info?

[John Clements]

Dovecot is crashing occasionally for me.  Today it crashed six times in quick 
succession, as I fired up a computer (Mac) I hadn't used in a while, and my 
mail application (Apple Mail) tried to synchronize many large mailboxes.

The log entries look like this:

Aug 26 10:26:15 computer dovecot: dovecot: child 23223 (imap) killed with 
signal 6 (core dumped)
Aug 26 10:26:30 computer dovecot: IMAP(granitemon): Panic: file 
istream-raw-mbox.c: line 583 (istream_raw_mbox_get_body_size): assertion 
failed: (rstream-body_offset != (uoff_t)-1)
Aug 26 10:26:30 computer dovecot: IMAP(granitemon): Raw backtrace: imap() 
[0x80f0e1e] - imap() [0x80f0e82] - imap() [0x80f0809] - 
imap(istream_raw_mbox_get_body_size+0x407) [0x8092f47] - 
imap(istream_raw_mbox_next+0x25) [0x8093025] - 
imap(istream_raw_mbox_seek+0x1f3) [0x8093323] - imap(mbox_file_seek+0x55) 
[0x8093745] - imap() [0x8095852] - imap() [0x8095c8d] - 
imap(index_mail_set_seq+0x153) [0x80a35c3] - imap() [0x8095fb9] - 
imap(index_storage_search_next_nonblock+0x13b) [0x80a763b] - 
imap(mailbox_search_next_nonblock+0x2a) [0x80b5c1a] - 
imap(mailbox_search_next+0x28) [0x80b5c68] - imap(imap_fetch_more+0x274) 
[0x806a4c4] - imap() [0x8062665] - imap() [0x806753f] - 
imap(client_output+0xeb) [0x806862b] - imap() [0x810007e] - 
imap(io_loop_handler_run+0xd6) [0x80f9aa6] - imap(io_loop_run+0x20) 
[0x80f8f20] - imap(main+0x5b4) [0x8070f24] - 
/lib/i686/cmov/libc.so.6(__libc_start_main+0xe6) [0xb75f3c76] - imap() 
[0x80603a1]
Aug 26 10:26:30 computer dovecot: dovecot: child 23228 (imap) killed with 
signal 6 (core dumped)

Here's the output of dovecot -n:

clements@computer:/home/granitemon$ sudo dovecot -n
# 1.2.15: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-5-686 i686 Debian 6.0.2 
log_timestamp: %Y-%m-%d %H:%M:%S 
login_dir: /var/run/dovecot/login
login_executable: /usr/lib/dovecot/imap-login
mail_privileged_group: mail
mbox_write_locks: fcntl dotlock
lda:
  postmaster_address: postmas...@brinckerhoff.org
  mail_plugins: sieve
auth default:
  passdb:
driver: pam
  userdb:
driver: passwd

... this is the version associated with debian stable.

Finally, since I had coredumps enabled, I'm in a position to provide 'bt full', 
but it looks like my binaries are stripped, so I'm not getting source code line 
numbers.

granitemon@computer:~$ gdb /usr/lib/dovecot/imap ./core 
GNU gdb (GDB) 7.0.1-debian
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as i486-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/lib/dovecot/imap...(no debugging symbols 
found)...done.

warning: Can't read pathname for load map: Input/output error.
Reading symbols from /lib/i686/cmov/libdl.so.2...(no debugging symbols 
found)...done.
Loaded symbols for /lib/i686/cmov/libdl.so.2
Reading symbols from /usr/lib/libldap_r-2.4.so.2...(no debugging symbols 
found)...done.
Loaded symbols for /usr/lib/libldap_r-2.4.so.2
Reading symbols from /lib/i686/cmov/librt.so.1...(no debugging symbols 
found)...done.
Loaded symbols for /lib/i686/cmov/librt.so.1
Reading symbols from /lib/i686/cmov/libc.so.6...(no debugging symbols 
found)...done.
Loaded symbols for /lib/i686/cmov/libc.so.6
Reading symbols from /lib/ld-linux.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /usr/lib/liblber-2.4.so.2...(no debugging symbols 
found)...done.
Loaded symbols for /usr/lib/liblber-2.4.so.2
Reading symbols from /lib/i686/cmov/libresolv.so.2...(no debugging symbols 
found)...done.
Loaded symbols for /lib/i686/cmov/libresolv.so.2
Reading symbols from /usr/lib/libsasl2.so.2...(no debugging symbols 
found)...done.
Loaded symbols for /usr/lib/libsasl2.so.2
Reading symbols from /usr/lib/libgnutls.so.26...(no debugging symbols 
found)...done.
Loaded symbols for /usr/lib/libgnutls.so.26
Reading symbols from /lib/i686/cmov/libpthread.so.0...(no debugging symbols 
found)...done.
Loaded symbols for /lib/i686/cmov/libpthread.so.0
Reading symbols from /usr/lib/libtasn1.so.3...(no debugging symbols 
found)...done.
Loaded symbols for /usr/lib/libtasn1.so.3
Reading symbols from /usr/lib/libz.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libz.so.1
Reading symbols from /usr/lib/libgcrypt.so.11...(no debugging symbols 
found)...done.
Loaded symbols for /usr/lib/libgcrypt.so.11
Reading symbols from /usr/lib/libgpg-error.so.0...(no debugging symbols 
found)...done.
Loaded symbols for /usr/lib/libgpg-error.so.0
Reading symbols from /lib/i686/cmov/libnss_compat.so.2...(no debugging symbols 
found)...done.
Loaded symbols for /lib/i686/cmov/libnss_compat.so.2
Reading symbols from /lib/i686/cmov/libnsl.so.1...(no debugging 

Re: [Dovecot] occasional dovecot crash, core captured but no symbol table info?

[mail...@securitylabs.it]

Il 26/08/2011 20:38, John Clements ha scritto:

Dovecot is crashing occasionally for me.  Today it crashed six times in quick 
succession, as I fired up a computer (Mac) I hadn't used in a while, and my 
mail application (Apple Mail) tried to synchronize many large mailboxes.

The log entries look like this:

Aug 26 10:26:15 computer dovecot: dovecot: child 23223 (imap) killed with 
signal 6 (core dumped)
Aug 26 10:26:30 computer dovecot: IMAP(granitemon): Panic: file 
istream-raw-mbox.c: line 583 (istream_raw_mbox_get_body_size): assertion failed: 
(rstream-body_offset != (uoff_t)-1)


Hello,

http://www.dovecot.org/list/dovecot/2010-March/047426.html

dunno if it has been fixed in 1.2.16 or 1.2.17, you may try to upgrade 
to 1.2.17 or apply the above patch.

Re: [Dovecot] Crash test :)

[Timo Sirainen]

On Sun, 2011-05-22 at 07:27 +0200, Kamil Jońca wrote:
  Um. :(  Files were created about 2 months ago. It was certainly 1.x, but
  now it is hard to say, what exactly version it was.
  
  But question is open: Can I (and how) restore mails from so old backup?
 
  Dovecot v2.0 should be able to read v1.x's dbox files. If it can, it can 
  restore the backups. The only difference I can think of is that in some 
  version I changed the default to have dbox save everything under 
  mailboxes/ directory. If your backups don't use that directory, you can 
  use something like:
 
  doveadm import sdbox:~/Mail/dbox-temp:MAILBOXDIR= #Dbox mailbox 
  spamcop/reports
 
 
 Unfortunately neither debian 2.0.12 nor 2.0.13 version can import
 these. Strange thing is that message Invalid dbox header size is
 printed after  creating dovecot-uidvalidity and dovecot-index* files
 for source dbox, u.* files are  not read at all.

Oh. I think it's entirely possible that current v2.0 can't really read
v1.x dbox without giving errors..

Re: [Dovecot] Crash test :)

[Kamil Jońca]

Timo Sirainen t...@iki.fi writes:

 On 21.5.2011, at 1.21, Kamil Jońca wrote:

 2. when I move dbox-Mails to proper place I got:
 
 doveadm(kjonca): Error: sdbox 
 /home/kjonca/Mail/dbox-temp/spamcop/reports/mailboxes/INBOX/dbox-Mails: 
 Invalid dbox header size
 
 What Dovecot version? I think this is fixed already.
 
 Um. :(  Files were created about 2 months ago. It was certainly 1.x, but
 now it is hard to say, what exactly version it was.
 
 But question is open: Can I (and how) restore mails from so old backup?

 Dovecot v2.0 should be able to read v1.x's dbox files. If it can, it can 
 restore the backups. The only difference I can think of is that in some 
 version I changed the default to have dbox save everything under mailboxes/ 
 directory. If your backups don't use that directory, you can use something 
 like:

 doveadm import sdbox:~/Mail/dbox-temp:MAILBOXDIR= #Dbox mailbox 
 spamcop/reports


Unfortunately neither debian 2.0.12 nor 2.0.13 version can import
these. Strange thing is that message Invalid dbox header size is
printed after  creating dovecot-uidvalidity and dovecot-index* files
for source dbox, u.* files are  not read at all.

KJ


-- 
http://blogdebart.pl/2010/03/17/dalsze-przygody-swinki-w-new-jersey/
Nie można wlecieć w trzecie tysiaclecie
  na drzwiach od stodoły - biskup polowy WP Sławoj Leszek Głódź.

[Dovecot] Crash test :)

[Kamil Jońca]

I'm considering to move my mails from maildir/mbox to mdbox. One of my
doubts is: how can I restore my mails when something terrribly wrong
happens. 

I understand that I should use doveadm import backup_location
mailbox all.

So I try to import with:
 
doveadm -v import sdbox:~/Mail/dbox-temp/spamcop/reports/ 
#Dbox/spamcop/reports all

#Dbox namespace were defined as:

--8---cut here---start-8---
namespace {
  hidden = no
  inbox = no
  list = yes
  location = mdbox:~/Mail/Dbox
  prefix = #Dbox/
  separator = /
  subscriptions = yes
  type = private
}
--8---cut here---end---8---

dbox-temp were defined earlier as 
--8---cut here---start-8---
namespace {
  hidden = no
  inbox = no
  list = yes
  location = sdbox:~/Mail/dbox-temp
  separator = /
  subscriptions = yes
  type = private
}
--8---cut here---end---8---

1. when I specified for example sdbox:~/Mail/dbox-temp/spamcop/reports/ doveadm
search mails under ~/Mail/dbox-temp/spamcop/reports/mailboxes/INBOX/dbox-Mails/
- am I missing something from documentation?  
(I expected rather ~/Mail/dbox-temp/mailboxes/spamcop/reports/dbox-Mails)


2. when I move dbox-Mails to proper place I got:

doveadm(kjonca): Error: sdbox 
/home/kjonca/Mail/dbox-temp/spamcop/reports/mailboxes/INBOX/dbox-Mails: Invalid 
dbox header size
doveadm(kjonca): Error: sdbox 
/home/kjonca/Mail/dbox-temp/spamcop/reports/mailboxes/INBOX/dbox-Mails: Invalid 
dbox header size

And nothing were imported.

Notices:

a) there were only u.* files, no indexes.
b) u.* files were created on i386 system, and import test on amd64.


KJ


-- 
http://blogdebart.pl/2010/03/17/dalsze-przygody-swinki-w-new-jersey/

Re: [Dovecot] Crash test :)

[Timo Sirainen]

On 20.5.2011, at 22.35, Kamil Jońca wrote:

 So I try to import with:
 
 doveadm -v import sdbox:~/Mail/dbox-temp/spamcop/reports/ 
 #Dbox/spamcop/reports all

You probably want something more like:

doveadm import sdbox:~/Mail/dbox-temp #Dbox mailbox spamcop/reports

 dbox-temp were defined earlier as 
 --8---cut here---start-8---
 namespace {
  hidden = no
  inbox = no
  list = yes
  location = sdbox:~/Mail/dbox-temp
  separator = /
  subscriptions = yes
  type = private
 }
 --8---cut here---end---8---

This isn't needed.

 2. when I move dbox-Mails to proper place I got:
 
 doveadm(kjonca): Error: sdbox 
 /home/kjonca/Mail/dbox-temp/spamcop/reports/mailboxes/INBOX/dbox-Mails: 
 Invalid dbox header size

What Dovecot version? I think this is fixed already.

 b) u.* files were created on i386 system, and import test on amd64.

Index files use the same format in 32bit and 64bit systems (but not in little 
vs big endian).

Re: [Dovecot] Crash test :)

[Kamil Jońca]

Timo Sirainen t...@iki.fi writes:

 On 20.5.2011, at 22.35, Kamil Jońca wrote:

 So I try to import with:
 
 doveadm -v import sdbox:~/Mail/dbox-temp/spamcop/reports/ 
 #Dbox/spamcop/reports all

 You probably want something more like:

 doveadm import sdbox:~/Mail/dbox-temp #Dbox mailbox spamcop/reports

Thanks.


 2. when I move dbox-Mails to proper place I got:
 
 doveadm(kjonca): Error: sdbox 
 /home/kjonca/Mail/dbox-temp/spamcop/reports/mailboxes/INBOX/dbox-Mails: 
 Invalid dbox header size

 What Dovecot version? I think this is fixed already.

Um. :(  Files were created about 2 months ago. It was certainly 1.x, but
now it is hard to say, what exactly version it was.

KJ


-- 
http://sporothrix.wordpress.com/2011/01/16/usa-sie-krztusza-kto-nastepny/
Zuzanka najwyraźniej pełni obowiązki Albina Siwaka w tej ekipie...
(C) Slawek Kotynski w dyskusj nt. pl.whatewer.SETI@home...

Re: [Dovecot] Crash test :)

[Kamil Jońca]

kjo...@o2.pl (Kamil Jońca) writes:

[...]

 2. when I move dbox-Mails to proper place I got:
 
 doveadm(kjonca): Error: sdbox 
 /home/kjonca/Mail/dbox-temp/spamcop/reports/mailboxes/INBOX/dbox-Mails: 
 Invalid dbox header size

 What Dovecot version? I think this is fixed already.

 Um. :(  Files were created about 2 months ago. It was certainly 1.x, but
 now it is hard to say, what exactly version it was.


But question is open: Can I (and how) restore mails from so old backup?

KJ


-- 
http://modnebzdury.wordpress.com/2009/10/01/niewiarygodny-list-prof-majewskiej-wprowadzenie/
Suma inteligencji na planecie jest stala, liczba ludzi powieksza sie.

Re: [Dovecot] Crash test :)

[Timo Sirainen]

On 21.5.2011, at 1.21, Kamil Jońca wrote:

 2. when I move dbox-Mails to proper place I got:
 
 doveadm(kjonca): Error: sdbox 
 /home/kjonca/Mail/dbox-temp/spamcop/reports/mailboxes/INBOX/dbox-Mails: 
 Invalid dbox header size
 
 What Dovecot version? I think this is fixed already.
 
 Um. :(  Files were created about 2 months ago. It was certainly 1.x, but
 now it is hard to say, what exactly version it was.
 
 But question is open: Can I (and how) restore mails from so old backup?

Dovecot v2.0 should be able to read v1.x's dbox files. If it can, it can 
restore the backups. The only difference I can think of is that in some version 
I changed the default to have dbox save everything under mailboxes/ 
directory. If your backups don't use that directory, you can use something like:

doveadm import sdbox:~/Mail/dbox-temp:MAILBOXDIR= #Dbox mailbox 
spamcop/reports

Re: [Dovecot] Crash in 2.0.8 dovecot/imap - information capture

[Timo Sirainen]

On Sun, 2010-12-12 at 10:51 -0500, Tom Talpey wrote:

 1) How can I be sure I get a core next time? I think it's because I
 run dovecot/imap under a mail uid and didn't have write permission
 to the cwd. Any way to verify that was it, and be sure it works?

http://dovecot.org/bugreport.html explains all of the things you need to
get core dumps. Although some of those settings are v1.x specific, so I
should look into updating the page..

Anyway, you can also test that you really get core dumps by manually
sending a SEGV signal to one test imap process.

 2) What other settings would provide more info if it happens again?

The gdb backtrace will be enough.

 Dec 10 08:43:53 master: Error: service(imap): child 30862 killed with 
 signal 11 (core dumps disabled)

Run ulimit -c unlimited before starting dovecot.

[Dovecot] Crash in 2.0.8 dovecot/imap - information capture

[Tom Talpey]

My dovecot logs revealed a crash in the dovecot/imap process a few
days ago. It appears to have dereferenced 0x0004 in the storage
shared lib. Unfortunately, I didn't get a core and I'm not sure how
to reproduce it. Dovecot 2.0.8 on linux32.

Two questions:

1) How can I be sure I get a core next time? I think it's because I
   run dovecot/imap under a mail uid and didn't have write permission
   to the cwd. Any way to verify that was it, and be sure it works?

2) What other settings would provide more info if it happens again?

Thanks!

dovecot.log excerpt:
Dec 10 08:43:53 master: Error: service(imap): child 30862 killed with 
signal 11 (core dumps disabled)
Dec 10 08:43:53 imap-login: Info: Login: user=x...@yy.com, method=PLAIN, 
rip=169.254.100.10, lip=169.254.100.100, mpid=2243


kernel dmesg:
imap[30862]: segfault at 4 ip b772ecd2 sp bfc90f90 error 4 in 
libdovecot-storage.so.0.0.0[b76e9000+b8000]


[~] # dovecot -n
# 2.0.8: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.33.2 i686  ext4
(not sure of exact config at time of crash, will capture next)

[Dovecot] Crash while accessing mdbox folders

[Matthias Rieber]

 Hi,

I've converted some accounts with dsync mirror maildir:~/Maildir. It 
seemed to work, but when I access the folders via IMAP I get the 
following error:


Jul 11 09:41:59 shrike dovecot: imap(matze): Debug: acl vfile: file 
/home/matze/mdbox/mailboxes/Telefon/dbox-Mails/dovecot-acl not found
Jul 11 09:41:59 shrike dovecot: imap(matze): Panic: file 
mailbox-list-fs.c: line 150 (fs_list_get_path): assertion failed: 
(mailbox_list_is_valid_pattern(_list, name))
Jul 11 09:41:59 shrike dovecot: imap(matze): Error: Raw backtrace: 
/usr/local/lib/dovecot/libdovecot.so.0 [0x2b344bcd2da2] - 
/usr/local/lib/dovecot/libdovecot.so.0 [0x2b344bcd2e0a] - 
/usr/local/lib/dovecot/libdovecot.so.0(i_error+0) [0x2
b344bcd31b3] - /usr/local/lib/dovecot/libdovecot-storage.so.0 
[0x2b344ba2eb8d] - /usr/local/lib/dovecot/lib01_acl_plugin.so 
[0x2b344c89c203] - 
/usr/local/lib/dovecot/lib01_acl_plugin.so(acl_mailbox_list_have_right+0x71) 
[0x2b344c8a0291]
 - /usr/local/lib/dovecot/lib01_acl_plugin.so [0x2b344c8a067c] - 
/usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_list_iter_next+0xa) 
[0x2b344b9fefaa] - /usr/local/lib/dovecot/lib01_acl_plugin.so 
[0x2b344c89feba] - /usr/local/lib
/dovecot/lib01_acl_plugin.so [0x2b344c8a0782] - 
/usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_list_iter_next+0xa) 
[0x2b344b9fefaa] - /usr/local/lib/dovecot/lib01_acl_plugin.so 
[0x2b344c89feba] - /usr/local/lib/dovecot/lib01_acl

_plugin.so [0x2b344c8a0782] - /usr/local/lib/dovecot/libdovecot-stor
Jul 11 09:41:59 shrike dovecot: master: Error: service(imap): child 3174 
killed with signal 6 (core dumped)


Backtrace:

#0  0x2b344c354ed5 in raise () from /lib/libc.so.6
No symbol table info available.
#1  0x2b344c3563f3 in abort () from /lib/libc.so.6
No symbol table info available.
#2  0x2b344bcd2db5 in default_fatal_finish (type=value optimized 
out, status=0) at failures.c:164
backtrace = 0xa983760 /usr/local/lib/dovecot/libdovecot.so.0 
[0x2b344bcd2da2] - /usr/local/lib/dovecot/libdovecot.so.0 
[0x2b344bcd2e0a] - /usr/local/lib/dovecot/libdovecot.so.0(i_error+0) 
[0x2b344bcd31b3] - /usr/local/l...
#3  0x2b344bcd2e0a in i_internal_fatal_handler (type=LOG_TYPE_PANIC, 
status=0, fmt=value optimized out, args=value optimized out) at 
failures.c:593

No locals.
#4  0x2b344bcd31b3 in i_panic (format=value optimized out) at 
failures.c:230
args = {{gp_offset = 40, fp_offset = 48, overflow_arg_area = 
0x7fff8edf67b0, reg_save_area = 0x7fff8edf66f0}}
#5  0x2b344ba2eb8d in fs_list_get_path (_list=0xa9b4fc8, 
name=0xa983700 Telefon/, type=MAILBOX_LIST_PATH_TYPE_MAILBOX) at 
mailbox-list-fs.c:150

root_dir = value optimized out
__FUNCTION__ = fs_list_get_path
#6  0x2b344c89c203 in acl_backend_vfile_object_init 
(_backend=0xa9b57d8, name=0xa983700 Telefon/) at acl-backend-vfile.c:171

aclobj = (struct acl_object_vfile *) 0xa9d0660
dir = value optimized out
#7  0x2b344c8a0291 in acl_mailbox_list_have_right (list=0xa9b4fc8, 
name=0xa983700 Telefon/, parent=false, acl_storage_right_idx=0, 
can_see_r=0x0) at acl-mailbox-list.c:63

alist = (struct acl_mailbox_list *) 0xa9b5210
backend = (struct acl_backend *) 0xc66
aclobj = value optimized out
ret = value optimized out
ret2 = value optimized out
#8  0x2b344c8a067c in acl_mailbox_list_iter_next (_ctx=value 
optimized out) at acl-mailbox-list.c:328

_data_stack_cur_id = 7
ctx = (struct acl_mailbox_list_iterate_context *) 0xa9cd900
info = value optimized out
ret = value optimized out
#9  0x2b344b9fefaa in mailbox_list_iter_next (ctx=0xc66) at 
mailbox-list.c:1048

info = value optimized out
#10 0x2b344c89feba in iter_mailbox_has_visible_children 
(ctx=0xa9cd520, only_nonpatterns=false) at acl-mailbox-list.c:299

iter = (struct mailbox_list_iterate_context *) 0xa9cd900
info = (const struct mailbox_info *) 0x1002
flags = 4098
pattern = value optimized out
prefix = 0xa983630 Telefon..*
i = value optimized out
prefix_len = 9
stars = false
ret = false
__FUNCTION__ = iter_mailbox_has_visible_children
#11 0x2b344c8a0782 in acl_mailbox_list_iter_next (_ctx=value 
optimized out) at acl-mailbox-list.c:332

_data_stack_cur_id = 6
ctx = (struct acl_mailbox_list_iterate_context *) 0xa9cd520
info = value optimized out
ret = 1
#12 0x2b344b9fefaa in mailbox_list_iter_next (ctx=0xc66) at 
mailbox-list.c:1048

info = value optimized out
#13 0x2b344c89feba in iter_mailbox_has_visible_children 
(ctx=0xa9caec0, only_nonpatterns=false) at acl-mailbox-list.c:299

iter = (struct mailbox_list_iterate_context *) 0xa9cd520
info = (const struct mailbox_info *) 0x1002
flags = 4098
pattern = value optimized out
prefix = 0xa9834d8 Telefon.*
i = value optimized out

Re: [Dovecot] Crash while accessing mdbox folders

[Matthias Rieber]

 Hi,

On 11.07.2010 09:46, Matthias Rieber wrote:

 Hi,

I've converted some accounts with dsync mirror maildir:~/Maildir. It 
seemed to work, but when I access the folders via IMAP I get the 
following error:


it crashed while issuing LIST. SELECT seems to work.

Regards,
Matthias

Re: [Dovecot] Crash while accessing mdbox folders

[Timo Sirainen]

On Sun, 2010-07-11 at 09:46 +0200, Matthias Rieber wrote:
 Jul 11 09:41:59 shrike dovecot: imap(matze): Panic: file 
 mailbox-list-fs.c: line 150 (fs_list_get_path): assertion failed: 
 (mailbox_list_is_valid_pattern(_list, name))

Fixed: http://hg.dovecot.org/dovecot-2.0/rev/54807112d1d6

Re: [Dovecot] mbox + bzip2 +dovecot = crash?

[Timo Sirainen]

On Mon, 2010-03-22 at 17:12 +0100, Kamil Jońca wrote:
 I have some archived  mails in compressed (by bzip2) mboxes and I would
 like to read them via imap  Unfortunately it looks like dovecot 
 crashes when tries to read them :(

Yeah, bzip2 support is broken in v1.x. Fixing it required a larger
rewrite so it'll work only in v2.0. gzip support in v1.x should work
fine though.



signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] mbox + bzip2 +dovecot = crash?

[Timo Sirainen]

On Mon, 2010-03-22 at 18:24 +0200, Timo Sirainen wrote:
 On Mon, 2010-03-22 at 17:12 +0100, Kamil Jońca wrote:
  I have some archived  mails in compressed (by bzip2) mboxes and I would
  like to read them via imap  Unfortunately it looks like dovecot 
  crashes when tries to read them :(
 
 Yeah, bzip2 support is broken in v1.x. Fixing it required a larger
 rewrite so it'll work only in v2.0. gzip support in v1.x should work
 fine though.

And looking your backtrace a bit more.. I guess it's possible that mbox
compression in general (even with gzip) isn't working fully correctly in
all situations. The larger rewrite for v2.0 included fixing some
fundamental things, and they can't really be backported to v1.2.



signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] Crash: imap process, Dovecot 1.2.4, related to ACLs (backtrace included)

[Andreas Ntaflos]

On Monday 14 September 2009 03:26:45 Andreas Ntaflos wrote:
 On Monday 14 September 2009 03:11:55 Timo Sirainen wrote:
  On Fri, 2009-08-28 at 02:46 +0200, Andreas Ntaflos wrote:
   Aug 28 01:08:01 mailtest0 dovecot:
   IMAP(andreas.ntaf...@example1.rise-s.com): Panic: file
   acl-backend-vfile.c: line 1124 (acl_backend_vfile_object_update):
   assertion failed: (!update-rights.global)
 
  Finally had time to look at this. I think the fix should be that
   global ACLs simply shouldn't be copied to child mailboxes. Is this
   also what you want? i.e. user can't delete mails from Sent, but
   can delete from Sent/child.
 
  http://hg.dovecot.org/dovecot-1.2/rev/6df681067e0a

 Thanks for not forgetting this :) I'll try out the patch first thing
 tomorrow.

So after some testing I think I can confirm that this crash is gone on 
my test server. I am in the process of setting up another mail server 
(which will go into production eventually) and will be testing this fix 
again. 

Is this patch in 1.2.5 as well? Didn't see anything mentioned in the 
release notes [1].

Anyway, thanks for taking care of the problem, Timo!

Andreas

[1] http://dovecot.org/list/dovecot-news/2009-September/000137.html
-- 
Andreas Ntaflos
Vienna, Austria

GPG Fingerprint: 6234 2E8E 5C81 C6CB E5EC  7E65 397C E2A8 090C A9B4


signature.asc
Description: This is a digitally signed message part.

Re: [Dovecot] Crash: imap process, Dovecot 1.2.4, related to ACLs (backtrace included)

[Timo Sirainen]

On Fri, 2009-08-28 at 02:46 +0200, Andreas Ntaflos wrote:
 Aug 28 01:08:01 mailtest0 dovecot: IMAP(andreas.ntaf...@example1.rise-s.com): 
 Panic: file acl-backend-vfile.c: line 1124 (acl_backend_vfile_object_update): 
 assertion failed: (!update-rights.global)

Finally had time to look at this. I think the fix should be that global
ACLs simply shouldn't be copied to child mailboxes. Is this also what
you want? i.e. user can't delete mails from Sent, but can delete from
Sent/child.

http://hg.dovecot.org/dovecot-1.2/rev/6df681067e0a



signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] Crash: imap process, Dovecot 1.2.4, related to ACLs (backtrace included)

[Timo Sirainen]

On Fri, 2009-08-28 at 02:46 +0200, Andreas Ntaflos wrote:
 Hi, 
 
 I started experimenting with ACLs and found I could reliably and reproducibly 
 crash the IMAP process when trying to create a subfolder of a folder that has 
 has ACLs set. The folder is called Sent with an ACL of owner lrwstipke. I 
 wanted to be able to have certain folders the the user cannot delete but 
 where 
 subfolders can be created freely.
..
   acl: vfile:/etc/dovecot/acl

You created a global ACL, right? So /etc/dovecot/acl/Sent?



signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] Crash: imap process, Dovecot 1.2.4, related to ACLs (backtrace included)

[Andreas Ntaflos]

On Friday 28 August 2009 19:42:47 Timo Sirainen wrote:
 On Fri, 2009-08-28 at 02:46 +0200, Andreas Ntaflos wrote:
  Hi,
 
  I started experimenting with ACLs and found I could reliably and
  reproducibly crash the IMAP process when trying to create a
  subfolder of a folder that has has ACLs set. The folder is called
  Sent with an ACL of owner lrwstipke. I wanted to be able to
  have certain folders the the user cannot delete but where
  subfolders can be created freely.

 ..

acl: vfile:/etc/dovecot/acl

 You created a global ACL, right? So /etc/dovecot/acl/Sent?

Exactly right. It contains the line owner lrwstipke.

I just now reproduced the crash again. None of the Maildir folders 
contain anything pertaining to ACLs (no dovecot-acl or dovecot-acl-list 
files) and the Sent folder is the only one with an ACL set. The log file 
again shows

Panic: file acl-backend-vfile.c: line 1124 
(acl_backend_vfile_object_update): assertion failed: (!update-
rights.global)

Anything else I can provide?

Andreas
-- 
Andreas Ntaflos 
Vienna, Austria 

GPG Fingerprint: 6234 2E8E 5C81 C6CB E5EC  7E65 397C E2A8 090C A9B4


signature.asc
Description: This is a digitally signed message part.

[Dovecot] Crash: imap process, Dovecot 1.2.4, related to ACLs (backtrace included)

[Andreas Ntaflos]

Hi, 

I started experimenting with ACLs and found I could reliably and reproducibly 
crash the IMAP process when trying to create a subfolder of a folder that has 
has ACLs set. The folder is called Sent with an ACL of owner lrwstipke. I 
wanted to be able to have certain folders the the user cannot delete but where 
subfolders can be created freely.

Relevant information follows and I hope the backtrace is useful (lots of 
value optimized out entries). You can also find everything from below on 
https://daff.pseudoterminal.org/misc/dovecot/.

Please tell me if I can provide more information.

dovecot -n:
===
# 1.2.4: /usr/local/etc/dovecot.conf
# OS: Linux 2.6.26-2-686 i686 Debian 5.0.2
log_timestamp: %Y-%m-%d %H:%M:%S
protocols: managesieve imap imaps pop3 pop3s
login_dir: /usr/local/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_executable(managesieve): /usr/local/libexec/dovecot/managesieve-login
mail_access_groups: mail
mail_privileged_group: mail
mail_location: maildir:~/Maildir
mail_drop_priv_before_exec: yes
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_executable(managesieve): /usr/local/libexec/dovecot/managesieve
mail_plugins(default): autocreate acl
mail_plugins(imap): autocreate acl
mail_plugins(pop3):
mail_plugins(managesieve):
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
mail_plugin_dir(managesieve): /usr/local/lib/dovecot/managesieve
namespace:
  type: public
  separator: .
  prefix: Public.
  location: 
maildir:/var/mail/public:CONTROL=~/Maildir/control/public:INDEX=~/Maildir/index/public
  list: yes
namespace:
  type: private
  separator: .
  prefix: Backup.
  location: maildir:~/Maildir-backup
  hidden: yes
  list: no
namespace:
  type: private
  separator: .
  inbox: yes
  list: yes
  subscriptions: yes
lda:
  log_path:
  info_log_path:
  auth_socket_path: /var/run/dovecot/auth-master
  postmaster_address: postmas...@mailtest0.rise-s.com
  mail_plugins: sieve acl
auth default:
  mechanisms: plain login
  passdb:
driver: pam
  passdb:
driver: sql
args: /etc/dovecot/dovecot-sql.conf
  userdb:
driver: passwd
  userdb:
driver: static
args: uid=vmail gid=vmail home=/var/vmail/%Ld/%Ln allow_all_users=yes
  socket:
type: listen
client:
  path: /var/spool/postfix/private/auth
  mode: 432
  user: postfix
  group: postfix
master:
  path: /var/run/dovecot/auth-master
  mode: 384
  user: vmail
plugin:
  sieve: ~/.dovecot.sieve
  sieve_dir: ~/sieve
  sieve_global_path: /etc/dovecot/sieve/default.sieve
  sieve_global_dir: /etc/dovecot/sieve/global/
  sieve_before: /etc/dovecot/sieve/before/
  autocreate: Trash
  autocreate2: Drafts
  autocreate3: Sent
  autocreate4: INBOX.Spam
  autosubscribe: Trash
  autosubscribe2: Drafts
  autosubscribe3: Sent
  autosubscribe4: INBOX.Spam
  acl: vfile:/etc/dovecot/acl

Log entry:
==

Aug 28 01:08:01 mailtest0 dovecot: IMAP(andreas.ntaf...@example1.rise-s.com): 
Panic: file acl-backend-vfile.c: line 1124 (acl_backend_vfile_object_update): 
assertion failed: (!update-rights.global)
Aug 28 01:08:01 mailtest0 dovecot: IMAP(andreas.ntaf...@example1.rise-s.com): 
Raw backtrace: imap [0x80f1ec1] - imap [0x80f1f42] - imap [0x80f18c9] - 
/usr/local/lib/dovecot/imap/lib01_acl_plugin.so [0xb7dddcf6] - 
/usr/local/lib/dovecot/imap/lib01_acl_plugin.so(acl_object_update+0x18) 
[0xb7ddb1a8] - /usr/local/lib/dovecot/imap/lib01_acl_plugin.so [0xb7de2ac7] -
 imap(cmd_create+0xf9) [0x80618d9] - imap [0x80679fc] - imap [0x8067a99] - 
imap(client_handle_input+0x2d) [0x8067c0d] - imap(client_input+0x5f) 
[0x806856f] - imap(io_loop_handler_run+0xe0) [0x80fac40] - 
imap(io_loop_run+0x20) [0x80fa0b0] - imap(main+0x5ea) [0x807104a] - 
/lib/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7e15455] - imap 
[0x8060291]
Aug 28 01:08:01 mailtest0 dovecot: dovecot: child 1588 (imap) killed with 
signal 6 (core dumped)

Backtrace:
==

#0  0xb7f70424 in __kernel_vsyscall ()
No symbol table info available.
#1  0xb7e2a640 in raise () from /lib/i686/cmov/libc.so.6
No symbol table info available.
#2  0xb7e2c018 in abort () from /lib/i686/cmov/libc.so.6
No symbol table info available.
#3  0x080f1ed5 in default_fatal_finish (type=value optimized out, status=0) 
at failures.c:160
backtrace = 0x93e5628 imap [0x80f1ec1] - imap [0x80f1f42] - imap 
[0x80f18c9] - /usr/local/lib/dovecot/imap/lib01_acl_plugin.so [0xb7dddcf6] - 
/usr/local/lib/dovecot/imap/lib01_acl_plugin.so(acl_object_update+0x18) 
[0xb...
#4  0x080f1f42 in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, 
fmt=0xb7de3094 file %s: line %d 

Re: [Dovecot] Crash in v1.2.3: istream.c: assertion failed on line 99

[Timo Sirainen]

On Aug 17, 2009, at 2:01 AM, Phillip Macey wrote:


On 17/08/2009 3:36 PM, Timo Sirainen wrote:

On Aug 17, 2009, at 1:31 AM, Phillip Macey wrote:


Also you could check if you have any mails with CRs in them:

perl -ne 's/\r$//;print if /\r/' *

This didn't print anything - I was sort of expecting it to at  
least print something (especially since your update seemed to fix  
the crash...)


Hmm. That is strange. What about in the destination mailbox where  
you copied the messages? I'm now wondering if there's still a data  
corruption bug.


Ok, I don't know what I did wrong the first time around - this time  
it printed a whole heap of stuff for both the source and destination  
mailboxes. Sorry about the false alarm.


Great, thanks. Time for v1.2.4 tomorrow then I guess. :)

Re: [Dovecot] Crash in v1.2.3: istream.c: assertion failed on line 99

[Phillip Macey]

On 17/08/2009 3:36 PM, Timo Sirainen wrote:

On Aug 17, 2009, at 1:31 AM, Phillip Macey wrote:


Also you could check if you have any mails with CRs in them:

perl -ne 's/\r$//;print if /\r/' *

This didn't print anything - I was sort of expecting it to at least 
print something (especially since your update seemed to fix the 
crash...)


Hmm. That is strange. What about in the destination mailbox where you 
copied the messages? I'm now wondering if there's still a data 
corruption bug.


Ok, I don't know what I did wrong the first time around - this time it 
printed a whole heap of stuff for both the source and destination 
mailboxes. Sorry about the false alarm.


--
Thanks,
 Phill Macey (CiSRA IT Services)

Re: [Dovecot] Crash in v1.2.3: istream.c: assertion failed on line 99

[Phillip Macey]

On 15/08/2009 3:17 AM, Timo Sirainen wrote:

Sorry about the long wait for a reply. The weekend and life away from a 
computer/work called :-)



See if this helps: http://hg.dovecot.org/dovecot-1.2/rev/4c42e72a3954
  
This seems to fix it - the process does not crash any more when I use 
either telnet or thunderbird. I can confirm that the mails were actually 
copied from source to destination ;-) I reverted back to an earlier 
version to make sure and the crashes returned. Once I went back to the 
latest version, it all started working again without crashes.


Thanks Timo! Should I consider this fixed. Do you still want more info 
about anything?



Also you could check if you have any mails with CRs in them:

perl -ne 's/\r$//;print if /\r/' *
  
This didn't print anything - I was sort of expecting it to at least 
print something (especially since your update seemed to fix the crash...)




--
Thanks,
 Phill Macey (CiSRA IT Services)

Re: [Dovecot] Crash in v1.2.3: istream.c: assertion failed on line 99

[Timo Sirainen]

On Aug 17, 2009, at 1:31 AM, Phillip Macey wrote:


Also you could check if you have any mails with CRs in them:

perl -ne 's/\r$//;print if /\r/' *

This didn't print anything - I was sort of expecting it to at least  
print something (especially since your update seemed to fix the  
crash...)


Hmm. That is strange. What about in the destination mailbox where you  
copied the messages? I'm now wondering if there's still a data  
corruption bug.

Re: [Dovecot] Crash in v1.2.3: istream.c: assertion failed on line 99

[Phillip Macey]

On 14/08/2009 12:29 PM, Timo Sirainen wrote:

On Aug 13, 2009, at 10:20 PM, Phillip Macey wrote:

Til now. It would seem that I can reproduce it at will - except that it
doesnt get logged if I have core dumps enabled :-) It could be specific
to my maildir or an email in my maildir?
Yes, it's very likely specific to your maildir. Can you anonymize it 
in some way that the crash still happens but you could also send me 
the mails? http://dovecot.org/tools/mbox-anonymize.pl does it to 
mboxes, looks like it should work for maildir files also as long as 
you put $hdr=1; to beginning.

Sorry - I cant do that. Im sure the perl script works quite well, but I
cant send you any of the emails in the maildir. For a start, there are
10k emails in the source folder and 20k in the destination. What I 

can do is start excluding emails from the copy and see when it starts
working. Maybe I can narrow it down to a particular email and then we
can take it from there. I have had a play around and here are some
things that I noticed:
* It seems to be an attribute of the destination folder. I can 
successfully move the mail into a new (empty) folder. As soon

as I try to move into that specific destination, it starts crashing.
* The other thing that I think is a pattern - using thunderbird, if I
select all the emails in the folder (eg Ctrl-A) and try to move them -
it crashes. If I hand select a smaller subset of the emails, they tend
to move successfully. The smaller the number the more likely it would be
successful. I tried to figure out if there was a point at which it
stopped working - but it seemed like the number kept on getting smaller
as I kept trying. By the end, I was not even able to move a single
email without getting a crash (restarting dovecot did not change this -
permanent storage? fluke?).
* If I move the mail into another temp folder (no problems doing this) 
and then try moving from the temp folder into the 'problem' folder, I 
still get the crash.


If you stepping through you mean you hit enter some thousand times, 
you could have also used continue command. :)

I think it was only 15 or 20 times. I didnt attach gdb to the process
until just before I did the copy. Maybe that means the crash happened
before it got around to reading all the emails or it was something in
the first couple of mails that triggered it.


#6  0x080f0098 in i_stream_read (stream=0x9b284c0) at istream.c:99
#7  0x080f25ca in i_stream_tee_read (stream=0x9b28578) at 
istream-tee.c:130

Oh, it's coming from tee_read().. I thought tee-istream was the problem.

(gdb) p ret
$4 = 15376
(gdb) p  old_size
No symbol old_size in current context.

ok, so this was dropped out by -O2

Sorry, I thought I had got rid of that.

(gdb) p _stream
$5 = (struct istream_private *) 0x9b28498
(gdb) p _stream.pos
$6 = 8191
(gdb) p _stream.skip
$7 = 0
(gdb)
But still, there is only 8 kB available but read() returned 15376 
bytes. That can't be correct. Could you do one more thing:


fr 6
p *stream
p *stream.real_stream
p *(struct file_istream *)stream.real_stream



(gdb) fr 6
#6  0x080f0098 in i_stream_read (stream=0x9b284c0) at istream.c:99
99  i_assert((size_t)ret+old_size == _stream-pos -
_stream-skip);
(gdb) p *stream
$13 = {v_offset = 745472, stream_errno = 0, mmaped = 0, blocking = 1,
closed = 0, readable_fd = 0, seekable = 0, eof = 0, real_stream = 0x9b28498}
(gdb) p *stream.real_stream
$14 = {iostream = {refcount = 1, close = 0x8100330
io_stream_default_close_destroy, destroy = 0x80f1750
i_stream_crlf_destroy,
   set_max_buffer_size = 0x80f1720 i_stream_crlf_set_max_buffer_size,
destroy_callback = 0, destroy_context = 0x0},
 read = 0x80f12b0 i_stream_crlf_read_lf, seek = 0x80f1630
i_stream_crlf_seek, sync = 0, stat = 0x80f11a0 i_stream_crlf_stat,
istream = {
   v_offset = 745472, stream_errno = 0, mmaped = 0, blocking = 1,
closed = 0, readable_fd = 0, seekable = 0, eof = 0, real_stream =
0x9b28498}, fd = 11,
 abs_start_offset = 0, statbuf = {st_dev = 0, __pad1 = 0, __st_ino = 0,
st_mode = 0, st_nlink = 0, st_uid = 0, st_gid = 0, st_rdev = 0, __pad2 = 0,
   st_size = -1, st_blksize = 0, st_blocks = 0, st_atim = {tv_sec =
1250213196, tv_nsec = 0}, st_mtim = {tv_sec = 1250213196, tv_nsec = 0},
st_ctim = {
 tv_sec = 1250213196, tv_nsec = 0}, st_ino = 0},
 buffer = 0x9b3b4b0 what is stored in this buffer? I dont know so I
have blanked it out. Let me know if you need to know more about its
contents. This string was 365 characters long...,
 w_buffer = 0x9b3b4b0 what is stored in this buffer? I dont know so I
have blanked it out. Let me know if you need to know more about its
contents. This string was 365 characters long..., buffer_size = 8192,
max_buffer_size = 8192, skip = 0, pos = 8191,
 parent = 0x9b29a30, parent_start_offset = 0, line_str = 0x0,
return_nolf_line = 0}
(gdb) p *(struct file_istream *)stream.real_stream
$15 = {istream = {iostream = {refcount = 1, close = 0x8100330
io_stream_default_close_destroy, destroy = 

Re: [Dovecot] Crash in v1.2.3: istream.c: assertion failed on line 99

[Timo Sirainen]

On Fri, 2009-08-14 at 16:38 +1000, Phillip Macey wrote:
 Maybe I can narrow it down to a particular email and then we
 can take it from there. 

Yeah, that would be good.

 * It seems to be an attribute of the destination folder. I can 
 successfully move the mail into a new (empty) folder. As soon
 as I try to move into that specific destination, it starts crashing.

It's most likely because of the caching decisions. You can use idxview
to get a list of them, e.g.

idxview ~/Maildir/.dest 
..

-- Cache fields --
 #  Name Type Size Dec  Last used
 0: flagsbit 4 tmp  2009-08-13 12:20
 1: date.sentfix 8 tmp  2009-08-07 18:22
 2: date.receivedfix 4 yes  2009-08-13 14:51
..
 8: hdr.FROM hdr - tmp  2009-08-13 18:37
..

If you duplicate the caching decisions, or at least add some caching
decisions, that might be enough to cause it to crash. You can add those
decisions simply by fetching that data. For example:

1 select mailbox
2 fetch 1 (body.peek[header.fields (from to)] bodystructure internaldate)

 * The other thing that I think is a pattern - using thunderbird, if I
 select all the emails in the folder (eg Ctrl-A) and try to move them -
 it crashes. If I hand select a smaller subset of the emails, they tend
 to move successfully. The smaller the number the more likely it would be
 successful. I tried to figure out if there was a point at which it
 stopped working - but it seemed like the number kept on getting smaller
 as I kept trying. By the end, I was not even able to move a single
 email without getting a crash 

Sounds like when destination mailbox got larger it got easier to crash?
Although I don't think that should have happened..

 (restarting dovecot did not change this -
 permanent storage? fluke?).

Restarting Dovecot rarely helps with anything. All state is stored in
index files.

  (gdb) p ret
  $4 = 15376

Wonder if this could also be wrong and caused by gdb being confused,
because -O2 was used. I don't see any way how this could happen with the
current code.


signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] Crash in v1.2.3: istream.c: assertion failed on line 99

[Timo Sirainen]

See if this helps: http://hg.dovecot.org/dovecot-1.2/rev/4c42e72a3954

Also you could check if you have any mails with CRs in them:

perl -ne 's/\r$//;print if /\r/' *



signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] Crash in v1.2.3: istream.c: assertion failed on line 99

[Charles Marcus]

On 8/12/2009, Phillip Macey (phillip.ma...@cisra.canon.com.au) wrote:
 I was able to fairly reliably trigger the same behaviour myself by
 attempting to move a bunch (thousands) of emails in my account using
 thunderbird

What version of TBird?

The upcoming v3 is supposed to be bringing a *lot* of IMAP fixes... can
you try it to see if this is at least limited to 2.0.0.x?

-- 

Best regards,

Charles