linuxrouter

I get that same failed to connect to server message with Langouste. However, the unit does generally go out. None of mine have failed to send yet. The send info ends up being recorded in a different log file in /tmp/langouste.

ls /tmp/langouste
cat <filename>

Thanks linuxrouter for responding.
I'll cancel my current work unit and reset it up without langouste, since it's probably not beneficial for me with the smaller 1920 work units anyway, and looks like it might be easier to troubleshoot.

Yeah, those are my GPU and uniprocessor client work units you see on EOC.

linuxrouter
...The send info ends up being recorded in a different log file in /tmp/langouste.

ls /tmp/langouste
cd /temp
cd langouste
more <filename>


The filename should be in this format: langouste-helper-XX.log

more will display what is in that file.

I found my problem reading the .log files, added a step to your quote above.

Reading the langouste log files, I do see the 'Results Successfully Sent' messages :)

So hopefully I'll see those points in the next couple of updates.

Thanks again for all your patient help linuxrouter

My work unit finished up. I got the same messages with "Couldn't send HTTP request to server" in the folding log. However, the work unit did send out and was shown as sent via the log in /tmp/langouste. I believe Langouste terminates the connection for the folding client in order to get it to start downloading a new work unit which is why you would see those errors. Then the previous unit is transmitted from another directory in /tmp/langouste via a helper script.

I came across this thread that explains the process in greater detail: 
 
http://foldingforum.org/viewtopic.php?f=44&t=10593&start=15

Take a look at the 7th post down.