I'm using Eclipse Kepler and connect to SVN via VPN. Sometimes VPN connection drops and when I try do do commit without connection I have to wait for 10 minutes until timeout.
The SVN console shows:
commit -m "...comment..." -N ...file_list...
org.apache.subversion.javahl.ClientException: Connection timed out
svn: Commit failed (details follow):
svn: Unable to connect to a repository at URL 'http://192.168.9.2:81/svn/...'
svn: Connection timed out
Why it takes 10 minutes to get timeout? How can I change it?
EDIT:
Maybe it is related to network routing problem. With VPN is disconnected ping 192.168.9.2 gets timeout instead of unreachable host.
(If you're connecting to your SVN using http protocol) Try setting the http-timeout property in ([global] or relevant server-group section of the) servers file in your subversion home (at %APPDATA%\Subversion\servers on Windows) to a low enough value (in seconds - say like 30), so that subversion realizes the connection is kaput sooner, and causes an error message pop-up!
(By default, bottom of) The file should looks something like this:
[global]
http-timeout = 30
History:
I also had issues with work VPN every now and then, and google took me to this old question. #lhasadad commented that he posted an answer but I couldn't see one (I don't know if this method did not work for him, or why the post was deleted, but I could confirm that it still works! (that is, it makes the handling of connection issue better)). Unfortunately that forum link is also giving 404 atm. So I dived into wayback machine and found a copy from April 2016! Credits go to "stefan", a moderator of that forum. He also mentions (if you have Tortoise), this servers file can be opened by "Settings\Network[Edit]" in that GUI.
Related
Following the doc from Rundeck, however the only button I have under "Sources tab" is "ResourceModelSource"
When I click that button I get a blank
PPS Issue happened on previous version - new to RunDeck, so I can't say that it EVER worked
I tried adding a manual resouces.xml in the project director y(Which I had to manually create, which tells me that's another issue) and reloading RD but that did not seem to work
While it's not the likely cause, I'll mention it here incase it IS relevant, I'm hosting on port 4440 however I'm using nginx to forward http (not https) requests on 443 to 4440, this is due to corp net sec policy.
I'm sure it's something where it's having an i/o issue on the local host, however I'm not seeing anything in the logs.
That is a known issue when you have Rundeck installed behind a proxy server, take a look at this: https://github.com/rundeck/rundeck/issues/6278 the solution is to set the grails.ServerURL (rundeck-config.properties file) with the exit URL defined for Rundeck in your proxy server (e.g: grails.serverURL=http://my_domain/rundeck), then restart the Rundeck service.
I have encountered this problem recently and I have never been able to find a coherent explanation or solution.
When attempting to push a specific branch to github, I am receiving the following error:
client_loop: send disconnect: Connection reset by peer
fatal: the remote end hung up unexpectedly
fatal: the remote end hung up unexpectedly
I am able to push other branches fine, so it cannot be a network error.
I vaguely remember in the past getting an error like this when I mistakenly included something like an auth token in the code. However, that is not the case here.
I am also not pushing any particularly large files (except maybe package-lock.json?)
How I can I find out more about what is causing github to reject my push?
Update
After a dozen tries over about 20 minutes the push was finally accepted. I am still curious whether there is an explanation.
I suppose there could be a number of reasons for this to occur, but in my case it was some issue on our VPN. I encountered the issue again today, hopped off the VPN and pushed again, and it immediately worked.
There is simple solution for this. Go to git bash and just follow the steps,
(1) vim .ssh/config
(2) insert- ServerAliveInterval 60
(3) close vim by Esc ---> ZZ
I'm currently trying to access a remote server using VS Code's Remote SSH extension. I haven't had a problem when using it before (that was around a month ago) but today when I tried to access the server I ran into some trouble.
I have the hostname and everything configured in a config file, and so I just click on that option and type in the password. However, VS Code seems to be stuck on "Opening Remote..." for the past hour or so. The dialogue I get in the terminal is as follows:
username#host's password:
Running remote connection script
Acquiring lock on /home/username/.vscode-server/bin/abcdefghijklmnop1234567989/
vscode-remote-lock.abcdefghijklmnop1234567989
Installing to /home/username/.vscode-server/bin/abcdefghijklmnop1234567989...
Downloading with wget
Does anybody know what the problem might be? Is this normal?
EDIT
As soon as I posted this the connection was successfully made. However, I would also like to still know what the problem was and if it normally takes around an hour, and what this process might be doing. I also believe it would be helpful to the community overall.
Thank you.
I've faced the same issue just now and realized that firewall protection has something to do with it.
As soon as I disabled it, the remote connection was established and I managed to see my code again.
Jmeter Environment Details
I am performing Jmeter testing on Microsoft Azure Cloud. I have created on VM(Virtual Machine) on the same cloud and from there I am hitting the application server on the same cloud environment. So in this case there is no network latency.
Problem Statement:
I am trying to run the load test for 300 users for 30 mins , but after 5 mins my script started failing, because of Socket connection refused error.
My Analysis based on information available on net:
I have read somewhere that this problem is because of limited socket connection limit on server, but when i run the same test from VM then my scripts run's just fine. so its definitely not server's issue. Can somebody please help me resolve this issue? Are there any settings needs to be done in jmeter, increase the socket connections?
Actual Screenshot of Error
enter image description here
Most likely:
Looks like situation described at Connection Reset since JMeter 2.10 ? wiki page. If you're absolutely sure that nothing is wrong with your server, you can follow the next recommendations:
Switch all your HTTP Request Samplers "Implementation" to be "HTTPClient4". The fastest and the easiest way of doing it is using HTTP Request Defaults.
Add the next lines to user.properties file (in JMeter's /bin folder)
httpclient4.retrycount=1
hc.parameters.file=hc.parameters
Add (or uncomment and edit) the following line in hc.parameters file
http.connection.stalecheck$Boolean=true
Alternative assumption:
"Good" browsers send "Connection: close" with the last request to the web server. "Bad" browsers don't and keep connection open. You can control this behaviour via "Use KeepAlive" checkbox in the HTTP Request Sampler/Defaults. If it's unchecked - you can try ticking it.
I am using Source anywhere for vss and while getting the update it gives me following error
Error at recv(): An existing connection was forcibly closed by the
remote host.
from your screenshot, the software is trying to retrieve the project/file tree structure. this error could happen if the internet connection between the client and the server is unstable. you may try refreshing to see whether the problem remains
It was some log files issue with Source any where . System Restart does the work. It's happens every few days and system restart does work. But I am still looking for proper solution