Hi :-) We use ssh-agent for batch jobs. The jobs get the key from the ssh-agent over the envoirment variables. When we start many jobs at the same time, the agent dont give the key to the job. We have tracet the our script an see the follow: ... 26918: 0.0004 so_socket(PF_UNIX, SOCK_STREAM, 0, "", 1) = 13 26918: 0.0001 fcntl(13, F_SETFD, 0x00000001) = 0 26918: 0.0003 connect(13, 0xFFBFEC60, 31, 1) Err#146 ECONNREFUSED 26918: 0.0001 close(13) = 0 ... The agent ist bussy when one client is connect to the stream socket. When we make small breaks in the script, the jobs runs fine. Is it an Error in the desing of the Agent ? Greetings Frank
Beckmann, Frank, VF-DE wrote: [...]> The agent ist bussy when one client is connect to the stream socket. > When we make small breaks in the script, the jobs runs fine. > > Is it an Error in the desing of the Agent ?More a limitation of named pipes on Unix. The agent client code could retry on failure. Does the attached patch help? -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: openssh-agent-retry.patch Url: http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20041221/9af219f3/attachment.ksh
Darren Tucker wrote:> Beckmann, Frank, VF-DE wrote: > [...] > >> The agent ist bussy when one client is connect to the stream socket. >> When we make small breaks in the script, the jobs runs fine. >> Is it an Error in the desing of the Agent ? > > More a limitation of named pipes on Unix.Just to clarify: that would be a UNIX-domain socket, not a named pipe, hmm? -- Jefferson Ogata <Jefferson.Ogata at noaa.gov> NOAA Computer Incident Response Team (N-CIRT) <ncirt at noaa.gov>
Beckmann, Frank, VF-DE wrote:> Hi :-) > > We use ssh-agent for batch jobs. > The jobs get the key from the ssh-agent over the envoirment variables. > When we start many jobs at the same time, the agent dont give the key to > the job.How many are you starting simultaneously? ssh-agent sets up a listen backlog of 128 connections by default. -d