Bug #26546 server logs fill with duplicate UUID error message from same agent
Submitted: 21 Feb 2007 22:17 Modified: 3 Apr 2007 21:07
Reporter: Sloan Childers Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Agent Severity:S2 (Serious)
Version: OS:
Assigned to: Jan Kneschke CPU Architecture:Any

[21 Feb 2007 22:17] Sloan Childers 
Description:
A rogue agent with a duplicate UUID can fill the server logs quite rapidly.  We need to either ignore it after the first log message or be able to tell the rogue agent to shutdown.

How to repeat:
Create a second agent with a duplicate UUID and fire it up.

Suggested fix:
1) the agent receives the duplicate UUID exception from the server and shuts down
or
2) implement a new agent command so the server can tell the agent to shutdown
[21 Feb 2007 23:09] Darren Oldag 
we don't need a command, necessarily.  if the agent recognizes the exception, it can shut down.
[21 Feb 2007 23:10] Darren Oldag 
jan (begrudgingly) agrees...
[22 Feb 2007 18:59] Jan Kneschke 
patch has been sent to Darren for review.
[23 Feb 2007 0:29] Darren Oldag 
the patch handles dup server name shutdown, but not dup uuid.

returning to jan for further fixing.
[26 Feb 2007 17:04] Jan Kneschke 
fixed in r4834
[3 Apr 2007 12:00] Carsten Segieth 
tested OK with 1.1.0.4973, agent now stops when duplicate UUID or SERVER-NAME is detected:

2007-04-03 13:27:42: (critical) exception received from server: E1402:  Duplicate agent uuid "4d8ba81c-0004-3300-0005-4d075c239ac7" detected.
2007-04-03 13:27:42: (critical) server asked us to shutdown

2007-04-03 13:29:34: (critical) exception received from server: E1403:  Server name "Merlin agent long name:3300" is in use by another agent with uuid "4d8ba81c-0004-3300-0005-4d075c239ac7".
2007-04-03 13:29:34: (critical) server asked us to shutdown
[3 Apr 2007 21:07] Peter Lavin 
Added to the changelog.