Bug #30680 agent dies on some OS when log file reaches 2.0 G size
Submitted: 28 Aug 2007 21:10 Modified: 12 Sep 2007 18:33
Reporter: Carsten Segieth Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Enterprise Monitor: Agent Severity:S2 (Serious)
Version:1.2.0.7335 OS:Linux (x86)
Assigned to: Jan Kneschke CPU Architecture:Any
Tags: mer 121

[28 Aug 2007 21:10] Carsten Segieth 
Description:
Two agents died when their log file reached the 2.0 G limit. Both debug logs end 'in the middle of the sentence' and have exact the same size: 2147483647.

Seen on RH4-x86 (net-qa1) and Turbolinux10-x86 (turbo-10-x86).

But on other OS (solaris8-x86, rhas4-ia64, solaris8-sparc-64bit, solaris10-x86_64, rhas3-ia64, rhas3-x86_64) I see log files > 2.0 G and no problems with the agents.

How to repeat:
start agent with debug log ... and wait
[10 Sep 2007 18:59] Mark Matthews 
See related BUG#29379.
[12 Sep 2007 20:56] Peter Lavin 
Added to "Known issues".
[13 Mar 2014 13:36] Omer Barnir 
This bug is not scheduled to be fixed at this time.