How can I execute a MySQLDebug.bat / MySQLDebug.sh file?
This
file is used to check if the connectivity and the Discovery of the MySQL Server
is possible from the Applications Manager installed server. This
standalone program is a excerpt of the same process we use to add the MySQL
Server monitor. The usage to run this file is as below
Via command prompt goto AppManager/bin/troubleshooting directory and execute the MySQLDebug file with the usage below.
Usage: MySQLDebug.bat [HostName / Ip] [Port Number] [Database Name] [Username] [password] [useSSL] [apmkeystore password]
[HostName / Ip] HostName or Ipaddress of the machine where MySQL server is running
[Port Number] Port number of the MySQL server
[Database Name] Database Name for connecting to the MySQL server
[Username] User name for connecting to MySQL
[Password] Password for connecting to MySQL. If no password enabled, leave it as blank
Via command prompt goto AppManager/bin/troubleshooting directory and execute the MySQLDebug file with the usage below.
Usage: MySQLDebug.bat [HostName / Ip] [Port Number] [Database Name] [Username] [password] [useSSL] [apmkeystore password]
[HostName / Ip] HostName or Ipaddress of the machine where MySQL server is running
[Port Number] Port number of the MySQL server
[Database Name] Database Name for connecting to the MySQL server
[Username] User name for connecting to MySQL
[Password] Password for connecting to MySQL. If no password enabled, leave it as blank
[useSSL] useSSL is true if the MySQL server is configured for forceful SSL authentication. It will be false for the respective MySQL server's default SSL behavior.
[apmkeystore password] APM Keystore password is required if useSSL is true to verify the certificates which are used to make a secure connection.
This will initiate the process to discover the MySQL Server and on success will also fetch the data for the default attributes monitored and shown as the output. From this, you will be able to find If discovery is possible If data is returned for all attributes or not. In case there is any issue for an attribute data it'll be shown as null. This infers that the data is not available in that server and has to be checked on the MySQL installed server.
For more info or assistance, do send us the output of the above command for analysis along with Support Information File.
New to ADSelfService Plus?
Related Articles
How to execute runWLSMbean.bat or sh file?
Execute the runWLSMbean.bat or sh file from the <AppManager_home>\bin\troubleshooting folder via command prompt or terminal. Eg. ~/Zoho/ManageEngine/ManagedServer/AppManager15/bin/troubleshooting$ ./runWLSMbean.sh It will prompt for the details to ...How to execute ServerSSHTroubleshoot.bat or sh file ?
Solution: Execute the file ServerSSHTroubleshoot.bat or sh from the <AppManager_home>\bin\troubleshooting folder (<AppManager_home>\bin in older versions of Applications Manager). Via command Prompt Execute the ServerSSHTroubleshoot.bat or sh file. ...How can I execute the GlassFishDebug.bat / GlassFishDebug.sh file?
Note: Although the script name mentions GlassFish Server, the script file can be used for troubleshooting any monitor connectivity issues, that comes under JMX mode of monitoring like JMXApplications, Apache Zookeeper, Apache Geronimo etc., This file ...How can I execute UpdateHostnameandIP.bat/sh ?
Here are the steps to execute UpdateHostnameandIP.bat/sh: 1) Execute <AppManager_Home>\bin\troubleshooting\UpdateHostaneandIP.bat/sh file. For example, updateHostNameAndIp.bat/sh [Previous HostName/IpAddress] [new HostName/IpAddress] ...How to execute WebsphereMQDebug.bat / WebsphereMQDebug.sh?
This file is used to check if the connectivity and the Discovery of the Websphere MQ Server is possible from the Applications Manager server. This standalone program is an excerpt of the same process we use to add the Websphere MQ Server monitor. The ...