Thank you for confirming this. Filed at http://jira.codehaus.org/browse/WAGON-253
-- Larry On Tue, Dec 30, 2008 at 2:33 PM, Dan Tran <[email protected]> wrote: > I can confirm that, the known_hosts file is rewritten for each ssh > connection. I can also confirm with the wagon code > ( 1.0-beta-4 ) thru debugger. > > So it has true potential of ssh connection collision when you have > multiple current maven deploy builds > > Please file a bug a against wagon > > -Dan > > > On Tue, Dec 30, 2008 at 10:05 AM, Larry Shatzer, Jr. <[email protected]> wrote: >> I have a Bamboo instance running quite a few builds using maven >> deploying the artifacts to an internal maven repository using scp. On >> occasion some of them seem to hang with "The authenticity of host >> HOSTNAME can't be established." We have to end up stopping the build, >> and restarting it. Looking over the mailing list and documentation it >> tells me to create the .ssh directory or the known_hosts file (by >> either using ssh/scp by hand to create it for me). The problem is that >> file already exists. I have noticed that when a mvn deploy task is run >> the timestamp on the known_hosts file is updated. Is maven rewriting >> the known_hosts file? Thereby creating a potential race condition if >> multiple maven deploys are being run at the same time, and the file is >> empty/non existant during the rewrite? It looks like it is looking at >> the code, in AbstractJschWagon.java around line 233-270 (with 270 >> doing the actual writing). I have started to notice that this is >> becoming more frequent, as there are now much more maven projects >> building under the Bamboo instance. >> >> I am using Maven 2.0.9. Any help would be appreciated. >> >> -- Larry >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
