当前位置: 首页 > 工具软件 > stack-log > 使用案例 >

CPU warning - abrt-watch-log

胡博艺
2023-12-01

I am running a Red Hat Enterprise Linux Server release 7.1 (Maipo) on Intel(R) Xeon(R) CPU X5690 @ 3.47GHz

I keep getting this error in abrt-watch-log.

root       888     1  0 Aug03 ?        00:00:00 /usr/bin/abrt-watch-log -F BUG: WARNING: at WARNING: CPU: INFO: possible recursive locking detected ernel BUG at list_del corruption list_add corruption do_IRQ: stack overflow: ear stack overflow (cur: eneral protection fault nable to handle kernel ouble fault: RTNL: assertion failed eek! page_mapcount(page) went negative! adness at NETDEV WATCHDOG ysctl table check failed : nobody cared IRQ handler type mismatch Machine Check Exception: Machine check events logged divide error: bounds: coprocessor segment overrun: invalid TSS: segment not present: invalid opcode: alignment check: stack segment: fpu exception: simd exception: iret exception: /var/log/messages -- /usr/bin/abrt-dump-oops -xtD

Answer:

The process abrt-watch-log takes strings to watch for and then runs a command. So what you're seeing as an error is just the strings to look for in /var/log/messages, which if found, is then sent to /usr/bin/abrt-dump-oops.

Please, do not be scared from that ugly command line. It is a perfectly valid command line where abrt-watch-log process is searching for the strange strings in
/var/log/messages and calling
/usr/bin/abrt-dump-oops if the tool finds a string present in the list of searched strings.

You can get the list of searched strings by issuing the following command:
$ abrt-dump-oops -m

In the upstream, we have replaced abrt-watch-log abrt-dump-oops with a single tool watching systemd-journal and the searched strings are no longer passed through command line arguments.

$ man abrt-watch-log:

NAME
       abrt-watch-log - Watch log file and run command when it grows or is replaced

SYNOPSIS
       abrt-watch-log [-vs] [-F STR] ... FILE PROG [ARGS]
 类似资料: