Hi Jamie,
I had these as well on a client server about a month ago for a few days
and they went away. They showed up in the postmaster logwatch email. I
traced them to the messages log.
I ran the following command (with output):
# cat messages* | grep -C 4 segfault
May 18 09:25:02 mail kernel: qmailmrtg[20759]: segfault at 604000 ip
0000000000400b17 sp 00007fff8f462560 error 4 in qmailmrtg[400000+2000]
May 18 09:25:02 mail abrt-server: Package 'qmailmrtg' isn't signed with
proper key
May 18 09:25:02 mail abrt-server: 'post-create' on
'/var/spool/abrt/ccpp-2016-05-18-09:25:02-20759' exited with 1
May 18 09:25:02 mail abrt-server: Deleting problem directory
'/var/spool/abrt/ccpp-2016-05-18-09:25:02-20759'
And, it looks like it has something to do with signing.
I got distracted and will have to investigate this further.
Eric
On 6/10/2016 9:15 AM, Jaime Lerner wrote:
I don't get segfaults from vchkpw anymore (not since raising my
softlimit), but I get from 1-3 segfaults from qmailmrtg daily. I don't
really need or want qmailmrtg, so if anyone can tell me how to turn it
off, that would be great. :) Otherwise, it's not causing any problems
for me since I don't use it.
[root@mail qmail]# grep segfault /var/log/messages
Jun 5 16:20:01 mail kernel: qmailmrtg[26761]: *segfault* at 604000 ip
0000000000400b17 sp 00007ffcbfdbc4a0 error 4 in qmailmrtg[400000+2000]
Jun 5 16:40:01 mail kernel: qmailmrtg[28163]: *segfault* at 604000 ip
0000000000400b17 sp 00007fffbac92110 error 4 in qmailmrtg[400000+2000]
Jun 5 16:55:01 mail kernel: qmailmrtg[29324]: *segfault* at 604000 ip
0000000000400b17 sp 00007fff8ca08810 error 4 in qmailmrtg[400000+2000]
Jun 6 12:20:01 mail kernel: qmailmrtg[30300]: *segfault* at 604000 ip
0000000000400b17 sp 00007ffe382ce270 error 4 in qmailmrtg[400000+2000]
Jun 7 11:25:01 mail kernel: qmailmrtg[10676]: *segfault* at 604000 ip
0000000000400b17 sp 00007fff0e24eff0 error 4 in qmailmrtg[400000+2000]
Jun 7 15:00:02 mail kernel: qmailmrtg[20856]: *segfault* at 604000 ip
0000000000400b17 sp 00007ffec310ee90 error 4 in qmailmrtg[400000+2000]
Jun 7 15:05:01 mail kernel: qmailmrtg[21134]: *segfault* at 604000 ip
0000000000400b17 sp 00007fff02dd4660 error 4 in qmailmrtg[400000+2000]
Jun 8 07:20:01 mail kernel: qmailmrtg[31909]: *segfault* at 604000 ip
0000000000400b17 sp 00007ffc923737e0 error 4 in qmailmrtg[400000+2000]
Jun 8 12:15:01 mail kernel: qmailmrtg[12908]: *segfault* at 604000 ip
0000000000400b17 sp 00007ffc75843060 error 4 in qmailmrtg[400000+2000]
Jun 9 12:15:01 mail kernel: qmailmrtg[11826]: *segfault* at 604000 ip
0000000000400b17 sp 00007ffd93dcda20 error 4 in qmailmrtg[400000+2000]
Jun 10 10:15:01 mail kernel: qmailmrtg[6510]: *segfault* at 604000 ip
0000000000400b17 sp 00007fff8e676c30 error 4 in qmailmrtg[400000+2000]
Jun 10 10:25:01 mail kernel: qmailmrtg[6931]: *segfault* at 604000 ip
0000000000400b17 sp 00007ffc884b8570 error 4 in qmailmrtg[400000+2000]
Jun 10 10:40:01 mail kernel: qmailmrtg[7683]: *segfault* at 604000 ip
0000000000400b17 sp 00007ffd97d86ab0 error 4 in qmailmrtg[400000+2000]
From: Steve Linberg <[email protected]
<mailto:[email protected]>>
Reply-To: <[email protected]
<mailto:[email protected]>>
Date: Friday, June 10, 2016 at 10:48 AM
To: <[email protected]
<mailto:[email protected]>>
Subject: Re: [qmailtoaster] vchkpw segfaults and spamdyke errors
Still working on the segfault problem; got dozens of them overnight when
I definitely wasn’t using any services. softlimit
in /var/qmail/supervise/submission/run is at 500 megs and rising, but
I’m still having trouble believing it needs to be that high or higher.
While I continue to push that: is there any way to know what process
chain is invoking the vchkpw process that’s segfaulting? Don’t a number
of different processes use it? I don’t know for a fact that submission
is the one that’s causing it. I can’t find any other clues in my logs,
like events happening at the same time as the segfaults, but are there
any other possible culprits that might invoke vchkpw without enough RAM
to do whatever it’s trying to do?
--
Steve Linberg, Chief Goblin
Silicon Goblin Technologies
http://silicongoblin.com
Be kind. Remember, everyone you meet is fighting a hard battle.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
