Alert Persist And Doesn't Clear Itself

[Aaron Lee]

I keep getting the following alerts and they don't seem to clear themselves, I have restarted MONyogd and clear the data dir

Server: db0

Sampling timeframe: All Time/Current

Type Group Name Threshold Value Advice

Critical Current Connections Percentage of max allowed reached 85 100.66%

1. Make sure that you have a reasonable high value for max_connections.

2. Design your application such that a MySQL connection is kept open for a very short period of time.

3. Try pooling connections or switch to persistent connections to reduce the number of active MySQL connections. For example try using mysql_pconnect() instead of mysql_connect()

This is my stats on /showall.html

Max allowed 151.00

Open connections 9.00

Connection usage 5.96%

Currently running threads 2

Highest no. of concurrent connections 152.00

Percentage of max allowed reached 100.66%

Idle time after which a client is disconnected 8 hrs

How can we have 9 open conn with 151 max allowed and still reach more than 100% ALL the time?

Seems like a bug

I am using 3.14, thanks

-Aaron

[peterlaursen]

 This alert does not alert about 'current situation' but about 'the worst situation that occurred in this respect since server was restarted lst time or FLUSH STATUS was executed last time (what btw. is obvious from the formula “Max_used_connections / max_connections”)

Execute 

1) SHOW GLOBAL STATUS LIKE 'Max_used_connections'

2)  SHOW GLOBAL VARIABLES LIKE 'max_connections'

.. perform the division yourself and you will get same result.

To reset  'Max_used_connections' status variable execute FLUSH STATUS.  But if it happens frequently you should investigate the reason for this. It could be an intrusion attempt for instance.

Please see how the counter/advisor is defined:

[attachment=1441:max.jpg]

[Aaron Lee]

Thanks Peter,

That solved the problem, would it be possible to include this in pop up help dialog box? This would help other users tremendously in the future versions.

-Aaron

'peterlaursen' wrote:

 This alert does not alert about 'current situation' but about 'the worst situation that occurred in this respect since server was restarted lst time or FLUSH STATUS was executed last time (what btw. is obvious from the formula “Max_used_connections / max_connections”)

Execute 

1) SHOW GLOBAL STATUS LIKE 'Max_used_connections'

2)  SHOW GLOBAL VARIABLES LIKE 'max_connections'

.. perform the division yourself and you will get same result.

To reset  'Max_used_connections' status variable execute FLUSH STATUS.  But if it happens frequently you should investigate the reason for this. It could be an intrusion attempt for instance.

Please see how the counter/advisor is defined:

[attachment=1441:max.jpg]

[Shalmali]

Currently we are working on clearing alerts with out executing FLUSH STATUS.

This enhancement should be out in the next couple of weeks.

Thanks!

-Shalmali

[Author]

Posts