Another Plesk Bug Lock Manager

It is gray when Plesk always changes anything, which then leads to the absolute gau, for example after a reboot! Tily thousands of bugs have already been found by administrators and new ones are constantly popping up, as they are now, when various administrators are despairing because they no longer get the plesk server running, after a reboot and the word round is also the case, the Plesk is also installed in the same way. Could, as simple as

that: The server stands and refuses to work with the following error messages:

Lock Manager error: '[LockManagerException] Can't open or create shared memory by shm.name: '/run/lock/lmlib/SharedLockManagerStorage0.2.4 '; Shm.start _ size: "8388608"; error ' Permission denied '.

Type PleskLockException
Message Lock Manager error: ' Ca[LockManagerException]n't open or create shared memory by shm.name: "/run/lock/lmlib/SharedLockManagerStorage0.2.4"; Shm.start _ size: "8388608"; error ' Permission denied '.
File Hierarchical.ê
Line 126


Here's how the Workarround works:


Cd/run/lock
chown root: Lock-manager lmli

b After that, just update the PHP with F5 function button!

Leave a Reply

Your email address will not be published. Required fields are marked *