Re: Trouble with ssh-agent (maybe opening socket?)
I want to re-anime this thread because until now i did not figure out what the problem is, and using ssh from an admin station without ssh-agent is annoying. The problem appears only when ssh-agent is _not_ started with the -d "==debug" option. So this means that only when ssh-agent forks after starting up it will start to eat full cpu after being connected through ssh-add. == here an example _with_ forking: == fi...@schlepptop ~ $ ssh-agent SSH_AUTH_SOCK=/tmp/ssh-332EpkBmHu/agent.5492; export SSH_AUTH_SOCK; SSH_AGENT_PID=4428; export SSH_AGENT_PID; echo Agent pid 4428; top tells me that ssh-agent is running but idling around... on other shell: fi...@schlepptop ~ $ export SSH_AUTH_SOCK=/tmp/ssh-332EpkBmHu/agent.5492; fi...@schlepptop ~ $ SSH_AGENT_PID=4428; export SSH_AGENT_PID; fi...@schlepptop ~ $ ssh-add <--- cursor blinking here... waiting top tells me that ssh-agent is running on 100% cpu load, i have to kill ssh-agent.exe. == example _without_ forking: == fi...@schlepptop ~ $ ssh-agent -d SSH_AUTH_SOCK=/tmp/ssh-AJrrAAHVZk/agent.932; export SSH_AUTH_SOCK; echo Agent pid 932; <-- cursor blinking here, ssh-agent did not fork other console: fi...@schlepptop ~ $ ssh-add Enter passphrase for /cygdrive/c/Dokume~1/C11188/.ssh/id_rsa: Identity added: /cygdrive/c/Dokume~1/C11188/.ssh/id_rsa (/cygdrive/c/Dokume~1/C11188/.ssh/id_rsa) Identity added: /cygdrive/c/Dokume~1/C11188/.ssh/id_dsa (/cygdrive/c/Dokume~1/C11188/.ssh/id_dsa) ---> everything works fine. So this might be a problem with forking. I did not get strace to connect to the forked process, the command strace -p just does not give me any output. Is there any way to gather more information so that you can help me? By the way, since i have this problem with ssh-agent i have also a problem with FreeNX Windows Client which - if i am not totally confused - also ships some cygwin dlls whith it. NX Client does authenticate to remote host, then stays in "Negotiating link parameters" and then dies. Maybe these two problems has something to do one with the other? I would be very happy if you could give me some good ideas. Christian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Trouble with ssh-agent (maybe opening socket?)
I occasionally see something similar. I can only describe it has managing to log in and get ssh-add started by my first shell before windows has sucessfully started something related to the network stack. In this case, ssh (and maybe any other cygwin socket programs) simply wont work. I have to either log out or maybe even reboot. strace shows a socket operation blocking. As long as I wait for the login process to finish (HD goes idle after login), it never happens. Its annoying because I can usually log in ssh out and read my mail then be done before windows even finished logging in. This behaviour started last fall after a windows update, if I recall correctly. On Tue, May 05, 2009 at 06:15:45AM -0400, Corinna Vinschen wrote: > On May 5 10:03, Christian Anton wrote: > > Now i have absolutely no idea what the problem is, i only see that > > ssh-agent > > starts to get crazy eating all cpu time it can get when ssh-add is trying to > > access its socket. > > I can't reproduce this problem. > > > Do you have any idea how to debug this problem? It is really annoying to > > work with ssh and entering the private key's password on every new > > connection... > > Maybe a BLODA problem? > See http://cygwin.com/1.7/faq/faq.using.html#faq.using.bloda > > > Corinna > > -- > Corinna Vinschen Please, send mails regarding Cygwin to > Cygwin Project Co-Leader cygwin AT cygwin DOT com > Red Hat > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Problem reports: http://cygwin.com/problems.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Trouble with ssh-agent (maybe opening socket?)
On May 5 10:03, Christian Anton wrote: > Now i have absolutely no idea what the problem is, i only see that ssh-agent > starts to get crazy eating all cpu time it can get when ssh-add is trying to > access its socket. I can't reproduce this problem. > Do you have any idea how to debug this problem? It is really annoying to > work with ssh and entering the private key's password on every new > connection... Maybe a BLODA problem? See http://cygwin.com/1.7/faq/faq.using.html#faq.using.bloda Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Trouble with ssh-agent (maybe opening socket?)
Hi cygwin community!
I use cygwin for a long time on my corporate Windows XP client to make
this operation system "usable". In fact i am using the cygwin shell as
ssh/scp client in most cases because it is the most familiar way for me to
work with ssh connections as i come from the unix/linux world.
Since a few days i have a strange problem with ssh-agent whithout having
changed anything in my cygwin configuration. I have not full control over
my windows client because as it is a corporate client the patches and
system changes are globally deployed via netinstaller-script.
in a script which i source in .bashrc if no ssh-agent is running i start a
new one with ssh-agent -s command. This works, in task manager
"ssh-agent.exe" appears.
Next step in the script is to add identities to ssh-agent using the
command ssh-add which results in a hanging ssh-add command and
ssh-agent.exe consuming 50% of CPU (which seems to mean that it totally
consumes one of the two cores).
Now i have absolutely no idea what the problem is, i only see that ssh-agent
starts to get crazy eating all cpu time it can get when ssh-add is trying to
access its socket.
Do you have any idea how to debug this problem? It is really annoying to
work with ssh and entering the private key's password on every new
connection...
Thanks a lot in advance
Christian
Here is the script i use to start ssh-agent (~/.ssh/sshagent.sh):
snip --
SSH_ENV="$HOME/.ssh/environment.`hostname`"
cat ${SSH_ENV}
function start_agent {
echo "Initialising new Secure Shell agent..."
ssh-agent -s | head -2 > ${SSH_ENV}
chmod 600 ${SSH_ENV}
. ${SSH_ENV} > /dev/null
ssh-add
}
# Source SSH settings, if applicable
if [ -f "${SSH_ENV}" ]; then
. ${SSH_ENV} > /dev/null
kill -0 ${SSH_AGENT_PID} 2>/dev/null || {
start_agent;
}
else
start_agent;
fi
snap --
In my .bashrc i have the following:
~/.ssh/sshagent.sh
source ~/.ssh/environment.`hostname`
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
