tis 2021-01-19 klockan 10:58 -0800 skrev Noah Meyerhans: > On Tue, Jan 19, 2021 at 09:28:58AM +0100, Simon Josefsson wrote: > > Hi. I noticed the following in my log recently. Any ideas? > > > > Jan 6 14:55:54 uggla kernel: [145284.855936] imap[18530]: segfault > > at 8 ip 000055c38b20f97c sp 00007ffe4baaaa40 error 4 in > > imap[55c38b1f7000+24000] > > Jan 6 14:55:54 uggla kernel: [145284.855945] Code: 5d 41 5c 41 5d > > e9 2b ca fe ff 0f 1f 40 00 45 89 ec 48 89 df 48 39 eb 75 bd 48 8b > > 45 00 48 8d 35 da f4 00 00 41 bc ff ff ff ff <48> 8b 78 08 e8 8b 77 > > ff ff 48 83 c4 08 44 89 e0 5b 5d 41 5c 41 5d > > Jan 6 14:55:54 uggla dovecot: > > imap(simon)<18530><7bj6fTy4vsof0Co6>: Fatal: master: service(imap): > > child 18530 killed with signal 11 (core dumps disabled - > > https://dovecot.org/bugreport.html#coredumps) > > > > The 1:2.3.4.1-5+deb10u5 packages were installed on 2021-01-04: > > > > 2021-01-04 22:34:01 status installed dovecot-imapd:amd64 1:2.3.4.1- > > 5+deb10u5 > > > > The machine was restarted minutes after that, so on 2021-01-06 > > (segfault > > log output above) it should have be running then-current packages. > > > > I'm not able to use ALLOW_COREDUMPS=1 to make sure I get core dumps > > in > > the future, but I'll report that separately. > > It seems from #980444 that you've got coredumps working. Can you > provide a stack trace for this?
No it happened randomly and I cannot reproduce it. The server is working fine for day-to-day use, so this is not causing any problem but I wanted to report it anyway in case others are seeing the same thing or if is a security-related problem. I have enabled core dumps and also rawlogs now, so I will be able to provide more information if this happens again. As you can see, I was logged into my own account (from what appears to be one of my usual IPs), so I doubt it is someone attacking the server unauthorized. /Simon
