Folding Forum

Using CPU client 6.20 here, with -verbosity 9 flag enabled. It stopped assigning WUs over a day ago. I did all the preliminary checks as instructed. What is up (or down, as the case may be) with this?

Thanks.

[17:39:27] + Attempting to get work packet
[17:39:27] - Will indicate memory of 2046 MB
[17:39:27] - Connecting to assignment server
[17:39:27] Connecting to http://assign.stanford.edu:8080/
[17:39:28] - Couldn't send HTTP request to server
[17:39:28] + Could not connect to Assignment Server
[17:39:28] Connecting to http://assign2.stanford.edu:80/
[17:39:29] - Couldn't send HTTP request to server
[17:39:29] + Could not connect to Assignment Server 2
[17:39:29] + Couldn't get work instructions.
[17:39:29] - Attempt #11 to get work failed, and no other work to do.
Waiting before retry.

This looks like a firewall or AV software kicked in and starting blocking all traffic.

Please also post more of the log file, starting with the ############### startup section. Thanks.

Thanks 7im:

Sorry, I've forgotten how to post a logfile in a scrolling window:

###

Launch directory: C:\Documents and Settings\joseph\Application Data\Folding@home-x86
Arguments: -verbosity 9

[18:39:44] - Ask before connecting: No
[18:39:44] - User name: joe53 (Team 80856)
[18:39:44] - User ID: 14E6E4BC48F7BF04
[18:39:44] - Machine ID: 1
[18:39:44]
[18:39:44] Loaded queue successfully.
[18:39:44] Initialization complete
[18:39:44] - Preparing to get new work unit...
[18:39:44] + Attempting to get work packet
[18:39:44] - Autosending finished units... [September 19 18:39:44 UTC]
[18:39:44] Trying to send all finished work units
[18:39:44] + No unsent completed units remaining.
[18:39:44] - Autosend completed
[18:39:44] - Will indicate memory of 2046 MB
[18:39:44] - Detect CPU. Vendor: GenuineIntel, Family: 15, Model: 4, Stepping: 4
[18:39:44] - Connecting to assignment server
[18:39:44] Connecting to http://assign.stanford.edu:8080/
[18:39:44] - Couldn't send HTTP request to server
[18:39:44] + Could not connect to Assignment Server
[18:39:44] Connecting to http://assign2.stanford.edu:80/
[18:39:45] - Couldn't send HTTP request to server
[18:39:45] + Could not connect to Assignment Server 2
[18:39:45] + Couldn't get work instructions.
[18:39:45] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.

I don't see this as being blocked by my Outpost Pro firewall, nor my ESET NOD32 AV; in both I have excluded the path to my Folding@home.exe.

I could be wrong, but this started suddenly. I have used Outpost and NOD32 for years now with no conflicts with F@H.

Thanks for the prompt reply.

What results did you get when doing this...

... try opening these sites in your browser
1) F@h CPU Clients (Classic, SMP2) -> http://assign.stanford.edu:8080/
2) F@h CPU Clients (Classic, SMP2) -> http://assign2.stanford.edu:80/


Make sure the folder containing the fah client is excluded from AV, and all .exes are include in FW (client and fahcores).

I could open both those sites in my IE8 browser; both opened to a page that just said "OK".

AFAIK all these F@H folders and exe's are excluded from my AV, and included in my FW. In any event, I have disabled both my AV (NOD32 v.5x) and my software FW (Outpost Pro 7.5) and I still get no connection.

I uninstalled F@H via my add/remove in control panel, and re-installed it, to no effect. I'm running out of ideas here. (Should I get a newer version?).

I should add that I'm having no other problems with my browsers or internet connections. My broadband internet connection speeds remain as robust as ever (18/1.0 Mbps, as per Speedtest.net).

Finally, I note I have no F@H service loading at startup with this CPU 6.20 client. Should I? (I could have sworn I once did, but maybe I'm confusing this with one of my other clients/operating systems).

No service unless you specifically installed it that way.

Personally, I like the v6.34 client, works well as either CPU or SMP, but it is console version only.

I also like the new V7 beta client.

7im wrote: Personally, I like the v6.34 client, works well as either CPU or SMP, but it is console version only.
I also like the new V7 beta client.

7im:

This is a 2005 Dell Dimension 9100 desktop with the following specs:

- Number of CPU(s): One Physical Processor / 2 Cores / 2 Logical Processors
- CPU Type: DualCore Intel Pentium D 830, 3000 MHz (15 x 200) with Hyper-Threading technology
- XP Pro/sp3

Will it even support v6.34 console or v7 beta client?

It is my workhorse desktop for work, and is still a fairly powerful machine. Until the other day, it was only generating maybe 100-200 ppd with the classic client running 24/7. I have recently purchased a new i7-2600 (3.4GHz) system that gets about 18,000 ppd with the 6.34 console, so I guess this is small potatoes by comparison.

Still, it irritates that a client that has worked so well and contributed for 3 years has suddenly gone belly-up.

A dual core Pentium should still be sufficient to run either two uniprocessor slots in V7 or a single SMP slot. I'd think the same would be true for the 6.34 console. There may be a temporary shortage of a specific type of WUs, though.

What she said.

Give the new V7 beta a try... they just released a newer version a day or two ago.

And there is a pretty good install guide for V7. http://folding.stanford.edu/English/WinGuide

(note: some of the screen shots have changed slightly because of the new release)

Thank you, gwildperson and 7im both for that feedback!

I'm glad to say I found the source of my my connection problem with v6.20 client. As you suspected, 7im, it was my NOD32 AV. I upgraded to its new v5.x about a week ago, and had just assumed it would save all my settings.

Today I had to drill far down into NOD's Setup> Advanced setup>Web and email>Protocol filtering>Web and email clients>Excluded applications, and put a check next to the Folding@home.exe. Bingo! Instant connection restored.

I'm not sure why it took several days for NOD32 to block my client, or why it objected at all. None of my other applications were interfered with, and none were excluded from protocol filtering, but there it is. My logfile does indicate that FahCore_a4.exe could not be found, and was either missing or corrupted. It succesfully downloaded a new copy.

Hopefully this info will help others in the same boat.

If I remain problem-free for a few days, I will give the 6.34 console a shot, since I'm already familiar with its setup and operation, at least in Win 7. Then maybe the V7 beta. (Baby steps ...)

Thanks again, I'm much obliged!

Great news!

We have several topics about NOD32 blocking FAH in the past (as do a few others as well). They seem to keep finding new ways to do it again.

joe53 wrote:Thank you, gwildperson and 7im both for that feedback!

I'm glad to say I found the source of my my connection problem with v6.20 client. As you suspected, 7im, it was my NOD32 AV. I upgraded to its new v5.x about a week ago, and had just assumed it would save all my settings.

Today I had to drill far down into NOD's Setup> Advanced setup>Web and email>Protocol filtering>Web and email clients>Excluded applications, and put a check next to the Folding@home.exe. Bingo! Instant connection restored.

I'm not sure why it took several days for NOD32 to block my client, or why it objected at all. None of my other applications were interfered with, and none were excluded from protocol filtering, but there it is. My logfile does indicate that FahCore_a4.exe could not be found, and was either missing or corrupted. It succesfully downloaded a new copy.

Hopefully this info will help others in the same boat.

If I remain problem-free for a few days, I will give the 6.34 console a shot, since I'm already familiar with its setup and operation, at least in Win 7. Then maybe the V7 beta. (Baby steps ...)

Thanks again, I'm much obliged!

thank you.....kinda same software: outpost and the new shining NOD32 version. At a certain moment i disabled all protection within NOD32 and even that didn't help. You have indeed to exclude it, FFS
i m still using the 6.29

v6.29 SMP client isn't fully supported any more. Please upgrade to v6.34.