Question
When I use the 'ps' command or the 'Process Manager' UI in WHM, I see a strange process with a lot of errors called abrt-watch-log:
/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 Kernel panic - not syncing: 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
This is normal, abrt-watch-log is watching the 'messages' log for those errors, the list of errors it looks for can be seen by using the command '/usr/bin/abrt-dump-oops -m', example:
/usr/bin/abrt-dump-oops -m
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
Kernel panic - not syncing:
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: