Syslog-ng has very high cpu usage [CONCLUDED]

[ds123]

For some reason, syslog-ng has been a cpu hog for a few weeks. I can't seem to find anything meaningful such as logs accumulating a great rate to account for this.

The range is typically somewhere between 50 and 85% utilization as shown using the top command.

Can someone provide me some guidance as to where to start looking for the problem?

Thanks

[think4urs11]

can you post your syslog-ng.conf?
What amount of logs do we talk about (do you collect logs from a bigger lan on that box)?

[ds123]

It is just the default config. I thought I'd try syslog-ng instead of metalog and I haven't gotten around to configuing it yet.

Code: Select all

# $Header: /var/cvsroot/gentoo-x86/app-admin/syslog-ng/files/syslog-ng.conf.gentoo,v 1.7 2007/08/02 04:52:1$
#
# Syslog-ng default configuration file for Gentoo Linux
# contributed by Michael Sterrett

options {
        chain_hostnames(off);
        sync(0);

        # The default action of syslog-ng 1.6.0 is to log a STATS line
        # to the file every 10 minutes.  That's pretty ugly after a while.
        # Change it to every 12 hours so you get a nice daily update of
        # how many messages syslog-ng missed (0).
        stats(43200);
};

source src {
    unix-stream("/dev/log" max-connections(256));
    internal();
    file("/proc/kmsg");
};

destination messages { file("/var/log/messages"); };

# By default messages are logged to tty12...
destination console_all { file("/dev/tty12"); };
# ...if you intend to use /dev/console for programs like xconsole
# you can comment out the destination line above that references /dev/tty12
# and uncomment the line below.
#destination console_all { file("/dev/console"); };

log { source(src); destination(messages); };
log { source(src); destination(console_all); };

Thanks for your help

[ds123]

oh, and to answer your other question, there are no other logs posted to this computer.

[ds123]

I have switched back to metalog and cpu issues are resolved.