130.237.232.237 Status 512 (wu not uploading)

[dubzhouse]

Got a question about uploading of wu's and internet speed. I am currently on satellite internet and have been folding a while. I can upload standard bigadv just fine but when it comes to trying to upload a 6903/4 i get the status 512 and couldnt send http request to server.
Is my upload speed (about 95kbps) too slow to upload the p6903/4 wu's?
Is there a minimum upload bandwith requirement for these big wu's?

Thanks

[bruce]

Welcome to foldingforum.org, dubzhouse.

There are effective upload bandwidth requirements but I don't know what they are.

The size of the file that must be uploaded varies depending on which project we're talking about. Those numbers are not reported anywhere that I know about.

Every server has a timeout which resets connections that have been active "too long" -- assuming that they're hung. The timeouts are not published either.

Divide the filesize by the timeout and you'll have a minimum bandwidth requirement, but as I said earlier, I don't know the numbers so I don't know if that's the problem you're dealing with. How long was your connection active before you got the error? How big was the file being uploaded?

[dubzhouse]

The wu was a 6903 but now sure of the size. Can check when I get home.
The wu was finished around 3 am pst and still hasn't uploaded yet. It keeps saying that it couldn't send http request to server. I can check the log file when I get home and let you know how long it went from the time I finished until I got the error.
I know it takes about 45 minutes to an hour to upload a standard bigadv wu.

[Jesse_V]

Every server has a timeout which resets connections that have been active "too long" -- assuming that they're hung. The timeouts are not published either.

This may answer it although I don't know where MtM got his info from: viewtopic.php?f=55&t=19458&p=194222&hilit=server+timeout#p194222

[7im]

Bruce's answer is non-specific for a reason. As he said, timeouts are not published. They also change as needed by server or by project needs. Any quoted timeout would be for only one server/project, and is likely to have changed as more time passes.

So any quoted timeout has a short shelf life. Bruce's answer is still the better answer, especially since the author of the quoted post admits the same problem a few posts later in that thread.

[dubzhouse]

I checked the log file and it went about 10 minutes of trying to upload a file before getting a new wu. I have langouste enabled for linux folding in virtual box.
The file size when finished was 230725040 and compressed to 222384162.
I got the couldnt send http request to server 3 minutes after the wu was compressed.

[bruce]

I'm going to add 130.237.232.237 to your topic title. There are other reports in this forum concerning troubles with that server. I believe the issues have been resolved, but perhaps not, and perhaps and your satellite connection may contribute to the difficulties that you're having.

Neither Virtual box nor Langouste are supported by Stanford. That doesn't mean they won't work, nor does it prevent somebody who happens to know something about either of them from offering suggestions. It only means that you may not find the answer you're looking for.

A connection dying after 3 minutes or after 10 minutes isn't because of a server timeout, particularly on servers which normally receive 200 MB files. Does it work if you disable Langouste? Does it work if you connect a native linux linux installation to that satellite connection?

Perhaps someone with that sort of configuration will report whether they have had either success or failure.

[dubzhouse]

I have ran linux and have the same issues. The first time I had this issue was in linux so I went back to windows and folded there to make sure wu's would upload and they did and then I went to vb to see what would happen. I had langouste disable for the first one in linux and it would give me the status 512 error and couldn't connect to the server. It tried and tried for almost 6 hours and still nothing.
From my knowledge of langouste it will download another wu and then send the finished wu back.

Not sure what is going on. I know it will upload a standard bigadv but the 6903/4' won't upload. It seems like maybe my internet upload just isn't fast enough.

All my rigs are connected through a router and then to the modem. The rig that won't upload the wu is able to get on the internet without any issues as I have done speed tests on it and browsed just to make sure.

[bruce]

From my knowledge of langouste it will download another wu and then send the finished wu back.

I have not used langouste and I'm certainly not an expert in how it works, but from what I've heard, it doesn't wait for the download to finish before starting to send the finished WU back. I have not used satellite connections and I am certainly no an expert, but from what I've heard, wired internet connections do a much better job of handling full duplex connections (sending and receiving simultaneously) than satellite connections do. If both are true, disabling langouste will reduce your throughput but it will be more likely to communicate successfully. I suggest trying to run FAH without it and see what happens.

[Grandpa_01]

I know 2 or 3 days ago that server was having some problems it took me 45min. to download a 54MB file form it on 4 different machines running linux it normally takes less than 2 min to download that file. I think that problem has been solved though because I fished and sent a 6903 today to that server and it only took 14 min. to upload the 200MB file. I did see that error on 2 of the 4 machines a couple of days ago when the server was having the problems though. And I have also seen that error when the servers are heavily loaded in the past. But I am not so sure the experiences I have had have anything in common with your issue. Have you tried disabling langoust and rebooting to see if it would send.

[dubzhouse]

I disabled langouste and rebooted. It started folding like normal and then tried to autosend the unit. I got the status 512 error and couldnt send http request to server again. It tried the 130.237.232.237 and 130.237.165.141 servers and both got the same issues. Im starting to think that it might just be my internet service i have. Maybe the files are to big and my internet is just to slow and cant upload them.
Looks like it is back to windows and folding standard bigadv.

[kasson]

How long does it take before you get the error? The maximum allowable upload time for that server is currently 2 hours; if your connection does not permit you to upload the work units within that period, we would recommend not running these work units.

[sco01]

kasson
Where you can find the time limit for sending more jobs to other servers?