Having trouble? See if we can help you out with your issue:
The error message: "Error No. 2003: Can't connect to MySQL server on 'localhost' (or some other host)"
Simply means that connection is not possible for one of the following (or similar) reasons:
Simply means that connection is not possible for one of the following (or similar) reasons:
SQL DM for MySQL can retrieve OS data from Linux operations systems if SSH shell access is possible or configured to that system. Note that SQL DM for MySQL can do this no matter on what Operating System SQL DM for MySQL itself is installed.
You need to always configure Opera to check if graphics was updated. Opera Tools > Preferences > Advanced > History. Opera alone has this option. This is a performance optimization that may be OK with largely static webpages that do not work properly with SQL DM for MySQL webpages. Set Check Images to Always.
On some systems that use a wide-screen monitor, earlier versions of the Opera browser (< 8.5) is not obeying the javascript command to open a new window for the display of a History/TRENDs graph. It opened in an ordinary tab instead. That resulted in the lower part of the graph to be invisible with relatively low screen resolutions (including the popular widescreen resolution 900*1440 (very common with laptops designed for Windows Vista)). You should upgrade Opera.
This error comes up because, if you give 'localhost' as the host, mysql client library trying to use the unix domain socket (file based) instead of the TCP one. And, every mysql client library has one path to the Unix domain socket.
So, if one software works the other breaks. To solve this problem review the following:
The command to create this is:
$ ln -s /var/run/mysqld/mysqld.sock /var/lib/mysql/mysql.sock |
This creates a symbolic link '/var/lib/mysql/mysql.sock' to '/var/run/mysqld/mysqld.sock'. So both applications work.
I can connect to my FTP server, but could not use that same user to get system counters. Even, I can use the same user in SQL DM for MySQL to tunnel to MySQL server. To collect system counters, the SSH user should have access to a shell. This is specified usually in '/etc/passwd' file. But to tunnel to MySQL server the SSH user does not need a shell access. You can check the shell access which is given in /etc/passwd file.
For FTP users generally shell access will be blocked. A typical FTP user has an entry something like this in the '/etc/passwd' file:
john:x:10009:10001:Jonathan:/var/www/vhosts/yourdomain.com:/bin/false |
A colon (:) is used to separate the fields. All the fields are explained below:
This user 'john' can not use a shell. That is the reason ’john’ can not be used for collecting system counters. But user 'john' can be used for tunneling to MySQL server.
A typical user entry with shell access has an entry in /etc/passwd something like:
jenny:x:10002:10003:Jenniffer:/home/jenny:/bin/bash |
Please note that for key based authentication SQL DM for MySQL supports only OpenSSH specified standard key format for public and private keys. SQL DM for MySQL does not work with the keys generated by other SSH related products. This list includes but not limited to key pairs generated by:
There may be two reasons for this error:
Problem: I have a log in a shared folder. I am able to access that log myself, but press test path button in Query Analyzer settings keeps throwing 'File Path Invalid' error.
Solution: By default SQL DM for MySQL installs on Windows with the privileges of the local system account. It does not automatically give you access to shared folders located on other systems. In the Windows service manager (Control Panel -> Administrative Tools -> Services) locate the MONyog(SQL DM for MySQL) service and select Properties from the context (right-click) menu. In the Log On tab, select an account that has sufficient privileges to access the shared folder on the remote system.
To resolve an error like the following:
"Failed to connect to SFTP: Error: offering public key failed, access denied, authentications that can continue: ...." or similar, check the following workaround:
Log file path could be fetched if the MySQL server you are registering is greater than 5.1.6. If your server is lesser than this, then all fields would be read only and you have entered the slow query log/general query log path yourself.
Say for example, in the Query Analyzer Page, the Total column value is 2:16:5.282 but in CSV it is displayed as 16:5.282.
This is a formatting problem in Excel instead if you open the export in Notepad or any other editor this problem will not persist. To view in Excel follow these steps:
After you have started Excel (this FAQ uses Excel 2003), follow these steps:
Set Delimiter to your locale-specific delimiter (COMMA " , " for English and SEMICOLON " ; " for most non-English) as you should have already defined in Preferences. Click Next.
In the Import Data dialog, either one of the following options should be performed:
SQL Diagnostic Manager for MySQL agentless and cost-effective performance monitoring for MySQL and MariaDB.
|