Symptoms
-
DMARC feature is enabled in Plesk at Tools & Settings > Mail Server Settings > Enable DMARC to check incoming mail.
-
The temporary mail files from
/usr/local/psa/handlers/spoolaren't removed and the disk space usage increases. -
In
/var/log/mail.logpersist following errors for emails from particular domains:CONFIG_TEXT: postfix-local[14661]: _mh_fork(): The child process with pid 14665 killed by signal 11
postfix-local[14661]: Error during 'dmarc' handler -
In
/var/log/messages:CONFIG_TEXT: kernel: [251579.818063] dmarc[14665]: segfault at 0 ip 00007f60f12ac0b0 sp 00007ffeeb867998 error 4 in libc-2.24.so[7f60f118b000+195000]
-
The following errors can be found in
dmesgoutput:# dmesg | grep 'segfault at'
[ 36.586810] dmarc[2446]: segfault at 0 ip 00007fe5465070b0 sp 00007ffd84f303e8 error 4 in libc-2.24.so[7fe5463e6000+195000]
Cause
Product issue:
- #PPPM-10547 "DMARC checks no longer result in a segmentation fault under specific circumstances, which caused errors to be written to the logs and temporary files not being cleaned up."
Fixed in:- Plesk Obsidian 21 January 2020 (Linux)
Resolution
Additional information
DMARC is segfaulted permanently: _mh_fork(): The child process with pid XXXX killed by signal 11
Comments
4 comments
Thank you for creating a bug ticket for this error what we have found.
I'm waiting for the solution. If you have any questions, or need more info, please pm me.
This can be helpful too: https://talk.plesk.com/threads/dmarc-changes-in-mu-51-introduce-new-segfault-error.352084/#post-863262
@Adam Dobruczky
I have forwarded this thread to the developers. Thank you for your cooperation!
That bug is still not solved mid October 2019 and has carried over to Obsidian as well.
Hello @TomBob,
You're right. There're plans to fix this bug.
However, the ETA will be available later.
Thank you for understanding.
Please sign in to leave a comment.