I have a problem with a SFTP connection on my project.
I succeed creating the connection (The Test button told me all was ok)
And i can browse through de folders of the connection.
I can upload my local files to it
But, i can't download files from it.
From the logs :
!ENTRY com.aptana.syncing.core 4 0 2012-02-15 11:39:59.821
!MESSAGE (Build 3.0.0.1321920947) [ERROR] Error during sync {0}
!STACK 0
java.lang.NullPointerException
at com.aptana.filesystem.ftp.internal.BaseFTPConnectionFileManager.getCanonicalURI(BaseFTPConnectionFileManager.java:103)
at com.aptana.core.io.efs.VirtualFile.toCanonicalURI(VirtualFile.java:215)
at com.aptana.core.io.efs.VirtualFile.toString(VirtualFile.java:230)
at com.aptana.core.io.efs.SyncUtils.copy(SyncUtils.java:89)
at com.aptana.ide.syncing.core.old.Synchronizer.downloadAndDelete(Synchronizer.java:827)
at com.aptana.ide.syncing.core.old.Synchronizer.download(Synchronizer.java:711)
at com.aptana.ide.syncing.ui.actions.DownloadAction$1.run(DownloadAction.java:146)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
I can download files in SFTP from this server via Filezilla
I had several project with the same organization( Debian server, SFTP connection, ..), it always worked well
Any ideas ?
Related
For my Selenium/Cucumber/Maven project I downloaded the latest version of the Chrome and IE driver via Webdrivermanager on an virtual machine with an internet connection. After this I used the same project (using the same Maven local repo folder) on a Windows server without an internet connection, set an override for the local Maven repo folder in IntelliJ and added the forceCache option:
ChromeDriverManager.getInstance().forceCache().setup();
driver = new ChromeDriver();
Version of webdrivermanager = 1.7.2
When executing a test via the command line of Windows with Maven command mvn test clean, I receive below connection error. The browser driver is available in the local repo.
INFO BrowserManager - Reading https://chromedriver.storage.googleapis.com/
to seek [chromedriver]
[main] INFO BrowserManager - Reading
https://chromedriver.storage.googleapis.com/ to seek [chromedriver]
[main] WARN BrowserManager - [1/3] Exception reading
https://chromedriver.storage.googleapis.com/ to seek [chromedriver]:
org.apache.http.conn.HttpHostConnectException Connect to
chromedriver.storage.googleapis.com:443
[chromedriver.storage.googleapis.com/216.58.212.208] failed: Connection
timed out: connect
UPDATE: I have executed my test again via the virtual machine with an internet connection. It looks like that Maven is still using the default .m2 folder, which doesn't contain the cached browser drivers and webdrivermanager tries to download the files. So this is not an webdrivermanager issue, but a Maven issue. Has anyone suggestions to fix this issue? I have already restarted my machine, but with no luck.
The cache used by WebDriverManager in a Windows machine is located at C:\Users\your-user\.m2\repository. Concretely, for chromedriver, the binary should be at C:\Users\your-user\.m2\repository\webdriver\chromedriver\win32\2.33\chromedriver.exe. Check this file actually exists, since this is what the forceCache() method is going to look for. I have doubled checked again and this feature is still working as expected. In your case, it seems that the cache file is not available, and therefore WebDriverManager tries to download it.
While configuring a TFS vNext build agent i am getting the error:
ErrorConnectingToTheServer
An error occurred while sending the request. the request.
I could not find any other error message in the event log or anywhere else.
Please help.
Update1: The SSL (https///tfs) did not work.but the plain http:// worked.
Update 2: I have removed the old agents and trying to configure new one. While doing that i am getting the below error that is present in the _diag folder:
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
....
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
....
System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
....
System.Net.Sockets.SocketException (0x80004005): An existing connection was forcibly closed by the remote host
Update 3:
I have two servers as below:
1 is application server and other is SharePoint and reporting server trying to configure the build in 3rd server.
TFS URL is configured with SSL 443.
If I try to configure the agent using http://tfs server/tfs it succeeds, but receives error while building.
When i try to configure using https i get the above error. Interestingly I had used this server for two agents, and in that case i had one more server where i am getting the error was working properly.
I finally found the solution to the issue:
Root cause:
TFS vNext agents use .Net framework 4.5... which by default does not support TLS 1.1/ TLS 1.2.
Solution:
We need to modify .Net framework registry entry to direct .Net framework to use TLS 1.2.
Use the command to update the registry:
reg add HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 /v SchUseStrongCrypto /t REG_DWORD /d 1 /reg:64 (and/or /reg:32)
Referred here:
https://stackoverflow.com/a/28502562/2939996
If next time you have encountered some issues during the build agent configuration. For trouble shooting you could check related configuration logs. To see what was going on, you just go to the folder where the agent was installed. In that folder, a _diag folder exists with logging.
The “ServerUrl” setting of agent listed the default URL for TFS. Which default is HTTP on port 8080. According to your update, if you have changed your configuration to run on HTTPS. So, your TFS was not at 8080, but some others such as 443. And you or other co-workers configured the build agent before changed to HTTPS.
If so, you may need to update the “settings.json” file in the build agent folder and replace the old URL with the new one. After changing this file, restart the build agent service, then go back to the Agent Pools, refresh the page.
I'm having issues deploying an asp.net mvc 4 project from the buildserver to Azure.
We have one azure web site (strictly with nothing deployed to it directly), with a number of Apps deployed in virtual directories underneath. It is with these apps / virtual directories I'm having problems deploying to.
I can deploy direct to Azure from within VS using publish profiles, and also from a batch file which uses publish profiles locally, but it sounds like you cannot use publish profiles on a build server, so I'm using the same settings to fire MSBuild with parameters instead.
The error being returned is:
error : Web deployment task failed.(Could not complete the request to remote agent URL 'http://[site].scm.azurewebsites.net:443/MSDEPLOYAGENTSERVICE'.)
Note this first error lists the main site, not the virtual directory, though this is the value from the .pubxml file that works through VS.
Other errors listed after the first (above) are..
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Web\Microsoft.Web.Publishing.targets(3847,5): error : This error indicates that you cannot connect to the server. Make sure the service URL is correct, firewall and network settings on this computer and on the server computer are configured properly, and the appropriate services have been started on the server.
error : Could not complete the request to remote agent URL 'http://[site].scm.azurewebsites.net:443/MSDEPLOYAGENTSERVICE'.
error : The underlying connection was closed: An unexpected error occurred on a receive.
error : Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
..and the batch file including the msbuild commands & paramaters is..
msbuild projectname.csproj
/P:Configuration=DevDeployMyApp
/p:DeployTarget=MSDeployPublish
/p:DeployOnBuild=True
/p:MsDeployServiceUrl=[Site].scm.azurewebsites.net:443
/p:AllowUntrustedCertificate=True
/p:VisualStudioVersion=11.0
/P:CreatePackageOnPublish=True
/p:username=[user]
/p:Password=[password]
/p:DeployIisAppPath=[site]/[VirtualDirectoryName]
/p:MSDeployPublishMethod=RemoteAgent
/p:IgnoreDeployManagedRuntimeVersion=True
Any ideas?
Is your service is already running, try going into the Azure portal and stopping it before publishing. That sometimes helps get it unstuck.
I'm trying to send some files to a remote machine using Ant <scp> but getting no response from server error.
Tried with verbose option and got following response.
[scp] Authentications that can continue: publickey,keyboard-interactive,password
[scp] Next authentication method: publickey
[scp] Authentications that can continue: keyboard-interactive,password
[scp] Next authentication method: keyboard-interactive
[scp] Authentications that can continue: password
[scp] Next authentication method: password
[scp] Authentication succeeded (password).
[scp] Disconnecting from xx-hostname-xx port 22
[scp] Caught an exception, leaving main loop due to socket closed
code has no issues since it's working fine with other host machines. Issue must be somewhere else. Have anyone came across this issue before? Thanks in advance.
P.S: I can connect to the remote machine from my local using putty without any issues. I have installed openssh on the remote machine.
Is the scp program installed on the remote system? The local scp instance (or ant in this case, I suppose) needs to run another copy of scp on the remote system. If the local program failed to run scp on the remote system, you'd get this behavior.
Edit:
Your local scp client (ant in this case) is going to make an ssh connection to the remote host. Through that connection it's going to try to run a program named "scp" on the remote system. The two scp instances will communicate to do the file transfer. So the program on the remote system has to be named "scp", and it has to be in the command path of the ssh session. I don't think WinSCP fulfills either of these criteria. It doesn't install a program named "scp" or "scp.exe". And at least on my PC, it didn't install itself into my command path.
The simple test would be to make an interactive ssh connection to the remote system and see if you can run "scp" within that session. If you get an error, then ant is also going to get an error.
when i open my website it's shows
Connection to 173.0.139.119 failed.
The system returned: (110) Connection timed out
what is Problem? from my Web Application or Server ?
note:
when i use proxy to open my site it's work fine