Resolved Internal error: Lock Manager error: 'No locks available'.

[Maximillian Schmidt]

Hey Plesk Community,

just updated to Onyx and after two weeks I ran the first update (#9). After finishing the update I've tried to login but this error message keeps showing up:

Message No locks available
File Hierarchical.php
Line 201
Type UnknownError

Any ideas on how to fix this? Thanks upfront for any suggestions

 

[IgorG]

Try to fix it with

# plesk repair installation

 

[AndrewF]

Hi, Maximillian.

Can you give us more information?:
- What is your OS?
- Is it any other proiblems on your Plesk?

A possible solution: you can clear LockManager-cache by restarting of sw-engine: service sw-engine restart.

And you can help us to improve quality of our product by creating of a ticket: https://cscontact.plesk.com/form/32/?Product=Plesk

 

[Maximillian Schmidt]

Hi, Maximillian.

Can you give us more information?:
- What is your OS?
- Is it any other proiblems on your Plesk?

A possible solution: you can clear LockManager-cache by restarting of sw-engine: service sw-engine restart.

And you can help us to improve quality of our product by creating of a ticket: https://cscontact.plesk.com/form/32/?Product=Plesk

CentOS 6.8 (Final)‬ on a Virtuozzo VPS. Checking the user_beancounters ("cat proc/user_beancounters") shows me the numflock value clipped a few times (200+ times). Rebooting the VPS and trying to update (Plesk Onyx 17.0.17 Update Nr. 7 to Update Nr. 11) again ends with the same error message and the same user_beancounters values.

 

[Maximillian Schmidt]

Ended up contacting my VPS host who raised my numflock value. Now everything works fine for me - thanks for the help!