[SOLVED] SSH server does not start of recent upgrade

Support
1

Great job, but after the update:

  1. ssh: connect to host 192.168.0.185 port 22: Connection refused
  2. http://freedombox/plinth/sys/ssh/ reports:

    Service Secure Shell (SSH) Server is not running.

Now I am next to my Raspberry 2 model B, but this can be a problem when I am away, because still wasn’t able to access the FreedomBox trough WAN (still debugging).

What can be done to prevent such failures in future?

Trying to start from _cockpit

5:07 PM
Failed to start OpenBSD Secure Shell server.
systemd
5:07 PM
ssh.service: Failed with result 'exit-code'.
systemd
5:07 PM
ssh.service: Start request repeated too quickly.
systemd
5:07 PM
Stopped OpenBSD Secure Shell server.
systemd
5:07 PM
ssh.service: Scheduled restart job, restart counter is at 5.
systemd

Failed to start OpenBSD Secure Shell server.

CODE_FILE src/core/job.c
CODE_FUNC job_log_done_status_message
CODE_LINE 940
INVOCATION_ID 0399188d17fb430abe119404459e2f8e
JOB_ID 43358
JOB_RESULT failed
JOB_TYPE start
MESSAGE_ID be02cf6855d2428ba40df7e9d022f03d
PRIORITY 3
SYSLOG_FACILITY 3
SYSLOG_IDENTIFIER systemd
TID 1
UNIT ssh.service
_BOOT_ID 1b27a15e39a64955bdd4eb88e52f48ac
_CAP_EFFECTIVE 1ffffffffff
_CMDLINE /sbin/init
_COMM systemd
_EXE /usr/lib/systemd/systemd
_GID 0
_HOSTNAME k___e
_MACHINE_ID 97__________________82
_PID 1
_SELINUX_CONTEXT unconfined
_SOURCE_REALTIME_TIMESTAMP 1662563363548420
_SYSTEMD_CGROUP /init.scope
_SYSTEMD_SLICE -.slice
_SYSTEMD_UNIT init.scope
_TRANSPORT journal
_UID 0
__CURSOR s=ff24a86d14c84f109a3dfae82c2d1ff1;i=1765;b=1b27a15e39a64955bdd4eb88e52f48ac;m=9caa9a4d1;t=5e817b2b36d67;x=659d6af97b4b58d3
__MONOTONIC_TIMESTAMP 42054821073
__REALTIME_TIMESTAMP 1662563363548519
2

@eapo, we have done any changes related to SSH in the recent release.

  • Does journalctl -f show any other messages?
  • Is there at least some free disk space on the machine?
  • Have you disabled SSH password based authentication in FreedomBox interface?
  • Please post /etc/ssh/sshd_config and /etc/ssh/sshd_config.d/*.
  • What is the status of dpkg -l openssh-server? Does running apt -f install or dpkg --configure -a do any fixing?
1 Like
3
  • Does journalctl -f show any other messages?

no journalctl -f messages after upgrade; not even when I press the Start service action-button on http://freedombox/_cockpit/system/services#/ssh.service

  • Is there at least some free disk space on the machine?
~$│df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            417M     0  417M   0% /dev
tmpfs            93M   12M   81M  13% /run
/dev/mmcblk0p3   30G   11G   19G  38% /
tmpfs           461M   28K  461M   1% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs            93M     0   93M   0% /run/user/10000
  • Have you disabled SSH password based authentication in FreedomBox interface?

No. Disable password authentication checkbox still empty on http://freedombox/plinth/sys/ssh/

Please post /etc/ssh/sshd_config and /etc/ssh/sshd_config.d/*.

Aaaand Yess! Thank you, i am responsible for this: I was trying to enable utf8 support for console following this stack and added SendEnv LANG LC_* to the end of /etc/ssh/ssh_config.Now removed, and instantly see

Failed password for root from 61.177.173.28 port 11756 ssh2

repeated in Service logs :smiley:

Thank you for the support.
Wish you a all the best to keep up with this amazing project.
I am trying to follow up to be able to support it somehow.

1 Like