[Sayan Chaliha]

Hi Sushil,

Could you check your sniffer settings for 'Data retention timeframe' and your 'Filter' settings for the Query Analyzer? When using a large data retention time-frame, a whole lot of data is accumulated, and as a result it will slow down the analysis process (as the entire data-set is processed unless you change the filter settings).

[Sayan Chaliha]

Hi Andrew,

This can be simply done by hard-coding another condition in replication-4.js. Here's an example:

Code:

obj = {

Group : “Replication”,
Name : “Slave I/O state”,
Formula : “Slave_IO_State”,
Value : function()
{
if(IsReplicationSlave(MONyog.Server.Config.IsReplicationSlave) == false || !MONyog.MySQL.Slave.Slave_IO_State || MONyog.Connections.ConnectionName == '')
return “(n/a)”;

return (MONyog.MySQL.Slave.Slave_IO_State);

},

DocText : “This value is same as the State Field of SHOW PROCESSLIST of slave I/O Thread.” +
” This gives you more details on what the thread is doing – whether its trying to connect to the master,”+
” waiting for events, reconnecting to the master, etc.”
};
_ALL_COUNTERS.push(obj);

This will disable it and display only '(n/a)' for the connection named ''. If you configured alerts for this counter, ie, MailAlert: 'Yes', this will also prevent mails from being sent for ''.

[Sayan Chaliha]

Hi Larsen,

Most pages in MONyog are updated in real-time with new data. This is somewhat like a full page refresh, except that you don't see the flicker. So, as it is now, it is not feasible to retain user-selected text between updates.

[Sayan Chaliha]

Hi Traian,

This forum is for MONyog — MySQL Monitor.

All SQLyog queries should be posted in the SQLyog forum, and I will move this thread there.

Thanks, and I'm sure someone will get back to you at the soonest.

[Sayan Chaliha]

What about the firewall settings on the AWS interface? You have to explicitly specify which host/ports to allow access to.

Also, did you check MONyog's log? There may be more information as to why the tunnel failed in the log.

[Sayan Chaliha]

Hi Karthik,

If I'm not mistaken, Amazon allows only key-based authentication for remote SSH logins to EC2. So, to have MONyog login to EC2, you'll need both the public- and private- keys. Do you have both keys? Also, what is the exact error message reported by MONyog? Can you check the error log as well?

[Sayan Chaliha]

Yes, human errors, mostly to do with assigning the right permissions, may cause quite a lot of confusion. If you could upload the log here, I can try and help you resolve the issues. About the graphs not loading soon enough — this may happen due to various reasons ranging from HDD I/O rates to connection speeds for the network. But, one thing's for sure, the graphs would've appeared even without you having to refresh the page, and they would've required the same amount of time that you spent refreshing the page.

[Sayan Chaliha]

Hi BenMc,

That's really weird.. No user has ever reported anything to that effect before. Anyway, I'm going to need a few details to get a clear view of your problem:

1) What is the OS of the system running MONyog?

2) What is the OS of the system running MySQL?

3) Which version of MONyog are you using?

Additionally, the MONyog error log (MONyog.log) can be found in:

— Windows XP: C:Documents and SettingsAll UsersApplication DataWebyogMONyog

— Linux: /usr/local/MONyog/

(if installation was done using the default settings).

[Sayan Chaliha]

Hey Brad,

“MySQL server has gone away” is generated by the MySQL client library (libmysql) that we use in MONyog. There are several reasons as to why this error occurs. I'd refer you to this blog post (note that it is in two parts), but in brief:

— This error occurs when MySQL does not respond to MONyog's (or any client's, for that matter) query after a successful connection;

— The most common cause in this case is that MySQL's 'wait_timeout' variable is set lower than MONyog's data collection interval. Use the following query to determine your server's 'wait_timeout':

Code:

SHOW GLOBAL VARIABLES LIKE 'wait_timeout';

— An immediate resolution to your problem would be to increase the 'wait_timeout' of your server:

Code:

SET GLOBAL wait_timeout=28800;

