[Bug 3177] sshd process had became into a defunct process and could not accept requests any more after many count sftp accesses.
bugzilla-daemon at mindrot.org
bugzilla-daemon at mindrot.org
Mon Jun 8 19:25:25 AEST 2020
https://bugzilla.mindrot.org/show_bug.cgi?id=3177
--- Comment #6 from longgang <zhlonggang at aliyun.com> ---
Darren Tucker, I have run the test on last weekend. The following is
the test result.
1. The openssh-8.3p1 complied with or without NO_SA_RESTART flags
defined, both had run into the problem as openssh-8.2p1. After a few
hours later, the java client program failed with the following
exception:
"Session.connect: java.net.SocketTimeoutException: Read timed out".
The sshd process became into defunct status.
[root at bjm7-9-10 ~]# ps -ef|grep sshd
root 1118 1 0 2019 ? 00:02:24 /usr/sbin/sshd
root 14170 16380 0 16:28 ? 00:00:00 [sshd] <defunct>
root 16380 1 0 08:57 ? 00:00:26 sshd:
/usr/local/openssh-8.3p1/sbin/sshd -p 99 -f
/etc/ssh/sshd_config_sftp.bad [listener] 0 of 10-100 startups
2. I also have run the openssh-8.1p1, the sshd process was normal and
did not become into defunct status, but the java client program failed
occasionally with the following exeption:
"java.io.IOException: inputstream is closed".
If the java client program catch the exception and ignore the error, it
will success next time.
3. My test with openssh-7.9p1 has already run 3 days so far,
everything is also ok, the problem also do not occur, and the java
client program has no errors as openssh-8.1p1.
I seems like openssh-7.9p1 is my best choice.
--
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.
More information about the openssh-bugs
mailing list