Mac Pro 4,1 OS 10.6.8
boinc 7.0.18 x86 widget 2.8.10

Completed tasks are not reporting back to their project servers. I've let them build up for 3 days a couple of times with nothing being sent but I do get new tasks.

When I manually update the projects the tasks do get sent to their servers.

I'm doing rosetta, milkyway, and seti and all fail to connect.

I'm running the beta because the release version stops working after about a day -- beta runs fine just doesn't communicate completed tasks back to the server.

Prefs are set to run while computer is in use
transfer at most 0
every 0 days
min work buffer .04
days of work buffer 4

Thanks for any ideas you have.

Nate

You now let them accumulate for 3 days, but your high water mark for work is 4 days. What happens on day 4, if you don't do anything?

---

Hi Jord,

Almost 5 days have passed since last connecting. There are a bunch (about 75) tasks waiting to report.

If it had connected on day 4 (yesterday) I would expect that it would have sent all the tasks that were ready to report, correct?

I notice that the boinc manager prefs for transfers at set at

Transfer at most 0 Mbytes every 0 days

Is that the correct setting? Or should the "every _ days" be set to 1?

I see that I can not enter a decimal in the "every _ days" field, only whole numbers (unlike the previous version which accepted decimals). I recall the old version was set at .4 days.

Thanks,

Nate

The connect is of course based on how good the original time estimates were for 4.4 days buffered work. What you tell is that that the client has been running 5 days now, so it's needing more time to do the work. Eventually when remaining time drops below 0.4 minimum, there will be 1 work call to get another 4 days over 0.4 minimum.

Had not heard before or realized that the Ready to Report rule of no later clearing than 24 hours after the oldest was done. Suspect that reporting will still be scheduled if the deadline comes near.

On that Every XX days change to integer, would not know what to do with a specification of say 100 Mb per 0.1 days or whatever. Whatever you recall, the default for that field is 0 as is the bandwidth budget field... basically no limits unless you specify them.

--//--

i think i'm confused. on all my other computers (10.6.x and 10.7.x) the manager/client automatically connects (perhaps based on the .04 days connect preference -- which is the same setting as on this PowerMac (the only PM -- the rest are MacBook Pros or older G5s).

All of them have a 4 day work buffer to allow for projects being down.

I don't understand why the work units (tasks) just build up on the PowerMac instead of completely uploading every so often.

The PowerMac is the only machine running the beta because 6.12.35 just stops working on that machine after a few hours (see different posts here about that issue).

I tried setting the prefs to connect every 1 day and will see what happens.

Nate

I've been testing on my Windows BOINC 7.0.20 for the past days. Took out <report_results_immediately/> from my cc_config.xml and had BOINC work with that. My low water mark is 1.0 days (previous connect to), high water is 0.5 days (previous additional days). I run Albert on GPU only, Einstein and Seti on CPU, Seti also on GPU.

14-Mar-2012 23:17:01 [Einstein@Home] [sched_op] Starting scheduler request
14-Mar-2012 23:17:01 [Einstein@Home] Sending scheduler request: To fetch work.
14-Mar-2012 23:17:01 [Einstein@Home] Reporting 7 completed tasks, requesting new tasks for CPU and ATI
14-Mar-2012 23:17:01 [Einstein@Home] [sched_op] CPU work request: 28693.30 seconds; 0.00 devices
14-Mar-2012 23:17:01 [Einstein@Home] [sched_op] ATI work request: 43982.71 seconds; 0.00 devices
14-Mar-2012 23:17:06 [Einstein@Home] Scheduler request completed: got 1 new tasks
14-Mar-2012 23:17:06 [Einstein@Home] [sched_op] Server version 611
14-Mar-2012 23:17:06 [Einstein@Home] Project requested delay of 60 seconds

14-Mar-2012 23:17:11 [SETI@home] [sched_op] Starting scheduler request
14-Mar-2012 23:17:11 [SETI@home] Sending scheduler request: To fetch work.
14-Mar-2012 23:17:11 [SETI@home] Reporting 1 completed tasks, requesting new tasks for CPU and ATI
14-Mar-2012 23:17:11 [SETI@home] [sched_op] CPU work request: 8567.78 seconds; 0.00 devices
14-Mar-2012 23:17:11 [SETI@home] [sched_op] ATI work request: 44101.55 seconds; 0.00 devices
14-Mar-2012 23:17:14 [Albert@Home] [checkpoint] result p2030.20111110.G39.07-00.55.N.b4s0g0.00000_2640_1 checkpointed
14-Mar-2012 23:17:15 [SETI@home] Scheduler request completed: got 2 new tasks
14-Mar-2012 23:17:15 [SETI@home] [sched_op] Server version 613
14-Mar-2012 23:17:15 [SETI@home] Project requested delay of 303 seconds

