Re: auth-worker fatal signal 11 core dump

FYI, I was able to get Portunus up with Openldap 2.6.4 to test Dovecot, but auth/auth-worker still crash as with 2.6.3. As before the authentication works fine. Is it the case that Dovecot has no issue tracker? -- Anthony Carrico

Re: auth-worker fatal signal 11 core dump

On 4/5/23 10:31, Aki Tuomi wrote: Hi! The crash occurs inside libldap. Aki Thanks Aki, It was against openldap 2.6.3. Subsequently, I tried openldap 2.6.4 which is in nixpkgs unstable, but I wasn't able to test this because of an issue at the Portunus/openldap end of things. I think I'm ou

Re: auth-worker fatal signal 11 core dump

Hi!   The crash occurs inside libldap.   Aki On 05/04/2023 16:54 EEST Anthony Carrico wrote:     Here is the stack trace:      PID: 2

Re: auth-worker fatal signal 11 core dump

Here is the stack trace:    PID: 2084981 (auth) Oh, and here is the stack trace of the other pid which also dumped: $ sudo coredumpctl info 2084984 PID: 2084984 (auth) UID: 0 (root) GID: 0 (root) Signal: 11 (SEGV) Timestamp: Tue 2023-04-04

auth-worker fatal signal 11 core dump

I'm testing out dovecot/tls/openldap(via portunus). It seems to work fine. I can access Maildir with Thunderbird as expected. However according to the logs, auth-worker crashes when slapd closes: Apr 04 22:11:56 silver slapd[1745983]: conn=1054 op=1 UNBIND Apr 04 22:11:56 silver slapd[1745983]: