/usr/libexec/dovecot/anvil crashes immediately
Dear list,
I built a dovecot package for openindiana (which is a Solaris derivative) from latest version 2.3.18. Everything compiles and builds fine without any issue. Even subsequent installation and startup of main dovecot process works as expected. But execution of /usr/libexec/dovecot/anvil immediately crashes. To get some more meaningful backtrace I compiled with -g. Below some facts of my environment and a backtrace. Maybe some of you are more familiar with this kind of issue as I, and can give some hint or share ideas how to nail down the problem. Or can it be a configuration issue? BTW it is running in a so-called zone. And former versions, I don't know exactly but I believe up to 2.3.17, did not show this crash.
gcc --version gcc (OpenIndiana 7.5.0-il-0) 7.5.0
Configure parameters:
gcc_OPT = -g
CONFIGURE_OPTIONS+= --sysconfdir=/etc
--localstatedir=/var
--with-gssapi=plugin
--with-ldap=plugin
--with-sql=plugin
--with-lua=plugin
--with-ssl=openssl
--with-ioloop=poll
--with-notify=none
--with-sodium
--with-mysql
--with-pgsql
--enable-static=no
--without-systemd
SSL_CFLAGS=-I/usr/openssl/1.1/include
SSL_LIBS="-L/usr/openssl/1.1/lib/amd64 -lssl
-lcrypto"
LDFLAGS="-lldap_r"
Backtrace:
(gdb) bt full
#0 0x00007fff5d2e6f2a in _lwp_kill () from /lib/64/libc.so.1
No symbol table info available.
#1 0x00007fff5d2dd7f0 in thr_kill () from /lib/64/libc.so.1
No symbol table info available.
#2 0x00007fff5d27ae7e in raise () from /lib/64/libc.so.1
No symbol table info available.
#3 0x00007fff5d254ad8 in abort () from /lib/64/libc.so.1
No symbol table info available.
#4 0x00007ffef05367c0 in default_fatal_finish (type=LOG_TYPE_PANIC,
status=0) at
/usr/src/myoi-userland/components/mail/dovecot/dovecot-2.3.18/src/lib/failures.c:459
backtrace = 0x4178b8
"/usr/lib/amd64/dovecot/libdovecot.so.0.0.0'backtrace_append_libc+0x4c
[0x7ffef0522042] ->
/usr/lib/amd64/dovecot/libdovecot.so.0.0.0'backtrace_append+0x18
[0x7ffef05221c5] -> /usr/lib/amd64/dovecot/li"...
recursed = 0
#5 0x00007ffef0536827 in fatal_handler_real (ctx=0x7fffbffff820,
format=0x7ffef05d8730 "file %s: line %d (%s): assertion failed: (%s)",
args=0x7fffbffff850)
at
/usr/src/myoi-userland/components/mail/dovecot/dovecot-2.3.18/src/lib/failures.c:471
status = 0
#6 0x00007ffef0536871 in default_fatal_handler (ctx=0x7fffbffff820,
format=0x7ffef05d8730 "file %s: line %d (%s): assertion failed: (%s)",
args=0x7fffbffff850)
at
/usr/src/myoi-userland/components/mail/dovecot/dovecot-2.3.18/src/lib/failures.c:479
No locals.
#7 0x00007ffef0536aed in i_panic (format=0x7ffef05d8730 "file %s: line
%d (%s): assertion failed: (%s)") at
/usr/src/myoi-userland/components/mail/dovecot/dovecot-2.3.18/src/lib/failures.c:524
ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp = 0x0,
timestamp_usecs = 0, log_prefix = 0x0, log_prefix_type_pos = 0}
args = {{gp_offset = 8, fp_offset = 48, overflow_arg_area =
0x7fffbffff930, reg_save_area = 0x7fffbffff870}}
#8 0x00007ffef056048b in io_loop_handle_add (io=0x42d7c0) at
/usr/src/myoi-userland/components/mail/dovecot/dovecot-2.3.18/src/lib/ioloop-poll.c:94
ctx = 0x423180
condition = IO_READ
old_count = 3221223792
index = 0
old_events = 59
fd = 4
__func__ = "io_loop_handle_add"
#9 0x00007ffef055c1ab in io_add_file (ioloop=0x423070, fd=4,
condition=IO_READ, source_filename=0x7ffef05d9f48
"/usr/src/myoi-userland/components/mail/dovecot/dovecot-2.3.18/src/lib/lib-signals.c",
source_linenum=192, callback=0x7ffef05698f4
Thanks a lot for any help,
Fritz
On 08/02/2022 20:04, Friedrich Kink wrote:
I built a dovecot package for openindiana (which is a Solaris derivative) from latest version 2.3.18. Everything compiles and builds fine without any issue. Even subsequent installation and startup of main dovecot process works as expected. But execution of /usr/libexec/dovecot/anvil immediately crashes.
I can't see what is wrong from your trace. You might get more help on the OpenIndiana mailing list.
I run dovecot on OmniOS (also a Solaris / illuminos derivative) without problem. I wonder why you are running dovecot on openindiana which is focused for desktop use; why not use OmniOS for a server? Your choice but you could run OpenIndiana global with a bhyve zone running OmniOS.
James.
participants (2)
-
Friedrich Kink
-
James