ssh-agent is broken after running Meerkat - can connect to git in terminal but not in Tower - no keychain access
Posted
by
marblegravy
on Super User
See other posts from Super User
or by marblegravy
Published on 2011-11-29T00:42:21Z
Indexed on
2011/11/29
1:54 UTC
Read the original article
Hit count: 316
My mac running Snow leopard 10.6.8 is having trouble handling it's ssh keys.
I could previously access all my git repo's via Tower without an issue. The other day I ran Meerkat to see what it was about and it looks like it has broken the way ssh works.
Terminal doesn't seem to have a problem and can still connect to Git, but it can't access the keychain. Tower doesn't seem to be able to access anything.
The Tower support crew have been super helpful, but I wanted to float this here and see if anyone has any ideas on how to fix my problem.
The only hints I have are:
$ which ssh
returns:
/usr/bin/ssh
and
echo $SSH_AUTH_SOCK
returns:
/tmp/ssh-nBhRYVEg8t/agent.199
(This one seems to be wrong as I think it's supposed to point to a Listener, but no idea how to fix it)
additional: Keychain first-aid finds no problems. The problem seems to be that ssh-agent is not being run properly... but that's just a guess.
© Super User or respective owner