Bug #47997 MEM agent skipping error message, no need to be critical

• Submitted: 12 Oct 2009 12:38
• Modified: 13 Oct 2009 17:36
• Reporter: Roger David Nay
• Status: Duplicate
• Category: MySQL Enterprise Monitor: Agent
• Severity: S4 (Feature request)
• OS: Any
• Assigned to: Assigned Account
• CPU Architecture: Any

[12 Oct 2009 12:38] Roger David Nay

Description:
The following skipping messages don't appear to be 'critical' should be logged as message or info.

2009-10-09 21:30:53: (critical) network-io.c:845:mysql_quanconfig_update(): we already have a task for mysql::server[304b93f2-e004-4258-bca9-6c61986f433c], skipping
2009-10-10 09:32:14: (critical) network-io.c:845:mysql_quanconfig_update(): we already have a task for mysql::server[304b93f2-e004-4258-bca9-6c61986f433c], skipping
2009-10-10 21:33:45: (critical) network-io.c:845:mysql_quanconfig_update(): we already have a task for mysql::server[304b93f2-e004-4258-bca9-6c61986f433c], skipping
2009-10-11 09:34:02: (critical) network-io.c:845:mysql_quanconfig_update(): we already have a task for mysql::server[304b93f2-e004-4258-bca9-6c61986f433c], skipping

How to repeat:
N/A.

Suggested fix:
Reduce the log-level for the skipping to an informational message.