Forums before death by AOL, social media and spammers... "We can't have nice things"
|    linux.debian.bugs.dist    |    Ohh some weird Debian bug report thing    |    28,835 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 28,064 of 28,835    |
|    Claudio Kuenzler to All    |
|    Bug#1128329: openssh-server: Service rel    |
|    18 Feb 26 12:30:01    |
      From: ck@claudiokuenzler.com              Package: openssh-server       Version: 1:10.0p1-7       Severity: important              Dear Maintainer,              This problem is experienced on Debian 13 (Trixie).              When trying to reload the Systemd controlled "ssh" service (using       systemctl reload ssh), the reload runs into an error:              root@debian13:~# systemctl reload ssh       Job for ssh.service failed because the control process exited with error code.       See "systemctl status ssh.service" and "journalctl -xeu ssh.service" for       details.              The logs show:              Feb 18 10:47:45 debian13 systemd[1]: Reloading ssh.service - OpenBSD Secure       Shell server...       Feb 18 10:47:45 debian13 sshd[163]: Received SIGHUP; restarting.       Feb 18 10:47:45 debian13 sshd[163]: fatal: Cannot bind any address.       Feb 18 10:47:45 debian13 systemd[1]: ssh.service: Main process exited,       code=exited, status=255/EXCEPTION       Feb 18 10:47:45 debian13 systemd[1]: ssh.service: Failed with result       'exit-code'.       Feb 18 10:47:45 debian13 systemd[1]: Reload failed for ssh.service - OpenBSD       Secure Shell server.              The Systemd service unit (/usr/lib/systemd/system/ssh.service) shows the       following ExecReload parameters:              ExecReload=/usr/sbin/sshd -t       ExecReload=/bin/kill -HUP $MAINPID              Running this command manually, results int he same problem:              root@debian13:~# kill -HUP $(pgrep -x sshd)              Feb 18 11:27:44 debian13 sshd[195958]: Received SIGHUP; restarting.       Feb 18 11:27:44 debian13 sshd[195958]: fatal: Cannot bind any address.       Feb 18 11:27:44 debian13 systemd[1]: ssh.service: Main process exited,       code=exited, status=255/EXCEPTION       Feb 18 11:27:44 debian13 systemd[1]: ssh.service: Failed with result       'exit-code'.              I stumbled into this when an Ansible task, which attempts to reload       the "ssh" service after config changes, ran into an error.              The service reload works on Debian 12 (bookworm).                            -- System Information:       Debian Release: 13.3        APT prefers stable-updates        APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,       'stable')       Architecture: amd64 (x86_64)              Kernel: Linux 6.1.0-40-amd64 (SMP w/2 CPU threads; PREEMPT)       Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not       set       Shell: /bin/sh linked to /usr/bin/dash       Init: systemd (via /run/systemd/system)              Versions of packages openssh-server depends on:       ii debconf [debconf-2.0] 1.5.91       ii init-system-helpers 1.69~deb13u1       ii libaudit1 1:4.0.2-2+b2       ii libc6 2.41-12+deb13u1       ii libcom-err2 1.47.2-3+b7       ii libcrypt1 1:4.4.38-1       ii libgssapi-krb5-2 1.21.3-5       ii libkrb5-3 1.21.3-5       ii libpam-modules 1.7.0-5       ii libpam-runtime 1.7.0-5       ii libpam0g 1.7.0-5       ii libselinux1 3.8.1-1       ii libssl3t64 3.5.4-1~deb13u2       ii libwrap0 7.6.q-36       ii libwtmpdb0 0.73.0-3+deb13u1       ii openssh-client 1:10.0p1-7       ii openssh-sftp-server 1:10.0p1-7       ii procps 2:4.0.4-9       ii runit-helper 2.16.4       ii systemd [systemd-sysusers] 257.9-1~deb13u1       ii sysvinit-utils [lsb-base] 3.14-4       ii ucf 3.0052       ii zlib1g 1:1.3.dfsg+really1.3.1-1+b1              Versions of packages openssh-server recommends:       ii libpam-systemd [logind] 257.9-1~deb13u1       pn ncurses-term |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca