SSH failing to launch

On May 16, 2008, at 7:40 AM, pbirdspeakeasy.net wrote:

> Link (dyld) error:
> Library not loaded: /usr/lib/libwrap.7.dylib Referenced from: /usr/
> sbin/sshd Reason: image not found
>
>
> There is indeed no "/usr/lib/librwap.7.dylib" file present.

Well, you've got a typo there -- I don't have "librwap.7.dylib"
either :-)

I do have a "libwrap" though (10.5.x):

   $ ls -la /usr/lib/libwrap.7.dylib
   -r--r--r-- 1 root wheel 149872 2007-09-23 20:45 /usr/lib/libwrap.
7.dylib
   $

I don't have a 10.4.x machine at hand to cross-check against, but my
hunch is that this file is missing, and if one file like this is
mysteriously missing, there could be others, too.

If you have the install discs handy, an archive & install might not be
a bad idea.

Otherwise, if you have access to another 10.4.x system, you should be
able to copy the file over via, say, a USB flash drive.

Let me know if you need a hand, I might be able to email a copy of the
file off list.


--
Chris Devers

On May 16, 2008, at 4:40 AM, pbirdspeakeasy.net wrote:

> 'm having a problem with the SSH server on my Tiger (10.4.11) G4 Mac
> that I hope someone can help me with. I'm getting errors when trying
> to connect saying "remote closed the connection" so I thought somehow
> it got turned off in System Preferences. A quick check in the Sharing
> pane shows that "Remote Login" is turned on as it should be. I even
> stopped and started it just to be sure. But I still don't see "sshd"
> in my process listing.
>
> On a hunch, I glanced through the system logs in the console. Sure
> enough, there's an entry for sshd crasing. The report from the
> CrashReporter says:

On my remaining Tiger machine (a G4 from 2001, which seems to run
Leopard in a quick test but isn't supported), before an attempt to ssh
into the machine, there was no sshd running.

After an unsuccessful attempt (doomed to failure, I forgot to specify
the right username in the ssh command) and a successful ssh connection
to the machine, there was an sshd running.

That led me to think "xinetd", which led me to see /etc/d-
migrated2launchd (an empty directory) (after noting that xinetd seems
not to have any configuration for sshd).

It seems likely that launchd is what now (in Tiger) watches the ssh
port and fires off sshd processes as needed.

If
    netstat -ln | grep '\.22 '
(note the space before the closing quote)
does not produce a listing for your machine's IP address on port 22,
then ssh won't work to the machine (assuming you're using the standard
ssh port).

If you do have such a line, something else is likely wrong.

   --John