15-Mar-2012 02:56:02 [Einstein@Home] [sched_op] Starting scheduler request
15-Mar-2012 02:56:02 [Einstein@Home] Sending scheduler request: To fetch work.
15-Mar-2012 02:56:02 [Einstein@Home] Reporting 3 completed tasks, requesting new tasks for CPU
15-Mar-2012 02:56:02 [Einstein@Home] [sched_op] CPU work request: 117686.25 seconds; 0.00 devices
15-Mar-2012 02:56:02 [Einstein@Home] [sched_op] ATI work request: 0.00 seconds; 0.00 devices
15-Mar-2012 02:56:06 [Einstein@Home] Scheduler request completed: got 3 new tasks
15-Mar-2012 02:56:06 [Einstein@Home] [sched_op] Server version 611
15-Mar-2012 02:56:06 [Einstein@Home] Project requested delay of 60 seconds

15-Mar-2012 12:06:17 [Albert@Home] [sched_op] Starting scheduler request
15-Mar-2012 12:06:17 [Albert@Home] Sending scheduler request: Requested by user.
15-Mar-2012 12:06:17 [Albert@Home] Reporting 1 completed tasks, not requesting new tasks
15-Mar-2012 12:06:17 [Albert@Home] [sched_op] CPU work request: 0.00 seconds; 0.00 devices
15-Mar-2012 12:06:17 [Albert@Home] [sched_op] ATI work request: 0.00 seconds; 0.00 devices
15-Mar-2012 12:06:19 [Albert@Home] Scheduler request completed
15-Mar-2012 12:06:19 [Albert@Home] [sched_op] Server version 700
15-Mar-2012 12:06:19 [Albert@Home] Project requested delay of 60 seconds

15-Mar-2012 12:07:40 [Einstein@Home] [sched_op] Starting scheduler request
15-Mar-2012 12:07:40 [Einstein@Home] Sending scheduler request: Requested by user.
15-Mar-2012 12:07:40 [Einstein@Home] Reporting 3 completed tasks, requesting new tasks for CPU
15-Mar-2012 12:07:40 [Einstein@Home] [sched_op] CPU work request: 110363.46 seconds; 0.00 devices
15-Mar-2012 12:07:40 [Einstein@Home] [sched_op] ATI work request: 0.00 seconds; 0.00 devices
15-Mar-2012 12:07:43 [Einstein@Home] Scheduler request completed: got 3 new tasks
15-Mar-2012 12:07:43 [Einstein@Home] [sched_op] Server version 611
15-Mar-2012 12:07:43 [Einstein@Home] Project requested delay of 60 seconds

16-Mar-2012 01:53:59 [Einstein@Home] Sending scheduler request: To fetch work.
16-Mar-2012 01:53:59 [Einstein@Home] Reporting 3 completed tasks, requesting new tasks for CPU
16-Mar-2012 01:53:59 [Einstein@Home] [sched_op] CPU work request: 80000.02 seconds; 0.00 devices
16-Mar-2012 01:53:59 [Einstein@Home] [sched_op] ATI work request: 0.00 seconds; 0.00 devices
16-Mar-2012 01:54:02 [Einstein@Home] Scheduler request completed: got 2 new tasks
16-Mar-2012 01:54:02 [Einstein@Home] [sched_op] Server version 611
16-Mar-2012 01:54:02 [Einstein@Home] Project requested delay of 60 seconds

17-Mar-2012 02:15:01 [Einstein@Home] [sched_op] Starting scheduler request
17-Mar-2012 02:15:01 [Einstein@Home] Sending scheduler request: To fetch work.
17-Mar-2012 02:15:01 [Einstein@Home] Reporting 7 completed tasks, requesting new tasks for CPU
17-Mar-2012 02:15:01 [Einstein@Home] [sched_op] CPU work request: 130142.46 seconds; 0.00 devices
17-Mar-2012 02:15:01 [Einstein@Home] [sched_op] ATI work request: 0.00 seconds; 0.00 devices
17-Mar-2012 02:15:05 [Einstein@Home] Scheduler request completed: got 3 new tasks
17-Mar-2012 02:15:05 [Einstein@Home] [sched_op] Server version 611
17-Mar-2012 02:15:05 [Einstein@Home] Project requested delay of 60 seconds

As can be seen, I don't have to update, it's doing it all by itself.

---