Find the answer to your Linux question:
Page 3 of 3 FirstFirst 1 2 3
Results 21 to 22 of 22
Thanks, some of the best support I've had in a while. Perhaps you could explain why (or if its normal) that when rebooting the Pup box and letting sshd start ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #21
    Just Joined!
    Join Date
    Sep 2009
    Posts
    16

    Thanks, some of the best support I've had in a while. Perhaps you could explain why (or if its normal) that when rebooting the Pup box and letting sshd start automatically I can log in remotely, but when I shut it down and run the binary manually /etc/sbin/sshd -d its not letting me connect? Still shows that symbols error previously mentioned.

  2. #22
    Trusted Penguin
    Join Date
    May 2011
    Posts
    4,353
    Quote Originally Posted by rfxcasey View Post
    Perhaps you could explain why (or if its normal) that when rebooting the Pup box and letting sshd start automatically I can log in remotely, but when I shut it down and run the binary manually /etc/sbin/sshd -d its not letting me connect? Still shows that symbols error previously mentioned.
    as to that, i'm not sure. but here's what i'd do to trouble-shoot, if you care to.

    first, see how it is being called, using "ps". it could be you have two different version of sshd on your system and one works and one doesn't. so after a reboot, and your good sshd is running, do:
    Code:
    ps auxww|grep sshd
    see which sshd is being called and see if there are any arguments. if they are indeed different sshd daemons, then perhaps the one you are calling manually is linked to a version of the openssl library that is not on your system. for any sshd you find, try the ldd command on it and see what libs it reports, e.g:

    Code:
    ldd /usr/sbin/sshd

Page 3 of 3 FirstFirst 1 2 3

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •