-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disabling smb v1 results in com.xebialabs.overthere.RuntimeIOException #198
Comments
Hi Rob, Yes there is such a possibility. From 5.5.6 onwards XLD has support for the SMBv2 protocol suite. You need to convert your There is a converter plugin available at: https://github.com/xebialabs-community/xld-overthere-smb-converter-plugin |
Also the regular XL support channel guys have some tools/scripts to help you. |
Thank you for the quick responce. |
Hello, I know this issue is closed, but has this been addressed in the "regular" overthere libraries (i.e. not just XLD)? I am also seeing this issue in my overthere libraries (v5.0.2). |
For overthere you need to switch to a different connection type (i.e. SMB instead of CIFS) to take advantage of the SMBv2 support. |
Does that mean I create my connection with If that's the case, how do I configure the Thanks for any help! |
The same as with |
Thank you! I am able to make the change to use SMB instead of CIFS, however, when I try to use WinRM over HTTP, I am unable to execute any commands, they result in a connection timeout. The process is that I make the connection, and copy a zip file and an "unzip.exe" file to the remote host. That works fine. When I then execute the "unzip.exe" command to extract the zip file contents, I get the following:
This is similar to another issue I reported, #220 Again, thanks for any help, I very much appreciate it! |
Recently we disabled smb v1 on our Windows environment. This result in the error below. Is there a way to configure the overthere framework to use SMB v2.X? The bug was confirmed when re-enabling smb v1. Currently we are using XLDeploy version 5.5.7 but I couldnt find a potential fix in the release notes of newer versions.
Uploading file to the temporary directory...
Cannot transfer files to x.x.x.x.x Please check the connection settings.
com.xebialabs.overthere.RuntimeIOException: Cannot determine existence of \1x.x.x.x.x\C$\windows\temp\ot-20170609T153247145: jcifs.smb.SmbException: Failed to connect: 0.0.0.0<00>/1x.x.x.x.x
jcifs.util.transport.TransportException
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(Unknown Source)
at java.net.SocketInputStream.read(Unknown Source)
at jcifs.util.transport.Transport.readn(Transport.java:29)
at jcifs.smb.SmbTransport.peekKey(SmbTransport.java:388)
at jcifs.smb.SmbTransport.negotiate(SmbTransport.java:288)
at jcifs.smb.SmbTransport.doConnect(SmbTransport.java:319)
at jcifs.util.transport.Transport.run(Transport.java:241)
at java.lang.Thread.run(Unknown Source)
at jcifs.util.transport.Transport.run(Transport.java:258)
at java.lang.Thread.run(Unknown Source)
at com.xebialabs.overthere.cifs.CifsFile.exists(CifsFile.java:89)
at com.xebialabs.overthere.spi.BaseOverthereConnection.getTempFile(BaseOverthereConnection.java:190)
at com.xebialabs.overthere.spi.BaseOverthereConnection.getTempFile(BaseOverthereConnection.java:165)
at com.xebialabs.deployit.plugin.overthere.step.CheckFileTransferStep.uploadFile(CheckFileTransferStep.java:61)
at com.xebialabs.deployit.plugin.overthere.step.CheckFileTransferStep.execute(CheckFileTransferStep.java:49)
at com.xebialabs.deployit.engine.tasker.StepExecutingActor.executeStep(StepExecutingActor.scala:90)
at com.xebialabs.deployit.engine.tasker.StepExecutingActor$$anonfun$receiveExecute$1.applyOrElse(StepExecutingActor.scala:54)
at scala.runtime.AbstractPartialFunction.apply(AbstractPartialFunction.scala:36)
at com.xebialabs.deployit.engine.tasker.ReceiveWithMdc.apply(ReceiveWithMdc.scala:58)
at com.xebialabs.deployit.engine.tasker.ReceiveWithMdc.apply(ReceiveWithMdc.scala:33)
at scala.PartialFunction$class.applyOrElse(PartialFunction.scala:123)
at com.xebialabs.deployit.engine.tasker.ReceiveWithMdc.applyOrElse(ReceiveWithMdc.scala:33)
at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:170)
at akka.actor.Actor$class.aroundReceive(Actor.scala:482)
at com.xebialabs.deployit.engine.tasker.StepExecutingActor.aroundReceive(StepExecutingActor.scala:36)
at akka.actor.ActorCell.receiveMessage(ActorCell.scala:526)
at akka.actor.ActorCell.invoke(ActorCell.scala:495)
at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:257)
at akka.dispatch.Mailbox.run(Mailbox.scala:224)
at akka.dispatch.Mailbox.exec(Mailbox.scala:234)
at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
Caused by: jcifs.smb.SmbException: Failed to connect: 0.0.0.0<00>/x.x.x.x.x
jcifs.util.transport.TransportException
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(Unknown Source)
at java.net.SocketInputStream.read(Unknown Source)
at jcifs.util.transport.Transport.readn(Transport.java:29)
at jcifs.smb.SmbTransport.peekKey(SmbTransport.java:388)
at jcifs.smb.SmbTransport.negotiate(SmbTransport.java:288)
at jcifs.smb.SmbTransport.doConnect(SmbTransport.java:319)
at jcifs.util.transport.Transport.run(Transport.java:241)
at java.lang.Thread.run(Unknown Source)
at jcifs.util.transport.Transport.run(Transport.java:258)
at java.lang.Thread.run(Unknown Source)
at jcifs.smb.SmbTransport.connect(SmbTransport.java:309)
at jcifs.smb.SmbTree.treeConnect(SmbTree.java:156)
at jcifs.smb.SmbFile.doConnect(SmbFile.java:911)
at jcifs.smb.SmbFile.connect(SmbFile.java:954)
at jcifs.smb.SmbFile.connect0(SmbFile.java:880)
at jcifs.smb.SmbFile.queryPath(SmbFile.java:1335)
at jcifs.smb.SmbFile.exists(SmbFile.java:1417)
at com.xebialabs.overthere.cifs.CifsFile.exists(CifsFile.java:87)
... 23 more
The text was updated successfully, but these errors were encountered: