application/octet-stream - is this normal?

[anko1]

This is the second time I've noticed this. My NVidia GPU client can't pick up a WU

Code: Select all

[04:39:10] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.
[04:44:34] + Attempting to get work packet
[04:44:34] - Will indicate memory of 3326 MB
[04:44:34] - Connecting to assignment server
[04:44:34] Connecting to http://assign-GPU.stanford.edu:8080/
[04:44:55] - Couldn't send HTTP request to server
[04:44:55] + Could not connect to Assignment Server
[04:44:55] Connecting to http://assign-GPU.stanford.edu:80/
[04:45:16] - Couldn't send HTTP request to server
[04:45:16] + Could not connect to Assignment Server 2
[04:45:16] + Couldn't get work instructions.
[04:45:16] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.
[04:55:57] + Attempting to get work packet
[04:55:57] - Will indicate memory of 3326 MB
[04:55:57] - Connecting to assignment server
[04:55:57] Connecting to http://assign-GPU.stanford.edu:8080/
[04:56:18] - Couldn't send HTTP request to server
[04:56:18] + Could not connect to Assignment Server
[04:56:18] Connecting to http://assign-GPU.stanford.edu:80/
[04:56:39] - Couldn't send HTTP request to server
[04:56:39] + Could not connect to Assignment Server 2
[04:56:39] + Couldn't get work instructions.
[04:56:39] - Attempt #9  to get work failed, and no other work to do.
Waiting before retry.

and when I enter 171.67.108.201 into my browser to see if I can get the OK, I get a message from Firefox saying that this is an application/octet-stream, and what would I like to do with this file. Is this normal? I got the server address from http://fah-web.stanford.edu/localinfo/contact.GPU.html

PS - I'm getting an OK on other server addresses.

PS - As of 9/1 5:18 got a WU.

[P5-133XL]

Generally, on an established folding setup, it means the server that the client is trying to get its WU from is either offline or too busy to service the clients request. There is nothing the user can do to help, and if you wait it out Stanford will resolve the server problem and the client will then continue working normally.

[toTOW]

Getting a file from a server is also a good answer : if you save this file on your drive and open it with a text editor, you'll see the OK.

It's just content encoding that has been modified from text to binary to better work in some situations.

[anko1]

P5 - Thanks for your response. I was just checking to make sure that the problem wasn't a connection issue on my end.

toTOW - thanks for the explanation. Now I know it's normal; I thought maybe it might be a clue to a problem.

Angela