MonitorWare Knowledge Base

I just finished setting up rsyslogd on a Centos 5.0 server. .. (dual, dual cores) ... with the MySQL plugin enabled. I use this server as a central syslogd server for about 7 other unix machines.

The volume of syslog messages we're getting is relatively low; yet rsyslogd takes up 100% CPU of one of the cores. MySQL on the other hand can't even be found in the top process list; so it's not like rsyslogd is hammering mysql.

Is this normal?

anyone?

Hi,

sorry, I overlooked this message initially. Can you tell me a bit more about your configuration, so that I can try to reproduce this behavior. Also, it would probably be helpful if you could run rsyslogd in interactive debug mode. The output generated can hopefully guide me to the actual problem area. You do this by adding the -d -n command line options.

Thanks,
Rainer

I have been experiencing this issue for a few versions now. I am not sure what causes it, but it always seems to happen after an upgrade while it was still running... on next run/start it would go 100% on the CPU.

I think I managed to grab a logfile with the -d switch, but I am unsure if it was behaving that way on that run.

I run rsyslog with -c3, the UDP and TCP (with native TLS) plugins for network logging, the imklog and and the imuxsock plugins.

Code: Select all

[root@poseidon] ~ # rsyslogd -v
rsyslogd 3.19.3, compiled with:
        FEATURE_REGEXP:                         Yes
        FEATURE_LARGEFILE:                      Yes
        FEATURE_NETZIP (message compression):   Yes
        GSSAPI Kerberos 5 support:              No
        FEATURE_DEBUG (debug build, slow code): No
        Runtime Instrumentation (slow code):    No

See http://www.rsyslog.com for more information.

Hi,

this is a know bug:

http://bugzilla.adiscon.com/show_bug.cgi?id=67

Patch is inside the bug tracker. I hope to be able to release the patched version today. I am finalizing some more work on TLS.

Rainer

Actually, I have just finished the new parts of TLS. I am about to release 3.19.4 within the next 1 to 3 hours. I suggest you wait until then. Announcement, as usual, via mailing list, home page and freshmeat.

Rainer

Thank you

I just upgraded to 3.19.4 and the issue *appears* to be resolved. I will keep an eye on the system for the next couple of days and post here if something changes.

Cheers,

Richard