Re: No longer can connect

On Wed, Jun 29, 2005 at 09:48:33AM -0700, Nathan Zabaldo wrote:
> That is it.  I've tried running /usr/bin/sshd from a command line thinking
> maybe it wasn't started, but I get all sorts off command not found errors
> and then a command substitution that is gobbly gook and begins with:
>
> "line 2: syntax error near unexpected token..." and then a whole bunch of
> strange characters.

Sounds like you have a corrupted /usr/bin/sshd, or you have one that's
built for a different operating system, or a different version of your
operating system.

> The only thing that has changed on my box recently was I installed ffmpeg,
> which upgraded a number of dependencies on my box, but none of them should
> have anything to do with openssh.

Well, that points toward corruption instead of version mismatch....

> I have reinstalled ssh several times from webmin.  Any help would be much
> appreciated.

Try reinstalling it normally, from the command line.

In general, as a long shot, you might try fsck'ing your file systems too.
In single-user mode, you should be able to umount and fsck all of them
except the root file system.  Forcing an fsck of the root file system
is something that's operating-system-specific and I have no idea how to
do it on Mac OS X.  (On Debian, you can touch /forcefsck and then reboot.)