From time-to-time I'm getting the following message:
ABRT has detected 1 problem(s). For more info run: abrt-cli list --since 1461792169
The output that the above command produces is:
[root@jpdsys1 ~]# abrt-cli list --since 1461792169
id f6f4445aa30895793096e8427d1dc0f596ee0bd5
Jul 31, 2015 Description of problem: abrt-console-notification tries to run 'abrt-cli status' on every login. If there is an '.lock' symlink in one of the problem directories (the directory is locked), abrt-cli waits until the locked directory is unlocked. This causes users must wait until the abrt-dbus kills the abrt-cli. 'abrt-cli status' timed out what is ABRT: ABRT is the Automatic Bug Reporting Tool. ABRT consists of a daemon, abrtd, which runs silently in the background most of the time.
Bug 1387821 - abrt speedtest-cli: ssl.py:570:read:socket.timeout: The read operation timed out.
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
-rw-r----- 1 root abrt 10 Apr 27 17:27 time
-rw-r----- 1 root abrt 10 Apr 27 17:27 last_occurrence
-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
-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
Bash Abrt Cli Status Timed Out
-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
-rw-r----- 1 root abrt 7 Apr 27 17:27 pkg_arch
Abrt Cli Status Timed Out Rhel
-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
-rw-r----- 1 root abrt 1 Apr 27 17:27 count
Where do I look to try and find out the hardware issue I'm having?
Abrt Cli Status Timeout
TIA