sshd start fail on hpux - SSH

This is a discussion on sshd start fail on hpux - SSH ; # /usr/sbin/sshd -d debug1: sshd version OpenSSH_3.8p1-CASPUR-K5/AFS debug1: read PEM private key done: type RSA debug1: private host key: #0 type 1 RSA debug1: read PEM private key done: type DSA debug1: private host key: #1 type 2 DSA debug1: ...

+ Reply to Thread
Results 1 to 14 of 14

Thread: sshd start fail on hpux

  1. sshd start fail on hpux

    # /usr/sbin/sshd -d
    debug1: sshd version OpenSSH_3.8p1-CASPUR-K5/AFS
    debug1: read PEM private key done: type RSA
    debug1: private host key: #0 type 1 RSA
    debug1: read PEM private key done: type DSA
    debug1: private host key: #1 type 2 DSA
    debug1: Bind to port 22 on 0.0.0.0.
    Bind to port 22 on 0.0.0.0 failed: Address already in use.
    Cannot bind any address.

    # uname -a
    HP-UX hp1 B.11.11 U 9000/785


  2. Re: sshd start fail on hpux

    On Sep 4, 8:52*am, TsanChung wrote:
    > # /usr/sbin/sshd -d
    > debug1: sshd version OpenSSH_3.8p1-CASPUR-K5/AFS
    > debug1: read PEM private key done: type RSA
    > debug1: private host key: #0 type 1 RSA
    > debug1: read PEM private key done: type DSA
    > debug1: private host key: #1 type 2 DSA
    > debug1: Bind to port 22 on 0.0.0.0.
    > Bind to port 22 on 0.0.0.0 failed: Address already in use.
    > Cannot bind any address.
    >
    > # uname -a
    > HP-UX hp1 B.11.11 U 9000/785


    However, ssh is not started:
    # ps -ax|grep ssh
    15519 pts/tb 0:00 grep ssh

  3. Re: sshd start fail on hpux

    On Sep 4, 8:56*am, TsanChung wrote:
    > On Sep 4, 8:52*am, TsanChung wrote:
    >
    > > # /usr/sbin/sshd -d
    > > debug1: sshd version OpenSSH_3.8p1-CASPUR-K5/AFS
    > > debug1: read PEM private key done: type RSA
    > > debug1: private host key: #0 type 1 RSA
    > > debug1: read PEM private key done: type DSA
    > > debug1: private host key: #1 type 2 DSA
    > > debug1: Bind to port 22 on 0.0.0.0.
    > > Bind to port 22 on 0.0.0.0 failed: Address already in use.
    > > Cannot bind any address.

    >
    > > # uname -a
    > > HP-UX hp1 B.11.11 U 9000/785

    >
    > However, ssh is not started:
    > # ps -ax|grep ssh
    > *15519 pts/tb * *0:00 grep ssh


    " Bind to port 22 on 0.0.0.0 failed: Address already in use. "

    either sshd is already running....or some other software is using that
    port.

    Since you appear to be starting it manually for debugging, I suspect
    that there is an instanance already running. what does "ps -ef | grep
    sshd" show?

    If it shows up, then its already running and you have two options.
    stop it and run the debug one manually,. or run the debug one using a
    different port

  4. Re: sshd start fail on hpux

    On Sep 4, 10:50*am, OldSchool wrote:
    > On Sep 4, 8:56*am, TsanChung wrote:
    >
    >
    >
    > > On Sep 4, 8:52*am, TsanChung wrote:

    >
    > > > # /usr/sbin/sshd -d
    > > > debug1: sshd version OpenSSH_3.8p1-CASPUR-K5/AFS
    > > > debug1: read PEM private key done: type RSA
    > > > debug1: private host key: #0 type 1 RSA
    > > > debug1: read PEM private key done: type DSA
    > > > debug1: private host key: #1 type 2 DSA
    > > > debug1: Bind to port 22 on 0.0.0.0.
    > > > Bind to port 22 on 0.0.0.0 failed: Address already in use.
    > > > Cannot bind any address.

    >
    > > > # uname -a
    > > > HP-UX hp1 B.11.11 U 9000/785

    >
    > > However, ssh is not started:
    > > # ps -ax|grep ssh
    > > *15519 pts/tb * *0:00 grep ssh

    >
    > " Bind to port 22 on 0.0.0.0 failed: Address already in use. "
    >
    > either sshd is already running....or some other software is using that
    > port.
    >
    > Since you appear to be starting it manually for debugging, I suspect
    > that there is an instanance already running. *what does "ps -ef | grep
    > sshd" show?
    >
    > If it shows up, then its already running and you have two options.
    > stop it and run the debug one manually,. or run the debug one using a
    > different port


    I reboot the computer but still has the same problem - cannot start
    sshd.
    # ps -ef | grep sshd
    root 3591 3157 0 02:19:22 pts/ta 0:00 grep sshd

  5. Re: sshd start fail on hpux

    On Sep 4, 11:04*am, TsanChung wrote:
    > On Sep 4, 10:50*am, OldSchool wrote:
    >
    >
    >
    >
    >
    > > On Sep 4, 8:56*am, TsanChung wrote:

    >
    > > > On Sep 4, 8:52*am, TsanChung wrote:

    >
    > > > > # /usr/sbin/sshd -d
    > > > > debug1: sshd version OpenSSH_3.8p1-CASPUR-K5/AFS
    > > > > debug1: read PEM private key done: type RSA
    > > > > debug1: private host key: #0 type 1 RSA
    > > > > debug1: read PEM private key done: type DSA
    > > > > debug1: private host key: #1 type 2 DSA
    > > > > debug1: Bind to port 22 on 0.0.0.0.
    > > > > Bind to port 22 on 0.0.0.0 failed: Address already in use.
    > > > > Cannot bind any address.

    >
    > > > > # uname -a
    > > > > HP-UX hp1 B.11.11 U 9000/785

    >
    > > > However, ssh is not started:
    > > > # ps -ax|grep ssh
    > > > *15519 pts/tb * *0:00 grep ssh

    >
    > > " Bind to port 22 on 0.0.0.0 failed: Address already in use. "

    >
    > > either sshd is already running....or some other software is using that
    > > port.

    >
    > > Since you appear to be starting it manually for debugging, I suspect
    > > that there is an instanance already running. *what does "ps -ef | grep
    > > sshd" show?

    >
    > > If it shows up, then its already running and you have two options.
    > > stop it and run the debug one manually,. or run the debug one using a
    > > different port

    >
    > I reboot the computer but still has the same problem - cannot start
    > sshd.
    > # ps -ef | grep sshd
    > * * root *3591 *3157 *0 02:19:22 pts/ta * *0:00 grep sshd- Hide quoted text -
    >
    > - Show quoted text -


    ok, so sshd is started on startup, as would be expected. You either
    have to stop the running sshd daemon (which wont allow anybody to
    connect via ssh until it is restarted).

    I'd recommend that you simply run a second instance of sshd using an
    available port, as in "sshd -d -p ".

    What problem are you trying to resolve that you're running the daemon
    manually?

  6. Re: sshd start fail on hpux

    On Sep 4, 12:08*pm, OldSchool wrote:
    > On Sep 4, 11:04*am, TsanChung wrote:
    >
    >
    >
    >
    >
    > > On Sep 4, 10:50*am, OldSchool wrote:

    >
    > > > On Sep 4, 8:56*am, TsanChung wrote:

    >
    > > > > On Sep 4, 8:52*am, TsanChung wrote:

    >
    > > > > > # /usr/sbin/sshd -d
    > > > > > debug1: sshd version OpenSSH_3.8p1-CASPUR-K5/AFS
    > > > > > debug1: read PEM private key done: type RSA
    > > > > > debug1: private host key: #0 type 1 RSA
    > > > > > debug1: read PEM private key done: type DSA
    > > > > > debug1: private host key: #1 type 2 DSA
    > > > > > debug1: Bind to port 22 on 0.0.0.0.
    > > > > > Bind to port 22 on 0.0.0.0 failed: Address already in use.
    > > > > > Cannot bind any address.

    >
    > > > > > # uname -a
    > > > > > HP-UX hp1 B.11.11 U 9000/785

    >
    > > > > However, ssh is not started:
    > > > > # ps -ax|grep ssh
    > > > > *15519 pts/tb * *0:00 grep ssh

    >
    > > > " Bind to port 22 on 0.0.0.0 failed: Address already in use. "

    >
    > > > either sshd is already running....or some other software is using that
    > > > port.

    >
    > > > Since you appear to be starting it manually for debugging, I suspect
    > > > that there is an instanance already running. *what does "ps -ef | grep
    > > > sshd" show?

    >
    > > > If it shows up, then its already running and you have two options.
    > > > stop it and run the debug one manually,. or run the debug one using a
    > > > different port

    >
    > > I reboot the computer but still has the same problem - cannot start
    > > sshd.
    > > # ps -ef | grep sshd
    > > * * root *3591 *3157 *0 02:19:22 pts/ta * *0:00 grep sshd- Hide quoted text -

    >
    > > - Show quoted text -

    >
    > ok, so sshd is started on startup, as would be expected. *You either
    > have to stop the running sshd daemon (which wont allow anybody to
    > connect via ssh until it is restarted).
    >
    > I'd recommend that you simply run a second instance of sshd using an
    > available port, as in "sshd -d -p ".
    >
    > What problem are you trying to resolve that you're running the daemon
    > manually?- Hide quoted text -
    >
    > - Show quoted text -


    "ok, so sshd is started on startup, as would be expected. You either
    > have to stop the running sshd daemon (which wont allow anybody to
    > connect via ssh until it is restarted)."


    That's incorrect, sorry.

    There is something currently using port 22. I've seen the SNAplus2
    use that port. "lsof" if availabe, will tell you what's running on 22
    currently.

    You can run sshd on a non-standard port with the -p option

  7. Re: sshd start fail on hpux

    On Sep 4, 12:08*pm, OldSchool wrote:
    > On Sep 4, 11:04*am, TsanChung wrote:
    >
    >
    >
    > > On Sep 4, 10:50*am, OldSchool wrote:

    >
    > > > On Sep 4, 8:56*am, TsanChung wrote:

    >
    > > > > On Sep 4, 8:52*am, TsanChung wrote:

    >
    > > > > > # /usr/sbin/sshd -d
    > > > > > debug1: sshd version OpenSSH_3.8p1-CASPUR-K5/AFS
    > > > > > debug1: read PEM private key done: type RSA
    > > > > > debug1: private host key: #0 type 1 RSA
    > > > > > debug1: read PEM private key done: type DSA
    > > > > > debug1: private host key: #1 type 2 DSA
    > > > > > debug1: Bind to port 22 on 0.0.0.0.
    > > > > > Bind to port 22 on 0.0.0.0 failed: Address already in use.
    > > > > > Cannot bind any address.

    >
    > > > > > # uname -a
    > > > > > HP-UX hp1 B.11.11 U 9000/785

    >
    > > > > However, ssh is not started:
    > > > > # ps -ax|grep ssh
    > > > > *15519 pts/tb * *0:00 grep ssh

    >
    > > > " Bind to port 22 on 0.0.0.0 failed: Address already in use. "

    >
    > > > either sshd is already running....or some other software is using that
    > > > port.

    >
    > > > Since you appear to be starting it manually for debugging, I suspect
    > > > that there is an instanance already running. *what does "ps -ef | grep
    > > > sshd" show?

    >
    > > > If it shows up, then its already running and you have two options.
    > > > stop it and run the debug one manually,. or run the debug one using a
    > > > different port

    >
    > > I reboot the computer but still has the same problem - cannot start
    > > sshd.
    > > # ps -ef | grep sshd
    > > * * root *3591 *3157 *0 02:19:22 pts/ta * *0:00 grep sshd- Hide quoted text -

    >
    > > - Show quoted text -

    >
    > ok, so sshd is started on startup, as would be expected. *You either
    > have to stop the running sshd daemon (which wont allow anybody to
    > connect via ssh until it is restarted).
    >
    > I'd recommend that you simply run a second instance of sshd using an
    > available port, as in "sshd -d -p ".
    >
    > What problem are you trying to resolve that you're running the daemon
    > manually?


    This does not work so I run the daemon manually.
    # /sbin/init.d/secsh start
    bash: /sbin/init.d/secsh: No such file or directory

  8. Re: sshd start fail on hpux

    On Sep 4, 12:11*pm, OldSchool wrote:
    > On Sep 4, 12:08*pm, OldSchool wrote:
    >
    >
    >
    > > On Sep 4, 11:04*am, TsanChung wrote:

    >
    > > > On Sep 4, 10:50*am, OldSchool wrote:

    >
    > > > > On Sep 4, 8:56*am, TsanChung wrote:

    >
    > > > > > On Sep 4, 8:52*am, TsanChung wrote:

    >
    > > > > > > # /usr/sbin/sshd -d
    > > > > > > debug1: sshd version OpenSSH_3.8p1-CASPUR-K5/AFS
    > > > > > > debug1: read PEM private key done: type RSA
    > > > > > > debug1: private host key: #0 type 1 RSA
    > > > > > > debug1: read PEM private key done: type DSA
    > > > > > > debug1: private host key: #1 type 2 DSA
    > > > > > > debug1: Bind to port 22 on 0.0.0.0.
    > > > > > > Bind to port 22 on 0.0.0.0 failed: Address already in use.
    > > > > > > Cannot bind any address.

    >
    > > > > > > # uname -a
    > > > > > > HP-UX hp1 B.11.11 U 9000/785

    >
    > > > > > However, ssh is not started:
    > > > > > # ps -ax|grep ssh
    > > > > > *15519 pts/tb * *0:00 grep ssh

    >
    > > > > " Bind to port 22 on 0.0.0.0 failed: Address already in use. "

    >
    > > > > either sshd is already running....or some other software is using that
    > > > > port.

    >
    > > > > Since you appear to be starting it manually for debugging, I suspect
    > > > > that there is an instanance already running. *what does "ps -ef |grep
    > > > > sshd" show?

    >
    > > > > If it shows up, then its already running and you have two options.
    > > > > stop it and run the debug one manually,. or run the debug one usinga
    > > > > different port

    >
    > > > I reboot the computer but still has the same problem - cannot start
    > > > sshd.
    > > > # ps -ef | grep sshd
    > > > * * root *3591 *3157 *0 02:19:22 pts/ta * *0:00 grep sshd- Hide quoted text -

    >
    > > > - Show quoted text -

    >
    > > ok, so sshd is started on startup, as would be expected. *You either
    > > have to stop the running sshd daemon (which wont allow anybody to
    > > connect via ssh until it is restarted).

    >
    > > I'd recommend that you simply run a second instance of sshd using an
    > > available port, as in "sshd -d -p ".

    >
    > > What problem are you trying to resolve that you're running the daemon
    > > manually?- Hide quoted text -

    >
    > > - Show quoted text -

    >
    > "ok, so sshd is started on startup, as would be expected. *You either
    >
    > > have to stop the running sshd daemon (which wont allow anybody to
    > > connect via ssh until it is restarted)."

    >
    > That's incorrect, sorry.
    >
    > There is something currently using port 22. *I've seen the SNAplus2
    > use that port. *"lsof" if availabe, will tell you what's running on 22
    > currently.
    >
    > You can run sshd on a non-standard port with the -p option


    I run sshd on a non-standard port with the -p option but after
    entering the password, the client cannot connect to the server.
    server# /usr/sbin/sshd -p 6010
    server# ps -ef|grep ssh
    root 3925 1 0 05:14:39 ? 0:00 /usr/sbin/sshd -p 6010
    root 3950 3157 0 05:17:17 pts/ta 0:00 grep ssh

    client$ ssh hp1.mycomp.com -v -p 6010
    OpenSSH_4.3p2, OpenSSL 0.9.8b 04 May 2006
    debug1: Reading configuration data /etc/ssh/ssh_config
    debug1: Applying options for *
    debug1: Connecting to hp1.mycomp.com [172.20.11.135] port 6010.
    debug1: Connection established.
    debug1: identity file /home/twong/.ssh/identity type -1
    debug1: identity file /home/twong/.ssh/id_rsa type 1
    debug1: identity file /home/twong/.ssh/id_dsa type -1
    debug1: Remote protocol version 2.0, remote software version
    OpenSSH_3.8p1-CASPUR-K5/AFS
    debug1: match: OpenSSH_3.8p1-CASPUR-K5/AFS pat OpenSSH_3.*
    debug1: Enabling compatibility mode for protocol 2.0
    debug1: Local version string SSH-2.0-OpenSSH_4.3
    debug1: SSH2_MSG_KEXINIT sent
    debug1: SSH2_MSG_KEXINIT received
    debug1: kex: server->client aes128-cbc hmac-md5 none
    debug1: kex: client->server aes128-cbc hmac-md5 none
    debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
    debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
    debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
    debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
    debug1: Host 'hp1.mycomp.com' is known and matches the RSA host key.
    debug1: Found key in /home/twong/.ssh/known_hosts:48
    debug1: ssh_rsa_verify: signature correct
    debug1: SSH2_MSG_NEWKEYS sent
    debug1: expecting SSH2_MSG_NEWKEYS
    debug1: SSH2_MSG_NEWKEYS received
    debug1: SSH2_MSG_SERVICE_REQUEST sent
    debug1: SSH2_MSG_SERVICE_ACCEPT received
    debug1: Authentications that can continue: publickey,gssapi-with-
    mic,password,keyboard-interactive
    debug1: Next authentication method: gssapi-with-mic
    debug1: Unspecified GSS failure. Minor code may provide more
    information
    No credentials cache found

    debug1: Unspecified GSS failure. Minor code may provide more
    information
    No credentials cache found

    debug1: Unspecified GSS failure. Minor code may provide more
    information
    No credentials cache found

    debug1: Next authentication method: publickey
    debug1: Trying private key: /home/twong/.ssh/identity
    debug1: Offering public key: /home/twong/.ssh/id_rsa
    debug1: Authentications that can continue: publickey,gssapi-with-
    mic,password,keyboard-interactive
    debug1: Trying private key: /home/twong/.ssh/id_dsa
    debug1: Next authentication method: keyboard-interactive
    debug1: Authentications that can continue: publickey,gssapi-with-
    mic,password,keyboard-interactive
    debug1: Next authentication method: password
    twong@hp1.mycomp.com's password:
    debug1: Authentication succeeded (password).
    debug1: channel 0: new [client-session]
    debug1: Entering interactive session.
    debug1: Sending environment.
    debug1: Sending env LANG = en_US.UTF-8
    Last login: Thu Sep 4 05:14:56 2008 from 172.20.11.66
    debug1: client_input_channel_req: channel 0 rtype exit-signal reply 0
    debug1: channel 0: free: client-session, nchannels 1
    Connection to hp1.mycomp.com closed.
    debug1: Transferred: stdin 0, stdout 0, stderr 45 bytes in 0.0 seconds
    debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 1560.3
    debug1: Exit status -1



  9. Re: sshd start fail on hpux

    TsanChung wrote:
    ....
    > Connection to hp1.mycomp.com closed.


    the server log should give you a clue why the connection was closed.

  10. Re: sshd start fail on hpux

    OldSchool wrote:
    > On Sep 4, 8:56 am, TsanChung wrote:
    >> On Sep 4, 8:52 am, TsanChung wrote:
    >>
    >>> # /usr/sbin/sshd -d
    >>> debug1: sshd version OpenSSH_3.8p1-CASPUR-K5/AFS
    >>> debug1: read PEM private key done: type RSA
    >>> debug1: private host key: #0 type 1 RSA
    >>> debug1: read PEM private key done: type DSA
    >>> debug1: private host key: #1 type 2 DSA
    >>> debug1: Bind to port 22 on 0.0.0.0.
    >>> Bind to port 22 on 0.0.0.0 failed: Address already in use.
    >>> Cannot bind any address.
    >>> # uname -a
    >>> HP-UX hp1 B.11.11 U 9000/785

    >> However, ssh is not started:
    >> # ps -ax|grep ssh
    >> 15519 pts/tb 0:00 grep ssh

    >
    > " Bind to port 22 on 0.0.0.0 failed: Address already in use. "
    >
    > either sshd is already running....or some other software is using that
    > port.
    >


    inetd?

  11. Re: sshd start fail on hpux

    On Sep 5, 2:29*am, Joachim Gann wrote:
    > TsanChung wrote:
    >
    > ...
    >
    > > Connection to hp1.mycomp.com closed.

    >
    > the server log should give you a clue why the connection was closed.


    /var/adm/syslog/syslog.log is like this:
    Sep 4 23:48:49 hp1 inetd[5110]: execv /usr/sbin/ssh: No such file or
    directory
    Sep 4 23:49:16 hp1 sshd[5112]: error: Could not get shadow
    information for twong
    Sep 4 23:49:16 hp1 sshd[5112]: Accepted password for twong from
    172.20.11.66 port 39313 ssh2
    Sep 5 00:11:04 hp1 sshd[5152]: error: Could not get shadow
    information for root
    Sep 5 00:11:04 hp1 sshd[5152]: Accepted password for root from
    172.20.11.66 port 43984 ssh2
    Sep 5 00:11:04 hp1 sshd[5152]: error: session_by_pid: unknown pid
    5155

    $ ls /usr/sbin/ssh*
    /usr/sbin/sshd


    Please help.
    Thanks.

  12. Re: sshd start fail on hpux

    TsanChung wrote:
    > On Sep 5, 2:29 am, Joachim Gann wrote:
    >> TsanChung wrote:
    >>
    >> ...
    >>
    >>> Connection to hp1.mycomp.com closed.

    >> the server log should give you a clue why the connection was closed.

    >
    > /var/adm/syslog/syslog.log is like this:
    > Sep 4 23:48:49 hp1 inetd[5110]: execv /usr/sbin/ssh: No such file or
    > directory
    > Sep 4 23:49:16 hp1 sshd[5112]: error: Could not get shadow
    > information for twong
    > Sep 4 23:49:16 hp1 sshd[5112]: Accepted password for twong from
    > 172.20.11.66 port 39313 ssh2
    > Sep 5 00:11:04 hp1 sshd[5152]: error: Could not get shadow
    > information for root
    > Sep 5 00:11:04 hp1 sshd[5152]: Accepted password for root from
    > 172.20.11.66 port 43984 ssh2
    > Sep 5 00:11:04 hp1 sshd[5152]: error: session_by_pid: unknown pid
    > 5155
    >
    > $ ls /usr/sbin/ssh*
    > /usr/sbin/sshd
    >
    >
    > Please help.
    > Thanks.



    well, as Frank Giessler suspected elsewhere in the thread, you seem to
    have inetd configured to listen on port 22 and try to run an ssh client
    (??). that ist the cause of your original problem of port 22 being used.
    rethink this or remove ssh from inetd.conf.

    the other errors (obviously from your successfully started sshd on a
    different port) seem to deal with the shadow file. maybe someone who is
    more aquainted with hpux can look at these.

    all in all I suggest sshd setup on this machine be looked over by
    someone familiar with sshd_config and startup scripts.


  13. Re: sshd start fail on hpux

    On Sep 4, 1:55*pm, TsanChung wrote:
    > On Sep 4, 12:08*pm, OldSchool wrote:
    >
    >
    >
    >
    >
    > > On Sep 4, 11:04*am, TsanChung wrote:

    >
    > > > On Sep 4, 10:50*am, OldSchool wrote:

    >
    > > > > On Sep 4, 8:56*am, TsanChung wrote:

    >
    > > > > > On Sep 4, 8:52*am, TsanChung wrote:

    >
    > > > > > > # /usr/sbin/sshd -d
    > > > > > > debug1: sshd version OpenSSH_3.8p1-CASPUR-K5/AFS
    > > > > > > debug1: read PEM private key done: type RSA
    > > > > > > debug1: private host key: #0 type 1 RSA
    > > > > > > debug1: read PEM private key done: type DSA
    > > > > > > debug1: private host key: #1 type 2 DSA
    > > > > > > debug1: Bind to port 22 on 0.0.0.0.
    > > > > > > Bind to port 22 on 0.0.0.0 failed: Address already in use.
    > > > > > > Cannot bind any address.

    >
    > > > > > > # uname -a
    > > > > > > HP-UX hp1 B.11.11 U 9000/785

    >
    > > > > > However, ssh is not started:
    > > > > > # ps -ax|grep ssh
    > > > > > *15519 pts/tb * *0:00 grep ssh

    >
    > > > > " Bind to port 22 on 0.0.0.0 failed: Address already in use. "

    >
    > > > > either sshd is already running....or some other software is using that
    > > > > port.

    >
    > > > > Since you appear to be starting it manually for debugging, I suspect
    > > > > that there is an instanance already running. *what does "ps -ef |grep
    > > > > sshd" show?

    >
    > > > > If it shows up, then its already running and you have two options.
    > > > > stop it and run the debug one manually,. or run the debug one usinga
    > > > > different port

    >
    > > > I reboot the computer but still has the same problem - cannot start
    > > > sshd.
    > > > # ps -ef | grep sshd
    > > > * * root *3591 *3157 *0 02:19:22 pts/ta * *0:00 grep sshd- Hide quoted text -

    >
    > > > - Show quoted text -

    >
    > > ok, so sshd is started on startup, as would be expected. *You either
    > > have to stop the running sshd daemon (which wont allow anybody to
    > > connect via ssh until it is restarted).

    >
    > > I'd recommend that you simply run a second instance of sshd using an
    > > available port, as in "sshd -d -p ".

    >
    > > What problem are you trying to resolve that you're running the daemon
    > > manually?

    >
    > This does not work so I run *the daemon manually.
    > # /sbin/init.d/secsh start
    > bash: /sbin/init.d/secsh: No such file or directory- Hide quoted text -
    >
    > - Show quoted text -


    ok, you've got a bunch of different things going on:

    1) the reason is won't start manually is that port 22 is already in
    use by something, as noted elsewhere repeatedly.

    2) if you start sshd with a non-standard port assignment as noted
    previously, the clients will need to use a non-standard port to
    connect to it. I believe this was noted previously as well.

    3) Is this in anyway related to the X problem you are trying to solve
    in another tread?

    4) "# /sbin/init.d/secsh start
    > bash: /sbin/init.d/secsh: No such file or directory"

    Is that the "problem" you are trying to fix (unclear as you are
    rambling all over with questions / issues). If so, the error message
    is clear, the file you are trying to run does not exist. some
    versions of sshd will install /sbin/init.d/sshd. You will have to
    check.

  14. Re: sshd start fail on hpux

    On Sep 5, 2:10*pm, OldSchool wrote:
    > On Sep 4, 1:55*pm, TsanChung wrote:
    >
    >
    >
    > > On Sep 4, 12:08*pm, OldSchool wrote:

    >
    > > > On Sep 4, 11:04*am, TsanChung wrote:

    >
    > > > > On Sep 4, 10:50*am, OldSchool wrote:

    >
    > > > > > On Sep 4, 8:56*am, TsanChung wrote:

    >
    > > > > > > On Sep 4, 8:52*am, TsanChung wrote:

    >
    > > > > > > > # /usr/sbin/sshd -d
    > > > > > > > debug1: sshd version OpenSSH_3.8p1-CASPUR-K5/AFS
    > > > > > > > debug1: read PEM private key done: type RSA
    > > > > > > > debug1: private host key: #0 type 1 RSA
    > > > > > > > debug1: read PEM private key done: type DSA
    > > > > > > > debug1: private host key: #1 type 2 DSA
    > > > > > > > debug1: Bind to port 22 on 0.0.0.0.
    > > > > > > > Bind to port 22 on 0.0.0.0 failed: Address already in use.
    > > > > > > > Cannot bind any address.

    >
    > > > > > > > # uname -a
    > > > > > > > HP-UX hp1 B.11.11 U 9000/785

    >
    > > > > > > However, ssh is not started:
    > > > > > > # ps -ax|grep ssh
    > > > > > > *15519 pts/tb * *0:00 grep ssh

    >
    > > > > > " Bind to port 22 on 0.0.0.0 failed: Address already in use. "

    >
    > > > > > either sshd is already running....or some other software is usingthat
    > > > > > port.

    >
    > > > > > Since you appear to be starting it manually for debugging, I suspect
    > > > > > that there is an instanance already running. *what does "ps -ef| grep
    > > > > > sshd" show?

    >
    > > > > > If it shows up, then its already running and you have two options..
    > > > > > stop it and run the debug one manually,. or run the debug one using a
    > > > > > different port

    >
    > > > > I reboot the computer but still has the same problem - cannot start
    > > > > sshd.
    > > > > # ps -ef | grep sshd
    > > > > * * root *3591 *3157 *0 02:19:22 pts/ta * *0:00 grep sshd- Hide quoted text -

    >
    > > > > - Show quoted text -

    >
    > > > ok, so sshd is started on startup, as would be expected. *You either
    > > > have to stop the running sshd daemon (which wont allow anybody to
    > > > connect via ssh until it is restarted).

    >
    > > > I'd recommend that you simply run a second instance of sshd using an
    > > > available port, as in "sshd -d -p ".

    >
    > > > What problem are you trying to resolve that you're running the daemon
    > > > manually?

    >
    > > This does not work so I run *the daemon manually.
    > > # /sbin/init.d/secsh start
    > > bash: /sbin/init.d/secsh: No such file or directory- Hide quoted text -

    >
    > > - Show quoted text -

    >
    > ok, you've got a bunch of different things going on:
    >
    > 1) the reason is won't start manually is that port 22 is already in
    > use by something, as noted elsewhere repeatedly.
    >
    > 2) if you start sshd with a non-standard port assignment as noted
    > previously, the clients will need to use a non-standard port to
    > connect to it. *I believe this was noted previously as well.
    >
    > 3) Is this in anyway related to the X problem you are trying to solve
    > in another tread?
    >
    > 4) "# /sbin/init.d/secsh start> bash: /sbin/init.d/secsh: No such file ordirectory"
    >
    > Is that the "problem" you are trying to fix (unclear as you are
    > rambling all over with questions / issues). *If so, the error message
    > is clear, the file you are trying to run does not exist. *some
    > versions of sshd will install /sbin/init.d/sshd. *You will have to
    > check.


    I installed a new sshd with T1471AA.depot on hpux and modify /etc/
    inetd.conf.
    Now problem is solved.
    Thanks.

+ Reply to Thread