You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Felipe Carvalho (JIRA)" <ji...@codehaus.org> on 2010/12/10 13:27:58 UTC
[jira] Created: (WAGON-318) Wagon scp fails: Auth fail
Wagon scp fails: Auth fail
--------------------------
Key: WAGON-318
URL: http://jira.codehaus.org/browse/WAGON-318
Project: Maven Wagon
Issue Type: Bug
Affects Versions: 1.0-beta-3
Environment: OS: Linux
Reporter: Felipe Carvalho
I'm trying to use wagon to scp a war file from the machine where Hudson is running (name=Oneiroi) to the machine where WebLogic is running (name=Lima) and, hence, be able to remotely deploy and start the application upon a successful build.
When I run the job, a get a message failure with the stacktrace below. I really don't have a clue about how to fix this. I've searched Jira and couldn't find anything that seemed to match my problem. I've reported it as a bug, but I don't really know if it's really a bug within the plugin or if I need to set anything in my configs, any help is greatly appreciated:
{code}
[INFO] Building srgd :: web
[INFO] task-segment: [wagon:upload-single] (aggregator-style)
[INFO] ------------------------------------------------------------------------
[INFO] [wagon:upload-single {execution: default-cli}]
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Unable to create a Wagon instance for scp://lima/
Embedded error: Cannot connect. Reason: Auth fail
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Unable to create a Wagon instance for scp://lima/
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at hudson.maven.agent.Main.launch(Main.java:165)
at hudson.maven.MavenBuilder.call(MavenBuilder.java:165)
at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:744)
at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:688)
at hudson.remoting.UserRequest.perform(UserRequest.java:114)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:270)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to create a Wagon instance for scp://lima/
at org.codehaus.mojo.wagon.AbstractWagonMojo.createWagon(AbstractWagonMojo.java:83)
at org.codehaus.mojo.wagon.AbstractSingleWagonMojo.execute(AbstractSingleWagonMojo.java:62)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:182)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
... 28 more
Caused by: org.apache.maven.wagon.authentication.AuthenticationException: Cannot connect. Reason: Auth fail
at org.apache.maven.wagon.providers.ssh.jsch.AbstractJschWagon.openConnectionInternal(AbstractJschWagon.java:264)
at org.apache.maven.wagon.AbstractWagon.openConnection(AbstractWagon.java:105)
at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:207)
at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:149)
at org.codehaus.mojo.wagon.shared.WagonUtils.createWagon(WagonUtils.java:65)
at org.codehaus.mojo.wagon.AbstractWagonMojo.createWagon(AbstractWagonMojo.java:79)
... 32 more
Caused by: com.jcraft.jsch.JSchException: Auth fail
at com.jcraft.jsch.Session.connect(Session.java:451)
at com.jcraft.jsch.Session.connect(Session.java:149)
at org.apache.maven.wagon.providers.ssh.jsch.AbstractJschWagon.openConnectionInternal(AbstractJschWagon.java:236)
... 37 more
{code}
Wagon is configured in my pom.xml as follows:
{code}
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>wagon-maven-plugin</artifactId>
<version>1.0-beta-3</version>
<executions>
<execution>
<id>Company</id>
<phase>deploy</phase>
<goals>
<goal>upload-single</goal>
</goals>
</execution>
</executions>
<configuration>
<serverId>Company</serverId>
<fromFile>target/srgd.war</fromFile>
<url>scp://lima/</url>
<toDir>/ebusiness/shared/Dev01v103/applications/srgd</toDir>
</configuration>
</plugin>
{code}
The Hudson's settings.xml is as follows:
{code}
<settings>
<proxies>
<proxy>
<id>company</id>
<active>true</active>
<protocol>http</protocol>
<username>SAHUDSON</username>
<password>w2f4h6k9</password>
<host>inet-sys.company.com</host>
<port>8080</port>
<nonProxyHosts>lima</nonProxyHosts>
</proxy>
</proxies>
<servers>
<server>
<id>Company</id>
<username>SAHUDSON</username>
<password>SAHUDSON0000</password>
</server>
</servers>
</profiles>
</settings>
{code}
The Hudson known_hosts is as follows:
{code}
suporte2,10.2.96.2 ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEAzSS1eSvQawu+CpvwV3YVSrYNpKpzSgEGcBLAeEnj4fnaLFsJdF/xI2qGjvZNqSG4LdSF+j8YeEi8kEDSFQq432cBGIxYohWx7IzPGCFa2REI+WV16Qj9KyJBx77P7kxkOUv4G5fUqIfvy1kFCvgHIIw+IzNHQxqNkfFylg4Enas=
porfirio ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEArxbs1smGv2bHjeUzREKJSW5IN/KaGwhzLFcGq/Vzngv3D4OY+MBCm8bjzC8ru0f3yryZNBheWlBx01wq0cdjdfpLgWrZynT6TXYuY44LIJLDRkqVERUoiHS9Ay6pUwS+1vI2LkacdhLDqXVps23VVnY0wbEck+yH31BMARkul/0dE6rcxbhKksm+njK2yTovzj1HZ93PqF9NQA5/vdAtfWQg8g7qU/Gn+p7rlHS1Wzlscm5JhJd2D1lhwQ+NUaVrNXDe2l7T3ewICZvplNhRMbmEQKyzYoQlmM8zot6i24sPrZFHxOKvKToxb6jw7hXXXNg2V5mD/Qk5eSPjLc+ZPw==
lima,10.21.108.105 ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAuFbDMNQBmIt+cB2+2dxrhL8F7pPxC1bnL9vi9xez9HNo9t+QMl4gE9Id4PlAQmjP5DWCD4GPCCTLVnAGPXg5UQ+VK8veQ9TIcZTmI6TVZOLf6FhaQZnN1cjkJY0/xZEcwHGh1tMmm+3Ko/SaV6Ftw6E1Qe5/GOUMl1AlxqCFMh4MHBXOtvmRxCLI6EGLekql7zdMfCFjcdJisB0JH476mFWdH4YIllIA/5JLPuU0zOjQYRmJLVxjLt4RMunQR1rp6+JwYmGJTWH3nbbG1ApcNlSHB/FjQCWz6iMajubLZC8y7dnfhwGgDwUXwVFaShC9SaKNwMCt+p6n/7QEKFz+Bw==
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira