Red Hat Bugzilla – Bug 448640
rsyslogd takes CPU all the to 99% to 100%
Last modified: 2013-06-18 10:35:13 EDT
Description of problem: rsyslogd takes CPU all the to 99% to 100% see : https://www.redhat.com/archives/fedora-test-list/2008-May/msg00861.html Version-Release number of selected component (if applicable): 3.19.3-1.fc10 How reproducible: always Steps to Reproduce: 1. Update rsyslog-3.19.3-1.fc10 2. Reboot 3. Actual results: Expected results: Additional info:
+1 It's the third thread (fourth created judging from the pids) that's the culprit. No syscalls made by it. gdb backtrace: #0 0xb8078ba2 in Syslog () from /usr/lib/rsyslog/imklog.so #1 0xb8079376 in ?? () from /usr/lib/rsyslog/imklog.so #2 0xb8079450 in klogLogKMsg () from /usr/lib/rsyslog/imklog.so #3 0xb80789d4 in ?? () from /usr/lib/rsyslog/imklog.so #4 0x0805954e in ?? () #5 0x435e451f in start_thread () from /lib/libpthread.so.0 #6 0x4351abde in clone () from /lib/libc.so.6 There is no activity in dmesg.
problem should be solved in rsyslog-3.19.4-1.fc10. Let me know, please. thnx.
Seeing this again with latest rsyslog-3.21.3-4.fc10.i386 .
This bug has been fixed and is not present in rsyslog-3.21.3-4, so what you're experiencing is probably unrelated to it. I haven't seen it in a quick test run. Do you have a reliable way to reproduce it? Have you done any changes to your configuration file?
No changes to the configuration file. To complicate the issue, I'm only seeing it on one of my 3 F-10 installations, about 50% of the time. Would you fancy an strace log ? If you rather prefer giving gdb instructions, I'll try to follow them too (rsyslog-debuginfo required, I guess ?).
Any additional information would be useful. strace log and if possible a backtrace from gdb - debuginfo is needed. Does it always appear at any precise time after boot?
I will have a look at that installation the next few days (it's a station which is not very often rebooted). Concerning the gdb backtrace : I asked for instructions because I am not closely acquainted with gdb. :)
Sorry for being so brief about the instructions, here they are: # gdb rsyslogd <pid> gdb may complain about missing debuginfo, e.g. "Missing separate debuginfos, use: debuginfo-install gcc.i386 zlib.i386" (gdb) bt This will display the backtrace.