• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

Plesk big problem, cannot using for webhosting

LukasK

New Pleskian
Hi I have problem with Plesk 12.0.18. Since version MU27 through MU28
When someone try to re-login to admin panel. Plesk stop respond and show error in panel.log

Code:
[2014-12-12 20:22:19] ERR [panel] Unable to get key: error: /etc/sw/keys/lock/repository: lock() failed: No locks available
[2014-12-12 20:22:19] ERR [panel] Unable to get key: error: /etc/sw/keys/lock/repository: lock() failed: No locks available
[2014-12-12 20:22:19] ERR [panel] Unable to get key: error: /etc/sw/keys/lock/repository: lock() failed: No locks available
[2014-12-12 20:22:19] ERR [panel] Unable to get key: error: /etc/sw/keys/lock/repository: lock() failed: No locks available
[2014-12-12 20:22:19] ERR [panel] Unable to get key: error: /etc/sw/keys/lock/repository: lock() failed: No locks available
[2014-12-12 20:22:19] ERR [panel] Unable to get key: error: /etc/sw/keys/lock/repository: lock() failed: No locks available
[2014-12-12 20:22:19] ERR [panel] Unable to get key: error: /etc/sw/keys/lock/repository: lock() failed: No locks available
[2014-12-12 20:22:19] ERR [panel] Unable to get key: error: /etc/sw/keys/lock/repository: lock() failed: No locks available

and in messages file
Code:
Dec 12 21:31:01 systemd: Stopping LSB: Start Plesk engine...
Dec 12 21:31:01 sw-engine: Stopping sw-engine-fpm: [  OK  ]
Dec 12 21:31:01 sw-engine: Fatal error: Call to undefined method Lock::clean_lock_manager_shm() in Command line code on line 1
Dec 12 21:31:01 systemd: Starting LSB: Start Plesk engine...
Dec 12 21:31:01 sw-engine: Starting sw-engine-fpm: Could not open Repository at "/etc/sw/keys": /etc/sw/keys/lock/repository: lock() failed: No locks available
Dec 12 21:31:01 sw-engine: Fri Dec 12 21:31:01 2014 (20653): Error Cannot create lock - No locks available (37)
Dec 12 21:31:01 sw-engine: [FAILED]
Dec 12 21:31:01 systemd: sw-engine.service: control process exited, code=exited status=1
Dec 12 21:31:01 systemd: Failed to start LSB: Start Plesk engine.
Dec 12 21:31:01 systemd: Unit sw-engine.service entered failed state.

Then server stop respond and I must run /etc/init.d/psa stopall and /etc/init.d/psa startall
 
Last edited:
Hi LukasK,

please check your permissions:

ls -ld /etc/sw /etc/sw/keys /etc/sw/keys/lock /etc/sw/keys/lock/repository

should all result in permissions for: root swkey-data
 
ls -ld /etc/sw /etc/sw/keys /etc/sw/keys/lock /etc/sw/keys/lock/repository
drwxr-xr-x 3 root root 4096 Nov 14 09:40 /etc/sw
drwxrws--- 7 root swkey-data 4096 Dec 12 04:19 /etc/sw/keys
drwxrws--- 2 root swkey-data 4096 Nov 14 09:40 /etc/sw/keys/lock
-rw-rw---- 1 root swkey-data 0 Aug 11 11:47 /etc/sw/keys/lock/repository
 
Hi LukasK,

please try to repair your Plesk installation with the bootstrapper repair:

/usr/local/psa/bootstrapper/pp12.0.18-bootstrapper/bootstrapper.sh repair
 
Hi it seems that the problem is back :-(
Code:
[2014-12-14 04:17:01] ERR [panel] Updates were not installed: No locks available
.
.
.
[2014-12-14 04:17:30] ERR [panel] Error: Repository is not opened
.
.
.
[2014-12-14 04:17:31] ERR [panel] Unable to get key: Repository is not opened
[2014-12-14 04:17:31] ERR [panel] Unable to get key: Repository is not opened
[2014-12-14 04:17:32] ERR [panel] Unable to get key: error: /etc/sw/keys/lock/repository: lock() failed: No locks available
[2014-12-14 04:17:32] ERR [panel] Unable to get key: error: /etc/sw/keys/lock/repository: lock() failed: No locks available
 
What sort of output of this command on your server?

# getenforce
 
I can only recommend to create a request to support team to do in-depth investigation to find the reason and to fix it. Please create a ticket to support at https://odin.com/hcap/support/request/ .
You may have free support, please check what kind of Plesk license you use for available support options at http://kb.odin.com/en/121580 .
If there’s no free support in your case, you can order Plesk per-incident support at http://odin.com/hcap/support/buy-support/. Support team will contact you as soon as purchase is processed, and they will do the best to resolve it.
If it is found that your problem was caused by product bug w/o available solution or workaround from Parallels, then your purchase will be re-funded.
 
Back
Top