Benches Uncategorized

2

Getting "Socket is not connected" message on in...

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

I've recently started seeing a warning message every time I ssh into my Mac Pro (10.5.6, all updates as of yesterday):

launch_msg(): Socket is not connected

This appears on the SSH client at some point in the early stages of the connection. When I ssh in for an interactive session, it usually appears right after the "Last login" message. For non-interactive sessions (like SVN for an svn+ssh://... repository) it usually but not always appears before any of the command's output. I've looked at the logs on both the clients and the server, and I can't see anything that's obviously related to this, and Google only turns up stuff about iPhones. This happens regardless of the client: I've been able to do this from both MacOS and Linux clients.

This doesn't seem to be causing any problems, but I'd like to find out what's going on and fix it if I can. I'm not completely certain, but I think that this started when I applied the latest security update from Apple.

What's going on here? Is this something to worry about?

Suggestions and information greatly appreciated.

Thanks,

Richard

2 replies

Sign in or join Beachball Help to reply.

  1. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Wild guess. Is there an ssh-agent running under the username you are logging into?

    I know that in Leopard when you interactively login, you get an ssh-agent created and most likely a socket is used to communicate with it.

    So I'm wondering launchd (which I think starts up the sshd) is having problems creating an ssh-agent for the login session.

    Again, this is a wild guess.

  2. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I'm almost always logged in on the server's console when I'm trying to ssh in, so there most likely is an ssh-agent running on the server. That doesn't seem to be relevant, though, as I tried logging out of the server and then ssh-ing in from another machine, and I got the same warning. This is independent of whether or not I have the ssh client set to forward connections to the agent.