Re: [pmacct-discussion] Bug in pmacct-0.12.0rc1?

[Paolo Lucente]

Hi Johannes,

The only idea coming to the mind is that two pmacctd instances
(each with two plugins) are fired up in parallel and trying to
write to the same MySQL tables. 

If it's not something in this sense, i would ask you to turn
on debugging on one of the two plugins (debug[inbound]: true
for example) and check what SQL queries are causing such
duplication. If it's not too much sensible data, you can
let me have a look aswell at the debug log by sending it
privately.

I assume this an upgrade of a working installation?

Let me know.

Cheers,
Paolo


___
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists

Re: [pmacct-discussion] timestamp rounding bug

[Paolo Lucente]

On Tue, Aug 04, 2009 at 09:18:22PM -0500, Karl O. Pinc wrote:
 On 08/04/2009 04:35:31 AM, Chris Wilson wrote:
 
  Is any real-world system set to UTC? I'm certainly not going to run 
  my
  
  firewall (where I run pmacct currently) on UTC. All my logs would be 
  screwed up and much harder to interpret.
 
 Setting the system clock to UTC is traditional in Unix, AFAIK.
 The obvious reason being that it makes it easy to compare
 times across systems.  It's up to the logging application 
 to decide whether to output UTC, localtime without time 
 zones, localtime with time zones etc.  Likewise other
 programs that produce times for human consumption.
 
 The Internet (e.g. rfc2822 and, iirc, rfc5424) tends
 to solve the human consumption problem by logging in localtime but
 including an offset from utc in the timestamp.

Chiming briefly into this to add to the thread that is common to
have systems set on UTC even in large networks that span across
multiple timezones and having local times wouldn't help the NOC
at all (given that pretty much all works on UTC, ie. maintenance
announcements). 

Cheers,
Paolo


___
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists