Page 1 of 2
assign2.stanford.edu:80
Posted: Sat Aug 08, 2009 1:18 pm
by mvnsnd
Anyone else having trouble getting work from this server? Our firewall blocks port 8080, but since mid day yesterday, I have not been able to get a work unit.
Here is some sample log:
Code: Select all
--- Opening Log file [August 8 12:58:57 UTC]
# Windows SMP Console Edition #################################################
###############################################################################
Folding@Home Client Version 6.24R3
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: C:\FAHSMP1
Executable: C:\FAHSMP1\FAH6_1.exe
Arguments: -smp -deino -verbosity 9
[12:58:57] - Ask before connecting: No
[12:58:57] - User name: JMS (Team 37336)
[12:58:57] - User ID: 4C10C24E72BE7ED3
[12:58:57] - Machine ID: 1
[12:58:57]
[12:58:57] Loaded queue successfully.
[12:58:57] - Preparing to get new work unit...
[12:58:57] - Autosending finished units... [August 8 12:58:57 UTC]
[12:58:57] Cleaning up work directory
[12:58:57] Trying to send all finished work units
[12:58:57] + No unsent completed units remaining.
[12:58:57] - Autosend completed
[12:58:57] + Attempting to get work packet
[12:58:57] - Will indicate memory of 3325 MB
[12:58:57] - Detect CPU. Vendor: GenuineIntel, Family: 6, Model: 7, Stepping: 6
[12:58:57] - Connecting to assignment server
[12:58:57] Connecting to http://assign.stanford.edu:8080/
[12:59:18] - Couldn't send HTTP request to server
[12:59:18] + Could not connect to Assignment Server
[12:59:18] Connecting to http://assign2.stanford.edu:80/
[12:59:19] Posted data.
[12:59:19] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[12:59:19] + Couldn't get work instructions.
[12:59:19] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[12:59:37] + Attempting to get work packet
[12:59:37] - Will indicate memory of 3325 MB
[12:59:37] - Connecting to assignment server
[12:59:37] Connecting to http://assign.stanford.edu:8080/
[12:59:58] - Couldn't send HTTP request to server
[12:59:58] + Could not connect to Assignment Server
[12:59:58] Connecting to http://assign2.stanford.edu:80/
[12:59:58] Posted data.
[12:59:58] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[12:59:58] + Couldn't get work instructions.
[12:59:58] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[13:00:15] + Attempting to get work packet
[13:00:15] - Will indicate memory of 3325 MB
[13:00:15] - Connecting to assignment server
[13:00:15] Connecting to http://assign.stanford.edu:8080/
[13:00:36] - Couldn't send HTTP request to server
[13:00:36] + Could not connect to Assignment Server
[13:00:36] Connecting to http://assign2.stanford.edu:80/
[13:00:37] Posted data.
[13:00:37] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[13:00:37] + Couldn't get work instructions.
[13:00:37] - Attempt #3 to get work failed, and no other work to do.
Waiting before retry.
[13:01:03] + Attempting to get work packet
[13:01:03] - Will indicate memory of 3325 MB
[13:01:03] - Connecting to assignment server
[13:01:03] Connecting to http://assign.stanford.edu:8080/
[13:01:24] - Couldn't send HTTP request to server
[13:01:24] + Could not connect to Assignment Server
[13:01:24] Connecting to http://assign2.stanford.edu:80/
[13:01:24] Posted data.
[13:01:24] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[13:01:24] + Couldn't get work instructions.
[13:01:24] - Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[13:02:15] + Attempting to get work packet
[13:02:15] - Will indicate memory of 3325 MB
[13:02:15] - Connecting to assignment server
[13:02:15] Connecting to http://assign.stanford.edu:8080/
[13:02:36] - Couldn't send HTTP request to server
[13:02:36] + Could not connect to Assignment Server
[13:02:36] Connecting to http://assign2.stanford.edu:80/
[13:02:36] Posted data.
[13:02:36] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[13:02:36] + Couldn't get work instructions.
[13:02:36] - Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
[13:04:11] + Attempting to get work packet
[13:04:11] - Will indicate memory of 3325 MB
[13:04:11] - Connecting to assignment server
[13:04:11] Connecting to http://assign.stanford.edu:8080/
[13:04:32] - Couldn't send HTTP request to server
[13:04:32] + Could not connect to Assignment Server
[13:04:32] Connecting to http://assign2.stanford.edu:80/
[13:04:32] Posted data.
[13:04:32] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[13:04:32] + Couldn't get work instructions.
[13:04:32] - Attempt #6 to get work failed, and no other work to do.
Waiting before retry.
[13:07:16] + Attempting to get work packet
[13:07:16] - Will indicate memory of 3325 MB
[13:07:16] - Connecting to assignment server
[13:07:16] Connecting to http://assign.stanford.edu:8080/
[13:07:37] - Couldn't send HTTP request to server
[13:07:37] + Could not connect to Assignment Server
[13:07:37] Connecting to http://assign2.stanford.edu:80/
[13:07:38] Posted data.
[13:07:38] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[13:07:38] + Couldn't get work instructions.
[13:07:38] - Attempt #7 to get work failed, and no other work to do.
Waiting before retry.
[13:13:12] + Attempting to get work packet
[13:13:12] - Will indicate memory of 3325 MB
[13:13:12] - Connecting to assignment server
[13:13:12] Connecting to http://assign.stanford.edu:8080/
[13:13:33] - Couldn't send HTTP request to server
[13:13:33] + Could not connect to Assignment Server
[13:13:33] Connecting to http://assign2.stanford.edu:80/
[13:13:34] Posted data.
[13:13:34] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[13:13:34] + Couldn't get work instructions.
[13:13:34] - Attempt #8 to get work failed, and no other work to do.
Waiting before retry.
I have restarted the clients a couple of times with the same behaviour.
Thanks,
Jeff
Re: assign2.stanford.edu:80
Posted: Sat Aug 08, 2009 3:56 pm
by 314159
Total reliance on port :80 is an exercise in futility as far as this project is concerned, IMHO and not having tried it.
Unblock (or have someone else do it) :8080 as soon as you can.
I am not even certain that assign2.stanford.edu:80 is active unless the primary AS is down (a RARE occurrence).
:8080 might be/(often is) required to return "certain" completed WUs to their Work Server on a prompt basis.
Re: assign2.stanford.edu:80
Posted: Sun Aug 09, 2009 11:54 am
by mvnsnd
John,
Thanks for your reply. I will ask the IT guys if they can open port 8080, at least for me and these clients.
I'm now up to six clients waiting for work. Can anyone shed some light on what might have changed? I have been running these clients for quite a while with no issues and only using port 80. I'll try to take a look on my end on Monday.
Re: assign2.stanford.edu:80
Posted: Sun Aug 09, 2009 11:57 am
by MtM
'Initial: 0000; + No appropriate work server was available; will try again in a bit.'
Looks just like an AS logic issue not an connection issue.
Re: assign2.stanford.edu:80
Posted: Sun Aug 09, 2009 12:43 pm
by 314159
That was my initial thought but mvnsnd is running the WIN SMP client.
I really think that he needs to get on the primary AS, which I believe that your post also suggests.
My experience is that when assign2 kicks in for the typical folder, i.e. Primary AS goes down, all "heck" breaks loose.
Bet that we have another case of an I.T. guy screwing around with a proxy or whatever.
It never seems to end.
Re: assign2.stanford.edu:80
Posted: Sun Aug 09, 2009 12:52 pm
by MtM
How can he then claim to be running with 8080 closed all the time, and the issues just started? I can remember from Bruce and 7im saying the same as you're saying, that you need port 8080 but I also remember that's mostly for what you also touched on, the return of work units when their primary collection server is not available.
Uhm, I'm really not sure tbh.
Edit: I mean to say, I think the server logic was upgraded some time back, so people should be able to run with only port 80, and that his issue probably was a server glitch where assign2 couldn't find a work server which was reachable under 80 so it returned the 'no work available' message to the client.
Someone with more knowledge about the fah servers would come in really handy right now
Re: assign2.stanford.edu:80
Posted: Sun Aug 09, 2009 1:21 pm
by 314159
I can summarize my thoughts easily.
Each and every experience that I have had when assign2 kicked in has resulted in problems.
I cringe at the mere mention of the darned thing.
I know that it is needed and am, at times, thankful that it exists -
BUT I would not want to rely upon it fulltime.
You're a
very experienced folder MtM.
As to the :80 and :8080 issues, take a peek at the serverstats page on a regular basis over a few day period.
I may have you convinced shortly.
Fold On!
Re: assign2.stanford.edu:80
Posted: Sun Aug 09, 2009 1:47 pm
by MtM
Hey the servers have been so much more stable compared to a year back I really can't complain
I'm not a that experienced folder, I treid doing my share of wu's but I'm known for hitting dry spells now and then, not to mention not having the budget to really buy f@h dedicated hardware. But, I do try to be an active participant which involves reading these forums quite a bit. If I had a better memory I'm quite sure I would be able to reiterate the exact official answer as I remember being active in simular threads in the past on more then one occasion
Which is why I said I think it's an AS logic issue, a conclusion also made more logical since OP has only recently had the issue. Also, when saying logic issue, it could very well be that the server was right, and at the time of request there was no work server reachable under port 8080 so it's not per se a logic flaw.
Re: assign2.stanford.edu:80
Posted: Sun Aug 09, 2009 5:53 pm
by 314159
We are pretty much saying the same thing, I think.
assign2, during the last time that the primary AS was down (quite a while ago), was making assignments without consideration of the "WEIGHT" parameters that the P.G. had entered for each WS. I do not think that assign2 is updated that often, but may be wrong.
(I have between 35 and 45 dedicated machines running at any one time, so I got "killed" when this happened)
<---sad not mad
Anyway, I would classify this as a "logic issue" as you do.
I have NO issues regarding the WS's. They are tremendously improved over days of old!
I have NO issues regarding the primary AS. It is tremendously improved over days of old!
I would give the CS's a grade of C minus but understand the issue and have no problems waiting for autosend.
P.S. Your Forum participation is greatly appreciated! THANK YOU!
Re: assign2.stanford.edu:80
Posted: Sun Aug 09, 2009 6:39 pm
by MtM
I only want to say that this project benefits allot more from people like you then it does from people like me. Yes, giving advice is a rewarding endavour on it's own, but I have allot off appriciation and admiration of the people able to do as much as you do for the science. Thank you, not thank me
Re: assign2.stanford.edu:80
Posted: Sun Aug 09, 2009 6:41 pm
by mvnsnd
Which is why I said I think it's an AS logic issue, a conclusion also made more logical since OP has only recently had the issue. Also, when saying logic issue, it could very well be that the server was right, and at the time of request there was no work server reachable under port 8080 so it's not per se a logic flaw.
I would have to agree with this for two reasons:
1. It doesn't look like others are having this issue because they are getting work from assign.stanford.edu :8080, and I only started with this issue mid-Friday.
2. One of my clients is on a laptop and has gotten two consecutive WU while on my home network, but was having issues while on the work network. It connected via assign.stanford.edu :8080 while on the home network.
So if Assign2 was assigning properly, it should have dished out WU's.
I'll still ask the IT guys if I can get port 8080 opened. I have no idea why it is restricted.
I'm not real versed in the communications of the clients, but this brings me to ask why doesn't assign.stanford.edu work on port 80 as well as 8080 before going to assign2.stanford.edu:8080?
Regards,
Jeff
Re: assign2.stanford.edu:80
Posted: Mon Aug 10, 2009 7:28 am
by bruce
314159 wrote:assign2, during the last time that the primary AS was down (quite a while ago), was making assignments without consideration of the "WEIGHT" parameters that the P.G. had entered for each WS. I do not think that assign2 is updated that often, but may be wrong.
Anyway, I would classify this as a "logic issue" as you do.
I agree that opening port 8080 is the best approach but I'm not as negative about AS2 as 314159 is.
First, the code on both AS and AS2 is essentially the same and they both collect data from each of the work servers that you see in serverstat. I don't see any differences in the update frequency. This was the first time I heard about the problem with WEIGHT on AS2. If it was reported here on the foldingforum, I missed it.
Second, an additional step was required on each Work Server. Note the column with the heading "80" Sometimes you will see a red "0" in that column meaning that the server does have work that might be assigned but AS2 isn't talking to it. With the OLD server code, this was a bad thing for those who needed to user port 80.
Lots of things have changed in the new server code that that could be one of them. Details like that are still being worked out and the heuristic understandings that we've developed may no longer apply.
Third, if you're only evaluating AS2 for cases when the primary AS has failed, you're getting a biased perspective. If AS2 fails, there's no comparable condition when all of the people who are normally serviced by AS2 are redirected to the primary AS -- they're SOL -- so AS never handles the entire load.
Re: assign2.stanford.edu:80
Posted: Mon Aug 10, 2009 12:19 pm
by martiou
I have the same problem since "August 7 13:54:08 UTC" at work.
Port 8080 is blocked and I can't do anything to change it.
I have 3 clients waiting for WU, 1 SMP linux, 1 linux and 1 Windows.
I will have 1 more linux waiting for WU this afternoon.
Servers who gave me the last WUs seem OK (171.65.103.160 and 171.64.65.56) with WUs available.
So I don't understand what is happening.
Edit : port 8080 and not 80
Re: assign2.stanford.edu:80
Posted: Mon Aug 10, 2009 2:10 pm
by mvnsnd
I just got port 8080 opened and WU's are coming through. We'll see how long I can keep that going.
Thanks for everyone's input.
Regards,
Jeff
Re: assign2.stanford.edu:80
Posted: Mon Aug 10, 2009 3:38 pm
by 314159
Hmm,
May I ask what you did to get :8080 opened (for future reference)?
THANKS!