Most of the time the upload goes up to 1.09 MB when it stucks, so smaller zip files will upload without problems.

I don't know if this will help, but I had a similar problem a year or two ago. It turned out to be with a device called a Riverbed, which is a network caching server, which needed to be reset. This was installed to cut down on interoffice network traffic (a lot of it repetitive), but it was also set inadvertently to cache internet traffic, and started causing trouble with CPDN uploads. If you have one of these at your location, maybe it could be the problem.

DON'T abort extra work that you get! That (those) models count against your "daily" quota.

Question: When these models crash (as they are wont to do), does that also count against your daily quota?

3)
Message boards :
Number crunching :
How many hours are in a day?
(Message 40165)
Posted 17 Jul 2010 by genes
Whoa. Suddenly got some new tasks for machine 1070830. 5 in all, so now all 8 cores are busy with these making up the debt, and the Beta tasks are in waiting. From looking at the task list, only these 5 have been added, no new phantoms. So, problem solved for the time being, at least for this machine. Thanks all.

Yes I read that thread, and was lamenting that so many people wouldn't notice that their machines were erroring out everything they got sent, and I also noticed your post alluding to phantom tasks on Jan 27 and again on Mar 12, which is what I think is happening here. These tasks never showed up on my system, which, AFAIK, does not have any networking issues. If they had showed up and then gotten errors, I would have taken appropriate action.

BTW, when your quota is "minussed", how does it show in the message from the server? Does it actually say -1?

Getting the quota message apparently tells BOINC to back off on communications, including trickles, so I now find myself checking every so often and doing them manually. If BOINC then asks for tasks again, it again gets the quota message from the server. Just did it again:

And again, BOINC has set a communications backoff for 6-1/2 hours this time. Mind you, I haven't had any new work from the project since June 29th, so I don't know where this quota is getting triggered.

What I was thinking is that it might have to do with the 20 tasks the server thinks that I have (which apparently were lost in the transactions), but even then, I haven't gotten anything recently, so why the "daily quota of 4"?

I guess I can wait until the work I have is finished, then detach and reattach to the project. That may fix it for my system, at least temporarily, but won't fix the real problem, which has got to be on the server side.

In the meantime, I still have the three tasks running, and 5 cores idle, but I will un-suspend Beta and they will get busy.

Also, every time I force CPDN to update and it gets this quota message, it backs off communication for a long time, in this case 11 hours. I then have to force it again when it's waiting to do a trickle.

7)
Message boards :
Number crunching :
How many hours are in a day?
(Message 40149)
Posted 16 Jul 2010 by genes
I'm not Jim, but I have a similar problem, and perhaps a clue to the answer. Take a look at this computer's tasks. Seems like it has a lot to work on, no? But the only valid tasks are the four issued on June 27-30, one of which, 11045389, just finished. The other three 11041787, 11040358, and 11040062 are still running, due to finish in the next few days. These are all like the last slab models issued before they were discontinued. There are 20 other tasks listed as in progress which never made it to my machine. Evidently they figure in the reluctance of the server to issue it more work. Thank goodness the Beta site doesn't have these issues, looks like it will take over as these slabs finish and I get no more work from the main site.

Both machines (1036631 and 1070830) are shared 50-50 with CPDN and CPDN Beta, so they need only work for two and four cores, respectively, and at the moment they still have it. In a few days, the current work will start to finish, so we'll see if any new work is forthcoming. In the past (more than a week ago), they would fill up as if all cores were working 100% for each project, something that still happens with Beta. I have BOINC set to "connect every 0.1 days" and "Additional work buffer" of 0 days, so I would expect them to ask for new work only as they are nearing completion of the current work.

The zip file in question is 15.83MB, and the transfer started and went very quickly up to 7.30MB, then abruptly halted. After a while, timeout ensued. The same thing is also happening on another machine which has 3 of these files trying to upload.

Don\'t abort! The CC is stupid in that CPDN does not care that the deadline has been passed, but with other projects, it is a big deal. The original bunch of work units were sent out with too short of a deadline. Later sulphurs had a deadline of about a year. Congratulations on getting so far with your P3 1 GHz and good luck on finishing!

OK, OK!! I\'ll take my finger off the button! ;-) Thanks for the quick reply.

Seriously, though, should I detach this machine from CPDN in the future? It looks like the new models will, if anything, require even more powerful CPU\'s. This machine is at the low end of my collection, so I will still be running CPDN with other, faster machines in any case. Is there a minimum recommended machine?

It is now overdue by 6 days, the BOINC CC is telling me I should abort it, but it is on phase 5. It seems that the deadline was a bit short on this WU, since I got it on Sept.12, 05, I thought these had about a year to finish.

Anyway, the WU is listed as \"over\" with \"too many total results\" as the error. Should I abort? I\'m really reluctant to do so since it is on phase 5, unless the result is worthless. It is continuing to run normally otherwise.

The machine is a 1GHz P3, it has no other project running at the moment, BOINC has been in EDF mode essentially since I got this WU. Now running BOINC CC 5.2.15.

19)
Message boards :
Number crunching :
Announcement: Database residual problem - misallocated WUs
(Message 12902)
Posted 26 May 2005 by genes
I just got some WU's on a couple of machines, but I don't see them listed in my "results" page (yet). Is there a delay before they show up?
-----
Actually, two results showed up for one of my machines, but they are different than the ones I got. The other machine's WU's did not show up. I'm thinking I will have to abort them all and try again.
-----
These are the problem WU's:
Host: 6415 - Result ID: 880949 - Name: 3y7o_100206157 (not on machine)
Host: 6415 - Result ID: 880941 - Name: 3y7g_100206149_0 (not on machine)
Host: 6415 - Name: 3zvo_100208339_0 (not in results page) - aborting
Host: 6415 - Name: 3zx7_100208394_0 (not in results page) - aborting
Host: 1113 - Name: 3zx1_100208388_0 (not in results page) - aborting
Host: 1113 - Name: 3xv6_100205703_0 (not in results page) - aborting
-----
Interesting note: Results 880941 and 880949 are listed as being sent to me at an earlier time than I got the other four units.
-----
Update: After aborting the 4 unlisted WU's, I got 1 WU per machine that DID show up on my results page. Whew!