Re: Crashes in lmtpproxyd, and a patch

2015-11-27 Thread Giles Malet via Cyrus-devel
h->conn = backend_connect(NULL, server, &mupdate_protocol, "", cbs, &status); Sorry, the crash is actually a few lines lower; it's dying in a call to syslog. For some reason my core file is not lining up properly, and that confused me: if (!h->conn) {

Re: Crashes in lmtpproxyd, and a patch

2015-11-27 Thread Giles Malet via Cyrus-devel
Again, conn is null at this point Er, sorry, that doesn't make sense that it crashes. I'll dig some more. g

Re: Crashes in lmtpproxyd, and a patch

2015-11-27 Thread Giles Malet via Cyrus-devel
Looking further, I found core files on the mupdate master, from mupdate, and suspect these are correlated with the downstream crashes. In this case the crash is here: #0 0x0036ed647e2c in vfprintf () from /lib64/libc.so.6 #1 0x0036ed6e4f10 in __vsyslog_chk () from /lib64/libc.so.6 #2

Crashes in lmtpproxyd, and a patch

2015-11-27 Thread Giles Malet via Cyrus-devel
We have a bunch of servers in a murder, and I recently took a look in /var/lib/imap/cores and found core files for lmtpd/lmtpproxyd all over the place. These seem to be generated in waves, and can occur on the front end imap proxy servers, the incoming e-mail servers, and the mailbox servers --