Lock Wait Timeout Exceeded in OnApp can be easily resolved with a little help from our experts. 

At Bobcares, we offer solutions for every query, big and small, as a part of our Server Management Services.

Let’s take a look at how our Support Team is ready to help customers deal with Lock Wait Timeout Exceeded in OnApp.

How to resolve Lock Wait Timeout Exceeded in OnApp

Have you been running into the following error message trouble while attempting to delete a virtual server?

Mysql2::Error: Lock wait timeout exceeded; try restarting transaction

If the answer is yes, you are in the right place. Our Support Techs have come up with a solution for this specific issue.

It involves increasing the lock wait timeout in the MySQL configuration. Let’s have a look at the process:

1. First, log into the control panel server as a root user via SSH.
2. Next, edit the /etc/my.cnf file and modify innodb_lock_wait_timeout=#### under the [mysqld] section. We have to replace #### with the number of seconds we prefer. By default, this value is 50.

   Our Support Techs recommend increasing it to 120 or higher. However, this depends on the volume of disk statistics of the virtual servers.
3. Then, verify if there are no transactions pending or running and stop the OnApp daemon with the following command:

   /etc/init.d/onapp stop
4. After that, we have to restart the MySQL server with this command:

   /etc/init.d/mysqld restart
5. We can also opt to verify the MySQL settings by running the following command after opening the MySQL CLI

   SELECT @@innodb_lock_wait_timeout;
6. Finally, start the OnApp daemon with the command below:

   /etc/init.d/onapp start

After following the above steps, we will be able to delete the virtual server successfully without running into any errors.

[Looking for a solution to another query? We are just a click away.]

Conclusion

To conclude, our skilled Support Engineers at Bobcares demonstrated how to deal with Lock Wait Timeout Exceeded in OnApp.