All large commits fail with a socket write error.
TheHarvesteR on Mon 09 Jan, 2012 17:19:13 +0000
Hi,
I’m having serious trouble making any commits larger than abuot 400kb here.
The upload progresses very slowly, and eventually dies out with a message saying the server’s reset the connection after a PUT request failed.
The failed request is always on the larger files on the commit...
This is happening constantly now, and I’ve been unable to make any commits since last week. Needless to say, I’m pretty stuck until this issue is resolved.
I’ve set up a support ticket (#23574) with this problem.
Thanks in advance for any help. This matter has grown to be quite urgent now.
Cheers
Well, that’s the worrying part. There is no firewall up here, nor am I using any proxies (Unless my ISP is putting up barriers, which would be really odd).
Should I have any ports forwarded on the router for SVN?
Sorry for double posting, but this is really urgent now, and I’ve made no progress so far...
On the notion that my router was putting up a barrier for SVN, I put my computer on the DMZ... however, that made absolutely no difference. I’ve set the network here to disable all firewalls to my computer, but no luck...
Now I’m completely stumped.
Again, thanks in advance for any help.
Cheers
I’ve restarted everything conceivable and even run diagnostics on your repository. Everything looks good.
Had a look at your HTTP requests and they are incomplete – there’s something that’s munging your PUT requests and they’re not reaching the server at all. I would check your network connection.
Another suggestion would be to try it from a different PC and see if it makes a difference.
I’m almost certain if I tried to check-in a 1MB file, it would work.
Hi,
Thanks mate! I figured it would be something on my end, or in between... I’m on the phone with my ISP support now...
Most likely the half-wits have my zone firewalled or something...
Cheers
Hi again,
Well, my ISP says I’m good up to their end, but we’ve found that from my end to the svn servers, there are 15 hops... that’s quite a lot, and lots of potential for data loss...
Indeed, I’ve been tracerouting xp-dev now, and my http headers are coming in with errors quite frequently... especially if SSL is enabled.
The ISP support says I should disconnect for a minimum of three hours to try and get myself a new IP address here, and hopefully a new route... Makes sense actually. It explains the sporadic nature of these failures.
Cheers
You do not have sufficient permissions to comment
Comment: Sorry for double posting, but this is really urgent now, and I've made no progress so far... On the notion that my router was putting up a barrier for SVN, I put my computer on the DMZ... however, that made absolutely no difference. Now I'm completely stumped. Again, thanks in advance for any help. Cheers → Sorry for double posting, but this is really urgent now, and I've made no progress so far... On the notion that my router was putting up a barrier for SVN, I put my computer on the DMZ... however, that made absolutely no difference. I've set the network here to disable all firewalls to my computer, but no luck... Now I'm completely stumped. Again, thanks in advance for any help. Cheers
Comment: Well, that's the worrying part. There is no firewall up here, nor am I using any proxies (Unless my ISP is putting up barriers, which would be really odd). → Well, that's the worrying part. There is no firewall up here, nor am I using any proxies (Unless my ISP is putting up barriers, which would be really odd). Should I have any ports forwarded on the router for SVN?
Reply
rs on Mon 09 Jan, 2012
From time to time we tend to get users who mention this. Invariably, most of the time it’s due to some software or firewall or proxy that’s mangling the requests. Do you mind turning it all off and retrying ?