Sann-X!

  • Content Count

    6
  • Joined

  • Last visited

  1. Workaround for ssh issue (create one shot service/daemon to make proper sshd dir): 0. Log in under root 1. Create file: touch /etc/systemd/system/create-ssh-dir.service 2. Grant access: chmod 664 /etc/systemd/system/create-ssh-dir.service 3. Edit content file: [Unit] Description=Creates sshd directory Before=ssh.service [Service] Type = oneshot ExecStart=mkdir -p /var/run/sshd [Install] WantedBy=multi-user.target 4. Enable service: systemctl enable create-ssh-dir.service 5. Reboot
  2. It's a new common linux issue: Nov 12 Redhat https://access.redhat.com/solutions/1519263 Nov 21 Ubuntu https://askubuntu.com/questions/1094776/systemd-tmpfiles-wont-start
  3. I found issue trigger. After this upgrade: Packages that will be upgraded: libnss-myhostname libpam-systemd libpython2.7-minimal libpython2.7-stdlib libpython3.5 libpython3.5-minimal libpython3.5-stdlib libsystemd0 libudev1 linux-libc-dev python2.7 python2.7-minimal python3.5 python3.5-minimal systemd systemd-sysv udev the 'systemd-tmpfiles-setup' service start failed at system boot.
  4. 1. h2tesw test finished without errors. 2. I wrote Armbian 5.35 image. Change root pswd, reboot. SSH is ok. 3. Then unattended upgrades are run. After upgrading the OS has 5.60 ver. Reboot. And now SSH service start failed at system boot. I can't log in via putty. Why so?
  5. Hi, I have two orange pi zero devices. But I can't log in via putty to both devices. There is connection refused error. Syslog contains this line: Nov 21 09:15:43 localhost sshd[996]: Missing privilege separation directory: /var/run/sshd But if I create this dir manually, ssh starts fine.. until next boot. I suppose it happens because 'systemd-tmpfiles-setup' service start failed at system boot: [FAILED] Failed to start Create Volatile Files and Directories. See 'systemctl status systemd-tmpfiles-setup.service' for details. Also before this