On Wed, Sep 03, 2014 at 10:03:49PM +0200, Olivier wrote: > OK I understand this point of view. Maybe stating this clearly "to have > details on fields, just look at the source code, ie src/dumpstats.c" :p
No problem, do you want to propose a patch for that ? :-) > > Please send a "show info" there, it is possible that for any reason > > you're connected to the old process (eg: if you got this from an > > automated tool which stays connected to this socket). I'm not seeing > > any reason for a session's age to be wrong otherwise. > > > No, I connected manually to the socket. The old process was still alive > though. > Unfortunately I was forced to fix my session issue and killed all haproxy > process and relaunched it cleanly. I cannot observe this behaviour anymore. This age is calculated from the wall-time clock, so another possibility would be that your server started with a wrong clock, and was synchronized after the first session came in. Just an idea. Hoping this helps, Willy
