• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Missing privilege separation directory: /var/run/sshd

Jasper

New Pleskian
I've got a VPS running Ubuntu 16.04 LTS with Plesk (Web Pro Edition) 17.8.11 Update #31, as provided by my host. After rebooting the system yesterday from within the web panel, I was unable to connect to the VPS using SSH. Connecting to the web panel resulted in an error 500, which was resolved by restarting the VPS once again. I then looked at the firewall settings, figuring they must have changed for some reason, but found that the SSH port was set to open.

Investigating the issue further, I managed to find the error listed in the title; "Missing privilege separation directory: /var/run/sshd". When looking in the /etc/init/ssh.conf file, it is set to create the directory and give the appropriate permissions. When looking in the /etc/init.d/ssh file, the check_privsep_dir() method clearly checks if the directory exists, and creates it if it doesn't.

I managed to "solve" the issue by adding the following cronjob:
@Reboot mkdir -p -m0755 /var/run/sshd && systemctl restart sshd.service

I don't find the solution particularly elegant, but it does the job for now... Could anyone tell me how this issue might happen, and how I could fix this without having additional cronjobs running?
 
Back
Top