28800 implies 8 Hrs, which is the default in most MySQL distributions.

— Note that this error doesn't affect MONyog's functionality nor that of MySQL's.

Also, it is improbable that you'd find 'lib/webyog/src/ymysql.cpp' or any other MONyog source file. The error log records the exact line number of the source file that generated the error so that our debugging team knows exactly which part of the source code registered the error.

[Sayan Chaliha]

Hi Rockeis,

Here are answers to your questions:

1. This would depend on which version of MONyog you are using. MONyog 3.5 and earlier has an option called “Minimum interval between notifications” in Edit Server –> Notification Settings. MONyog generates alerts when this interval has elapsed. Newer versions of MONyog use a different concept: Counters are checked at every data collection, and alerts are sent immediately if a counter's value is above the threshold for a specified number of counts (specified by the option Edit Server –> Notification Settings : “Notify when alert-able _____ times”). Subsequent alerts for the same event are sent after another specified number of counts (specified by the option Edit Server –> Notification Settings : “Notify again after every _____ alert-able cycles”), to a max of 4 alerts.

2. MONyog sends them all in one e-mail itself.

3. Alerts for % of refused connections from MONyog means that MONyog was able to connect to the MySQL server successfully, and that the MySQL server was refusing too many other (not MONyog's) connections (perhaps because of invalid credentials, or an attempt at hacking?).

[Sayan Chaliha]

Hi Ron,

The test mail is sent to the account you use to login in to the SMTP server. For example, suppose you entered the following details:

SMTP Server: smtp.gmail.com

Port: 465

Encryption: SSL

Username: sayan.chaliha

Password: xxxxxxxxxxxxxxx

Then, the test mail will be sent to sayan.chaliha AT gmail.com…

[Sayan Chaliha]

Hey Ratheesh,

First of, assuming that you are using MONyog 3.6 Trial, we discovered a serious bug, and made a new release with a fix (MONyog 3.61). I suggest that you use the 3.61 trial instead.

Now, coming to the notification settings, here's how they work:

— The 'Notify when alert-able __________ times' field: The number you put in this field is the number of times that MONyog should detect a counter's value as above the threshold in a row before it considers that counter for an alert. The next obvious question is, when does MONyog check the counter's value? MONyog does this at every data collection. Suppose your data collection interval is 5 minutes, and you've specified 2 in the above field, then the counter should be in an alert state for 10 minutes continuously before MONyog reports it.

— The 'Notify again after every _________ alert-able cycles' field: After the first notification, MONyog will send the next notification if the counter remains in a warning or critical state for the number of times specified here.

[Sayan Chaliha]

Hi Ratheesh,

I am afraid that would not be possible through the JavaScript customization feature of the Monitors/Advisors. However, the good news is that I have added your request for this feature to our issue tracker, and you can expect it in a future release of MONyog.

[Sayan Chaliha]

Hi Ratheesh,

For 'Percentage of Full Table Scans' to be reported correctly, the MySQL server should be running for some time, ie, the server has to warm-up. By default, MONyog sets this warm-up time to 3 hours (which can be changed from Tools –> Preferences). So, only after MySQL has been running for 3 hours, MONyog considers that counter's value for alerting.

Can you find out your MySQL server's uptime (from 'General Info' –> 'Running For' in the Monitors/Advisors page), and get back to us here?

[Sayan Chaliha]

That would entirely depend on the SNMP client software that you are using. For example, here's a screenshot of how traps appear in the lightweight receiver from iReasoning:

[attachment=1295:screenshot.GIF]

I suspect that there should be a way to load MIB files from your SNMP client. That way, you wouldn't even have to add the OIDs manually, and much of the gibberish numbers are actually converted into much more meaningful strings.

For instance, on iReasoning's MIB Browser, enterprises.34330.1.1.1.0 appears as enterprises.webyog.monyog.monitor.ServerName.0

Which SNMP client are you using, anyhow? Maybe I can play around with it a bit, and then I can give some pointers.

[Author]

Posts