Re: mupdate thread died with SIGSEGV

[JoĆ£o Assad]

Joćo Assad wrote:

This doesnt seem to be related to the mmap problem

The only errors I got on cyrus log when it happened were a bunch of this:

Apr 10 16:35:03 cyrus-fe1 cyrus/lmtp[30983]: mupdate-client: connect(10.1.5.101): Connection timed out

This time I have strace and gdb logs. Im sending attached the last 1000 lines of the mupdate process strace, the last 1000 of the mupdate thread strace and the gdb trace I managed to extract from the core dump.

Note that strace was configured to not log futex calls.

I got the same error again this morning. Im sending new backtraces attached.

Regards

strace.thread.output.gz
Description: application/gzip-compressed

gdb.output.gz

Description: application/gzip-compressed


strace.process.output.gz

Description: application/gzip-compressed