Bug #25824 Setting the log purge setting truncates all logs after 1 day
Submitted: 24 Jan 2007 12:56 Modified: 15 Feb 2007 14:46
Reporter: Mark Leith Email Updates:
Status: Closed Impact on me:
Category:MySQL Enterprise Monitor: Server Severity:S2 (Serious)
Version: OS:Linux (RHEL4 (all?))
Assigned to: CPU Architecture:Any
Tags: Logs, Merlin, purge

[24 Jan 2007 12:56] Mark Leith
Setting the log purge system option (to a value such as 4 weeks) purges all of the logs after 1 day. 

This is pretty serious, as it impairs supports ability to help diagnose customers issues.

How to repeat:
Set log purging to 4 weeks, observe one day later. 

Suggested fix:
Don't purge until the timeframe is reached.
[24 Jan 2007 20:23] Darren Oldag
integer calculations were being used in the millisecond time resolution.  this caused an overflow, resulting in negative cutoff values.  Hence, all logs were deleted.

the fix was to use proper 'long' math where milliseconds are used.
[15 Feb 2007 14:46] Mark Leith
Verified fixed.