For some reason my main PC isn't downloading new work! I've not touched BOINC on it for ages, but noticed earlier today it hadn't uploaded for a while. It had uploaded by the time i got home from work today though, but hasn't downloaded any new work. It usually has ~16 jobs queued (E6420 C2D @ 3.2GHz, WinXP) but it's almost finished its last two jobs now, and isn't trying to download any more. I've just rebooted it to see if that makes a difference, but hasn't. Here's BM messages post reboot:

23/05/2007 18:36:16||Starting BOINC client version 5.8.16 for windows_intelx86
23/05/2007 18:36:16||log flags: task, file_xfer, sched_ops
23/05/2007 18:36:16||Libraries: libcurl/7.16.0 OpenSSL/0.9.8a zlib/1.2.3
23/05/2007 18:36:16||Executing as a daemon
23/05/2007 18:36:16||Data directory: E:BOINC
23/05/2007 18:36:16||BOINC is running as a service and as a non-system user.
23/05/2007 18:36:16||No application graphics will be available.
23/05/2007 18:36:16||Processor: 2 GenuineIntel Intel(R) Core(TM)2 CPU          6420  @ 2.13GHz [x86 Family 6 Model 15 Stepping 6] [fpu tsc pae nx sse sse2 mmx]
23/05/2007 18:36:16||Memory: 1022.48 MB physical, 2.40 GB virtual
23/05/2007 18:36:16||Disk: 1.95 GB total, 1.84 GB free
23/05/2007 18:36:16|rosetta@home|URL: https://boinc.bakerlab.org/rosetta/; Computer ID: 481396; location: work; project prefs: work
23/05/2007 18:36:16||General prefs: from rosetta@home (last modified 2006-10-28 01:11:37)
23/05/2007 18:36:16||Host location: work
23/05/2007 18:36:16||General prefs: using separate prefs for work
23/05/2007 18:36:29|rosetta@home|Restarting task CNTRL_01ABRELAX_SAVE_ALL_OUT_-1opd_-_filters_1737_5602_0 using rosetta version 564
23/05/2007 18:36:29|rosetta@home|Restarting task 1gidA_BOINC_MG_CHAINBREAK5_ALTSECSTRUCT_RNA_ABINITIO_RNA_CONTACT_RNA_LONG_RANGE_CONTACT_RNA_SASA-1gidA-_1735_48831_0 using rosetta version 564
23/05/2007 18:40:05|rosetta@home|Sending scheduler request: Requested by user
23/05/2007 18:40:05|rosetta@home|(not requesting new work or reporting completed tasks)
23/05/2007 18:40:10|rosetta@home|Scheduler RPC succeeded [server version 509]
23/05/2007 18:40:10|rosetta@home|Deferring communication for 4 min 2 sec
23/05/2007 18:40:10|rosetta@home|Reason: requested by project
23/05/2007 18:45:15|rosetta@home|Sending scheduler request: Requested by user
23/05/2007 18:45:15|rosetta@home|(not requesting new work or reporting completed tasks)
23/05/2007 18:45:20|rosetta@home|Scheduler RPC succeeded [server version 509]
23/05/2007 18:45:20|rosetta@home|Deferring communication for 4 min 2 sec
23/05/2007 18:45:20|rosetta@home|Reason: requested by project

Every time it contacts the server it says (not requesting new work or reporting completed tasks). I tried 'Retry Comms' and 'Update', but its not after new work - any ideas why?

P.S. No New Tasks isn't selected!

---

same here ??? ANY input...

---

as a temp measure i've changed the run time on my machine to 16hrs. If anyone wants to know how:

Stop BOINC (if it's running as a service you can use Run > cmd > net stop boinc)
Using notepad, edit BoincDiraccount_boinc.bakerlab.org_rosetta.xml
Increase the xxxxx value under the correct profile (work/home/school) here: <cpu_run_time>xxxxx</cpu_run_time>
Save the file
Restart BOINC (for service: net start boinc)

---

Here is one idea if you also crunch SETI. I see WARP does also crunch SETI, so this should be exactly the case for them.

I've been noticing the same on my machines, and it seems that the scheduler takes in to account suspended tasks now, when it did not previously do so. In my case, once I released all the tasks, and increased my cache preference, I was able to get more work.

I've also had problems with the transfers getting hung up, and I've found that suspending network traffic and enabling it again seems to reset the problem (this is done via the "activity" pulldown menu.

By changing your runtime preference, you may actually confuse BOINC further.

What is your General Preference for "connect every ... days"?

For reference, here's a link to the host you provided the messages from (host ID was in the startup messages).

---

Rosetta Moderator: Mod.Sense

We have been having random upload problems as well.....I don't know if this is another symptom of the same problem but it is usually rectified by stopping BOINC and doing a restart. Next time we'll try the suspension of nwk traffic option suggested by Mod.Sense....thanks for the tip....Cheers, Rog.

Here is one idea if you also crunch SETI. I see WARP does also crunch SETI, so this should be exactly the case for them.

I've been noticing the same on my machines, and it seems that the scheduler takes in to account suspended tasks now, when it did not previously do so. In my case, once I released all the tasks, and increased my cache preference, I was able to get more work.

I've also had problems with the transfers getting hung up, and I've found that suspending network traffic and enabling it again seems to reset the problem (this is done via the "activity" pulldown menu.

By changing your runtime preference, you may actually confuse BOINC further.

What is your General Preference for "connect every ... days"?

For reference, here's a link to the host you provided the messages from (host ID was in the startup messages).

Not running anything but rosetta, have rebooted with no effect, and 'connect every 2 days.

I am using Boincstats BAM though... i've just detatched from that and updated with no effect.

[edit] rebooted again and went to watch the footy and it's downloaded some jobs now :D

---