Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#6980 - syslog-ng stats flooding syslog

Attached to Project: Arch Linux
Opened by mangus (mangus) - Sunday, 22 April 2007, 22:03 GMT
Last edited by Tobias Powalowski (tpowa) - Saturday, 07 March 2009, 16:17 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Aaron Griffin (phrakture)
Architecture All
Severity Low
Priority Normal
Reported Version 0.8 Voodoo
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No


I find quite annoying syslog-ng flooding syslog and eventually an
attached tty with his atats every 10 minutes.
According with doc it can be limited to a more realable time , say
a stats report every 12 hours adding this to options:
# 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).
Closed by  Tobias Powalowski (tpowa)
Saturday, 07 March 2009, 16:17 GMT
Reason for closing:  Fixed
Additional comments about closing:  fixed syslog-ng 3.0.1 in testing
Comment by Jud (judfilm) - Wednesday, 30 May 2007, 09:16 GMT
Can the installed default to be changed?
One option is to add "stats (0);"

Comment by Jud (judfilm) - Wednesday, 20 June 2007, 12:27 GMT
Found out some more info.

new options:
stats_freq (0); # replaces stats
mark_freq (0); # new
flush_lines (0); # replaces sync

Can these new options be changed/added to the default .conf file?
Comment by Tobias Powalowski (tpowa) - Thursday, 25 October 2007, 07:07 GMT
it seems the latest package isn't flooding anymore, at elast i ahve not such messages on my system with default config.
Comment by Lee Jackson (ProfessorTomoe) - Thursday, 05 February 2009, 15:57 GMT
  • Field changed: Percent Complete (100% → 0%)
Flooding has returned in version 2.1.3. Messages similar to the following appears every 10 minutes in syslog.log:

Log statistics; processed='center(queued)=2602', processed='center(received)=1045', processed='destination(acpid)=7', processed='destination(console)=0', processed='destination(debug)=0', processed='destination(mail)=0', processed='destination(user)=0', processed='destination(uucp)=0', processed='destination(messages)=592', processed='destination(ppp)=0', processed='destination(news)=0', processed='destination(iptables)=0', processed='destination(everything)=970', processed='destination(lpr)=0', processed='destination(cron)=0', processed='destination(syslog)=267', processed='destination(authlog)=75', processed='destination(errors)=3', processed='destination(kernel)=641', processed='destination(daemon)=47', processed='destination(console_all)=0', processed='source(src)=1045'

Again, can this be reduced in the default .conf file?
Comment by Thomas B├Ąchler (brain0) - Friday, 06 March 2009, 14:52 GMT
In my configuhration file, I added stats(0); which solves this all (I don't need any of these stats). Should we add this to the default config file?
Comment by Aaron Griffin (phrakture) - Friday, 06 March 2009, 17:18 GMT
Adding a stats(0) by default seems good for me. Needed the stats is an edge case