Notifications from ABRT are received: autoresponder killed by SIGABRT

Applicable to:

#PPPM-9637 "Autoresponder aborted in case of response frequency reached (as PPP-36512)"
Fixed in:
- Plesk Obsidian Release Candidate 1.0 04 June 2019
#PPP-36512 "Auto-reply no longer fails with an error if the response frequency is reached."
Fixed in:
- Plesk Obsidian Release Candidate 1.0 04 June 2019
- Plesk Onyx 17.9 Preview 6 25 September 2018 (Linux)

Please consider updating your server:

Notifications from ABRT are received:

CONFIG_TEXT: autoresponder killed by SIGABRT
In /var/log/messages the message below appeas:

CONFIG_TEXT: web1 abrt-hook-ccpp: Process 47804 (autoresponder) of user 30 killed by SIGABRT - dumping core
web1 abrt-hook-ccpp: Process 47591 (autoresponder) of user 30 killed by SIGABRT - dumping core
web1 abrt-hook-ccpp: Process 16703 (autoresponder) of user 30 killed by SIGABRT - dumping core
The output below may be seen in the list of the ABRT reports:

# abrt-cli list
id 9c96d191ee574883fcf3f4eef07f5c1a0019d3ca
reason: autoresponder killed by SIGABRT
time: Wed 14 Nov 2018 05:23:17 PM GMT
cmdline: /usr/local/psa/handlers/hooks/autoresponder responder bounces+1584407-b607-frances.morrissey=piersemotors.ie@sendgrid.net frances.morrissey@piersemotors.ie
package: psa-mail-driver-common-17.8.11-cos7.build1708180424.19
uid: 30 (popuser)
count: 12
Directory: /var/spool/abrt/ccpp-2018-11-14-17:23:17-23106
Reported: file:///tmp/abrt.log
Run 'abrt-cli report /var/spool/abrt/ccpp-2018-11-14-17:23:17-23106' for creating a case in Red Hat Customer Portal

The issue is caused by Plesk bug: PPPM-9637, that is is going to be fixed in Plesk Obsidian.

Until a fix is available, these messages may be ignored, or ABRT may be disabled the following way:

Connect to the server via SSH;
Stop service and disable it from starting after the reboot:

# systemctl stop abrtd
# systemctl disable abrtd