• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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