Displaying 4 results from an estimated 4 matches for "jeffandjessi".
2017 Jun 02
1
updated to dove 2.30.1 and still the same error ....
Well.. updated to 2.30.1 hoping it would fix this mysterious seg fault
... ,but nope ...
auth: Fatal: master: service(auth): child 14502 killed with signal 11
(core dumped)
the core dump shows
gdb) bt #0 0x00007f7ff4a06bee in ?? ()
#1 0x00007f7ff74a4f44 in io_loop_handle_remove () from
/usr/local/lib/dovecot/libdovecot.so.0
#2 0x00007f7ff74a3765 in io_remove_full () from
2017 May 22
1
dovecot: auth-worker: Fatal: master: service(auth-worker): child XXXXX killed with signal 11
Trying to track down a dovecot issue ....
The error message is:
dovecot: auth-worker: Fatal: master: service(auth-worker): child XXXXX
killed with signal 11 (core not dumped - set service auth-worker {
drop_priv_before_exec=yes })
The setup is dovecot 2.2.29.1 with passwd and mysql auth db's and a very
basic config.
both authentications work ... the symptom is that after a connection
2017 May 26
1
dovecot: auth-worker: Fatal: master: service(auth-worker): child XXXXX killed with signal 11
Still Trying to track down a dovecot issue ....
The error message is:
dovecot: auth-worker: Fatal: master: service(auth-worker): child XXXXX
killed with signal 11 (core not dumped - set service auth-worker {
drop_priv_before_exec=yes })
The setup is dovecot 2.2.29.1 with passwd and mysql auth db's and a very
basic config.
both authentications work ... the symptom is that after a
2017 May 24
0
dovecot: auth-worker: Fatal: master: service(auth-worker): child XXXXX killed with signal 11
Trying to track down a dovecot issue ....
The error message is:
dovecot: auth-worker: Fatal: master: service(auth-worker): child XXXXX
killed with signal 11 (core not dumped - set service auth-worker {
drop_priv_before_exec=yes })
The setup is dovecot 2.2.29.1 with passwd and mysql auth db's and a very
basic config.
both authentications work ... the symptom is that after a connection