Page 1 of 1

129.74.85.15 - can't send or receive WU

Posted: Tue Aug 24, 2010 7:31 pm
by geneabug
For the past 4 days, I haven't been able to submit the WU I completed, nor can I download a new one. I'm including a portion of the log below:

Code: Select all

[14:07:29] Loaded queue successfully.
[14:07:29] Deleting incompletely fetched item (4) from queue position #8
[14:07:29] Initialization complete
[14:07:29] - Preparing to get new work unit...
[14:07:29] Project: 10016 (Run 2783, Clone 0, Gen 20)


[14:07:29] + Attempting to send results [August 24 14:07:29 UTC]
[14:07:29] + Attempting to get work packet
[14:07:29] - Connecting to assignment server
[14:07:50] - Couldn't send HTTP request to server
[14:07:50] + Could not connect to Assignment Server
[14:07:50] - Couldn't send HTTP request to server
[14:07:50] + Could not connect to Work Server (results)
[14:07:50]     (129.74.85.15:8080)
[14:07:50] + Retrying using alternative port
[14:07:51] + No appropriate work server was available; will try again in a bit.
[14:07:51] + Couldn't get work instructions.
[14:07:51] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[14:07:59] - Couldn't send HTTP request to server
[14:07:59] + Could not connect to Work Server (results)
[14:07:59]     (129.74.85.15:80)
[14:07:59] - Error: Could not transmit unit 07 (completed August 20) to work server.


[14:07:59] + Attempting to send results [August 24 14:07:59 UTC]
[14:08:11] + Attempting to get work packet
[14:08:11] - Connecting to assignment server
[14:08:20] - Couldn't send HTTP request to server
[14:08:20] + Could not connect to Work Server (results)
[14:08:20]     (129.74.85.16:8080)
[14:08:20] + Retrying using alternative port
[14:08:29] - Couldn't send HTTP request to server
[14:08:29] + Could not connect to Work Server (results)
[14:08:29]     (129.74.85.16:80)
[14:08:29]   Could not transmit unit 07 to Collection server; keeping in queue.
[14:08:32] - Couldn't send HTTP request to server
[14:08:32] + Could not connect to Assignment Server
[14:08:32] + No appropriate work server was available; will try again in a bit.
[14:08:32] + Couldn't get work instructions.
[14:08:32] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[14:08:43] + Attempting to get work packet
[14:08:43] - Connecting to assignment server
[14:09:05] - Couldn't send HTTP request to server
[14:09:05] + Could not connect to Assignment Server
[14:09:05] + No appropriate work server was available; will try again in a bit.
[14:09:05] + Couldn't get work instructions.
[14:09:05] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Slot 07 *Done     
Project: 10016 (Run 2783, Clone 0, Gen 20), Core: b4
Work server: 129.74.85.15:8080
Collection server: 129.74.85.16
Download date: August 16 04:31:02
Finished date: August 20 11:40:36
Failed uploads: 18

PF: 0.852169 based on last 4 slot(s)
[14:21:24] + Attempting to get work packet
[14:21:24] - Connecting to assignment server
[14:21:45] - Couldn't send HTTP request to server
[14:21:45] + Could not connect to Assignment Server
[14:21:46] + No appropriate work server was available; will try again in a bit.
[14:21:46] + Couldn't get work instructions.
[14:21:46] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

[17:14:32] + Attempting to get work packet
[17:14:32] - Connecting to assignment server
[17:14:53] - Couldn't send HTTP request to server
[17:14:53] + Could not connect to Assignment Server
[17:14:53] + No appropriate work server was available; will try again in a bit.
[17:14:53] + Couldn't get work instructions.
[17:14:53] - Attempt #13  to get work failed, and no other work to do.
Waiting before retry.
[18:02:59] + Attempting to get work packet
[18:02:59] - Connecting to assignment server
[18:03:20] - Couldn't send HTTP request to server
[18:03:20] + Could not connect to Assignment Server
[18:03:21] + No appropriate work server was available; will try again in a bit.
[18:03:21] + Couldn't get work instructions.
[18:03:21] - Attempt #14  to get work failed, and no other work to do.
Waiting before retry.
[18:51:34] + Attempting to get work packet
[18:51:34] - Connecting to assignment server
[18:51:55] - Couldn't send HTTP request to server
[18:51:55] + Could not connect to Assignment Server
[18:51:56] + No appropriate work server was available; will try again in a bit.
[18:51:56] + Couldn't get work instructions.
[18:51:56] - Attempt #15  to get work failed, and no other work to do.
Waiting before retry.
I don't think my firewall is blocking the server. (I had that problem earlier.) Any ideas as to what could be causing the problem?

Re: 129.74.85.15 - can't send or receive WU

Posted: Tue Aug 24, 2010 8:49 pm
by 7im

Re: 129.74.85.15 - can't send or receive WU

Posted: Tue Aug 24, 2010 9:27 pm
by geneabug
I'm using the system tray version, so that's never come up.

Re: 129.74.85.15 - can't send or receive WU

Posted: Wed Aug 25, 2010 12:44 am
by 7im
Click on them. ;)

When your web browser application opens, does it then display a blank white page with "OK" in the top left corner or something else?

Re: 129.74.85.15 - can't send or receive WU

