Message-Id: <200503232358.j2NNwo8f006437@delorie.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Resent-date: Wed, 23 Mar 2005 15:58:14 -0800 Date: Wed, 23 Mar 2005 15:55:21 -0800 Resent-from: David Rothenberger From: David Rothenberger Subject: Re: ssh-agent people (and others) please try latest snapshot In-reply-to: <20050323181923.GA9283@trixie.casa.cgf.cx> Resent-to: cygwin To: cygwin AT cygwin DOT com Resent-message-id: <42420296 DOT 2040107 AT acm DOT org> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7bit Resent-User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) References: <20050323181923 DOT GA9283 AT trixie DOT casa DOT cgf DOT cx> User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com On 3/23/2005 10:19 AM, Christopher Faylor wrote: > The latest (2005-03-23 as of this writing) snapshot has some more > improvements from Corinna wrt unix domain sockets. > > We're coming close to a 1.5.14 release so I would appreciate it if > people would try the latest snapshot and report their successes or > failures here. This snapshot is not working as well as the 20050322 snapshot for me. I start ssh-agent, add a key to it, and then run while true; do date; ssh-add -l; done in four rxvt windows simultaneously. With the previous snapshot this worked fine. With this snapshot, the loops occasionally all hang up for a while and then several windows print Error writing to authentication socket. Error writing to authentication socket. The agent has no identities. instead of the fingerprint for the key as they should. I tried this with a bash script that would run ssh-add in a loop using strace. I eventually got the same error. I used Ctrl-Z to suspend the scripts and then "kill %1" to kill them. In one window, this caused bash to use 100% of the CPU. When it finally did return to the window, I saw these errors: 8 [main] bash 6920 sig_send: wait for sig_complete event failed, signal -41, rc 258, Win32 error 0 5 [main] bash 4560 sig_send: wait for sig_complete event failed, signal -41, rc 258, Win32 error 0 "kill %1" and "kill -9 %1" had no effect, bash continued to use 100% of the CPU, and I eventually had to kill bash with the Windows Task Manager. I did, however, capture strace output from the ssh-add execution that failed and the ssh-agent. They are here http://mysite.verizon.net/res00a7j/ssh-agent.zip http://mysite.verizon.net/res00a7j/ssh-agent.strace.txt http://mysite.verizon.net/res00a7j/ssh-add.2.strace.txt http://mysite.verizon.net/res00a7j/ssh-add.2.strace.2.txt (The ssh-agent.strace.txt file is 500MB.) ssh-add.2.strace.txt is the strace of the execution that failed. ssh-add.2.strace.2.txt is the strace from the previous execution of ssh-add in that window, which succeeded. I notice the following in ssh-add.2.strace.txt: 385 252744 [main] ssh-add 6592 fhandler_socket::sec_event_connect: sec_event_connect called 1079 253823 [main] ssh-add 6592 fhandler_socket::signal_secret_event: signaled secret_event 9999551 10253374 [main] ssh-add 6592 fhandler_socket::check_peer_secret_event: WFSO rc=258 116 10253490 [main] ssh-add 6592 fhandler_socket::sec_event_connect: accept from unauthorized server 429 10253919 [main] ssh-add 6592 __set_winsock_errno: sec_event_connect:404 - winsock error 10061 -> errno 111 HTH, Dave -- David Rothenberger spammer? -> spam AT daveroth DOT dyndns DOT org GPG/PGP: 0x7F67E734, C233 365A 25EF 2C5F C8E1 43DF B44F BA26 7F67 E734 To do two things at once is to do neither. -- Publilius Syrus -- 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/