Hi all!
Last week my C2D, which is running with BOINCpe, started to get only one WU per request, although much more work is requested and I did not change the preferences. There are two projects attached: Pirates@Home and PrimeGrid.
Here's a part from the logfile:

06.08.2007 10:03:48|PrimeGrid|Sending scheduler request: To fetch work
06.08.2007 10:03:48|PrimeGrid|Requesting 325679 seconds of new work
06.08.2007 10:03:53|PrimeGrid|Scheduler RPC succeeded [server version 511]
06.08.2007 10:03:53|PrimeGrid|Deferring communication for 7 sec
06.08.2007 10:03:53|PrimeGrid|Reason: requested by project
06.08.2007 10:03:55|PrimeGrid|[file_xfer] Started download of file llrTPS_7055979
06.08.2007 10:03:56|PrimeGrid|[file_xfer] Finished download of file llrTPS_7055979
06.08.2007 10:03:56|PrimeGrid|[file_xfer] Throughput 425 bytes/sec
06.08.2007 10:04:03|PrimeGrid|Sending scheduler request: To fetch work
06.08.2007 10:04:03|PrimeGrid|Requesting 325041 seconds of new work
06.08.2007 10:04:08|PrimeGrid|Scheduler RPC succeeded [server version 511]
06.08.2007 10:04:08|PrimeGrid|Deferring communication for 7 sec
06.08.2007 10:04:08|PrimeGrid|Reason: requested by project
06.08.2007 10:04:10|PrimeGrid|[file_xfer] Started download of file llrTPS_7054620
06.08.2007 10:04:11|PrimeGrid|[file_xfer] Finished download of file llrTPS_7054620
06.08.2007 10:04:11|PrimeGrid|[file_xfer] Throughput 512 bytes/sec

...and so on...
At that time I was using BOINC 5.8.15, I updated to 5.10.13 at first, now 5.10.18, but still the same behaviour (my other host's are running fine and getting lots of PG-WUs per request). I also tried different prefs, but nothing changed.

Today I discovered <connected_frac>-1.000000</connected_frac> in the client_state.xml. Because this is the only difference form my other host's (there it is 0), I think that this is the reason.

I tried to manually set it to different values from 0 to 1 (client closed before that), but after restarting the client, it was -1 again.

---

The connected frac should have nothing to do with anything. It is suposed to measure how often you are connected to the internet, but it has never worked properly on *nix and is not reliable on windows. So as far as I know it is ignored. The other time stats may have a bearing on your problem though.

---

BOINC WIKI

BOINCing since 2002/12/8

The connected frac should have nothing to do with anything. It is suposed to measure how often you are connected to the internet, but it has never worked properly on *nix and is not reliable on windows. So as far as I know it is ignored. The other time stats may have a bearing on your problem though.

The other time stats are normal, and since this is the only difference to my other hosts, I thought this might be the problem.
OK, this host is running WinXP on a RAM Disk, while the other ones are on Win2k, but before last week it worked well...

I will test another project, as soon as I can access it again, to see if it is a problem with the host and/or PrimeGrid's server-update.

---

I will test another project, as soon as I can access it again, to see if it is a problem with the host and/or PrimeGrid's server-update.

Works well with ABC@home, so it is a PrimeGrid problem. I'll ask over there again.

---