How to solve abrtd doesn't belong to any package and ProcessUnpackaged is set to...
source link: https://computingforgeeks.com/how-to-solve-abrtd-doesnt-belong-to-any-package-and-processunpackaged-is-set-to-no/
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Have you encountered the error message “abrtd doesn’t belong to any package and ProcessUnpackaged is set to ‘no’” on your CentOS or Red Hat Linux system?. Automatic Bug Reporting Tool, abbreviated as ABRT, consists of the abrtd daemon and a number of system services and utilities to process, analyze, and report detected problems.
The abrtd daemon always runs in the background and springs into action when an application crashes or a kernel oops is detected to collect the relevant problem data such as a core file if there is one, the crashing application’s command-line parameters, and other data of forensic utility.
The path where the problems detected are logged is:
/var/spool/abrt - (CentOS 6) /var/tmp/abrt - (CentOS 7)
Note you may need to install ABRT CentOS 7 by running the command:
sudo yum install abrt-cli
The aforementioned error message means abrtd cannot create the core of a program which does not belong to any package. This means a process that crashed has an executable which does not belong to any package
To solve this limitation, you need to edit the file
sudo vim /etc/abrt/abrt-action-save-package-data.conf
Then change the parameter ProcessUnpackaged to yes
# Process crashes in executables which do not belong to any package? # ProcessUnpackaged = yes
Restart abrtd service after making the change
sudo systemctl restart abrtd # CentOS 7,x sudo service abrtd restart # CentOS 6.x
That’s all, ABRT should now be able to create the core of a program when it crashes.
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK