Abrt Cli Status Timed Out



From time-to-time I'm getting the following message:

If abrtd is running like that there’s a reason- something else on the machine is typically failing and triggering it. While it shouldn’t spin at 100%, just disabling it without figuring out what’s broke is a. In Red Hat/CentOS you can collect core dump using abrt and abrt-addon-ccpp Before you start make sure the system is set up to generate application cores by removing the core limits: # ulimit -c unlimited. Next install these rpms in your environment # yum install abrt abrt-addon-ccpp abrt-tui. Ensure the ccpp hooks are installed. The Automatic Bug Reporting Tool or ABRT, consists of the abrtd daemon is a daemon that watches for application crashes and stores them into core dump file and takes according to the defined configuration “abrt.conf”. Hello, Getting time out while accessing server remotely. After entering root password getting 'abrt-cli status' timed out' Please help. Is there a way to mass delete these reports to clean things up? I looked at abrt-cli and it has a -delete command, but only does them one at a time, too. View 2 Replies View Related Fedora:: Any Way To Reduce Size Of ABRT Cache? Is there a way to clean (reduce size of) the abrt cache (/var/cache/abrt)?


ABRT has detected 1 problem(s). For more info run: abrt-cli list --since 1461792169
The output that the above command produces is:Abrt
[root@jpdsys1 ~]# abrt-cli list --since 1461792169
id f6f4445aa30895793096e8427d1dc0f596ee0bd5
reason: mce: [Hardware Error]: Machine check events logged
time: Wed 27 Apr 2016 05:27:26 PM EDT
cmdline: BOOT_IMAGE=/vmlinuz-3.10.0-327.13.1.el7.x86_64 root=/dev/mapper/vg_jpd1opsys-lv_root ro rd.md.uuid=4f8d2a8d:592b5d40:b2252a29:3c16213c rd.lvm.lv=vg_jpd1opsys/lv_root rd.md.uuid=c9603f45:a906643b:9f9d90c3:80524d94 rd.md.uuid=59b572b4:a34e7962:9abc3452:4b84b738 rd.lvm.lv=vg_jpd1swap/lv_swap rd.lvm.lv=vg_jpd1opsys/lv_usr rhgb quiet LANG=en_US.UTF-8
package: kernel
uid: 0 (root)
count: 1
Directory: /var/spool/abrt/oops-2016-04-27-17:27:26-3121-0
Reported: cannot be reported
When I go to the directory, I see the following:
[root@jpdsys1 ~]# cd /var/spool/abrt/oops-2016-04-27-17:27:26-3121-0 ;; ls -ltr
total 204
-rw-r----- 1 root abrt 1 Apr 27 17:27 uid
Abrt Cli Status Timed Out-rw-r----- 1 root abrt 10 Apr 27 17:27 time
-rw-r----- 1 root abrt 10 Apr 27 17:27 last_occurrence

Abrt Cli Status Timed Out Rhel

-rw-r----- 1 root abrt 6 Apr 27 17:27 architecture
-rw-r----- 1 root abrt 393 Apr 27 17:27 os_info
-rw-r----- 1 root abrt 24 Apr 27 17:27 hostname
-rw-r----- 1 root abrt 10 Apr 27 17:27 type
-rw-r----- 1 root abrt 269 Apr 27 17:27 suspend_stats
-rw-r----- 1 root abrt 50 Apr 27 17:27 reason
-rw-r----- 1 root abrt 6432 Apr 27 17:27 proc_modules

Shell Script Timeout

-rw-r----- 1 root abrt 37 Apr 27 17:27 os_release
-rw-r----- 1 root abrt 347 Apr 27 17:27 cmdline
-rw-r----- 1 root abrt 10 Apr 27 17:27 analyzer
-rw-r----- 1 root abrt 6 Apr 27 17:27 abrt_version
-rw-r----- 1 root abrt 6 Apr 27 17:27 package
-rw-r----- 1 root abrt 6 Apr 27 17:27 component
-rw-r----- 1 root abrt 5 Apr 27 17:27 username
-rw-r----- 1 root abrt 4 Apr 27 17:27 runlevel
-rw-r----- 1 root abrt 0 Apr 27 17:27 event_log
-rw-r----- 1 root abrt 135 Apr 27 17:27 machineid
-rw-r----- 1 root abrt 81835 Apr 27 17:27 dmesg
-rw-r----- 1 root abrt 40 Apr 27 17:27 uuid
-rw-r----- 1 root abrt 105 Apr 27 17:27 not-reportable
-rw-r----- 1 root abrt 40 Apr 27 17:27 duphash
-rw-r----- 1 root abrt 27 Apr 27 17:27 kernel
-rw-r----- 1 root abrt 624 Apr 27 17:27 backtrace
-rw-r----- 1 root abrt 7 Apr 27 17:27 pkg_name

Abrt Cli Status Timed Out Of Computer


-rw-r----- 1 root abrt 7 Apr 27 17:27 pkg_arch
-rw-r----- 1 root abrt 7 Apr 27 17:27 pkg_version
-rw-r----- 1 root abrt 13 Apr 27 17:27 pkg_release
-rw-r----- 1 root abrt 2 Apr 27 17:27 pkg_epoch

Bash Timeout


Su 'abrt-cli Status' Timed Out

-rw-r----- 1 root abrt 1 Apr 27 17:27 count

Abrt Cli Status Timed Out 1


Where do I look to try and find out the hardware issue I'm having?
TIA

Abrt-cli Status' Timed Out Fix


Gene