Posted: Wed Aug 25, 2010 4:41 am
by geneabug
I'm sorry, I thought you were talking about a screen within the program. I haven't been getting much sleep lately, so I just wasn't thinking clearly.

Anyway, I only got the OK screen at 171.64.65.121. 129.74.85.15 and 129.74.85.16 came back with a completely blank white screen. The other 2 simply time out.

Re: 129.74.85.15 - can't send or receive WU

Posted: Wed Aug 25, 2010 5:08 am
by bruce
From here, both http://129.74.85.15:8080/ and http://129.74.85.16:8080/ get the "OK" message, so I believe that it's possible to upload/download to those servers -- but you'll need to be sure that your firewall doesn't block port 8080.

Both http://129.74.85.15/ and http://129.74.85.16/ fail from here, so apparently the default http port 80 doesn't work on those servers at this time.

How about http://assign.stanford.edu:8080/ and http://assign2.stanford.edu/? Both work from here, but if it's your firewall, the first one will fail and the second one will succeed. If my assumptions are correct, your client should be redirected to some other sever for downloads, though I can't explain how you got those WUs in the first place or how you're going to return them without opening port 8080 in your firewall.

Re: 129.74.85.15 - can't send or receive WU

Posted: Thu Aug 26, 2010 2:55 am
by geneabug
I tried both of those links and got the "OK" message from both. So then I tried both http://129.74.85.15:8080 and http://129.74.85.16:8080 again, and they came back "OK" as well. At least that's when I had my laptop at the local library. But when I'm at my apartment, port 8080 clonks out. So I'm wondering if there's a problem with my internet connection. At least my client eventually managed to receive a WU from 129.74.85.15:8080 before I left the library; otherwise, I'd probably still be in the same boat. However, it still couldn't send the WU it had already finished. Any thoughts?

Re: 129.74.85.15 - can't send or receive WU

Posted: Thu Aug 26, 2010 5:30 am
by 7im
As you suspected in your original post, it looks like you have some kind of AV or FW software/hardware blocking ports.

And getting WUs from a work server on port 8080 at the library obviously won't upload very easily from home if home is blocking port 8080. ;)

Re: 129.74.85.15 - can't send or receive WU

Posted: Mon Aug 30, 2010 6:45 pm
by geneabug
I finally figured out what the problem was: it was my router's firewall that was blocking the port. Once my brother got that straightened out, my client's back up and running again. :D

Re: 129.74.85.15 - can't send or receive WU

Posted: Sun Sep 05, 2010 4:51 am
by lanbrown
Now the server cannot be contacted at all. The server status page just shows no response. So the server has either crashed or has died. Can someone check to see if it needs to be on life support or not?
http://fah-web.stanford.edu/logs/129.74.85.15.log.html

Re: 129.74.85.15 - can't send or receive WU

Posted: Sun Sep 05, 2010 3:07 pm
by DrSpalding
I am seeing no luck in uploading to 129.74.85.15:8080 since yesterday around 13:20 PDT. http://129.74.85.15/ and http://129.74.85.15:8080/ both are non-responsive and time out. It also has tried 129.74.85.16:80 and 129.74.85.16:8080 with the safe results. From rDNS, these two servers appear to have the names:
fahnd03.crc.nd.edu and fahnd04.crc.nd.edu and are at the University of Notre Dame.

Re: 129.74.85.15 - can't send or receive WU

Posted: Sun Sep 05, 2010 6:46 pm
by PeterA
I'm having the same problem. Server status page has it down since 6:50AM PDT Sat. Someone needs to give it a kick. ;)

Collection server not having any luck either. :(

Code: Select all

[18:35:34] Project: 10022 (Run 1323, Clone 0, Gen 18)
...
[18:35:59] - Couldn't send HTTP request to server
[18:35:59] + Could not connect to Work Server (results)
[18:35:59]     (129.74.85.15:8080)
[18:35:59] + Retrying using alternative port
[18:36:24] - Couldn't send HTTP request to server
[18:36:24] + Could not connect to Work Server (results)
[18:36:24]     (129.74.85.15:80)
[18:36:24] - Error: Could not transmit unit 02 (completed September 4) to work server.
[18:36:24] - Read packet limit of 540015616... Set to 524286976.


[18:36:24] + Attempting to send results [September 5 18:36:24 UTC]
[18:36:35] + Running on battery power. Pausing work until computer is plugged in.
[18:38:03] - Couldn't send HTTP request to server
[18:38:03] + Could not connect to Work Server (results)
[18:38:03]     (129.74.85.16:8080)
[18:38:03] + Retrying using alternative port
[18:38:16] - Couldn't send HTTP request to server
[18:38:16] + Could not connect to Work Server (results)
[18:38:16]     (129.74.85.16:80)
[18:38:16]   Could not transmit unit 02 to Collection server; keeping in queue.

Re: 129.74.85.15 - can't send or receive WU

Posted: Mon Sep 06, 2010 12:31 am
by 7im
I asked the researcher responsible for these servers to look in to it (as note in the 129.74.85.16 thread ). Being a holiday weekend, it could take a while.

Re: 129.74.85.15 - can't send or receive WU

Posted: Mon Sep 06, 2010 6:38 pm
by DrSpalding
It appears that the 129.74.85.15 server is back up. The machine successfully uploaded at 00:04 UTC on 6 Sept. That is 17:04 PDT on 5 Sept.