• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

can't disable domains on 7.5.5

A

amram

Guest
When I connect to plesk via admin account and try to disable a domain I get this:

_____________
Unable to activate/deactivate doamin: Unable to update domain data: Unable to update domain:
bsdomain: Lock wait timeout exceeded; try restarting transaction..
____________

I get this when disabling most of them not all!
Also when I connect to the server via RDP and connect to plesk locally from there I can Disable these domains!!

Please Help!
 
now there is a domain that gives this error even when I try to disable it locally form server.
 
It seems that you should configure my.ini file of admin's mysql with

innodb_lock_wait_timeout=200

parametr. You can configure different values (by default it is 50)
You should add it to [PleskSQLServer] field and restart Plesk's MySQL.
 
thank you for the hint Gris. I will do that and will share the results.
Also I noticed something, I have scheduled statistics.exe to run every hour and it takes about
10 to 15 minute for more than 500 doamins to complete.
every time I try to disable a domain during this period I get
the error and I keep getting this error even after the statistics.exe has finished it's work and
terminated.
But if I wait until after the termination of the next scheduled statistics.exe and try again the error
is gone and these domains get disabled!!!!!
 
humm.. its a good information amram

So, raise the time betwenn schedule os statistics ;)
I'll expect the results of the topic...

A good day for all
 
changed the innodb_lock_wait_timeout=200 as Gris said but I still get the same error. also rising the time between scheduled statistics.exe will increase the execution duration and increases the chance of getting the error.
so now each time I want to activate and deactivate a domain have to keep an eye on taskmanager for statistics.exe to avoid getting the error.
BTW has any one else got this error, or it's just me?
 
Back
Top