[sandhya.r]

Hi Johan,

 

ClientAliveInterval value is in seconds. If your data collection interval is 3 minutes, we recommend you to set “ClientAliveInterval” as 300 seconds(which is > 3minutes).

 

Thanks,

Sandhya.

[sandhya.r]

Hi,

 

Can you please tell the value of “ClientAliveInterval” in “/etc/ssh/sshd_config”?

 

Please try increasing the value of “ClientAliveInterval” parameter? the value is in seconds (and the default value is 0). 

The “ClientAliveInterval” value should be greater than the data collection interval of that server(Edit a server –> Advanced Settings –> Data collection interval).

If your data collection is set to 5 minutes (i.e. 300 seconds) the “ClientAliveInterval” can be set to, say, 900 seconds. which is greater than data collection interval specified in MONyog.

 

Also, you will need to set “KeepAlive” to yes. For the changes to be effective you will need to restart your sshd service.

Let us know whether this resolves your problem. 

 

Thanks,

Sandhya

Team MONyog

[sandhya.r]

Hi,

 

We will check this and get back to you with more details on this. 

 

 

Regards,

Team MONyog.

[sandhya.r]

Hi,

 

We are planning to support EXPLAIN plan for PROCESSLIST based sniffer and Slow-log TABLE based query analysis. However, EXPLAIN plan cannot be supported for Slow-log and General-log FILE (and TABLE) for the following reasons:

 

1. For Slow-log FILE based logging “Use database;” statement does not get recorded consistently. Also, MONyog reads the logs in chunks and if in that chunk “Use database;” statement is skipped then MONyog does not know which database query belongs to. Same applies to General-log FILE based logging.

 

2. For General-log TABLE based logging there is no “Database” column available in the ‘general_log’ table which is required to execute EXPLAIN plan for a query and hence it cannot be supported.

 

For MySQL v5.6.14 (and above), MONyog performs query sniffing based on Performance_schema tables. EXPLAIN plan is available here. 

 

 

Regards,

Team MONyog. 

[sandhya.r]

Hi,

 

Issue reproducible. We will fix this and it will be available in the next public release.

 

Thanks for reporting.

 

Regards,

Sandhya

Team MONyog

[sandhya.r]

Hi,

We have tried in our environment and we are not able to reproduce this issue.

Can you please tell us the following details

1. Which browser and the exact version you are using? I guess it's IE when you mention “Error on page”.

2. Does this issue happen with all counters or any particular counter?

3. Are there any CSO's enabled?

4. Is this the same behavior on other browsers? (Chrome or Firefox)

5. Is MONyog running on Windows or on Linux machine? 32 or 64 Bit architecture?

I think you have created a ticket in our support system. We will continue the discussion there.

Thanks,

MONyog team

[sandhya.r]

Hi,

We have LDAP authentication for login into MONyog on the schedule. You can expect this in the upcoming versions of MONyog.

Stay tuned to our blogs to get information on our releases.

Thanks,

Team MONyog

[sandhya.r]

Issue Confirmed.

The problem was with “Id” column. It is fixed now.

We will provide you a special build to verify this bug fix. Please tell which MONyog build you are using(Windows/Linux32/LInux64)?

[sandhya.r]

Can you please

1) Attach the output of the query “SHOW FULL PROCESSLIST”.

2) Make a duplicate connection of the problematic server and try whether it is reproducible with that server or not.

[sandhya.r]

Hi,

Issue confirmed.

We will fix this in next version.

Thanks for reporting.

Regards,

Sandhya

[sandhya.r]

Hi,

We have found the location of the crash and analyzing the possibilities.

We'll update you tomorrow.

Regards,

Sandhya

[sandhya.r]

Hi,

We are trying to reproduce the issue at our end with similar configuration as yours, but with no luck.

We have received the core dump and we are analyzing the dump.

Regards,

Sandhya

[sandhya.r]

Hi,

In ini file the data path is missing and registration details contains some special charaters. This means file may have been corrupted.

Reinstalling MONyog will solve this problem. Reinstalling MONyog will not cause any data lose.

Regards,

Sandhya

[sandhya.r]

Hi,

Can you please confirm whether the data folder exists or not?

You can find the data folder in,

{System_drive}:Documents and SettingsAll UsersApplication DataWebyogMONyogdata

And also, please check whether the ini file is corrupted or not.

Regards,

Sandhya

[sandhya.r]

Hi,

We observed with latest MONyog version too that Internet Explorer is hanging while loading MONyog login page.

Environment:IE6(6.0.2800) on Windows 2000 professional.

We are looking into this issue.

Can you confirm same behaviour you have observed with v3.73?

Also does MONyog interface works fine with other browser like IE 7/8 or Firefox?

[Author]

Posts