It looks for any new client, the server is pushed to the background. Using "fg" to bring it to front, the clients will work. But I don't understand why the server behaves like this on Linux server and how we avoid it? I don't think we need any stdin for the server process, right? Your help is highly appreciated.
On Mon, Aug 29, 2016 at 8:42 AM, Paul Z Wu <[email protected]> wrote: > > ---------- Forwarded message ---------- > From: Paul Z Wu <[email protected]> > Date: Fri, Aug 26, 2016 at 1:57 PM > Subject: Why the server running on Ubuntu/Redhat cannot have a second > client to connect to it? > To: [email protected] > > > > I tried the server (after fixing the class name in sshd.sh in 1.2.0 or > 1.1.1) like this: > > > > > > > > *[zw251y@zld00735 bin]$ sshd.shStarting SSHD on port 8000Aug 26, 2016 > 3:50:56 PM org.apache.sshd.common.util.Se > <http://org.apache.sshd.common.util.Se>curityUtils$BouncyCastleRegistration > callINFO: Trying to register BouncyCastle as a JCE providerAug 26, 2016 > 3:50:57 PM org.apache.sshd.common.util.Se > <http://org.apache.sshd.common.util.Se>curityUtils$BouncyCastleRegistration > callINFO: Registration succeeded* > > Then I connected to the server from another server: > > > > > *[zw251y@zld00733 ~]$ ssh nrsapp2@zld00735 -p 8000Welcome to SSHDstdin: is > not a ttysh-4.1$* > > Then, I tried to open another client: > > > > *[zw251y@zld00733 ~]$ ssh nrsapp@zld00735 -p 8000Welcome to SSHD* > The server process now has this exception: > > [ > > > > > > > > > > > > > > > > > > *zw251y@zld00735 bin]$ sshd.shStarting SSHD on port 8000Aug 26, 2016 > 3:50:56 PM org.apache.sshd.common.util.Se > <http://org.apache.sshd.common.util.Se>curityUtils$BouncyCastleRegistration > callINFO: Trying to register BouncyCastle as a JCE providerAug 26, 2016 > 3:50:57 PM org.apache.sshd.common.util.Se > <http://org.apache.sshd.common.util.Se>curityUtils$BouncyCastleRegistration > callINFO: Registration succeededAug 26, 2016 3:53:03 PM > org.apache.sshd.server.auth.pubkey.StaticPublickeyAuthenticator > handleAcceptanceWARNING: > authenticate(nrsapp2[ServerSessionImpl[null@/135.49.205.150 > <http://135.49.205.150>:64243]][RSA][SHA256:ySE7pROsdujvRliQR2c4cuHZRHhvUjkWswp5LSg8xTs]: > accepted without checkingAug 26, 2016 3:53:03 PM > org.apache.sshd.server.session.ServerUserAuthService > handleAuthenticationSuccessINFO: Session nrsapp2@/135.49.205.150:64243 > <http://135.49.205.150:64243> authenticatedAug 26, 2016 3:54:21 PM > org.apache.sshd.server.auth.pubkey.StaticPublickeyAuthenticator > handleAcceptanceWARNING: > authenticate(nrsapp[ServerSessionImpl[null@/135.49.205.150 > <http://135.49.205.150>:64325]][RSA][SHA256:ySE7pROsdujvRliQR2c4cuHZRHhvUjkWswp5LSg8xTs]: > accepted without checkingAug 26, 2016 3:54:21 PM > org.apache.sshd.server.session.ServerUserAuthService > handleAuthenticationSuccessINFO: Session nrsapp@/135.49.205.150:64325 > <http://135.49.205.150:64325> authenticated[1]+ Stopped > sshd.sh* > However, the server process is still running (by ps -aux to see it) , but > now it does not accept anything from the client. What is wrong here? Your > help is highly appreciated. > > > > >
