Overview
This article explains the steps to follow when you observe a slow response while using the MGR GUI that is related to the MySQL database.
Solution
Check for the following MySQL database errors in the specified log files:
- tp_mgr_error_log.txt:
 Error: Database Error: DBD::mysql::st execute failed: MySQL server has gone away
- mgr_error_log.<ID>:
 I/O warning : failed to load external entity
If you find these errors in the log files while the MGR GUI runs slowly, please restart the MGR by running the following commands as a root user:
    Note: Keep a note of the output of steps 1 and 4, since they may be required for further troubleshooting if the issue remains unresolved.
  
  - systemctl status mgr
- systemctl stop mgr
- systemctl start mgr
- systemctl status mgr
If you have trouble running the systemctl commands, please restart the MGR process by running the following commands as a root user:
- /usr/TextPass/bin/tp_mgr_stop
- /usr/TextPass/bin/tp_mgr_start
    Note: If the issue persists after restarting the MGR, file a support request in the Skyvera Support Portal and share details of all the steps followed and the saved output of the above commands.
  
  
Priyanka Bhotika
Comments