[Bug 702217] New: syslog-ng stats_freq option not interpreted correctly

newer
[Bug 738073] VUL-0: NetworkManager...

older
[Bug 749978] New: SUSE:SLE-11:SP2...

bugzilla_noreply＠novell.com

26 Jun 2011 26 Jun '11

12:32

https://bugzilla.novell.com/show_bug.cgi?id=702217 https://bugzilla.novell.com/show_bug.cgi?id=702217#c0 Summary: syslog-ng stats_freq option not interpreted correctly Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jschrod@acm.org QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.19) Gecko/20110420 SUSE/2.0.14-4.1 SeaMonkey/2.0.14 syslog-ng 3.2.2-5.1: When one uses the option stats_freq(60140); a statistics log record should be output roughly every week. Instead it's output every 10 seconds. That number 10 depends on 60140, if I change the latter, the former changes accordingly. Reproducible: Always Steps to Reproduce: 1. Add option stats_freq(60140); to syslog-ng.conf 2. Restart syslog-ng. 3. Wait 10 seconds. :-) Actual Results: Statistics log message is output every 10 seconds. Expected Results: Statistics log message should be output every 60140 seconds. 60140 seconds is, of course, a contrived example. I wanted weekly stats records (i.e., every 60480 seconds). But then you have to wait ca. 6 minutes for the superfluous log records. ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Show replies by date

bugzilla_noreply＠novell.com

26 Jun 26 Jun

16:42

New subject: [Bug 702217] syslog-ng stats_freq option not interpreted correctly

https://bugzilla.novell.com/show_bug.cgi?id=702217 https://bugzilla.novell.com/show_bug.cgi?id=702217#c Petr Uzel changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |mt@novell.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

27 Jun 27 Jun

19:33

New subject: [Bug 702217] syslog-ng stats_freq option not interpreted correctly

https://bugzilla.novell.com/show_bug.cgi?id=702217 https://bugzilla.novell.com/show_bug.cgi?id=702217#c1 --- Comment #1 from peter czanik 2011-06-27 19:33:48 UTC --- Tested it and confirmed. Forwarded the bugs to upstream developers. CzP -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

1 Jul 1 Jul

14:44

New subject: [Bug 702217] syslog-ng stats_freq option not interpreted correctly

https://bugzilla.novell.com/show_bug.cgi?id=702217 https://bugzilla.novell.com/show_bug.cgi?id=702217#c2 Balázs Scheidler changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bazsi@balabit.hu --- Comment #2 from Balázs Scheidler 2011-07-01 14:44:53 UTC --- Hmm... I couldn't reproduce it with the latest syslog-ng 3.2 git tree, however I can't remember any fixes in the area. Are you sure you wrote the correct number of digits in the error report? I mean one week is 24*60*60*7 = 604800 and not 60480 (one digit less). This number is multiplied by 1000 to get msec instead of seconds, but that still gits into the 32 bit integer it is stored in. (around 600 million, but we're ok until about 2 billion). The glib version can matter too, in my build environment I use 2.14.6, yours is probably newer. This might also be a factor. (for instance if glib uses nanoseconds internally, that would already overflow) But anyway, I'd suggest to use shorter timeouts, is one per day so much extra traffic? This way you can check message drops etc So I wouldn't want to fix this upstream, especially as syslog-ng 3.3 is using a completely different event library (ivykis instead of glib). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

15:13

New subject: [Bug 702217] syslog-ng stats_freq option not interpreted correctly

https://bugzilla.novell.com/show_bug.cgi?id=702217 https://bugzilla.novell.com/show_bug.cgi?id=702217#c3 --- Comment #3 from peter czanik 2011-07-01 15:13:47 UTC --- Yes, it is 60480 which gives stat in every ten seconds. Just tested 3.2.4 on factory, and that does not seem to be affected. Obviously many other packages were updated too. I'll try to compile 3.2.4 for openSUSE 11.4 and give it a try. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

28 Feb 28 Feb

10:03

New subject: [Bug 702217] syslog-ng stats_freq option not interpreted correctly

https://bugzilla.novell.com/show_bug.cgi?id=702217 https://bugzilla.novell.com/show_bug.cgi?id=702217#c4 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mt@suse.com AssignedTo|mt@suse.com |bnc-team-gnome@forge.provo. | |novell.com --- Comment #4 from Marius Tomaschewski 2012-02-28 10:03:47 UTC --- This is a glib integer overflow and fix for this issue is in commit c2fbef4125977d0c1aa1a9859491e694c9c71b05. See also: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606618 https://bugzilla.gnome.org/show_bug.cgi?id=642052 I think it makes sense to fix it in glib2. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.