Plesk is not accessible: Can't open or create shared memory by




  • Avatar
    Julian Fürderer


    this problem occured today, but i cant try this an the following solutions


    Unable to open Plesk: Lock Manager error: Can't open or create shared memory by


    Plesk is unavailable after upgrade: Can't open or create shared memory by

    because i can currently only connect to Server via SSH when in rescue mode. (Dont know why ... idea how to enable/check SSH, so i can connect in normal mode ??)

    How can i fix the problem when the rescue mode is running?

  • Avatar

    Hey is there a solution when i don't have ssh access anymore?? Only the in system rescue... Thanks!

  • Avatar
    Alexandr Redikultsev

    Hi, @Sean Unett and @Julian Fürderer.

    In rescue mode, create a cron task under root user to change the ownership and permissions, like this for example:

    */1 * * * * mkdir -p /run/lock/pmlib && chown root:lock-manager /run/lock/lmlib && chmod -R 0770 /run/lock/lmlib

    Then reboot the server and wait for some time, cron task should do the trick.

  • Avatar
    Pera Burek (Edited )

    VPS Server hosted by - Strato Support Team refuses to support Plesk

    Plesk Support Team refuses to support Plesk-key-by-Strato, playing ping-pong with user


    server is not accessible for days, because not only Plesk admin interface is broken, but SSH is blocked by Plesk for unknown reason


    here is output from Strato Rescue system:


    Welcome to Ubuntu 16.04.2 LTS (GNU/Linux 4.4.0-042stab134.3 x86_64)

    * Documentation:
    * Management:
    * Support:
    =============== VPS REPAIR MODE ===============
    Your VPS is under repair mode now.
    You can access the file system of your VPS under /repair directory.
    To finish repair mode login into the Customer Service Area
    ( and select
    'Server Configuration' -> 'RecoveryManager'.
    =============== VPS REPAIR MODE ===============
    Last login: Mon Nov 26 11:30:59 2018 from -- cut --

    when I run Plesk "solution" it causes chown error

    root@h2669559:~# mkdir -p /run/lock/pmlib && chown root:lock-manager /run/lock/lmlib && chmod -R 0770 /run/lock/lmlib
    chown: invalid group: 'root:lock-manager'

    if I try with "/repair" in front, it causes chown error

    root@h2669559:~# mkdir -p /repair/run/lock/pmlib && chown root:lock-manager /repair/run/lock/lmlib && chmod -R 0770 /repair/run/lock/lmlib
    chown: invalid group: 'root:lock-manager'


    here is stat output

    root@h2669559:~# stat /repair/run/lock/lmlib
    File: '/repair/run/lock/lmlib'
    Size: 4096 Blocks: 8 IO Block: 4096 directory
    Device: 9157h/37207d Inode: 499647313 Links: 2
    Access: (0770/drwxrwx---) Uid: ( 0/ root) Gid: ( 100/ users)
    Access: 2018-11-23 13:18:54.222952461 +0100
    Modify: 2018-11-23 13:18:54.222952461 +0100
    Change: 2018-11-23 13:38:57.523406743 +0100
    Birth: -


    Solution suggested by @Alexandr Redikultsev doesn't work

    Do you have solution for this problem?

  • Avatar

    Hi @Alexandr Redikultsev,

    Thanks for the reaction...

    I tried your solution! I edditing the /repair/etc/contab file and added the line you provided. But when i restart my server it still gets the same error.

    I also tried instead of run. var in the line! But it doesnt do it...

  • Avatar
    Claus Siebeneicher

    Seems as if plesk also uses other files in the /run/lock/ directory if plesk's "Enhanced security mode" is enabled, which could cause issues with (plesk) firewall changes, ssh(d) etc.,  right? 

  • Avatar
    Ivan Postnikov

    Hello @Pera

    Thank you for the feedback.

    As I can see the issue now is resolved with the assistance of Plesk support:

    1. To make Plesk accessible engineer has added corn task manually via rescue mode.
    The path: repair/var/spool/cron/crontabs/root
    The task: 

    @reboot mkdir -p /run/lock/lmlib && chown root:lock-manager /run/lock/lmlib && chmod -R 0770 /run/lock/lmlib

    2. After reboot Plesk became accessible and to make SSH work you have created the following scheduled task at Plesk Scheduled Task manager:
    mkdir /var/run/sshd && chmod 0755 /var/run/sshd && /etc/init.d/ssh start

    After that, the issue was resolved.

    This article will be updated to give more details.

  • Avatar
    Nico Weis (Edited )

    Got the same problem, PLESK noch reachable, no access by ssh


    Check that /repair/run/lock/lmlib and /repair/var/lock/lmlib exists 

    -> Both directorys are not existing
    Just /repair/run/lock/pmlib and /repair/var/lock/pmlib

    Any Ideas? No solution fixed my problem :( 


    root@h2756151:~# stat /repair/run/lock/pmlib

      File: '/repair/run/lock/pmlib'

      Size: 4096      Blocks: 8          IO Block: 4096   directory

    Device: ddf0b6e1h/3723540193d Inode: 23593373    Links: 2

    Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)

    Access: 2018-11-27 19:36:37.696311335 +0100

    Modify: 2018-11-27 19:19:30.726094850 +0100

    Change: 2018-11-27 19:19:30.726094850 +0100

    Birth: -

  • Avatar
    Alexandr Redikultsev

    Hi @Nico Weis and @Sean Unett,

    Thank you for your feedback!

    My colleague Ivan Postnikov suggested a little bit different solution for the problem. We also sent a notice to Strato regarding this issue.

    I have also added this information to the article under "In case SSH connection to the server is not possible" section.

    Please, check it and let me know whether or not it helps.

  • Avatar
    Alexandr Redikultsev

    Hi @ Claus Siebeneicher,

    'Enhanced security mode' is related to the internal Plesk logic of storing the passwords, sending notifications and other stuff, however it does not affect other services like SSH.

    Let me know if you still face issues with the new solution suggested in the article.

Please sign in to leave a comment.

Have more questions? Submit a request