Re: dovecot-2.3.17: "Panic: file ioloop.c: line 865"

[Piper Andreas]

Hello,

  
Can you install dovecot debug symbols and redo the gdb backtrace? Package name is likely `dovecot-dbg`.




done, thanks for the hint.

Andreas

(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x7f4e58be0921 in __GI_abort () at abort.c:79
#2  0x7f4e59427a11 in default_fatal_finish (status=0, 
type=LOG_TYPE_PANIC) at failures.c:459
#3  fatal_handler_real (ctx=, format=, 
args=) at failures.c:471
#4  0x7f4e59427b01 in i_internal_fatal_handler (ctx=, 
format=, args=)

at failures.c:872
#5  0x7f4e593744a7 in i_panic (format=format@entry=0x7f4e5946ab88 
"file %s: line %d (%s): assertion failed: (%s)")

at failures.c:524
#6  0x7f4e5944121c in io_loop_destroy 
(_ioloop=_ioloop@entry=0x7ffd0e203e68) at ioloop.c:865
#7  0x563d0150ffb6 in doveadm_print_server_flush () at 
doveadm-print-server.c:106

#8  0x563d01508fb7 in doveadm_print (
value=0x563d0269ced8 "AQAAAFoYRziwaStNyDEAAEKX94joZK5JAwQ", 'A' 
, "DMu73BjjBalfFPQAANPIMJnB2rkkBAg", 'A' 
, "EAAAD3Gkc4sGkrTcgxAABCl/eI02OuSQID", 'A' 
, "gAAAD4SNQYx691evBkAANXM"...)

at doveadm-print.c:87
#9  0x563d014f4427 in cmd_dsync_run (_ctx=0x563d01fc7cc8, 
user=) at doveadm-dsync.c:713
#10 0x563d014f6a44 in doveadm_mail_next_user 
(ctx=ctx@entry=0x563d01fc7cc8, error_r=error_r@entry=0x7ffd0e204108)

at doveadm-mail.c:462
#11 0x563d014f76be in doveadm_mail_single_user 
(ctx=ctx@entry=0x563d01fc7cc8, error_r=error_r@entry=0x7ffd0e204108)

at doveadm-mail.c:493
#12 0x563d014f7c6f in doveadm_mail_cmd_exec (wildcard_user=0x0, 
ctx=0x563d01fc7cc8) at doveadm-mail.c:654
#13 doveadm_cmd_ver2_to_mail_cmd_wrapper (cctx=) at 
doveadm-mail.c:983
#14 0x563d01508c1b in doveadm_cmd_run_ver2 (argc=argc@entry=9, 
argv=argv@entry=0x563d01f6b3d0, cctx=cctx@entry=0x7ffd0e204260)

at doveadm-cmd.c:465
#15 0x563d0150d612 in doveadm_cmd_server_run_ver2 
(cctx=0x7ffd0e204260, argv=0x563d01f6b3d0, argc=9, conn=0x563d01fc1988)

at client-connection-tcp.c:187
#16 doveadm_cmd_handle (cctx=0x7ffd0e204260, argv=, 
argc=, cmd_name=,

conn=0x563d01fc1988) at client-connection-tcp.c:214
#17 client_handle_command (args=, conn=0x563d01fc1988) at 
client-connection-tcp.c:284
#18 client_connection_tcp_input (conn=0x563d01fc1988) at 
client-connection-tcp.c:436
#19 0x7f4e594406d9 in io_loop_call_io (io=0x563d01fc5950) at 
ioloop.c:737
#20 0x7f4e59442034 in io_loop_handler_run_internal 
(ioloop=ioloop@entry=0x563d01f73ed0) at ioloop-epoll.c:222
#21 0x7f4e594407e0 in io_loop_handler_run (ioloop=) 
at ioloop.c:789
#22 0x7f4e59440a18 in io_loop_run (ioloop=0x563d01f73ed0) at 
ioloop.c:762
#23 0x7f4e593a6a23 in master_service_run (service=0x563d01f73d30, 
callback=) at master-service.c:863
#24 0x563d014e6922 in main (argc=, argv=out>) at main.c:124


--

Dr. Andreas Piper, Hochschulrechenzentrum der Philipps-Univ. Marburg
  Hans-Meerwein-Straße 6, 35032 Marburg, Germany
Phone: +49 6421 28-23521  Fax: -26994  E-Mail: pi...@hrz.uni-marburg.de



smime.p7s
Description: S/MIME Cryptographic Signature

dovecot-2.3.17: "Panic: file ioloop.c: line 865"

[Piper Andreas]

Hello,

since the upgrade from dovecot-2.3.16 to 2.3.17 I get 'Panic'-errors in 
the system-log of my replicator hosts. See below for log messages, 
doveconf-output and gdb-backtrace. Storage filesystem is ZFS.


The error seems to be correlated with exactly one user-mailbox, this 
user is repeatedly noted as 'failed' in replication status, although 
replication of this mailbox seems to work, as the mailbox status shows 
always the identical size on both replicators. The error can be produced 
by forcing replication of this individual mailbox.


Is there anything I can do to repair this mailbox?

Thanks for any hints,
Andreas

Example log-messages:

Nov 11 07:17:50 vhrz311 dovecot: doveadm(119455): Error: write() 
failed: Timed out after 60 seconds
Nov 11 07:17:50 vhrz311 dovecot: doveadm(119455): Panic: file ioloop.c: 
line 865 (io_loop_destroy): assertion failed: (ioloop == cur

rent_ioloop)
Nov 11 07:17:50 vhrz311 dovecot: doveadm(119455): Error: Raw backtrace: 
/usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7
f4e59419182] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) 
[0x7f4e5941929e] -> /usr/lib/dovecot/libdovecot.so.0(+0xf8a5e)
[0x7f4e59427a5e] -> /usr/lib/dovecot/libdovecot.so.0(+0xf8b01) 
[0x7f4e59427b01] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f
4e593744a7] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_destroy+0x2dc) 
[0x7f4e5944121c] -> dovecot/doveadm-server(+0x46fb6) [0x563d0
150ffb6] -> dovecot/doveadm-server(doveadm_print+0x27) [0x563d01508fb7] 
-> dovecot/doveadm-server(+0x2b427) [0x563d014f4427] -> dove
cot/doveadm-server(+0x2da44) [0x563d014f6a44] -> 
dovecot/doveadm-server(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x2cf) 
[0x563d014f7c6f]
 -> dovecot/doveadm-server(doveadm_cmd_run_ver2+0x43b) [0x563d01508c1b] 
-> dovecot/doveadm-server(+0x44612) [0x563d0150d612] -> /usr
/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7f4e594406d9] -> 
/usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal
+0x134) [0x7f4e59442034] -> 
/usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x50) 
[0x7f4e594407e0] -> /usr/lib/dovecot/libdovec
ot.so.0(io_loop_run+0x38) [0x7f4e59440a18] -> 
/usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) 
[0x7f4e593a6a23] -> dovecot/
doveadm-server(main+0x102) [0x563d014e6922] -> 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f4e58bc1bf7] 
-> dovecot/d

oveadm-server(_start+0x2a) [0x563d014e69aa]
Nov 11 07:17:50 vhrz311 dovecot: doveadm(119455): Fatal: master: 
service(doveadm): child 119455 killed with signal 6 (core dumped)


'doveconf -n':

