Bug #42139 Agent password error does not log originating host

• Submitted: 15 Jan 2009 20:20
• Modified: 5 Feb 2009 12:40
• Reporter: Mark Leith
• Status: Closed
• Category: Monitoring: Server
• Severity: S3 (Non-critical)
• Version: 2.0.1.7125
• OS: Any
• Assigned to: MC Brown
• Target Version: 2.0 ASAP

[15 Jan 2009 20:20] Mark Leith

Description:
The agent password error on the service manager does not log the originating host, making
it impossible to get to the agent in question:

Error	Jan 5, 2009 4:56:08 PM	<?xml version='1.0'?><exceptions><error><![CDATA[E1702:
IncorrectPasswordException: [agent]]]></error></exceptions>

How to repeat:
o Start an agent with the wrong agent password 
o Check the misc log

Suggested fix:
Log the IP/hostname of the originating agent

[21 Jan 2009 4:14] Mark Matthews

Fixed for the next builds of 2.1 (trunk) and 2.0. Authentication failures are now logged
at INFO in the Security log, and they contain client IP addresses (but nothing else, at
the risk of info disclosure).

[22 Jan 2009 18:42] Diego Medina

Verified fixed on 2.0.4.7138

We now see

Security  	Info  	Jan 22, 2009 12:41:49 PM  	Incorrect password from client x.x.x.x

on the service manager's log

[2 Feb 2009 21:24] Diego Medina

Verified fixed on 2.0.4.7141

You now see messages like

INFO [http-18443-2:com.mysql.security] Last message repeated 30 times
ERROR [http-18443-2:com.mysql.misc] Last message repeated 28 times

[5 Feb 2009 12:40] Tony Bedford

An entry was added to the 2.0.4 changelog:

The agent password error in the Service Manager did not log the originating host, making
it impossible to determine the agent that failed to log in:

Error Jan 5, 2009 4:56:08 PM<?xml version='1.0'?><exceptions><error><![CDATA[E1702:
IncorrectPasswordException: [agent]]]></error></exceptions>