• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Server Error 500 Plesk\Lock\Exception

plesk installer --select-release-current --reinstall-patch --upgrade-installed-components

You can not run this command from a rescue system.
When you start the rescue system your server will not be booted regularly.
It is just another OS where your filesystem is mounted under /repair.
So you can change files in the file system, but you cannot run commands in your system.
 
Strato informs:

No Plesk login possible? "Can't open or create shared memory by shm.name"
Dear customer,

Some PLESK users may not be able to login to PLESK due to a bug.
The message may appear in the browser:

[LockManagerException] Can't open or create shared memory by shm.name: "/run/lock/lmlib/SharedLockManagerStorage0.2.3"; shm.start_size: "8388608"; error "Permission denied".

or

PLESK_INFO: Plesk\Lock\Exception
Message 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 "No such file or directory"'.
File Hierarchical.php
Line 126

There is a known workaround:
1. log on to your server via SSH.

2. start
# crontab -e

3. add the following line
@Reboot mkdir -p /run/lock/lmlib && chown root:lock-manager /run/lock/lmlib && chmod -R 0770 /run/lock/lmlib

Restart your server, after the reboot the rights will be set correctly and you can log back into Plesk.

Note: If there is no /run/lock/lmlib on your server, use /var/lock/lmlib instead.

For more information, see the following URL
Plesk is not accessible: Can't open or create shared memory by shm.name

Yours sincerely
Your STRATO Team

Translated with www.DeepL.com/Translator


Kein Plesk-Login möglich? “Can’t open or create shared memory by shm.name”
Sehr geehrte Kundin,
sehr geehrter Kunde,

bei manchen Nutzern von PLESK kann aufgrund eines Bugs ein Login in PLESK unmöglich sein.
Im Browser erscheint möglicherweise die Meldung:

[LockManagerException] Can't open or create shared memory by shm.name: "/run/lock/lmlib/SharedLockManagerStorage0.2.3"; shm.start_size: "8388608"; error "Permission denied"

oder

PLESK_INFO: Plesk\Lock\Exception
Message 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 "No such file or directory"'.
File Hierarchical.php
Line 126

Es gibt einen bekannten Workaround:
1. Loggen Sie sich per SSH auf Ihrem Server ein.

2. starten Sie
# crontab -e

3. Fügen Sie folgende Zeile hinzu
@Reboot mkdir -p /run/lock/lmlib && chown root:lock-manager /run/lock/lmlib && chmod -R 0770 /run/lock/lmlib

4. Starten Sie ihren Server neu, nach dem Reboot werden die Rechte korrekt gesetzt und Sie können sich in Plesk wieder einloggen.

Hinweis: Falls es kein /run/lock/lmlib auf Ihrem Server gibt, verwenden sie stattdessen /var/lock/lmlib

Weitere Informationen finden Sie unter der folgenden URL
Plesk is not accessible: Can't open or create shared memory by shm.name

Mit freundlichen Grüßen
Ihr STRATO Team
 
@GerdSchrewe - I do NOT have access to SSH

adding this from Strato Rescue System does NOT resolve problem

when Plesk admin interface was affected, Plesk firewalled has blocked SSH port for unknown reason
SSH is blocked for all IP addresses, I have tried to access SSH from different IPs (VPN, etc.) it doesn't work

so the question is, how to resolve this problem when you DO NOT have SSH access to your VPS due to multiple Plesk bugs?
 
If you have no SSH access:
When you are @Strato and use a V-Server:
Login to https://login.stratoserver.net
Start the rescue System
Here it is important to first change "into your own system".
so
1.) start rescue
2) ssh -> hint to /repair folder comes.
3.) change to your own system
chroot /repair
4.) plesk installer.... (or whatever. here you will find all commands you can use otherwise)

If you have no Plesk access use this link (it helped me):
Plesk is not accessible: Can't open or create shared memory by shm.name

Strato is now aware of the problem as well and you can call the Hotline for support (f you have the time to stay on hold for that long :) )
 
Dear all,

I went into the same issue. I booted my stratoserver into repair mode, cleaned out my directories and modified the /repair/etc/rc.local as discribed in the ubuntu bug tracer.

Comment #7 : Bug #45234 : Bugs : openssh package : Ubuntu

Code:
# Create the sshd folder
if [ ! -d /var/run/sshd ]; then
   mkdir /var/run/sshd
   chmod 0755 /var/run/sshd
fi

# Create the fail2ban folder
if [ ! -d /var/run/fail2ban ]; then
   mkdir /var/run/fail2ban
   chmod 0755 /var/run/fail2ban
fi


# Create the lmlib folder
if [ ! -d /run/lock/lmlib ]; then
   mkdir /run/lock/lmlib
   chown root:lock-manager /run/lock/lmlib
   chmod -R 0770 /run/lock/lmlib
fi

After a reboot everything worked like expected, but I will do an migration to 18.04 LTS
 
Back
Top