4 Replies Latest reply: Apr 22, 2007 7:21 PM by webjedi
Rui Matos Level 1 Level 1 (0 points)
Hello all,

I've been using remote login without any problems on my mac mini. Now since this last update I can't ssh into it any longer, even locally:

$ ssh utilizador@localhost
sshexchangeidentification: read: Connection reset by peer

I couldn't find the answer to this, but here are some logs:

Mar 17 00:51:20 macmini launchd: com.openssh.sshd: exited with exit code: 255
Mar 17 00:51:20 macmini launchd: com.openssh.sshd: 9 more failures without living at least 60 seconds will cause job removal

Mar 17 00:51:21 macmini sshd[532]: Connection from UNKNOWN port 65535
Mar 17 00:51:21 macmini sshd[532]: Did not receive identification string from UNKNOWN

Anyone knows what I can do about this?

Thanks,

Rui

mac mini, Mac OS X (10.4.9)
  • Rui Matos Level 1 Level 1 (0 points)
    After some more poking it seems that the problem lies in inetd since ftpd and samba also don't work and their logs speak about invalid sockets.
  • Kevin_P Level 1 Level 1 (5 points)
    OK, so I assuming that you checked for the process, but, I was messing up my ssh connection to a Solaris server.
    I have to use; ssh -l username servername for my ssh sessions to connect to Solaris.

    MacBook (black)   Mac OS X (10.4.9)  
  • adhanani Level 1 Level 1 (5 points)
    I am experiencing the same problem. On restart, the systems log shows

    Mar 19 14:39:27 GPISH-Server launchd: com.openssh.sshd: exited with exit code: 255
    Mar 19 14:39:27 GPISH-Server launchd: com.openssh.sshd: 9 more failures without living at least 60 seconds will cause job removal
    Mar 19 14:39:27 GPISH-Server launchd: com.openssh.sshd: exited with exit code: 255
    Mar 19 14:39:27 GPISH-Server launchd: com.openssh.sshd: 8 more failures without living at least 60 seconds will cause job removal
    Mar 19 14:39:27 GPISH-Server launchd: com.openssh.sshd: exited with exit code: 255
    Mar 19 14:39:27 GPISH-Server launchd: com.openssh.sshd: 7 more failures without living at least 60 seconds will cause job removal
    Mar 19 14:39:27 GPISH-Server launchd: com.openssh.sshd: exited with exit code: 255
    Mar 19 14:39:27 GPISH-Server launchd: com.openssh.sshd: 6 more failures without living at least 60 seconds will cause job removal
    Mar 19 14:39:27 GPISH-Server launchd: com.openssh.sshd: exited with exit code: 255
    Mar 19 14:39:27 GPISH-Server launchd: com.openssh.sshd: 5 more failures without living at least 60 seconds will cause job removal
    Mar 19 14:39:27 GPISH-Server launchd: com.openssh.sshd: exited with exit code: 255
    Mar 19 14:39:27 GPISH-Server launchd: com.openssh.sshd: 4 more failures without living at least 60 seconds will cause job removal
    Mar 19 14:39:27 GPISH-Server launchd: com.openssh.sshd: exited with exit code: 255
    Mar 19 14:39:27 GPISH-Server launchd: com.openssh.sshd: 3 more failures without living at least 60 seconds will cause job removal
    Mar 19 14:39:27 GPISH-Server launchd: com.openssh.sshd: exited with exit code: 255
    Mar 19 14:39:27 GPISH-Server launchd: com.openssh.sshd: 2 more failures without living at least 60 seconds will cause job removal
    Mar 19 14:39:27 GPISH-Server launchd: com.openssh.sshd: exited with exit code: 255
    Mar 19 14:39:27 GPISH-Server launchd: com.openssh.sshd: 1 more failure without living at least 60 seconds will cause job removal
    Mar 19 14:39:28 GPISH-Server launchd: com.openssh.sshd: exited with exit code: 255
    Mar 19 14:39:28 GPISH-Server launchd: com.openssh.sshd: too many failures in succession

    A similar problem occurs with samba.nmbd

    The problem may be specific to Intel-based Macs as sshd is running fine on my Powerbook G4 after the 10.4.9 upgrade.



    IMac Intel   Mac OS X (10.4.9)  
  • webjedi Level 1 Level 1 (0 points)
    If you're also looking for stuff that broke, try the ftpd issue now highlighted here:

    http://discussions.apple.com/thread.jspa?messageID=4448600#4448600