# 2.3.17 (e2aa53df5b): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.17 (054dddfa)
# OS: Linux 4.15.0-162-generic x86_64 Ubuntu 18.04.6 LTS
# Hostname: vhrz311.HRZ.Uni-Marburg.DE
auth_cache_negative_ttl = 0
auth_cache_size = 10 M
auth_master_user_separator = *
auth_worker_max_count = 1024
base_dir = /var/run/dovecot/
default_client_limit = 1
default_vsz_limit = 6 G
doveadm_password = # hidden, use -P to show it
doveadm_port = 12345
first_valid_gid = 1
first_valid_uid = 1
imap_max_line_length = 640 k
last_valid_gid = 1
last_valid_uid = 1
mail_attribute_dict = file:%h/mdbox/dovecot-attributes
mail_gid = 1
mail_location = mdbox:%h/mdbox
mail_plugins = " mail_log notify zlib notify replication"
mail_privileged_group = mail
mail_uid = 1
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope 
encoded-character vacation subaddress comparator-i;ascii-numeric 
relational regex imap4flags copy include variables body enotify 
environment mailbox date index ihave duplicate mime foreverypart extracttext

namespace inbox {
  hidden = no
  inbox = yes
  list = yes
  location =
  prefix =
  separator = /
  subscriptions = yes
  type = private
}
passdb {
  args = /etc/dovecot.deny
  deny = yes
  driver = passwd-file
}
passdb {
  args = /etc/dovecot/private/passwd.masterusers
  driver = passwd-file
  master = yes
}
passdb {
  args = /etc/dovecot/dovecot-ldap.hrz.conf.ext
  driver = ldap
  name = passdb_ldap_hrz
}
passdb {
  args = /etc/dovecot/dovecot-ldap.staff.conf.ext
  driver = ldap
  name = passdb_ldap_staff
}
passdb {
  args = /etc/dovecot/dovecot-ldap.students.conf.ext
  driver = ldap
  name = passdb_ldap_students
}
plugin {
  mail_replica = tcp:172.25.1.95
  sieve = file:~/sieve;active=~/.dovecot.sieve
  sieve_default = /var/lib/dovecot/default.sieve
  sieve_max_actions = 55
  sieve_max_redirects = 50
}
pop3_uidl_format = %08Xv%08Xu
postmaster_address = postmas...@hrz.uni-marburg.de
protocols = imap pop3 lmtp sieve
replication_dsync_parameters = -d -n INBOX -l 30 -U
replication_max_conns = 20
service aggregator {
  fifo_listener replication-notify-fifo {
user = vmail
  }
  unix_listener replication-notify {
user = vmail
  }
}
service auth-worker {
  user = $default_internal_user
}
service auth {
  client_limit = 1
}
service config {
  process_min_avail = 8
}
service doveadm {
  inet_listener {
port 

Re: [2.3.8] possible replication issue

[Piper Andreas via dovecot]

Hello Timo,

upgrading both replicators did the job! Both replicators now run v2.3.9 
and replication works fine, all sync-jobs which queued up during the 
upgrading have been processed successfully.


Thanks for the reassurement and all your great work with dovecot,

Andreas


Am 05.12.19 um 13:15 schrieb Timo Sirainen via dovecot:
I think there's a good chance that upgrading both will fix it. The bug 
already existed in old versions, it just wasn't normally triggered. 
Since v2.3.8 this situation is triggered on one dsync side, so the 
v2.3.9 fix needs to be on the other side.


On 5. Dec 2019, at 8.34, Piper Andreas via dovecot 
mailto:dovecot@dovecot.org>> wrote:


Hello,

upgrading to 2.3.9 unfortunately does *not* solve this issue:

I upgraded one of my replicators from 2.3.7.2 to 2.3.9 and after some 
seconds replication stopped. The other replicator remained with 
2.3.7.2. After downgrading to 2.3.7.2 replication is again working fine.


I did not try to upgrade both replicators up to now, as this is a live 
production system. Is there a chance, that upgrading both replicators 
will solve the problem?


The machines are running Ubuntu 18.04

Any help is appreciated.

Thanks,
Andreas

Am 18.10.19 um 13:52 schrieb Carsten Rosenberg via dovecot:

Hi,
some of our customers have discovered a replication issue after
upgraded from 2.3.7.2 to 2.3.8.
Running 2.3.8 several replication connections are hanging until defined
timeout. So after some seconds there are $replication_max_conns hanging
connections.
Other replications are running fast and successful.
Also running a doveadm sync tcp:... is working fine for all users.
I can't see exactly, but I haven't seen mailboxes timeouting again and
again. So I would assume it's not related to the mailbox.
From the logs:
server1:
Oct 16 08:29:25 server1 dovecot[5715]:
dsync-local(userna...@domain.com 
<mailto:userna...@domain.com>): Error:

dsync(172.16.0.1): I/O has stalled, no activity for 600 seconds (version
not received)
Oct 16 08:29:25 server1 dovecot[5715]:
dsync-local(userna...@domain.com 
<mailto:userna...@domain.com>): Error:

Timeout during state=master_recv_handshake
server2:
Oct 16 08:29:25 server2 dovecot[8113]: doveadm: Error: read(server1)
failed: EOF (last sent=handshake, last recv=handshake)
There aren't any additional logs regarding the replication.
I have tried increasing vsz_limit or reducing replication_max_conns.
Nothing changed.
--
Both customers have 10k+ users. Currently I couldn't reproduce this on
smaller test systems.
Both installation were downgraded to 2.3.7.2 to fix the issue for now
--
I've attached a tcpdump showing the client showing the client stops
sending any data after the mailbox_guid table headers.
Any idea what could be wrong here or the debug this issue?
Thanks.
Carsten Rosenberg







smime.p7s
Description: S/MIME Cryptographic Signature

Re: [2.3.8] possible replication issue

[Piper Andreas via dovecot]

Hello,

upgrading to 2.3.9 unfortunately does *not* solve this issue:

I upgraded one of my replicators from 2.3.7.2 to 2.3.9 and after some 
seconds replication stopped. The other replicator remained with 2.3.7.2. 
After downgrading to 2.3.7.2 replication is again working fine.


I did not try to upgrade both replicators up to now, as this is a live 
production system. Is there a chance, that upgrading both replicators 
will solve the problem?


The machines are running Ubuntu 18.04

Any help is appreciated.

Thanks,
Andreas

Am 18.10.19 um 13:52 schrieb Carsten Rosenberg via dovecot:

Hi,

some of our customers have discovered a replication issue after
upgraded from 2.3.7.2 to 2.3.8.

Running 2.3.8 several replication connections are hanging until defined
timeout. So after some seconds there are $replication_max_conns hanging
connections.
Other replications are running fast and successful.

Also running a doveadm sync tcp:... is working fine for all users.

I can't see exactly, but I haven't seen mailboxes timeouting again and
again. So I would assume it's not related to the mailbox.

 From the logs:

server1:
Oct 16 08:29:25 server1 dovecot[5715]:
dsync-local(userna...@domain.com): Error:
dsync(172.16.0.1): I/O has stalled, no activity for 600 seconds (version
not received)
Oct 16 08:29:25 server1 dovecot[5715]:
dsync-local(userna...@domain.com): Error:
Timeout during state=master_recv_handshake

server2:

Oct 16 08:29:25 server2 dovecot[8113]: doveadm: Error: read(server1)
failed: EOF (last sent=handshake, last recv=handshake)

There aren't any additional logs regarding the replication.

I have tried increasing vsz_limit or reducing replication_max_conns.
Nothing changed.

--

Both customers have 10k+ users. Currently I couldn't reproduce this on
smaller test systems.

Both installation were downgraded to 2.3.7.2 to fix the issue for now

--

I've attached a tcpdump showing the client showing the client stops
sending any data after the mailbox_guid table headers.



Any idea what could be wrong here or the debug this issue?

Thanks.

Carsten Rosenberg




--

Dr. Andreas Piper, Hochschulrechenzentrum der Philipps-Univ. Marburg
  Hans-Meerwein-Straße 6, 35032 Marburg, Germany
Phone: +49 6421 28-23521  Fax: -26994  E-Mail: pi...@hrz.uni-marburg.de



smime.p7s
Description: S/MIME Cryptographic Signature

Re: sieve scripts not synching for 2.3.5.1 pre-built

[Piper Andreas via dovecot]

Hello,

Am 02.04.19 um 21:51 schrieb Timo Sirainen via dovecot:
> On 2 Apr 2019, at 22.37, Timo Sirainen via dovecot  > wrote:
>>
>> On 2 Apr 2019, at 17.03, Jan-Pieter Cornet via dovecot
>> mailto:dovecot@dovecot.org>> wrote:
>>>
>>> Hi,
>>>
>>> We're synching mailboxes, changing format from maildir to mdbox,
>>> using doveadm backup/doveadm sync.
>>>
>>> When still running 2.2.36, 'doveadm backup' also synched the sieve
>>> scripts, without issues.
>>>
>>> After the upgrade to 2.3.5.1, the sieve sync stopped working. We're
>>> using the pre-built 2.3 packages from
>>> https://repo.dovecot.org/ce-2.3-latest/debian/stretch
>>
>> Looks like this is trivial to reproduce. It used to work still in
>> v2.3.1, but then something broke it. Tracking internally in DOP-1062.
> 
> Reverting 
> https://github.com/dovecot/pigeonhole/commit/479c5e57046dec76078597df844daccbfc0eb75f
>  fixes
> this.
> 

has this been fixed in 2.3.6 ?

In my first tests sieve scripts still seem not to be replicated with
dovecot-2.3.6

Regards,
Andreas



smime.p7s
Description: S/MIME Cryptographic Signature

Re: dovecot-keywords are not preserved any more when moving mails between folders

[Piper Andreas via dovecot]

Hello Timo,

Am 12.03.19 um 22:31 schrieb Timo Sirainen via dovecot:
> On 12 Mar 2019, at 17.55, Dan Christensen via dovecot  
> wrote:
>>
>> On Mar 12, 2019, Aki Tuomi via dovecot  wrote:
>>
>>> On 12.3.2019 13.46, Piper Andreas via dovecot wrote:
>>>
>>>> after an upgrade of dovecot-2.2.5 to dovecot-2.3.4 the dovecot-keywords,
>>>> which in my case are set by thunderbird, are not preserved any more when
>>>> moving a mail between folders.
>>>
>>> We are aware of this bug, and it's being tracked as DOP-842.
>>
>> Could this bug also be causing flags to be lost when using dsync
>> (as I described in some messages to this list Feb 16 to 23)?
>>
>> It seems like it might be a different bug, since in my experience
>> the flags are sometimes synced and then removed later.
> 
> That bug is fixed with attached patch.
> 

I assume, this patch is not included in dovecot-2.3.5?

Because I still observe the same problem (dovecot-keywords set by
thunderbird are lost when moving mail between folders) on my
migration-machines which are running dovecot-2.3.5:

# 2.3.5 (513208660): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.5 (2483b085)
# OS: Linux 4.15.0-46-generic x86_64 Ubuntu 18.04.2 LTS zfs

Regards,
Andreas





smime.p7s
Description: S/MIME Cryptographic Signature

Re: dovecot-keywords are not preserved any more when moving mails between folders

[Piper Andreas via dovecot]

Am 12.03.19 um 12:57 schrieb Aki Tuomi via dovecot:
> 
> On 12.3.2019 13.46, Piper Andreas via dovecot wrote:
>> Hello,
>>
>> after an upgrade of dovecot-2.2.5 to dovecot-2.3.4 the dovecot-keywords,
>> which in my case are set by thunderbird, are not preserved any more when
>> moving a mail between folders.
>>
> 
> Hi!
> 
> We are aware of this bug, and it's being tracked as DOP-842.
> 
> Aki
> 
Hello Aki,

thanks for the immediate answer.

To which version would I have to downgrade to avoid this problem?

Andreas
-- 

Dr. Andreas Piper, Hochschulrechenzentrum der Philipps-Univ. Marburg
  Hans-Meerwein-Straße 6, 35032 Marburg, Germany
Phone: +49 6421 28-23521  Fax: -26994  E-Mail: pi...@hrz.uni-marburg.de



smime.p7s
Description: S/MIME Cryptographic Signature

dovecot-keywords are not preserved any more when moving mails between folders

[Piper Andreas via dovecot]

Hello,

after an upgrade of dovecot-2.2.5 to dovecot-2.3.4 the dovecot-keywords,
which in my case are set by thunderbird, are not preserved any more when
moving a mail between folders.

Are there any ideas, what may be the reason.

Thanks for any hints on that,
Andreas

'doveconf -n' gives:

# 2.3.4 (0ecbaf23d): /etc/opt/csw/dovecot/dovecot.conf
# Pigeonhole version 0.5.4 (60b0f48d)
# OS: SunOS 5.11 i86pc
# Hostname: x.hrz.uni-marburg.de
auth_cache_negative_ttl = 0
auth_cache_size = 10 M
auth_master_user_separator = *
auth_username_chars =
abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_
auth_username_format = %u
auth_worker_max_count = 1024
base_dir = /var/run/dovecot/
default_vsz_limit = 1 G
first_valid_gid = 3
first_valid_uid = 3
imap_max_line_length = 640 k
mail_debug = yes
mail_location = maildir:%h/.maildir
mail_plugins = " mail_log notify"
mail_privileged_group = mail
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope
encoded-character vacation subaddress comparator-i;ascii-numeric
relational regex imap4flags copy include variables body enotify
environment mailbox date index ihave duplicate mime foreverypart extracttext
namespace {
  hidden = no
  inbox = yes
  list = yes
  location = maildir:%h/.maildir
  prefix =
  separator = /
  subscriptions = yes
  type = private
}
namespace inbox {
  hidden = yes
  inbox = no
  list = no
  location = maildir:%h/.maildir
  prefix = mail/
  separator = /
  subscriptions = no
  type = private
}
passdb {
  args = /etc/dovecot.deny
  deny = yes
  driver = passwd-file
}
passdb {
  args = /etc/opt/csw/dovecot/private/passwd.masterusers
  driver = passwd-file
  master = yes
}
passdb {
  args = /etc/opt/csw/dovecot/dovecot-ldap.conf.ext
  driver = ldap
}
plugin {
  sieve = file:~/sieve;active=~/.dovecot.sieve
  sieve_default = /var/lib/dovecot/default.sieve
}
pop3_uidl_format = %08Xv%08Xu
postmaster_address = postmas...@hrz.uni-marburg.de
protocols = imap pop3 lmtp sieve
service auth-worker {
  user = $default_internal_user
}
service auth {
  client_limit = 6000
}
service imap-login {
  process_min_avail = 64
  service_count = 0
}
service imap {
  process_limit = 4096
}
service lmtp {
  inet_listener lmtp {
port = 24
  }
}
service managesieve-login {
  inet_listener sieve {
port = 4190
  }
}
ssl_cert = 

smime.p7s
Description: S/MIME Cryptographic Signature

Fwd: dovecot/lmtp dumps core when proxying to multiple recipients via protocol=smtp

[Piper Andreas via dovecot]

Hello,

is there already any idea on this topic? Do you need additional information?

I would appreciate any input, as my migration scenario depends on this.

With many thanks and best regards,
Andreas

 Weitergeleitete Nachricht 
Betreff: dovecot/lmtp dumps core when proxying to multiple recipients
via protocol=smtp
Datum: Thu, 14 Feb 2019 13:53:07 +0100
Von: Piper Andreas via dovecot 
Antwort an: Piper Andreas 
An: dovecot@dovecot.org

Hello,

when trying to set up a migration scenario from my old mailbox-servers
to my new dovecot-cluster, I get a coredump from dovecot/lmtp when
proxying mail-delivery to more than one recipient on the old mailbox-server.

My setup:

3 director-hosts (Debian stretch) are proxying to a pair of
replicator-hosts and during migration also to the old mailbox-server.
For migration the not-migrated user-addresses are included via a
passwd-file with entries like:

grte...@hrz.uni-marburg.de:::director_tag=hrz protocol=smtp user=grtest1
grte...@hrz.uni-marburg.de:::director_tag=hrz protocol=smtp user=grtest2
...

The director_tag points to the old mailbox-server, with 'protocol=smtp'
SMTP is used for delivery, as the old machine is not capable of LMTP.

The setup works fine for imap-proxying and for mail-delivery to single
recipients. But if a mail is addressed to more than one recipient, lmtp
produces a coredump after delivering to all recipients.

The error-message in the log is:

Feb 14 12:15:05 vhrzxxx dovecot[63861]: lmtp(64663): Connect from 127.0.0.1
Feb 14 12:15:05 vhrzxxx dovecot[63861]: lmtp(64663):
206UIrlNZVyX/AAAGwthQA: Sent message to  at 137.248.xxx.yyy:25:
250 2.0.0 x1EBF5Ro016092 Message accepted for delivery (1/2 at 79 ms)
Feb 14 12:15:05 vhrzxxx dovecot[63861]: lmtp(64663):
206UIrlNZVyX/AAAGwthQA: Sent message to  at 137.248.xxx.yyy:25:
250 2.0.0 x1EBF5Ro016092 Message accepted for delivery (2/2 at 79 ms)
Feb 14 12:15:05 vhrzxxx dovecot[63861]: lmtp(64663): Fatal: master:
service(lmtp): child 64663 killed with signal 11 (core dumped)

The backtrace from the coredump is:

Reading symbols from /usr/lib/dovecot/lmtp...(no debugging symbols
found)...done.
[New LWP 64663]
[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/lmtp'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f347fc7a2c0 in ?? () from /usr/lib/dovecot/libdovecot.so.0
(gdb) bt full
#0  0x7f347fc7a2c0 in ?? () from /usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#1  0x7f347fc77d73 in smtp_client_command_fail_reply () from
/usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#2  0x7f347fc77fbe in smtp_client_commands_list_fail_reply () from
/usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#3  0x7f347fc7c8dc in smtp_client_connection_disconnect () from
/usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#4  0x7f347fc7cf19 in smtp_client_connection_unref () from
/usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#5  0x7f347fc7e35d in ?? () from /usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#6  0x7f347fd1f5d5 in io_loop_call_io () from
/usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#7  0x7f347fd20fd9 in io_loop_handler_run_internal () from
/usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#8  0x7f347fd1f6e6 in io_loop_handler_run () from
/usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#9  0x7f347fd1f8f8 in io_loop_run () from
/usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#10 0x7f347fc93d43 in master_service_run () from
/usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#11 0x5613fcbc1f70 in main ()
No symbol table info available.
(gdb)

doveconf -n gives:

# 2.3.4.1 (3c0b8769e): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.4 (60b0f48d)
# OS: Linux 4.9.0-8-amd64 x86_64 Debian 9.7
# Hostname: vhrzxxx.HRZ.Uni-Marburg.DE
auth_cache_negative_ttl = 0
auth_cache_size = 10 M
auth_master_user_separator = *
auth_worker_max_count = 1024
base_dir = /var/run/dovecot/
default_vsz_limit = 1 G
director_mail_servers = 172.25.1.93 172.25.1.95 137.248.xxx.yyy@hrz
137.248.xxx.zzz@staff 137.248.aaa.bbb@students
director_servers = 172.25.1.42:9090 172.25.1.41:9090 172.25.1.92:9090
director_username_hash = %Ln@%Ld
doveadm_password = # hidden, use -P to show it
doveadm_port = 12345
imap_max_line_length = 640 k
lmtp_proxy = yes
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope
encoded-character vacation subaddress comparator-i;ascii-numeric
relational regex imap4flags copy include variables body enotify
environment mailbox date index ihave duplicate mime foreverypart extracttext
passdb {
  args = /etc/dovecot.deny
  deny = yes
  driver = passwd-file
}
passdb {
  args = /etc/dovecot/private/passwd.masteruser

dovecot/lmtp dumps core when proxying to multiple recipients via protocol=smtp

[Piper Andreas via dovecot]

Hello,

when trying to set up a migration scenario from my old mailbox-servers
to my new dovecot-cluster, I get a coredump from dovecot/lmtp when
proxying mail-delivery to more than one recipient on the old mailbox-server.

My setup:

3 director-hosts (Debian stretch) are proxying to a pair of
replicator-hosts and during migration also to the old mailbox-server.
For migration the not-migrated user-addresses are included via a
passwd-file with entries like:

grte...@hrz.uni-marburg.de:::director_tag=hrz protocol=smtp user=grtest1
grte...@hrz.uni-marburg.de:::director_tag=hrz protocol=smtp user=grtest2
...

The director_tag points to the old mailbox-server, with 'protocol=smtp'
SMTP is used for delivery, as the old machine is not capable of LMTP.

The setup works fine for imap-proxying and for mail-delivery to single
recipients. But if a mail is addressed to more than one recipient, lmtp
produces a coredump after delivering to all recipients.

The error-message in the log is:

Feb 14 12:15:05 vhrzxxx dovecot[63861]: lmtp(64663): Connect from 127.0.0.1
Feb 14 12:15:05 vhrzxxx dovecot[63861]: lmtp(64663):
206UIrlNZVyX/AAAGwthQA: Sent message to  at 137.248.xxx.yyy:25:
250 2.0.0 x1EBF5Ro016092 Message accepted for delivery (1/2 at 79 ms)
Feb 14 12:15:05 vhrzxxx dovecot[63861]: lmtp(64663):
206UIrlNZVyX/AAAGwthQA: Sent message to  at 137.248.xxx.yyy:25:
250 2.0.0 x1EBF5Ro016092 Message accepted for delivery (2/2 at 79 ms)
Feb 14 12:15:05 vhrzxxx dovecot[63861]: lmtp(64663): Fatal: master:
service(lmtp): child 64663 killed with signal 11 (core dumped)

The backtrace from the coredump is:

Reading symbols from /usr/lib/dovecot/lmtp...(no debugging symbols
found)...done.
[New LWP 64663]
[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/lmtp'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f347fc7a2c0 in ?? () from /usr/lib/dovecot/libdovecot.so.0
(gdb) bt full
#0  0x7f347fc7a2c0 in ?? () from /usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#1  0x7f347fc77d73 in smtp_client_command_fail_reply () from
/usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#2  0x7f347fc77fbe in smtp_client_commands_list_fail_reply () from
/usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#3  0x7f347fc7c8dc in smtp_client_connection_disconnect () from
/usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#4  0x7f347fc7cf19 in smtp_client_connection_unref () from
/usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#5  0x7f347fc7e35d in ?? () from /usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#6  0x7f347fd1f5d5 in io_loop_call_io () from
/usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#7  0x7f347fd20fd9 in io_loop_handler_run_internal () from
/usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#8  0x7f347fd1f6e6 in io_loop_handler_run () from
/usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#9  0x7f347fd1f8f8 in io_loop_run () from
/usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#10 0x7f347fc93d43 in master_service_run () from
/usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#11 0x5613fcbc1f70 in main ()
No symbol table info available.
(gdb)

doveconf -n gives:

# 2.3.4.1 (3c0b8769e): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.4 (60b0f48d)
# OS: Linux 4.9.0-8-amd64 x86_64 Debian 9.7
# Hostname: vhrzxxx.HRZ.Uni-Marburg.DE
auth_cache_negative_ttl = 0
auth_cache_size = 10 M
auth_master_user_separator = *
auth_worker_max_count = 1024
base_dir = /var/run/dovecot/
default_vsz_limit = 1 G
director_mail_servers = 172.25.1.93 172.25.1.95 137.248.xxx.yyy@hrz
137.248.xxx.zzz@staff 137.248.aaa.bbb@students
director_servers = 172.25.1.42:9090 172.25.1.41:9090 172.25.1.92:9090
director_username_hash = %Ln@%Ld
doveadm_password = # hidden, use -P to show it
doveadm_port = 12345
imap_max_line_length = 640 k
lmtp_proxy = yes
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope
encoded-character vacation subaddress comparator-i;ascii-numeric
relational regex imap4flags copy include variables body enotify
environment mailbox date index ihave duplicate mime foreverypart extracttext
passdb {
  args = /etc/dovecot.deny
  deny = yes
  driver = passwd-file
}
passdb {
  args = /etc/dovecot/private/passwd.masterusers
  driver = passwd-file
  master = yes
}
passdb {
  args = /etc/dovecot/dovecot-ldap.staff.conf.ext
  driver = ldap
  result_success = continue-ok
}
passdb {
  args = /etc/dovecot/migration/migrate-staff
  driver = passwd-file
  name = passdb_staff_query
}
passdb {
  args = /etc/dovecot/dovecot-ldap.students.conf.ext
  driver = ldap
  result_success = continue-ok
}
passdb {
  args = /etc/dovecot/migration/migrate-students
  driver = passwd-file
  name = 

Re: cannot login to imap under load

[Piper Andreas]

Hello,

> 
> It does indeed run from systemd, so this is what's currently in the
> dovecot unit file ( /etc/systemd/system/dovecot.service ):
> 
...
> [Service]
> Type=simple
> ExecStart=/usr/sbin/dovecot -F
> NonBlocking=yes
> TasksMax=1
> LIMIT_NOFILE=1

...

the parameter should be named

LimitNOFile=1

(without the underscore), see
http://man7.org/linux/man-pages/man7/systemd.directives.7.html and
http://man7.org/linux/man-pages/man5/systemd.exec.5.html


--Andreas




smime.p7s
Description: S/MIME Cryptographic Signature

Re: 2.2.25 dumps core with "Panic: file imap-client.c: line 837 (client_check_command_hangs): assertion failed: (client->io != NULL)"

[Piper Andreas]

Am 12.09.2016 um 08:16 schrieb Aki Tuomi:
> 
> 
> On 12.09.2016 09:02, Piper Andreas wrote:
>> Am 01.09.2016 um 14:17 schrieb Aki Tuomi:
>>>
>>> On 01.09.2016 14:20, Piper Andreas wrote:
>>>> Hello Timo,
>>>>
>>>> with the newly build CSW-package the crashes still occur, today already
>>>> twice within two hours. The log shows always the same:
>>>>
>>>> Sep  1 11:50:13 surz113 dovecot: [ID 583609 mail.crit] imap(user):
>>>> Panic: file imap-client.c: line 837 (client_check_command_hangs):
>>>> assertion failed: (client->io != NULL)
>>>> Sep  1 11:50:13 surz113 dovecot: [ID 583609 mail.error] imap(user):
>>>> Error: Raw backtrace: 0x80ffb633d88d -> 0x80ffb636ae82 ->
>>>> 0x41eba0 -> 0x41ecf3 -> 0x80ffb635d248 -> 0x80ffb6350d2f ->
>>>> 0x80ffb63519e0 -> 0x80ffb6350dce -> 0x80ffb6350f90 ->
>>>> 0x80ffb62e3ebb -> 0x42f169 -> 0x41292c
>>>> Sep  1 11:50:13 surz113 dovecot: [ID 583609 mail.crit] imap(user):
>>>> Fatal: master: service(imap): child 11227 killed with signal 6 (core not
>>>> dumped - set service imap { drop_priv_before_exec=yes })
>>>>
>>>> This happens with different users, the last one with a relatively small
>>>> mailbox of 600MB.
>>>>
>>>> doveconf -n is attached.
>>>>
>>>> Dovecot 2.2.25
>>>> OS: Solaris 11 (SunOS 5.11 11.3 i86pc i386 i86pc)
>>>> Virtualization: VMware
>>>> Filesystem: ZFS
>>>> active users: ~4000
>>>>
>>>> The system was transferred at beginning of last week from an old
>>>> SPARC-station with Solaris 10 running dovecot-2.2.15 to this virtualized
>>>> platform under VMware. The mailboxes (maildir-format) were transferred
>>>> without change by switching the storage-hardware to the new server. I
>>>> had to remove all dovecot.index*-files for errors of "CPU Architecture
>>>> changed", but after doing this all seemed to work ok except for these
>>>> occasional crashes.
>>>>
>>>> If you need more information, please let me know.
>>>>
>>>> Thanks for any help,
>>>> Andreas
>>>>
>>>>> Hi Jake,
>>>>>
>>>>> thanks for fixing this. I have installed now the newly built package on
>>>>> my production system and will report, if any more core dumps occur.
>>>>>
>>>>> Regards,
>>>>> Andreas
>>>>>
>>> Hi!
>>>
>>> Is it possible for you test out a small patch (attached) to see if it
>>> fixes this issue?
>>>
>>> Aki
>>>
>> Hello Aki,
>>
>> your patch missed a trailing '{', which was corrected by the
>> OpenCSW-maintainer, who implemented the patch into a test-version of
>> dovecot-2.2.25 for me.
>>
>> I started this version on my production system on Friday morning (09.
>> Sep, 07:30). After that the server crashed once on Sunday evening
>> (11.Sep, 20:40), but with a completely different error message:
>>
>> Sep 11 20:40:37 surz113 dovecot: [ID 583609 mail.crit] imap(user1):
>> Panic: file imap-fetch.c: line 555 (imap_fetch_more): assertion failed:
>> (ctx->client->output_cmd_lock == NULL || ctx->client->output_cmd_lock ==
>> cmd)
>> Sep 11 20:40:37 surz113 dovecot: [ID 583609 mail.error] imap(user1):
>> Error: Raw backtrace: 0x80ffb5fcd88d -> 0x80ffb5ffae82 ->
>> 0x4225c1 -> 0x4153e5 -> 0x41ffae -> 0x41e4bf -> 0x41e865 -> 0x41ede4 ->
>> 0x80ffb5fe0d2f -> 0x80ffb5fe19e0 -> 0x80ffb5fe0dce ->
>> 0x80ffb5fe0f90 -> 0x80ffb5f73ebb -> 0x42f169 -> 0x41292c
>> Sep 11 20:40:37 surz113 dovecot: [ID 583609 mail.crit] imap(user1):
>> Fatal: master: service(imap): child 12150 killed with signal 6 (core not
>> dumped - set service imap { drop_priv_before_exec=yes })
>>
>> May this be related to your patch, or is it something completely different?
>>
>> Thanks and best regards,
>> Andreas
> Hi!
> 
> Apologies, I forgot to send you an email about this, it should be fixed with
> https://github.com/dovecot/core/commit/cd9cf45dcf9fcabc89e156117c4dcf464ec4eb85
> 
> Aki
> 

Hello and thanks for this information,

the OpenCSW-maintainer has implemented this fix into another test
version, which is now running on my production system. I'll report, if
there are any more problems.

Best regards,
Andreas




smime.p7s
Description: S/MIME Cryptographic Signature

Re: 2.2.25 dumps core with "Panic: file imap-client.c: line 837 (client_check_command_hangs): assertion failed: (client->io != NULL)"

[Piper Andreas]

Am 01.09.2016 um 14:17 schrieb Aki Tuomi:
> 
> 
> On 01.09.2016 14:20, Piper Andreas wrote:
>> Hello Timo,
>>
>> with the newly build CSW-package the crashes still occur, today already
>> twice within two hours. The log shows always the same:
>>
>> Sep  1 11:50:13 surz113 dovecot: [ID 583609 mail.crit] imap(user):
>> Panic: file imap-client.c: line 837 (client_check_command_hangs):
>> assertion failed: (client->io != NULL)
>> Sep  1 11:50:13 surz113 dovecot: [ID 583609 mail.error] imap(user):
>> Error: Raw backtrace: 0x80ffb633d88d -> 0x80ffb636ae82 ->
>> 0x41eba0 -> 0x41ecf3 -> 0x80ffb635d248 -> 0x80ffb6350d2f ->
>> 0x80ffb63519e0 -> 0x80ffb6350dce -> 0x80ffb6350f90 ->
>> 0x80ffb62e3ebb -> 0x42f169 -> 0x41292c
>> Sep  1 11:50:13 surz113 dovecot: [ID 583609 mail.crit] imap(user):
>> Fatal: master: service(imap): child 11227 killed with signal 6 (core not
>> dumped - set service imap { drop_priv_before_exec=yes })
>>
>> This happens with different users, the last one with a relatively small
>> mailbox of 600MB.
>>
>> doveconf -n is attached.
>>
>> Dovecot 2.2.25
>> OS: Solaris 11 (SunOS 5.11 11.3 i86pc i386 i86pc)
>> Virtualization: VMware
>> Filesystem: ZFS
>> active users: ~4000
>>
>> The system was transferred at beginning of last week from an old
>> SPARC-station with Solaris 10 running dovecot-2.2.15 to this virtualized
>> platform under VMware. The mailboxes (maildir-format) were transferred
>> without change by switching the storage-hardware to the new server. I
>> had to remove all dovecot.index*-files for errors of "CPU Architecture
>> changed", but after doing this all seemed to work ok except for these
>> occasional crashes.
>>
>> If you need more information, please let me know.
>>
>> Thanks for any help,
>> Andreas
>>
>>> Hi Jake,
>>>
>>> thanks for fixing this. I have installed now the newly built package on
>>> my production system and will report, if any more core dumps occur.
>>>
>>> Regards,
>>> Andreas
>>>
> 
> Hi!
> 
> Is it possible for you test out a small patch (attached) to see if it
> fixes this issue?
> 
> Aki
> 

Hello Aki,

your patch missed a trailing '{', which was corrected by the
OpenCSW-maintainer, who implemented the patch into a test-version of
dovecot-2.2.25 for me.

I started this version on my production system on Friday morning (09.
Sep, 07:30). After that the server crashed once on Sunday evening
(11.Sep, 20:40), but with a completely different error message:

Sep 11 20:40:37 surz113 dovecot: [ID 583609 mail.crit] imap(user1):
Panic: file imap-fetch.c: line 555 (imap_fetch_more): assertion failed:
(ctx->client->output_cmd_lock == NULL || ctx->client->output_cmd_lock ==
cmd)
Sep 11 20:40:37 surz113 dovecot: [ID 583609 mail.error] imap(user1):
Error: Raw backtrace: 0x80ffb5fcd88d -> 0x80ffb5ffae82 ->
0x4225c1 -> 0x4153e5 -> 0x41ffae -> 0x41e4bf -> 0x41e865 -> 0x41ede4 ->
0x80ffb5fe0d2f -> 0x80ffb5fe19e0 -> 0x80ffb5fe0dce ->
0x80ffb5fe0f90 -> 0x80ffb5f73ebb -> 0x42f169 -> 0x41292c
Sep 11 20:40:37 surz113 dovecot: [ID 583609 mail.crit] imap(user1):
Fatal: master: service(imap): child 12150 killed with signal 6 (core not
dumped - set service imap { drop_priv_before_exec=yes })

May this be related to your patch, or is it something completely different?

Thanks and best regards,
Andreas
-- 

Dr. Andreas Piper, Hochschulrechenzentrum der Philipps-Univ. Marburg
  Hans-Meerwein-Straße, 35032 Marburg, Germany
Phone: +49 6421 28-23521  Fax: -26994  E-Mail: pi...@hrz.uni-marburg.de



smime.p7s
Description: S/MIME Cryptographic Signature

Re: 2.2.25 dumps core with "Panic: file imap-client.c: line 837 (client_check_command_hangs): assertion failed: (client->io != NULL)"

[Piper Andreas]

Am 01.09.2016 um 14:17 schrieb Aki Tuomi:
> 
> 
> On 01.09.2016 14:20, Piper Andreas wrote:
>> Hello Timo,
>>
>> with the newly build CSW-package the crashes still occur, today already
>> twice within two hours. The log shows always the same:
>>
>> Sep  1 11:50:13 surz113 dovecot: [ID 583609 mail.crit] imap(user):
>> Panic: file imap-client.c: line 837 (client_check_command_hangs):
>> assertion failed: (client->io != NULL)
>> Sep  1 11:50:13 surz113 dovecot: [ID 583609 mail.error] imap(user):
>> Error: Raw backtrace: 0x80ffb633d88d -> 0x80ffb636ae82 ->
>> 0x41eba0 -> 0x41ecf3 -> 0x80ffb635d248 -> 0x80ffb6350d2f ->
>> 0x80ffb63519e0 -> 0x80ffb6350dce -> 0x80ffb6350f90 ->
>> 0x80ffb62e3ebb -> 0x42f169 -> 0x41292c
>> Sep  1 11:50:13 surz113 dovecot: [ID 583609 mail.crit] imap(user):
>> Fatal: master: service(imap): child 11227 killed with signal 6 (core not
>> dumped - set service imap { drop_priv_before_exec=yes })
>>
>> This happens with different users, the last one with a relatively small
>> mailbox of 600MB.
>>
>> doveconf -n is attached.
>>
>> Dovecot 2.2.25
>> OS: Solaris 11 (SunOS 5.11 11.3 i86pc i386 i86pc)
>> Virtualization: VMware
>> Filesystem: ZFS
>> active users: ~4000
>>
>> The system was transferred at beginning of last week from an old
>> SPARC-station with Solaris 10 running dovecot-2.2.15 to this virtualized
>> platform under VMware. The mailboxes (maildir-format) were transferred
>> without change by switching the storage-hardware to the new server. I
>> had to remove all dovecot.index*-files for errors of "CPU Architecture
>> changed", but after doing this all seemed to work ok except for these
>> occasional crashes.
>>
>> If you need more information, please let me know.
>>
>> Thanks for any help,
>> Andreas
>>
>>> Hi Jake,
>>>
>>> thanks for fixing this. I have installed now the newly built package on
>>> my production system and will report, if any more core dumps occur.
>>>
>>> Regards,
>>> Andreas
>>>
> 
> Hi!
> 
> Is it possible for you test out a small patch (attached) to see if it
> fixes this issue?
> 
> Aki
> 

Hello and thanks for this patch,

I will try to have it implemented by the OpenCSW-maintainers for a test
version as I do not have a compilation environment ready at hand.

I'll report the results asap.

Thanks again,
Andreas





smime.p7s
Description: S/MIME Cryptographic Signature

Re: 2.2.25 dumps core with "Panic: file imap-client.c: line 837 (client_check_command_hangs): assertion failed: (client->io != NULL)"

[Piper Andreas]

Hello Timo,

with the newly build CSW-package the crashes still occur, today already
twice within two hours. The log shows always the same:

Sep  1 11:50:13 surz113 dovecot: [ID 583609 mail.crit] imap(user):
Panic: file imap-client.c: line 837 (client_check_command_hangs):
assertion failed: (client->io != NULL)
Sep  1 11:50:13 surz113 dovecot: [ID 583609 mail.error] imap(user):
Error: Raw backtrace: 0x80ffb633d88d -> 0x80ffb636ae82 ->
0x41eba0 -> 0x41ecf3 -> 0x80ffb635d248 -> 0x80ffb6350d2f ->
0x80ffb63519e0 -> 0x80ffb6350dce -> 0x80ffb6350f90 ->
0x80ffb62e3ebb -> 0x42f169 -> 0x41292c
Sep  1 11:50:13 surz113 dovecot: [ID 583609 mail.crit] imap(user):
Fatal: master: service(imap): child 11227 killed with signal 6 (core not
dumped - set service imap { drop_priv_before_exec=yes })

This happens with different users, the last one with a relatively small
mailbox of 600MB.

doveconf -n is attached.

Dovecot 2.2.25
OS: Solaris 11 (SunOS 5.11 11.3 i86pc i386 i86pc)
Virtualization: VMware
Filesystem: ZFS
active users: ~4000

The system was transferred at beginning of last week from an old
SPARC-station with Solaris 10 running dovecot-2.2.15 to this virtualized
platform under VMware. The mailboxes (maildir-format) were transferred
without change by switching the storage-hardware to the new server. I
had to remove all dovecot.index*-files for errors of "CPU Architecture
changed", but after doing this all seemed to work ok except for these
occasional crashes.

If you need more information, please let me know.

Thanks for any help,
Andreas

> Hi Jake,
> 
> thanks for fixing this. I have installed now the newly built package on
> my production system and will report, if any more core dumps occur.
> 
> Regards,
> Andreas
> 
# 2.2.25 (7be1766): /etc/opt/csw/dovecot/dovecot.conf
# OS: SunOS 5.11 i86pc  
auth_cache_negative_ttl = 0
auth_cache_size = 10 M
auth_master_user_separator = *
auth_username_chars = 
abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_
auth_username_format = %u
auth_worker_max_count = 1024
base_dir = /var/run/dovecot/
default_vsz_limit = 2 G
first_valid_gid = 3
first_valid_uid = 3
mail_location = maildir:%h/.maildir
mail_plugins = " mail_log notify"
mail_privileged_group = mail
namespace {
  hidden = no
  inbox = yes
  list = yes
  location = maildir:%h/.maildir
  prefix = 
  separator = /
  subscriptions = yes
  type = private
}
namespace inbox {
  hidden = yes
  inbox = no
  list = no
  location = maildir:%h/.maildir
  prefix = mail/
  separator = /
  subscriptions = no
  type = private
}
passdb {
  args = /etc/dovecot.deny
  deny = yes
  driver = passwd-file
}
passdb {
  args = /etc/opt/csw/dovecot/private/passwd.masterusers
  driver = passwd-file
  master = yes
}
passdb {
  args = blocking=yes cache_key=%u%s *
  driver = pam
}
pop3_uidl_format = %08Xv%08Xu
postmaster_address = postmas...@staff.uni-marburg.de
protocols = imap pop3
service auth-worker {
  user = $default_internal_user
}
service auth {
  client_limit = 6000
}
service imap-login {
  process_min_avail = 64
  service_count = 0
}
service imap {
  process_limit = 6000
}
ssl_cert = 

smime.p7s
Description: S/MIME Cryptographic Signature

Re: 2.2.25 dumps core with "Panic: file imap-client.c: line 837 (client_check_command_hangs): assertion failed: (client->io != NULL)"

[Piper Andreas]

Hi Jake,

thanks for fixing this. I have installed now the newly built package on
my production system and will report, if any more core dumps occur.

Regards,
Andreas

Am 31.08.2016 um 20:19 schrieb Jake Goerzen:
> Hi Andreas & Timo,
> 
> 
>   I've found out what is causing the incorrect hash in the built
> packages.  Our build system use here at OpenCSW has internal git
> patching capability.  I disabled it and rebuild again.  This time all
> architectures and memory model's are reporting the correct git-commit
> hash 7be1766.  Thank you Andreas for noticing and reporting this.
> 
> 
> regards,
> 
> Jake
> 
> 
> On 08/31/2016 06:17 AM, Piper Andreas wrote:
>> Hello Timo,
>>
>> from the maintainer of the OpenCSW package I got the below answer.
>>
>> As the newly build package yields another different commit hash (which I
>> cannot find on GitHub too), I would ask, if you are sure that the commit
>> hash-output in 'doveconf -n' is generated correctly?
>>
>> The headline of 'doveconf -n' with the newly build package is
>> # 2.2.25 (68082dc): /etc/opt/csw/dovecot/dovecot.conf
>>
>> Many thanks for your help,
>> Andreas
>>
>>  Weitergeleitete Nachricht 
>> Betreff: Re: OpenCSW question about package CSWdovecot
>> Datum: Tue, 30 Aug 2016 08:56:44 -0700
>> Von: jgoerzen <jgoer...@opencsw.org>
>> An: pi...@hrz.uni-marburg.de
>>
>> Hello Andreas,
>>
>>
>> The OpenCSW dovecot package was built using the 2.2.25 version
>> release tarball.  No code changes or patches have been applied. I'm not
>> sure what happened.  I will respin new packages and then check to see if
>> the git-commit hash is correct.  When the packages are done building
>> I'll put them in the experimental catalog:
>>
>>
>> http://buildfarm.opencsw.org/experimental.html#jgoerzen
>>
>>
>> Thanks,
>>
>> Jake
>>
>>
>>
>>
>>
>>
>>
>> On 08/29/2016 11:59 PM, pi...@hrz.uni-marburg.de wrote:
>>> Hello,
>>>
>>> with your newest dovecot-package 2.2.25,REV=2016.07.01, I sometimes
>>> get core-dumps as documented in my bug-report at the
>>> dovecot-mailing-list:
>>> http://dovecot.org/list/dovecot/2016-August/105321.html
>>> In reaction to my bug-report, Timo Sirainen asks, which git-commit of
>>> the dovecot-sources was used for this package:
>>> http://dovecot.org/list/dovecot/2016-August/105332.html
>>>
>>> Could you shed some light on this?
>>>
>>> Thanks a lot,
>>> Andreas
>>
> 






smime.p7s
Description: S/MIME Cryptographic Signature

Re: 2.2.25 dumps core with "Panic: file imap-client.c: line 837 (client_check_command_hangs): assertion failed: (client->io != NULL)"

[Piper Andreas]

Hello Timo,

from the maintainer of the OpenCSW package I got the below answer.

As the newly build package yields another different commit hash (which I
cannot find on GitHub too), I would ask, if you are sure that the commit
hash-output in 'doveconf -n' is generated correctly?

The headline of 'doveconf -n' with the newly build package is
# 2.2.25 (68082dc): /etc/opt/csw/dovecot/dovecot.conf

Many thanks for your help,
Andreas

 Weitergeleitete Nachricht 
Betreff: Re: OpenCSW question about package CSWdovecot
Datum: Tue, 30 Aug 2016 08:56:44 -0700
Von: jgoerzen 
An: pi...@hrz.uni-marburg.de

Hello Andreas,


   The OpenCSW dovecot package was built using the 2.2.25 version
release tarball.  No code changes or patches have been applied. I'm not
sure what happened.  I will respin new packages and then check to see if
the git-commit hash is correct.  When the packages are done building
I'll put them in the experimental catalog:


http://buildfarm.opencsw.org/experimental.html#jgoerzen


Thanks,

Jake







On 08/29/2016 11:59 PM, pi...@hrz.uni-marburg.de wrote:
> Hello,
>
> with your newest dovecot-package 2.2.25,REV=2016.07.01, I sometimes get 
> core-dumps as documented in my bug-report at the dovecot-mailing-list: 
> http://dovecot.org/list/dovecot/2016-August/105321.html
> In reaction to my bug-report, Timo Sirainen asks, which git-commit of the 
> dovecot-sources was used for this package: 
> http://dovecot.org/list/dovecot/2016-August/105332.html
>
> Could you shed some light on this?
>
> Thanks a lot,
> Andreas




smime.p7s
Description: S/MIME Cryptographic Signature

Re: 2.2.25 dumps core with "Panic: file imap-client.c: line 837 (client_check_command_hangs): assertion failed: (client->io != NULL)"

[Piper Andreas]

Hello Timo,

> 
>> Find attached the output of 'doveconf -n'.
> ..
>> # 2.2.25 (f5ac02c): /etc/opt/csw/dovecot/dovecot.conf
> 
> What is this version? 2.2.25 release had 7be1766. I can't find any such 
> commit hash from git.
> 

This is the dovecot-package from OpenCSW:
https://www.opencsw.org/packages/CSWdovecot/
I have no idea, if these guys apply any changes to the code, but I'll
ask the maintainer.

Andreas




smime.p7s
Description: S/MIME Cryptographic Signature

2.2.25 dumps core with "Panic: file imap-client.c: line 837 (client_check_command_hangs): assertion failed: (client->io != NULL)"

[Piper Andreas]

Hello,

Dovecot 2.2.25
OS: Solaris 11 (SunOS 5.11 11.3 i86pc i386 i86pc)
Virtualization: VMware
Filesystem: ZFS
active users: ~4000

About once a day Dovecot crashes with
"Panic: file imap-client.c: line 837 (client_check_command_hangs):
assertion failed: (client->io != NULL)"

The log shows in each case:

Aug 29 12:59:00 surz113 dovecot: [ID 583609 mail.crit] imap(username):
Panic: file imap-client.c: line 837 (client_check_command_hangs):
assertion failed: (client->io != NULL)
Aug 29 12:59:00 surz113 dovecot: [ID 583609 mail.error] imap(username):
Error: Raw backtrace: 0x80ffb6f3d88d -> 0x80ffb6f6ae82 ->
0x41eba0 -> 0x41ecf3 -> 0x80ffb6f5d248 -> 0x80ffb6f50d2f ->
0x80ffb6f519e0 -> 0x80ffb6f50dce -> 0x80ffb6f50f90 ->
0x80ffb6ee3ebb -> 0x42f169 -> 0x41292c
Aug 29 12:59:00 surz113 dovecot: [ID 583609 mail.crit] imap(username):
Fatal: master: service(imap): child 1461 killed with signal 6 (core not
dumped - set service imap { drop_priv_before_exec=yes })

It happens with different users, all with mailbox-sizes of 9 to 17
GByte. The server stops completely for all users with this Panic and is
then restarted automatically from Solaris Service Management.

Find attached the output of 'doveconf -n'.

Please let me know, if you need any more infos.

Thanks for any help on this issue,
Andreas, postmas...@uni-marburg.de
# 2.2.25 (f5ac02c): /etc/opt/csw/dovecot/dovecot.conf
# OS: SunOS 5.11 i86pc  
auth_cache_negative_ttl = 0
auth_cache_size = 10 M
auth_master_user_separator = *
auth_username_chars = 
abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_
auth_username_format = %u
auth_worker_max_count = 1024
base_dir = /var/run/dovecot/
default_vsz_limit = 2 G
first_valid_gid = 3
first_valid_uid = 3
mail_location = maildir:%h/.maildir
mail_plugins = " mail_log notify"
mail_privileged_group = mail
namespace {
  hidden = no
  inbox = yes
  list = yes
  location = maildir:%h/.maildir
  prefix = 
  separator = /
  subscriptions = yes
  type = private
}
namespace inbox {
  hidden = yes
  inbox = no
  list = no
  location = maildir:%h/.maildir
  prefix = mail/
  separator = /
  subscriptions = no
  type = private
}
passdb {
  args = /etc/dovecot.deny
  deny = yes
  driver = passwd-file
}
passdb {
  args = 
  driver = passwd-file
  master = yes
}
passdb {
  args = blocking=yes cache_key=%u%s *
  driver = pam
}
pop3_uidl_format = %08Xv%08Xu
postmaster_address = postmas...@staff.uni-marburg.de
protocols = imap pop3
service auth-worker {
  user = $default_internal_user
}
service auth {
  client_limit = 6000
}
service imap-login {
  process_min_avail = 64
  service_count = 0
}
service imap {
  process_limit = 6000
}
ssl_cert = 

smime.p7s
Description: S/MIME Cryptographic Signature

[Dovecot] Dovecot 2.2.1: typo in src/lib-http/Makefile.in

[Piper Andreas]

Hello,

there seems to be a typo in the dovecot-2.2.1-sources:

in dovecot-2.2.1/src/lib-http/Makefile.in at line 758 the two lines

   ../lib-test/libtest.la \
   ../lib/liblib.la

do not fit into the Makefile-syntax. At compile-time they produce the error

make: Fatal error in reader: Makefile, line 725: Unexpected end of line seen

If I remove these two lines, everything compiles fine.

Could you please check this.

Thanks, Andreas
-- 

Dr. Andreas Piper, Hochschulrechenzentrum der Philipps-Univ. Marburg
  Hans-Meerwein-Straße, 35032 Marburg, Germany
Phone: +49 6421 28-23521  Fax: -26994  E-Mail: pi...@hrz.uni-marburg.de