Blob Blame History Raw
From 4bfbbd5840a21257cf319936b3c59b7aaa1519ad Mon Sep 17 00:00:00 2001
From: Jakub Filak <>
Date: Fri, 24 Oct 2014 15:50:02 +0200
Subject: [ABRT PATCH 74/75] a-a-g-machine-id: suppress its failures in

If an event script exits with a non-zero code, abrtd deletes entire dump

Failures of a-a-g-machine-id must not lead to the deletion of a dump

It is also expected that dmidecode-less systems will print an error
message related to the fact that dmidecode doesn't work, hence
forwarding of STDOUT and STDERR to 'event_log' file.

Related to rhbz#1139552

Signed-off-by: Jakub Filak <>
 src/daemon/abrt_event.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/daemon/abrt_event.conf b/src/daemon/abrt_event.conf
index deda7c7..54e1b3f 100644
--- a/src/daemon/abrt_event.conf
+++ b/src/daemon/abrt_event.conf
@@ -94,7 +94,7 @@ EVENT=post-create
 # Example: if you want to include *machineid* in dump directories:
-    /usr/libexec/abrt-action-generate-machine-id -o $DUMP_DIR/machineid
+    /usr/libexec/abrt-action-generate-machine-id -o $DUMP_DIR/machineid >>event_log 2>&1 || :
 # Example: if you want to upload data immediately at the moment of a crash: