Page 1 of 2
130.237.232.140 seems to have a problem ...
Posted: Mon Mar 01, 2010 4:04 am
by Graeme
Trying to download a work packet ...
Code: Select all
[03:37:24] + Attempting to get work packet
[03:37:24] Passkey found
[03:37:24] - Will indicate memory of 1879 MB
[03:37:24] - Connecting to assignment server
[03:37:24] Connecting to htp://assign.stanford.edu:8080/
[03:37:28] Posted data.
[03:37:28] Initial: ED82; - Successful: assigned to (130.237.232.140).
[03:37:28] + News From Folding@Home: Welcome to Folding@Home
[03:37:28] Loaded queue successfully.
[03:37:28] Connecting to http://130.237.232.140:8080/
[03:37:29] Posted data.
[03:37:29] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[03:37:29] - Attempt #15 to get work failed, and no other work to do.
Waiting before retry.
Is there anything I can do at my end to get things going, or do I just need to "sit tight" and let the people at Stanford sort things out?
Re: 130.237.232.140 seems to have a problem ...
Posted: Mon Mar 01, 2010 4:31 am
by bruce
I'm not sure about the bad packet type error. Have you gotten that on each of the 15 download attempts? Do you have a proxy?
In your client configuration, do you have Small/Normal/Big set to Big? The News Blog says that there's a shortage of small WUs and I'm not sure there are all that many WUs for classic clients of any size. When the servers have to deal with a lot of clients looking for a few WUs, the assignment servers have to work really hard to try to sort everything out.
Re: 130.237.232.140 seems to have a problem ...
Posted: Mon Mar 01, 2010 4:58 am
by Graeme
bruce wrote:I'm not sure about the bad packet type error. Have you gotten that on each of the 15 download attempts? Do you have a proxy?
Attempts 2, 9, & 15 have had the "bad packet type" message; all the others had ended akin to ...
Code: Select all
[04:25:39] Posted data.
[04:25:39] Initial: 0000; - Receiving payload (expected size: 4300928)
[04:26:28] - Downloaded at ~85 kB/s
[04:26:28] - Averaged speed for that direction ~64 kB/s
[04:26:28] + Received work.
[04:26:28] - Attempt #16 to get work failed, and no other work to do.
Waiting before retry.
No proxy being used.
bruce wrote:In your client configuration, do you have Small/Normal/Big set to Big? The News Blog says that there's a shortage of small WUs and I'm not sure there are all that many WUs for classic clients of any size. When the servers have to deal with a lot of clients looking for a few WUs, the assignment servers have to work really hard to try to sort everything out.
Size is set for big (bigpackets=big). The only recent change to the config (have been folding on this VM for months) was to add a passkey after upgrading the folding client on Tuesday of last week, and I know it was still working OK then as it completed a few work packets during the 2nd half of the week. (I usually check each day to make sure things are still running OK, which I definitely did on Wednesday/Thursday/Friday last week as I wanted to make sure the new client was behaving OK prior to installing it on another VM and my main home PC. I upgraded the other VM on Thursday or Friday, and it is still working OK.)
Re: 130.237.232.140 seems to have a problem ...
Posted: Mon Mar 01, 2010 5:02 am
by Graeme
Hmm... just noticed that my other VM (which is busy folding) has -advmethods in its launch line, but this idle one doesn't ... think I'll add the -advmethods switch to this idle one and see if that makes a difference.
Re: 130.237.232.140 seems to have a problem ...
Posted: Mon Mar 01, 2010 5:10 am
by bruce
That was going to be my next suggestion. Adding -advmethods does give you a wider choice of assignments and it can be helpful when there's a shortage of certain classes of projects.
I've never seen these two messages together before and they seem contradictory.
[04:26:28] + Received work.
[04:26:28] - Attempt #16 to get work failed, and no other work to do.
Re: 130.237.232.140 seems to have a problem ...
Posted: Mon Mar 01, 2010 5:14 am
by Graeme
Nup, still going nowhere.
Re: 130.237.232.140 seems to have a problem ...
Posted: Mon Mar 01, 2010 5:48 am
by Wrish
Had 2 SMP clients both download A3's from that IP about half an hour ago, so I'd start looking at network/firewall/permission settings or perhaps reinstalling the FAH folder.
Code: Select all
[05:09:24] - Preparing to get new work unit...
[05:09:24] Cleaning up work directory
[05:09:24] + Attempting to get work packet
[05:09:24] Passkey found
[05:09:24] - Connecting to assignment server
[05:09:25] - Successful: assigned to (130.237.232.140).
[05:09:25] + News From Folding@Home: Welcome to Folding@Home
[05:09:25] Loaded queue successfully.
[05:09:31] + Closed connections
Code: Select all
[05:12:39] - Preparing to get new work unit...
[05:12:39] Cleaning up work directory
[05:12:39] + Attempting to get work packet
[05:12:39] Passkey found
[05:12:39] - Connecting to assignment server
[05:12:40] - Successful: assigned to (130.237.232.140).
[05:12:40] + News From Folding@Home: Welcome to Folding@Home
[05:12:40] Loaded queue successfully.
[05:12:47] + Closed connections
Re: 130.237.232.140 seems to have a problem ...
Posted: Mon Mar 01, 2010 6:18 am
by Graeme
Wrish wrote:Had 2 SMP clients both download A3's from that IP about half an hour ago, so I'd start looking at network/firewall/permission settings or perhaps reinstalling the FAH folder.
Code: Select all
[05:09:24] - Preparing to get new work unit...
[05:09:24] Cleaning up work directory
[05:09:24] + Attempting to get work packet
[05:09:24] Passkey found
[05:09:24] - Connecting to assignment server
[05:09:25] - Successful: assigned to (130.237.232.140).
[05:09:25] + News From Folding@Home: Welcome to Folding@Home
[05:09:25] Loaded queue successfully.
[05:09:31] + Closed connections
Code: Select all
[05:12:39] - Preparing to get new work unit...
[05:12:39] Cleaning up work directory
[05:12:39] + Attempting to get work packet
[05:12:39] Passkey found
[05:12:39] - Connecting to assignment server
[05:12:40] - Successful: assigned to (130.237.232.140).
[05:12:40] + News From Folding@Home: Welcome to Folding@Home
[05:12:40] Loaded queue successfully.
[05:12:47] + Closed connections
Your log snippets don't include work packet download - did that complete successfully?
Re: 130.237.232.140 seems to have a problem ...
Posted: Mon Mar 01, 2010 12:46 pm
by Wrish
Indeed both WU have uploaded by this morning. When I point my web browser to the IP, port 80 fails to connect, but port 8080 returns an "OK". It may be that 8080 is blocked by your ISP. What happens when you browse to the IP?
Re: 130.237.232.140 seems to have a problem ...
Posted: Mon Mar 01, 2010 10:19 pm
by Graeme
Nup, our ISP blocks nothing
... pointed browser at 130.237.232.140:8080 and received "OK" back.
Think I might "blow away" the fah client directory and set it up fresh ...
Re: 130.237.232.140 seems to have a problem ...
Posted: Tue Mar 02, 2010 9:00 am
by toTOW
Did you check your settings ? Do you accept Big WUs ? Are flags correctly set ? How much RAM do you report ?
Re: 130.237.232.140 seems to have a problem ...
Posted: Tue Mar 02, 2010 9:32 am
by Graeme
toTOW wrote:Did you check your settings ? Do you accept Big WUs ? Are flags correctly set ? How much RAM do you report ?
What/which flags are you refering to?
(For answers to your other 3 questions, read my 1st 2 posts in this thread.)
Re: 130.237.232.140 seems to have a problem ...
Posted: Tue Mar 02, 2010 9:37 am
by toTOW
I double checked, and it seems that you're getting assigned somewhere ... but the client fails to get work ... that sounds like a connection issue to me (transparent proxy or firewall that alters or drop packets).
Re: 130.237.232.140 seems to have a problem ...
Posted: Tue Mar 02, 2010 9:48 am
by Graeme
It uses exactly the same internet connection (and connection setup/config) as the other VM), so I think I'll go ahead with re-doing the F@H client install tomorrow if nothing further surfaces before then.
Re: 130.237.232.140 seems to have a problem ...
Posted: Tue Mar 02, 2010 10:04 pm
by Graeme
Deleted folding client directory (and contents), created a fresh folding directory and did the install & configure ... and now it is working.
Strange it broke, but now it is working ... so thanks for the input/assistance.