You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are looking for Ubuntu 24 installations and experience a problem:
On a fresh install, the openssh-server is not started yet. Therefore the "/run/sshd" directory is missing, which is required for the validation of the config:
err | Puppet | Execution of '/usr/sbin/sshd -tf /etc/ssh/sshd_config20241106-2171-1prqvcn' returned 255: Missing privilege separation directory: /run/sshd
err | /Stage[main]/Ssh::Server::Config/Concat[/etc/ssh/sshd_config]/File[/etc/ssh/sshd_config]/content | change from '{sha256}9ce65293b15513398541fad559786ef310a9045bdda398005477fda6ebf3c0f0' to '{sha256}8e740c5c770cf9c254e52e80004d078f329b8411fc4aff04ad723a5d92638c31' failed: Execution of '/usr/sbin/sshd -tf /etc/ssh/sshd_config20241106-2171-1prqvcn' returned 255: Missing privilege separation directory: /run/sshd
warning | /Stage[main]/Ssh::Server::Service/Service[ssh] | Skipping because of failed dependencies
(Output taken from Foreman, which explains why it looks a bit different as usual)
The service comes later in the dependency try of this module, thats why it never will succeed without manual interaction.
I have no good idea how to fix this, an idea could be to add a mkdir /run/sshd && at the beginning of the validate-command?
The text was updated successfully, but these errors were encountered:
We are looking for Ubuntu 24 installations and experience a problem:
On a fresh install, the openssh-server is not started yet. Therefore the "/run/sshd" directory is missing, which is required for the validation of the config:
(Output taken from Foreman, which explains why it looks a bit different as usual)
The service comes later in the dependency try of this module, thats why it never will succeed without manual interaction.
I have no good idea how to fix this, an idea could be to add a
mkdir /run/sshd &&
at the beginning of the validate-command?The text was updated successfully, but these errors were encountered: