"systemctl reload docecot" crashed.
   systemctl start and restart work fine before and after the reload crash.
   Running on archlinux (using the arch dovecot 2.4.1 package).
   Probably about 15-20 connected clients at time of crash .
   Is this a known issue I wonder?
   thanks
   gene
   All I have at this point is systemd reported trace of the crash:
   Process 1381 (dovecot) of user 0 dumped core.
   Stack trace of thread 1381:
   #0 0x00007e78fad7ed1d n/a (libc.so.6 + 0x16ed1d)
   #1 0x00007e78fac758d8 n/a (libc.so.6 + 0x658d8)
   #2 0x00007e78fac99e2e n/a (libc.so.6 + 0x89e2e)
   #3 0x00007e78fac705d6 snprintf (libc.so.6 + 0x605d6)
   #4 0x00007e78fad271e1 n/a (libc.so.6 + 0x1171e1)
   #5 0x00007e78fad27943 __syslog_chk (libc.so.6 + 0x117943)
   #6 0x00007e78faf38ce5 n/a (libdovecot.so.0 + 0x138ce5)
   #7 0x00007e78faf36d4d n/a (libdovecot.so.0 + 0x136d4d)
   #8 0x00007e78faf3701e i_syslog_error_handler (libdovecot.so.0 + 0x13701e)
   #9 0x000058ca208bd7bf n/a (/usr/bin/dovecot + 0x87bf)
   #10 0x00007e78faf355e6 i_warning (libdovecot.so.0 + 0x1355e6)
   #11 0x000058ca208c79fa n/a (/usr/bin/dovecot + 0x129fa)
   #12 0x00007e78faf5b698 n/a (libdovecot.so.0 + 0x15b698)
   #13 0x00007e78faf536e4 io_loop_call_io (libdovecot.so.0 + 0x1536e4)
   #14 0x00007e78faf54c8b io_loop_handler_run_internal (libdovecot.so.0 +
   0x154c8b)
   #15 0x00007e78faf54d47 io_loop_handler_run (libdovecot.so.0 + 0x154d47)
   #16 0x00007e78faf54f49 io_loop_run (libdovecot.so.0 + 0x154f49)
   #17 0x00007e78fae9fc00 master_service_run (libdovecot.so.0 + 0x9fc00)
   #18 0x000058ca208bd017 main (/usr/bin/dovecot + 0x8017)
   #19 0x00007e78fac376b5 n/a (libc.so.6 + 0x276b5)
   #20 0x00007e78fac37769 __libc_start_main (libc.so.6 + 0x27769)
   #21 0x000058ca208bd605 _start (/usr/bin/dovecot + 0x8605)
   ELF object binary architecture: AMD x86-64
   --
   Gene

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
dovecot mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to