Could Not Upload Error 135 Socket Write Error
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business socket write error ftp Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation
Software Caused Connection Abort: Socket Write Error
Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like socket write error minecraft you, helping each other. Join them; it only takes a minute: Sign up What causes: Error -135: socket write error up vote 1 down vote favorite 1 I am trying to upload a 12MB .wav file on a socket write error connection reset by peer minecraft Mac running Transmit to a Linux box running Apache and get the following error after uploading just 160KB of the file: error-135-socket-write-error Any clues why I may be getting this? I have successfully uploaded much larger files in the past and nothing has changed on the configuration. ftp share|improve this question edited Mar 22 '10 at 16:52 asked Mar 22 '10 at 16:31 fmz 2,862184897 Belongs on superuser –Paul R Mar 22 '10
Transmit Write Error
at 16:39 I edited the question. You can take away the -1 now. –fmz Mar 22 '10 at 16:52 I still don't see anything programming-related in the question. –Paul R Mar 22 '10 at 16:58 I vote we close it. I added it to superuser. Thanks. –fmz Mar 22 '10 at 18:32 Questions are automatically migrated to other sites when they get enough appropriate close votes. –Helen Mar 23 '10 at 18:37 add a comment| 3 Answers 3 active oldest votes up vote 6 down vote accepted The disk was full and this caused the error -135. share|improve this answer edited Dec 9 '11 at 0:04 answered Mar 23 '10 at 18:17 fmz 2,862184897 add a comment| up vote 1 down vote Check the File Name are there spaces or symbles in it share|improve this answer answered Dec 6 '11 at 16:51 Antimatter 111 add a comment| up vote 0 down vote Hard to say without knowing which OS is running on the client and the server (i.e. where the error code might come from). The error means that the client couldn't send any more data to the server. This is either because the server stops accepting more bytes (hangup, disk full, quota exceeded) or because the connection times out (but then, I'd expect a "connection
fine (the FTP details are correct) but after trying for a few seconds (about 10) the upload stops and freeway reports "cannot complete upload because the server reported an error". It happens mainly on PDFs which get uploaded with the main site (I have a ftp connection reset by peer socket write error ‘downloads' page where users can download PDFs). So, I tried two other FTP packages instead, Cyberduck and error socket write error Transmit. Both managed everything but the PDFs (the PDFs are only 1.2meg each and the file names contain no illegal characters), at which point the upload stopped - Cyberduck reporting a ‘broken pipe' and Transmit ‘Error 135: socket write error'. Which led me to believe there's an issue with my net connection. My upload speed is on average 0.6meg a sec, and handles everything I throw at http://stackoverflow.com/questions/2493970/what-causes-error-135-socket-write-error it everyday fine - many Gmail attachments along with my Livedrive backup which often handles gigabytes a week. So finally I tried it with CuteFTP on Windows 7 running on the same Mac in bootcamp. Upload worked straight away, no issues. So, it's a Mac issue then? I'm using OSX 10.7.3, MacPro 3gb Ram. At least I know it's not a problem attributed directly to Freeway, but thought I'd ask here in case anyone else has had the problem. If anyone can shed some https://freewaytalk.softpress.com/thread/view/107820 light onto it I'd appreciate it. Many thanks. Neil. quote DeltaDave 11 Apr 2012, 4:55 pm There are different upload settings possible - try toggling between them. They are Automatic (default) Passive and Non-passive So if you are on Auto try Passive, if that doesn't work try Non-passive. David quoteGlasgow, Scotland iMac 27 5K El Cap and Pro Final Neil 11 Apr 2012, 5:18 pm Hi David, Thanks for the reply. I forgot to mention that I'd tried all three, same error I'm afraid. Thanks, Neil. quote DeltaDave 11 Apr 2012, 7:06 pm In that case make sure that you save the log file and send it in to support(at)softpress.com You will find it at User>library>logs>Freeway 5>FTP logs D quoteGlasgow, Scotland iMac 27 5K El Cap and Pro Final Neil 12 Apr 2012, 9:07 am Hi Dave, Thanks for the reply, I'll send the log off to Softpress and see what they say. Cheers, Neil. quote Neil 12 Apr 2012, 11:36 am SORTED!! Didn't get round to sending to Softpress as I've just sorted it. The offending item is my LiveDrive Briefcase software, it's a bit like Dropbox. As soon as I unmounted it from my desktop, all FTP works just fine. Given my LiveDrive Briefcase handles anything up to 3gig a day sometimes I can only asume it's doing something with my net connection, even though I set it to pause whilst doing uploads. So if it's any help to anyone else, that was the problem! Neil. quote Back
posted 2013-May-8, 5:02 pm ref: whrl.pl/RdAfKA posted 2013-May-8, 5:02 pm O.P. I am at a bit of a loss with this. When uploading to my http://forums.whirlpool.net.au/archive/2097099 personal hosting account the connection continuously drops. I have tried different file sizes, types, directories, ftp upload methods, different applications, different computers. All the same. Ping and traceroute seem ok, 0 packet loss. The strange thing is I am able to successfully upload, without timeouts, to my members.iinet.net.au account as well as client FTP accounts. And to make it more confusing, my Telstra 3G write error USB connection uploads to my personal (the same) hosting account with no socket write errors. There seems to be a problem between iinet and my hosting? I have spent hours on the line with customer service already. While I understand this may be strange, the CS team seems fairly incompetent repeatedly asking me to try things I have already discussed with them. So, hoping someone socket write error here has an idea or two... User #46036 29443 posts Frey Whirlpool Forums Addict reference: whrl.pl/RdAfNh posted 2013-May-8, 5:13 pm ref: whrl.pl/RdAfNh posted 2013-May-8, 5:13 pm Tried lowering your MTU? User #561954 9 posts briantfx I'm new here, please be nice reference: whrl.pl/RdAfXq posted 2013-May-8, 5:45 pm ref: whrl.pl/RdAfXq posted 2013-May-8, 5:45 pm O.P. On a mac. It is set automatically (1500). Have lowered to lowest range option (1280). Same issue occurs. User #332406 2303 posts Adam O'Grady Whirlpool Forums Addict reference: whrl.pl/RdAgdL posted 2013-May-8, 6:59 pm ref: whrl.pl/RdAgdL posted 2013-May-8, 6:59 pm Have you tested another computer on that same connection and checked if it has the same errors or not? briantfx writes... my Telstra 3G USB connection uploads to my personal (the same) hosting account with no socket write errors. Is this testing the same computer on both connections? User #561954 9 posts briantfx I'm new here, please be nice reference: whrl.pl/RdAgfv posted 2013-May-8, 7:07 pm ref: whrl.pl/RdAgfv posted 2013-May-8, 7:07 pm O.P. Yes. Tested with another mac computer. Same error. Tested with Telstra USB on both computers and it results in a solid, complete upload. No