Langouste -- WU upload/download de-coupler (+upload capping)

[Blasphemous Cannibal]

Kris,

No problems to report, I'm now going to buy an i7 to fold bigadv WU's & sell my GTX 200 cards...Just kidding , well maybe the bit about selling the cards anyway.

Thanks for all your support.

Kind regards
Phil

[tear]

Thanks Phil.

Langouste 0.15.6 is now released. Details available in the first post.

[the animal]

Thanks for your work on this, tear.

[tear]

Hey, you're welcome and thanks for the feedback -- much appreciated.

Post here shall you encounter any issues. Our friendly support staff is standing by

[Hyperlife]

Since upgrading to the v6.34 client on Linux, I've been having some trouble uploading, and it seems to fix itself by taking Langouste out of the equation.

Can anyone confirm they have Langouste working with the v6.34 Linux client? I suspect the problem is on my end, but I wanted to confirm that others aren't having the same problem.

[tear]

It's working fine here:

Code: Select all

$ grep "Results succ"  langouste-helper-*
langouste-helper-18866.log:[12:56:11] + Results successfully sent
langouste-helper-19954.log:[14:11:02] + Results successfully sent
langouste-helper-21056.log:[15:30:28] + Results successfully sent
$ 

If you don't find anything wrong at your end feel free to post Langouste+helper logs.

Are you running on FreeBSD? Are you using traffic shaping feature? What version are you running?

[Hyperlife]

It's working fine here:

Code: Select all

$ grep "Results succ"  langouste-helper-*
langouste-helper-18866.log:[12:56:11] + Results successfully sent
langouste-helper-19954.log:[14:11:02] + Results successfully sent
langouste-helper-21056.log:[15:30:28] + Results successfully sent
$ 

If you don't find anything wrong at your end feel free to post Langouste+helper logs.

Are you running on FreeBSD?

Thanks, tear. These are on my Ubuntu 10.04 rigs, no QOS or anything funny at the router. I'll give it another shot -- if it doesn't work, I'll post the logs.

[tear]

OK.

When I said traffic shaping I was actually thinking of Langouste's "rate limiting" feature (vide first post), sorry about that.
Was this Langouste 0.15.6 or some earlier version?

Thanks,
tear

[Hyperlife]

OK.

When I said traffic shaping I was actually thinking of Langouste's "rate limiting" feature (vide first post), sorry about that.
Was this Langouste 0.15.6 or some earlier version?

Ah, okay. No, I'm not using rate limiting, and I'm running 0.15.6.

I just downloaded a fresh copy of the source, compiled, ran it in daemon mode, and changed the proxy on my Q6600. It'll finish its current WU in a few more hours. I'll post the results then.

[Hyperlife]

Hit the problem again. As soon as a WU finishes, the client tries to get a new one but can't connect to the assignment server:

Code: Select all

[21:23:21] + Attempting to send results [March 1 21:23:21 UTC]
[21:23:21] - Reading file work/wuresults_03.dat from core
[21:23:21]   (Read 3526400 bytes from disk)
[21:23:21] Connecting to http://130.237.165.141:8080/
[21:23:21] - Couldn't send HTTP request to server
[21:23:21] + Could not connect to Work Server (results)
[21:23:21]     (130.237.165.141:8080)
[21:23:21] + Retrying using alternative port
[21:23:21] Connecting to http://130.237.165.141:80/
[21:23:21] - Couldn't send HTTP request to server
[21:23:21] + Could not connect to Work Server (results)
[21:23:21]     (130.237.165.141:80)
[21:23:21]   Could not transmit unit 03 to Collection server; keeping in queue.
[21:23:21] + Sent 0 of 1 completed units to the server
[21:23:21] - Preparing to get new work unit...
[21:23:21] Cleaning up work directory
[21:23:22] + Attempting to get work packet
[21:23:22] Passkey found
[21:23:22] - Will indicate memory of 2008 MB
[21:23:22] - Connecting to assignment server
[21:23:22] Connecting to http://assign.stanford.edu:8080/
[21:23:22] - Couldn't send HTTP request to server
[21:23:22] + Could not connect to Assignment Server
[21:23:22] Connecting to http://assign2.stanford.edu:80/
[21:23:22] - Couldn't send HTTP request to server
[21:23:22] + Could not connect to Assignment Server 2
[21:23:22] + Couldn't get work instructions.
[21:23:22] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[21:23:30] + Attempting to get work packet
[21:23:30] Passkey found
[21:23:30] - Will indicate memory of 2008 MB
[21:23:30] - Connecting to assignment server
[21:23:30] Connecting to http://assign.stanford.edu:8080/
[21:23:30] - Couldn't send HTTP request to server
[21:23:30] + Could not connect to Assignment Server
[21:23:30] Connecting to http://assign2.stanford.edu:80/
[21:23:30] - Couldn't send HTTP request to server
[21:23:30] + Could not connect to Assignment Server 2
[21:23:30] + Couldn't get work instructions.
[21:23:30] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.

I removed the proxy and everything was OK again -- finished WU was sent, and a new WU was downloaded.

Meanwhile, the only thing in /tmp/fah is a file called "f1", and the contents contain (what looks like) a PID number and the FAH client directory path.

[tear]

Can you try starting langouste not as a daemon and provide langouste's
log (grab it from the terminal or use -L)?

[tear]

P.S.
Langouste's default temp directory is /tmp/langouste-$USER (is anything in there?)

One more question -- is Langouste still running? (as in: perhaps it died hence the failures)

[tear]

How did you configure the proxy in the client? Did you use IP address? Host name?
What port number are you using? (please confirm that Langouste is listening on the same port -- netstat -tlnp | grep langous ougtta do it).

[Hyperlife]

There's nothing in /tmp right now except for the aforementioned fah directory, and Langouste still has a PID.

I configured it using localhost, port 8880.

Output of netstat:

Code: Select all

daz@flatline:~$ netstat -tlnp | grep langous
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0 127.0.0.1:8880          0.0.0.0:*               LISTEN      8902/langouste3

/etc/hosts includes localhost pointing to 127.0.0.1.

My other Ubuntu rig has a WU finishing in about 5 hours. I've started Langouste on it (not in daemon mode) and will let you know what happens. I tried putting 127.0.0.1 instead of localhost in the client's proxy field this time.

[tear]

Roger that. Thanks. And clients are also set up for port 8880? (sorry for asking the obvious, need to double check...)

Care to do a manual test on either of the machines?

Telnet to 127.0.0.1 8880, then type:
GET / HTTP/1.1
Host: darkswarm.org
then press Enter _twice_.

That should yield something along these lines:

Code: Select all

$ telnet 127.0.0.1 8880
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
GET / HTTP/1.1
Host: darkswarm.org

HTTP/1.1 200 OK
Date: Tue, 01 Mar 2011 22:02:14 GMT
Server: Apache/2.2.3 (CentOS)
Last-Modified: Sat, 30 Oct 2010 14:14:44 GMT
ETag: "5617b-19-493d6325bbd00"
Accept-Ranges: bytes
Content-Length: 25
Connection: close
Content-Type: text/html; charset=UTF-8

Intentionally left blank.Connection closed by foreign host.
$ 

Thanks,
tear