Applicable to:
- Plesk Onyx for Linux
Symptoms
-
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 - In
/var/log/audit/audit.log
occurs the following:CONFIG_TEXT: type=ANOM_ABEND msg=audit(1564846840.226:23261239): auid=4294967295 uid=30 gid=31 ses=4294967295 subj=system_u:system_r:sendmail_t:s0 pid=11831 comm="autoresponder" reason="memory violation" sig=6
- In
/var/log/mail.log
occurs the following:CONFIG_TEXT: onyx autoresponder[11831]: Unable to write message into stdout
onyx postfix-local[11830]: _mh_fork(): The child process with pid 11831 killed by signal 6
onyx postfix-local[11830]: Error during 'autoresponder' handler -
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-john.doe=jane.doe@example.net john.doe@example.com
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
Cause
Product issue:
- #PPPM-9637 "Auto-reply no longer fails with an error if the response frequency is reached."
Fixed in:- Plesk Obsidian 25 September 2018 (fixed as PPP-36512, Linux)
Resolution
Workaround
If update is not possible for some reason you may try the following
Until a fix is available, these messages may be safely ignored,
Also, it is possible to disable ABRT in the following way:
Note: the abrtd
cannot be installed on some virtual machines such a Virtuozzo containers thus cannot be disabled
-
Connect to the server via SSH;
-
Stop service and disable it from starting after the reboot:
# systemctl stop abrtd
# systemctl disable abrtd
Comments
0 comments
Please sign in to leave a comment.