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

2016-09-14 Thread 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)"

2016-09-12 Thread 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

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

2016-09-12 Thread 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)"

2016-09-01 Thread 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)"

2016-09-01 Thread 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
diff --git a/src/imap/imap-client.c b/src/imap/imap-client.c
index 3327788..3a4a510 100644
--- a/src/imap/imap-client.c
+++ b/src/imap/imap-client.c
@@ -1055,9 +1055,7 @@ static bool client_handle_next_command(struct client *client, bool *remove_io_r)
 
 	if (client->input_lock != NULL) {
 		if (client->input_lock->state ==
-		CLIENT_COMMAND_STATE_WAIT_UNAMBIGUITY ||
-		(client->output_cmd_lock != NULL &&
-		 client->output_cmd_lock != client->input_lock)) {
+		CLIENT_COMMAND_STATE_WAIT_UNAMBIGUITY)
 			*remove_io_r = TRUE;
 			return FALSE;
 		}

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

2016-09-01 Thread 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)"

2016-08-31 Thread 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 
>> 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)"

2016-08-31 Thread 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 
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

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

2016-08-31 Thread 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)"

2016-08-30 Thread 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

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

2016-08-29 Thread Timo Sirainen 
On 29 Aug 2016, at 02:00, Piper Andreas  wrote:
> 
> Hello,
> 
> Dovecot 2.2.25
..
> About once a day Dovecot crashes with
> "Panic: file imap-client.c: line 837 (client_check_command_hangs):
> assertion failed: (client->io != NULL)"

I fixed one such crash in git master branch, but it was never in 2.2.25..

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

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

2016-08-29 Thread Aki Tuomi 


On 29.08.2016 15:00, Piper Andreas wrote:
> 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

Hi!

Thank you for your report, we are looking into this.

Aki Tuomi
Dovecot oy

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

2016-08-29 Thread 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