Join 34,000+ subscribers and receive articles from our blog about software quality, testing, QA and security.

Testrail cant connect to MySQL


Hello there. We have testrail on a virtual machine that works. But every month we need to reboot the server because when a user tries to logon on to the webpage the user gets the following error:

Can’t connect to MySQL server on ‘’ (111)

We do use backup exec to backup the virtual. When we get the error, we just reboot and everything is fine. Has anyone else ran into this issue?



Thanks for your posting. This means that there’s an issue with your MySQL server and it seems that your MySQL is shutting down from time to time (a reboot would start the MySQL service again). This would be independent of TestRail and can you check the MySQL logs (can usually be found under /var/log/mysql/)?



This is the error that I get:

160810 23:48:02 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
160810 23:48:02 [Note] Plugin ‘FEDERATED’ is disabled.
160810 23:48:02 InnoDB: The InnoDB memory heap is disabled
160810 23:48:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160810 23:48:02 InnoDB: Compressed tables use zlib 1.2.8
160810 23:48:02 InnoDB: Using Linux native AIO
160810 23:48:02 InnoDB: Initializing buffer pool, size = 128.0M
160810 23:48:02 InnoDB: Completed initialization of buffer pool
160810 23:48:02 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
160810 23:48:02 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files…
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer…
160810 23:48:05 InnoDB: Waiting for the background threads to start
160810 23:48:06 InnoDB: 5.5.50 started; log sequence number 21880380965
160810 23:48:06 [Note] Server hostname (bind-address): ‘’; port: 3306
160810 23:48:06 [Note] - ‘’ resolves to ‘’;
160810 23:48:06 [Note] Server socket created on IP: ‘’.
160810 23:48:06 [Note] Event Scheduler: Loaded 0 events
160810 23:48:06 [Note] /usr/sbin/mysqld: ready for connections.
Version: ‘5.5.50-0ubuntu0.14.04.1’ socket: ‘/var/run/mysqld/mysqld.sock’ port: 3306 (Ubuntu)
160810 23:48:07 [ERROR] /usr/sbin/mysqld: Table ‘./mysql/proc’ is marked as crashed and should be repaired
160810 23:48:07 [Warning] Checking table: ‘./mysql/proc’


This looks like something is wrong with your database and the following line needs attention:

160810 23:48:07 [ERROR] /usr/sbin/mysqld: Table './mysql/proc' is marked
as crashed and should be repaired

Do you have the option to contact your IT and/or TestRail administrator to look into? We aren’t able to provide support for something else than TestRail unfortunately, especially when it concerns other important systems such as your database.