MySQL Bugs: #42407: merlin reports replication state unknown but it appears to be working fine

Bug #42407	merlin reports replication state unknown but it appears to be working fine
Submitted:	28 Jan 2009 10:17	Modified:	26 Jun 2009 16:33
Reporter:	Simon Mudd (OCA)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Web	Severity:	S3 (Non-critical)
Version:	Server:2.0.4.7138 Agent: 2.0.4.7141	OS:	Any
Assigned to:	MC Brown	CPU Architecture:	Any
Tags:	windmill

Description:
This may be an agent or a server issue. It's not clear to me.

The replication status shown for a server mc01intmdb-01 is shown as unknown. The agent logs no errors and the server shows no other event problems. In fact it's shown as up and the db connection is shown as up.

How to repeat:
.

Suggested fix:
Report the correct state or indicate why the correct state can not be determined.

unknown status for the server.

Attachment: Picture 43.png (image/png, text), 37.44 KiB.

After a fresh install of 2.0.4.7138 server I no longer see the problem. So I can't repeat it. 

I guess it's best to close the bug report.

Closed based on last comment.

There has been a new occurrence. Log files and screen shots attached.

Note:

Original report on: Server:2.0.1.7125 Agent: 2.0.4.7139
Latest report on:   Server:2.0.4.7138 Agent: 2.0.4.7141

I'll update the version details in the heading info.

2.0.5 (to be released shortly) will contain a fix we hope makes this disappear: the agent now reads the master.info file and we use that to unambiguously identify the master (if we don't have it, we fall back to IP address, etc.)

Verified fixed on 2.0.5.7148

An entry was added to the 2.0.5 changelog:

The replication status of a server was displayed as “unknown”. However, the agent logged no errors and the server showed no other event problems. The server status was displayed as “up” and the database connection was also displayed as “up”.