Troubleshooting

Some of the problems that you might encounter during the course of deploying the MySQL agent and managing the MySQL server are listed below. The cause of the snag and the key to its resolution are offered to prevent you from facing a deadlock.

1. Problem: Unable to start the agent in Unix systems. The following error occurs when trying to start the agent in Unix systems:
   
   Error while loading shared libraries: libmysqlclient.so.10: cannot open shared object file: No such file or directory
   
   Cause: This happens when the MySQL client libraries are not present under /usr/lib or the path specified by LD_LIBRARY_PATH.
   Solution: Install the libmysqlclient.so under /usr/lib or the path specified by LD_LIBRARY_PATH.
    

2. Problem: The tables , such as Slow Query table, Update Query table, General Query table, and Error table are empty.
   Cause: When the AdventNet SO/DLL is not deployed in the MySQL server, all the mentioned tables will not be exposed.
   Solution: Deploy the AdventNet SO/DLL in the machine where MySQL server is running at the location specified below:
   
   For Windows: Deploy the adventnetmma.dll file present under <AdventNet Micro Agent Home>/lib into the %WINDIR%\system directory of Windows.
   
   For Linux/Solaris: deploy the adventnetmma_linux.so/adventnetmma_solaris.so file present under <AdventNet Micro Agent Home>/lib into the /usr/lib directory of Linux/Solaris.
    

3. Problem: Inconsistent restarts with MySQL 3.23.52 in Linux machines.
   Cause: When the agent connects to the MySQL server, there are some problems in resolving the host name.
   Solution: Use the --skip-name-resolve option while starting the MySQL server.