bugzilla-daemon at mindrot.org
2023-Sep-26  07:41 UTC
[Bug 3616] New: SSHD Server Not Working After 9.4p1 Upgrade
https://bugzilla.mindrot.org/show_bug.cgi?id=3616
            Bug ID: 3616
           Summary: SSHD Server Not Working After 9.4p1 Upgrade
           Product: Portable OpenSSH
           Version: 9.4p1
          Hardware: amd64
                OS: Linux
            Status: NEW
          Severity: critical
          Priority: P5
         Component: sshd
          Assignee: unassigned-bugs at mindrot.org
          Reporter: tidakeajay2771 at gmail.com
I have followed the following steps to upgrade the OpenSSH
sudo yum install -y gcc openssl-devel zlib-devel mlocate autoconf
wget
https://cdn.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-9.4p1.tar.gz
tar zxvf openssh-9.4p1.tar.gz
cd openssh-9.4p1
./configure --prefix=/usr
make
sudo make install
But the server is not working after upgrade. Here are the logs
Sep 26 07:33:02 ip-10-12-38-163.stg.ymc.local sshd[43387]: Server
listening on 0.0.0.0 port 22.
Sep 26 07:33:02 ip-10-12-38-163.stg.ymc.local sshd[43387]: Server
listening on :: port 22.
Sep 26 07:34:32 ip-10-12-38-163.stg.ymc.local systemd[1]: sshd.service:
start operation timed out. Terminating.
Sep 26 07:34:32 ip-10-12-38-163.stg.ymc.local sshd[43387]: Received
signal 15; terminating.
Sep 26 07:34:32 ip-10-12-38-163.stg.ymc.local systemd[1]: sshd.service:
Failed with result 'timeout'.
?? Subject: Unit failed
?? Defined-By: systemd
?? Support:
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
??
?? The unit sshd.service has entered the 'failed' state with result
'timeout'.
Sep 26 07:34:32 ip-10-12-38-163.stg.ymc.local systemd[1]: Failed to
start sshd.service - OpenSSH server daemon.
?? Subject: A start job for unit sshd.service has failed
?? Defined-By: systemd
?? Support:
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
??
?? A start job for unit sshd.service has finished with a failure.
??
?? The job identifier is 21321 and the job result is failed.
-- 
You are receiving this mail because:
You are watching the assignee of the bug.
bugzilla-daemon at mindrot.org
2023-Sep-26  08:40 UTC
[Bug 3616] SSHD Server Not Working After 9.4p1 Upgrade
https://bugzilla.mindrot.org/show_bug.cgi?id=3616
Darren Tucker <dtucker at dtucker.net> changed:
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dtucker at dtucker.net
--- Comment #1 from Darren Tucker <dtucker at dtucker.net> ---
(In reply to Ajay from comment #0)> I have followed the following steps to upgrade the OpenSSH
> sudo yum install [...]
Which distro is this?  Looks Redhat flavoured.
[...]> Sep 26 07:33:02 ip-10-12-38-163.stg.ymc.local sshd[43387]: Server
> listening on :: port 22.
> Sep 26 07:34:32 ip-10-12-38-163.stg.ymc.local systemd[1]:
> sshd.service: start operation timed out. Terminating.
This looks like your vendor modified sshd to report startup status back
to systemd and you replaced it with a stock one that doesn't, and after
a 90 second timeout systemd thinks sshd failed to start.
There's some discussion in bug#2641 about how to make sshd and systemd
play nicely together although the discussion fizzled out without
resolution.
-- 
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
bugzilla-daemon at mindrot.org
2024-Dec-04  10:31 UTC
[Bug 3616] SSHD Server Not Working After 9.4p1 Upgrade
https://bugzilla.mindrot.org/show_bug.cgi?id=3616
Darren Tucker <dtucker at dtucker.net> changed:
           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |DUPLICATE
             Status|NEW                         |RESOLVED
--- Comment #2 from Darren Tucker <dtucker at dtucker.net> ---
The systemd code was added in bug#2641 and was in 9.8p1 and newer.  We
believe that this should resolve the problem reported here.
*** This bug has been marked as a duplicate of bug 2641 ***
-- 
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.