Nope, i was hoping that everything will work fine with syslog-ng, but now it keeps the CPU again at 100 percent. /top - 15:40:20 up 6:53, 2 users, load average: 1.59, 3.35, 3.86 Tasks: 141 total, 2 running, 139 sleeping, 0 stopped, 0 zombie Cpu(s): 12.5%us, 38.4%sy, 0.0%ni, 48.9%id, 0.0%wa, 0.0%hi, 0.2%si, 0.0%st Mem: 2060488k total, 1506968k used, 553520k free, 104856k buffers Swap: 2931820k total, 0k used, 2931820k free, 975856k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 2528 root 20 0 3464 1416 832 R *100* 0.1 259:49.18 syslog-ng /I have attached the config file, instalation has been done with: sudo apt-get install syslog-ng. Version: cosmin@CosminDell:~$ syslog-ng -V syslog-ng 2.0.9 I was doing some learning with GNS3, and only 3 cisco IOS loaded. My machine has this hardware/software: Linux CosminDell 2.6.28-13-generic #45-Ubuntu SMP Tue Jun 30 19:49:51 UTC 2009 i686 GNU/Linux cosmin@CosminDell:~$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz stepping : 13 cpu MHz : 2001.000 cache size : 2048 KB cosmin@CosminDell:~$ cat /proc/meminfo MemTotal: 2060488 kB MemFree: 553376 kB Buffers: 104980 kB Stiil the cpu stays at 100%. When i have install syslog-ng, the folowing repos were configured: cosmin@CosminDell:~$ less /etc/apt/sources.list | grep deb /deb http://ro.archive.ubuntu.com/ubuntu/ jaunty main restricted deb-src http://ro.archive.ubuntu.com/ubuntu/ jaunty main restricted deb http://ro.archive.ubuntu.com/ubuntu/ jaunty-updates main restricted deb-src http://ro.archive.ubuntu.com/ubuntu/ jaunty-updates main restricted deb http://ro.archive.ubuntu.com/ubuntu/ jaunty universe deb-src http://ro.archive.ubuntu.com/ubuntu/ jaunty universe deb http://ro.archive.ubuntu.com/ubuntu/ jaunty-updates universe deb-src http://ro.archive.ubuntu.com/ubuntu/ jaunty-updates universe deb http://ro.archive.ubuntu.com/ubuntu/ jaunty multiverse deb-src http://ro.archive.ubuntu.com/ubuntu/ jaunty multiverse deb http://ro.archive.ubuntu.com/ubuntu/ jaunty-updates multiverse deb-src http://ro.archive.ubuntu.com/ubuntu/ jaunty-updates multiverse deb http://security.ubuntu.com/ubuntu jaunty-security main restricted deb-src http://security.ubuntu.com/ubuntu jaunty-security main restricted deb http://security.ubuntu.com/ubuntu jaunty-security universe deb-src http://security.ubuntu.com/ubuntu jaunty-security universe deb http://security.ubuntu.com/ubuntu jaunty-security multiverse deb-src http://security.ubuntu.com/ubuntu jaunty-security multiverse deb http://archive.ubuntu.com/ubuntu jaunty universe multiverse deb-src http://archive.ubuntu.com/ubuntu jaunty universe multiverse/ I have even restarted syslog-ng, and still stays at 100%. / / Cosmin Neagu NOC Team Leader Str. I. G. Duca nr 36 Otopeni, Judetul Ilfov, 075100 Romania Tel: 021 303 3159 / 0732 669 193 www.omnilogic.ro Cosmin Neagu wrote:
The config is like this (i will only show what i have added, the rest is the default config):
source s_internal { internal(); }; source s_local {file ("/proc/kmsg" log_prefix("kernel: ")); unix-stream ("/dev/log"); }; destination d_remote {udp ("192.168.53.248" port(514)); }; log { source(s_internal); destination(d_remote); };
The thing is that i have noticed this only twice, and the last time was when i have used the PC for a day, without network conectivity. I think that the next day, when i started the PC with network connectivity, syslog was taking his time sending all the logs from previos day. I will watch to see if that happends again and in what condition, until then, now is working ok, no high cpu anymore.
PS: i never doubt that i could'nt get help here, without your replys, syslog-ng would not have been running right now :)
Cosmin Neagu NOC Team Leader Str. I. G. Duca nr 36 Otopeni, Judetul Ilfov, 075100 Romania Tel: 021 303 3159 / 0732 669 193 www.omnilogic.ro
Balazs Scheidler wrote:
On Tue, 2009-07-07 at 09:49 +0300, Cosmin Neagu wrote:
Sorry for answering so late. You were right guys about the firewall, on the Fedora server iptables was on, and as soon as I turned it off, everything worked great. Know i have to learn how to configure iptables, cause i don't want to leave it off. Anyone knows a good starting point for iptables?
And another thing that bothers me...why the hell does the cpu stays most of the time at 100% because of the syslog-ng process?
top - 09:42:37 up 55 min, 2 users, load average: 1.10, 1.07, 0.98 Tasks: 134 total, 3 running, 131 sleeping, 0 stopped, 0 zombie Cpu(s): 12.3%us, 39.0%sy, 0.0%ni, 48.6%id, 0.0%wa, 0.0%hi, 0.2%si, 0.0%st Mem: 2060488k total, 850036k used, 1210452k free, 77172k buffers Swap: 2931820k total, 0k used, 2931820k free, 460408k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 2527 root 20 0 3344 1268 848 R 100 0.1 32:13.86 syslog-ng 3028 root 20 0 305m 34m 11m S 2 1.7 1:04.90 Xorg 22 root 15 -5 0 0 0 S 0 0.0 0:00.12 ata/1 3788 cosmin 20 0 221m 102m 26m S 0 5.1 1:12.27 firefox
I have a dual core processor, and either CPU1 or CPU2 stays at 100% utilization...
This seems to be a bug, however I don't know anything similar in 2.0.
Can you please post your configuration file which shows this symptom? Do you get this right after you start syslog-ng? Is it always reproducible? Can you list the exact version you are using and the way you got it compiled? Is it a distribution package?
So as you may see, we're happy to help you, but we need more information.
------------------------------------------------------------------------
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.campin.net/syslog-ng/faq.html
# # Configuration file for syslog-ng under Debian # # attempts at reproducing default syslog behavior # the standard syslog levels are (in descending order of priority): # emerg alert crit err warning notice info debug # the aliases "error", "panic", and "warn" are deprecated # the "none" priority found in the original syslogd configuration is # only used in internal messages created by syslogd ###### # options options { # disable the chained hostname format in logs # (default is enabled) chain_hostnames(0); # the time to wait before a died connection is re-established # (default is 60) time_reopen(10); # the time to wait before an idle destination file is closed # (default is 60) time_reap(360); # the number of lines buffered before written to file # you might want to increase this if your disk isn't catching with # all the log messages you get or if you want less disk activity # (say on a laptop) # (default is 0) #sync(0); # the number of lines fitting in the output queue log_fifo_size(2048); # enable or disable directory creation for destination files create_dirs(yes); # default owner, group, and permissions for log files # (defaults are 0, 0, 0600) #owner(root); group(adm); perm(0640); # default owner, group, and permissions for created directories # (defaults are 0, 0, 0700) #dir_owner(root); #dir_group(root); dir_perm(0755); # enable or disable DNS usage # syslog-ng blocks on DNS queries, so enabling DNS may lead to # a Denial of Service attack # (default is yes) use_dns(no); # maximum length of message in bytes # this is only limited by the program listening on the /dev/log Unix # socket, glibc can handle arbitrary length log messages, but -- for # example -- syslogd accepts only 1024 bytes # (default is 2048) #log_msg_size(2048); #Disable statistic log messages. stats_freq(0); # Some program send log messages through a private implementation. # and sometimes that implementation is bad. If this happen syslog-ng # may recognise the program name as hostname. Whit this option # we tell the syslog-ng that if a hostname match this regexp than that # is not a real hostname. bad_hostname("^gconfd$"); }; ###### # sources # all known message sources source s_all { # message generated by Syslog-NG internal(); # standard Linux log source (this is the default place for the syslog() # function to send logs to) unix-stream("/dev/log"); # messages from the kernel file("/proc/kmsg" log_prefix("kernel: ")); # use the following line if you want to receive remote UDP logging messages # (this is equivalent to the "-r" syslogd flag) # udp(); }; ###### # destinations # some standard log files destination df_auth { file("/var/log/auth.log"); }; destination df_syslog { file("/var/log/syslog"); }; destination df_cron { file("/var/log/cron.log"); }; destination df_daemon { file("/var/log/daemon.log"); }; destination df_kern { file("/var/log/kern.log"); }; destination df_lpr { file("/var/log/lpr.log"); }; destination df_mail { file("/var/log/mail.log"); }; destination df_user { file("/var/log/user.log"); }; destination df_uucp { file("/var/log/uucp.log"); }; # these files are meant for the mail system log files # and provide re-usable destinations for {mail,cron,...}.info, # {mail,cron,...}.notice, etc. destination df_facility_dot_info { file("/var/log/$FACILITY.info"); }; destination df_facility_dot_notice { file("/var/log/$FACILITY.notice"); }; destination df_facility_dot_warn { file("/var/log/$FACILITY.warn"); }; destination df_facility_dot_err { file("/var/log/$FACILITY.err"); }; destination df_facility_dot_crit { file("/var/log/$FACILITY.crit"); }; # these files are meant for the news system, and are kept separated # because they should be owned by "news" instead of "root" destination df_news_dot_notice { file("/var/log/news/news.notice" owner("news")); }; destination df_news_dot_err { file("/var/log/news/news.err" owner("news")); }; destination df_news_dot_crit { file("/var/log/news/news.crit" owner("news")); }; # some more classical and useful files found in standard syslog configurations destination df_debug { file("/var/log/debug"); }; destination df_messages { file("/var/log/messages"); }; # pipes # a console to view log messages under X destination dp_xconsole { pipe("/dev/xconsole"); }; # consoles # this will send messages to everyone logged in destination du_all { usertty("*"); }; ###### # filters # all messages from the auth and authpriv facilities filter f_auth { facility(auth, authpriv); }; # all messages except from the auth and authpriv facilities filter f_syslog { not facility(auth, authpriv); }; # respectively: messages from the cron, daemon, kern, lpr, mail, news, user, # and uucp facilities filter f_cron { facility(cron); }; filter f_daemon { facility(daemon); }; filter f_kern { facility(kern); }; filter f_lpr { facility(lpr); }; filter f_mail { facility(mail); }; filter f_news { facility(news); }; filter f_user { facility(user); }; filter f_uucp { facility(uucp); }; # some filters to select messages of priority greater or equal to info, warn, # and err # (equivalents of syslogd's *.info, *.warn, and *.err) filter f_at_least_info { level(info..emerg); }; filter f_at_least_notice { level(notice..emerg); }; filter f_at_least_warn { level(warn..emerg); }; filter f_at_least_err { level(err..emerg); }; filter f_at_least_crit { level(crit..emerg); }; # all messages of priority debug not coming from the auth, authpriv, news, and # mail facilities filter f_debug { level(debug) and not facility(auth, authpriv, news, mail); }; # all messages of info, notice, or warn priority not coming form the auth, # authpriv, cron, daemon, mail, and news facilities filter f_messages { level(info,notice,warn) and not facility(auth,authpriv,cron,daemon,mail,news); }; # messages with priority emerg filter f_emerg { level(emerg); }; # complex filter for messages usually sent to the xconsole filter f_xconsole { facility(daemon,mail) or level(debug,info,notice,warn) or (facility(news) and level(crit,err,notice)); }; ###### # logs # order matters if you use "flags(final);" to mark the end of processing in a # "log" statement # these rules provide the same behavior as the commented original syslogd rules # auth,authpriv.* /var/log/auth.log log { source(s_all); filter(f_auth); destination(df_auth); }; # *.*;auth,authpriv.none -/var/log/syslog log { source(s_all); filter(f_syslog); destination(df_syslog); }; # this is commented out in the default syslog.conf # cron.* /var/log/cron.log #log { # source(s_all); # filter(f_cron); # destination(df_cron); #}; # daemon.* -/var/log/daemon.log log { source(s_all); filter(f_daemon); destination(df_daemon); }; # kern.* -/var/log/kern.log log { source(s_all); filter(f_kern); destination(df_kern); }; # lpr.* -/var/log/lpr.log log { source(s_all); filter(f_lpr); destination(df_lpr); }; # mail.* -/var/log/mail.log log { source(s_all); filter(f_mail); destination(df_mail); }; # user.* -/var/log/user.log log { source(s_all); filter(f_user); destination(df_user); }; # uucp.* /var/log/uucp.log log { source(s_all); filter(f_uucp); destination(df_uucp); }; # mail.info -/var/log/mail.info log { source(s_all); filter(f_mail); filter(f_at_least_info); destination(df_facility_dot_info); }; # mail.warn -/var/log/mail.warn log { source(s_all); filter(f_mail); filter(f_at_least_warn); destination(df_facility_dot_warn); }; # mail.err /var/log/mail.err log { source(s_all); filter(f_mail); filter(f_at_least_err); destination(df_facility_dot_err); }; # news.crit /var/log/news/news.crit log { source(s_all); filter(f_news); filter(f_at_least_crit); destination(df_news_dot_crit); }; # news.err /var/log/news/news.err log { source(s_all); filter(f_news); filter(f_at_least_err); destination(df_news_dot_err); }; # news.notice /var/log/news/news.notice log { source(s_all); filter(f_news); filter(f_at_least_notice); destination(df_news_dot_notice); }; # *.=debug;\ # auth,authpriv.none;\ # news.none;mail.none -/var/log/debug log { source(s_all); filter(f_debug); destination(df_debug); }; # *.=info;*.=notice;*.=warn;\ # auth,authpriv.none;\ # cron,daemon.none;\ # mail,news.none -/var/log/messages log { source(s_all); filter(f_messages); destination(df_messages); }; # *.emerg * log { source(s_all); filter(f_emerg); destination(du_all); }; # daemon.*;mail.*;\ # news.crit;news.err;news.notice;\ # *.=debug;*.=info;\ # *.=notice;*.=warn |/dev/xconsole log { source(s_all); filter(f_xconsole); destination(dp_xconsole); }; source s_internal { internal(); }; source s_local { file ("/proc/kmsg" log_prefix("kernel: ")); unix-stream ("/dev/log"); }; destination d_localfile { file ("/home/cosmin/syslog.log"); }; destination d_remote {udp ("192.168.53.248" port(514)); }; #log { source(s_local); destination(d_localfile); }; #log { source(s_internal); destination(d_localfile); }; #log { source(s_local); destination(d_remote); }; log { source(s_internal); destination(d_remote); };