[Bug 219821] mail/dovecot2: occasional auth process crashing as of 2.2.30.1
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Tue Jun 6 13:11:58 UTC 2017
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219821
Bug ID: 219821
Summary: mail/dovecot2: occasional auth process crashing as of
2.2.30.1
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Keywords: crash, regression
Severity: Affects Some People
Priority: ---
Component: Individual Port(s)
Assignee: adamw at FreeBSD.org
Reporter: vlad-fbsd at acheronmedia.com
Assignee: adamw at FreeBSD.org
Flags: maintainer-feedback?(adamw at FreeBSD.org)
Since the upgrade to 2.2.30.1, I see occasional auth process crashes:
> Jun 06 11:11:27 auth: Panic: file auth-request-handler.c: line 849 (auth_request_handler_flush_failures): assertion failed: (auth_request->state == AUTH_REQUEST_STATE_FINISHED)
> Jun 06 11:11:27 auth: Fatal: master: service(auth): child 76992 killed with signal 6 (core not dumped - set service auth { drop_priv_before_exec=yes })
> Jun 06 11:11:27 imap-login: Info: Disconnected (auth process communication failure): user=<>, method=PLAIN, rip=<CENSORED>, lip=10.0.0.8, TLS, session=<A4jJAEdRlCJbw2cs>
With the kernel logging SIGABRT:
> Jun 6 11:11:27 xoth kernel: pid 76992 (auth), uid 143: exited on signal 6
Also:
> Jun 06 14:07:43 auth: Fatal: master: service(auth): child 84326 killed with signal 11 (core not dumped - set service auth { drop_priv_before_exec=yes })
> Jun 06 14:36:42 auth: Fatal: master: service(auth): child 9104 killed with signal 11 (core not dumped - set service auth { drop_priv_before_exec=yes })
With the kernel logging SIGSEGV on both.
Talking to people in #dovecot on Freenode, it appears to be known issue, and
there are similar reports upstream in thread like this:
https://www.dovecot.org/pipermail/dovecot/2017-June/108266.html
So this PR is just a heads-up to the maintainer and a log that it has been
noticed happening on FreeBSD too.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list