Page History

...

TOP

Anchor
FAQ-32 FAQ-32

32. Failed to connect to MySQL: Unknown MySQL server host... What can

...

I do about this?

You get this error if SQL DM for MySQL cannot resolve the hostname of a MySQL server. Ensure that other programs like ping, telnet, MySQL shell client are able to resolve the hostname to an IP-address. If yes, check "/etc/nsswitch.conf" of SQL DM for MySQL host. If the hosts section reads "files mdns4_minimal [NOTFOUND=return] dns mdns4", please change it to "files mdns4_minimal dns mdns4" or "files dns". This is introduced in some current Linux distribution. If other programs are not able to resolve the hostname, please check if host to ip IP resolution is properly defined inside "/etc/host" or in DNS server.

...

SQL DM for MySQL can fetch the queries from the Slow Query log and General query log on Amazon RDS instance using the RDS REST APIs. SQL DM for MySQL requires the AWS access keys to fetch the file-based logs. Go to the Edit Server->Advanced->MySQL Query log and enable the option of "Monitor MySQL Query Log". Click on the Fetch logs(down arrow) button and provide the AWS access key and secret access key to enable SQL DM for MySQL to monitor the log files.

...

SQL DM for MySQL is an important product for us. We plan to add new features as well as to 'refine' existing features. With the latest release we have completed what we originally planned for SQL DM for MySQL (and a little more actually).

• It is now possible to get OS metrics from Amazon RDS/Aurora
• Added more notification channels (Slack, Pagerduty and Syslog) for SQL DM for MySQL alerts."

These features have all been requested by users. SQL DM for MySQL development has always been and will continue continues to be very attentive to user requests. We will update information here when plans for future developments have been decided.

...

SQL DM for MySQL does not support the key generated from PuTTY for SSH connection. However, there is a workaround for it that you can use, you can convert the private key generated from "PuTTY key generator" into an open SSH key, and then you can use this key in SQL DM for MySQL to connect to the server. Here are the steps to follow:

• Go to PuTTY key generator, and generate a public/private key on your local system (refer the screenshot). Click on the Generate button to generate the keys.

...

• Copy the public key generated under the "Key" space to the authorized_keys file, which is located in the .ssh directory on the remote host that you want to connect to.
• Go to "Conversions" in PuTTY key generator and click on "Export openssh key" and save the new converted private key in a file.
• Now open the file containing the converted OpenSSH private key, copy this key and paste in the "Private key" field in SQL DM for MySQL (Edit server -> SSH settings -> Private key).

...

Users can make use of the "MONyog" script shipped with the Monyog(SQL DM for MySQL) package to auto-start MONyog(SQL DM for MySQL) service with OS reboot. The SQL DM for MySQL script is located at " /MONyog/bin/". Please follow the steps below steps:

• Copy the 'Monyog' to "/etc/init.d/" from " /MONyog/bin/"
• Open the 'Monyog' script located at "/etc/init.d/" and edit the variable "curdir" (line number 15) and set it to the path of bin. After editing, it should look like this: curdir="/home/Users/Downloads/MONyog/bin/"
• Make the script executable by 'chmod +x /etc/init.d/MONyog'
• Use debian utility update-rc.d to install the script: update- rc .d MONyog defaults

...

The SQL DM for MySQL binaries are shipped in 3 packages: .tar, .rpm and .exe. The upgrade process is simple and depends on your package. The below steps will help you Follow the steps below to upgrade to the latest version of SQL DM for MySQL version without a hassle:

For .rpm package :

rpm -Uvh <MONyog_package>.rpm

This command will install installs the latest build on top of your current installation.

...

For Windows (.exe) package:

Executing the file will install installs SQL DM for MySQL on top of the current installation.

All SQL DM for MySQL data and the configuration files are stored in an a SQLite repository. In some of the SQL DM for MySQL GA releases, we modify/change the monitor definition in the SQLite files due to some bug or enhancements. In such cases, on upgrading, all the local changes made by the user in the previous version gets get replaced with the default shipped value and these local changes are shown as a conflict. You can see the conflicts as a notification on the top right-hand corner.

...

You can resolve these conflicts from the “Settings “Settings -> Manage changes” changes” page, herein you get 2 options for all the listed conflicts: Use your changes/Discard your changes. 1- Use your changes will restore , restores the local modifications which you had made in the previous version. 2- Discard your changes, will replace replaces your changes with the default values.

...

Uncomment the below lines in the file to enable web interface. You can login to the web interface using the username as ‘admin’ and password as ‘monit’.

set httpd port 2812 and
use address localhost  # only accept connection from localhost
allow localhost        # allow localhost to connect to the server and
allow admin:monit      # require user 'admin' with password 'monit'

Also add the below lines in the config configuration file to enable the monitoring of MONyog(SQL DM for MySQL) service:

...