| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: is the upload server full again |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 10
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
just noticed i have a completed task in boinc that has not left and the soft reboot did not help any ideas
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
never mind looks like a old fashion update did the trick
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
If making a dud post or OP, you can delete it, long as there's no response... button above the post.
In this case, if the disk is full on the server side, it will print that in the Event Log [Ctrl+Shft+E to open in v7 clients, else the Message tab in v6]. Crunch On. Oh and "Ready to Report" are -intentionally- accumulated on the client side. There's about 14 situations they will self-clear such as during a work fetch, but no later than 24 hours after the oldest was readied. The techs love you for not hitting the update button... it's the difference of the server scheduler being connected with millions of times a day or a few hundred thousand. The more hits, the more chance the client gets a back-off instruction due a form of overload and we've had many of these in the past few days. |
||
|
|
cjslman
Master Cruncher Mexico Joined: Nov 23, 2004 Post Count: 2082 Status: Offline Project Badges: 
|
Rob... I confess that I'm one of the "Update" button users. Didn't know what was happening behind the scenes by using it. I think it would be good for you to post a post (sorry for the redundancy
---------------------------------------- ) explaining the evils associated with going wild with that button. Knowing the reasons/explanations of the misuse of the update button may help educate other "Update" abusers.THanks, CJSL Crunching for a better world... |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Tangent topic continued: The techs already, out of probable despair, implemented an enforced back-off of currently 182 seconds [3:02 minutes]. Briefly they lowered that value some weeks ago to 60 seconds, but were quick to put the 182 count back. Hit that button twice within that period and you get a "too soon" logged. The request gets simply bounced and the counter resumes from 182 again, meaning, if you keep hitting the client will never succeed. Not so long ago we had 30 seconds and even 10-12 seconds. The price of success ;O)
Actually this is covered in several Start Here FAQ's in amongst the detail "Ready to Report" topic. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Well there actually still is a issue for some reason I am not getting new cases maybe I might have to re-install software all of this is so new to me sorry guys
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
and no I also did not know I could delete my own post. I just know right now is I gotta run be back later.
|
||
|
|
cjslman
Master Cruncher Mexico Joined: Nov 23, 2004 Post Count: 2082 Status: Offline Project Badges:
|
Rob, thanks for the detailed info (although I wasn't whacking the "Update" button every few minutes... more like 2 or 3 times a day... when I saw there were WUs ready to report). I imagine that the "Ready to Report" status is explained in the FAQ, but not everybody reads the FAQ section like if it were a novel, so this tidbit of info might have been obviated by some crunchers (specially the new ones). I'll give my tiny bit of cooperation and cook up a post to remind the crunchers to take it easy on the "Update" button.
----------------------------------------Thanks, CJSL Gotta keep crunching, there's a world to save !!! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
If making a dud post or OP, you can delete it, long as there's no response... button above the post. In this case, if the disk is full on the server side, it will print that in the Event Log [Ctrl+Shft+E to open in v7 clients, else the Message tab in v6]. Crunch On. Oh and "Ready to Report" are -intentionally- accumulated on the client side. There's about 14 situations they will self-clear such as during a work fetch, but no later than 24 hours after the oldest was readied. The techs love you for not hitting the update button... it's the difference of the server scheduler being connected with millions of times a day or a few hundred thousand. The more hits, the more chance the client gets a back-off instruction due a form of overload and we've had many of these in the past few days. Like I said I am totally new to this I will be more patient about tasks accumulating in my account sorry for the dud post |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Rob, thanks for the detailed info (although I wasn't whacking the "Update" button every few minutes... more like 2 or 3 times a day... when I saw there were WUs ready to report). I imagine that the "Ready to Report" status is explained in the FAQ, but not everybody reads the FAQ section like if it were a novel, so this tidbit of info might have been obviated by some crunchers (specially the new ones). I'll give my tiny bit of cooperation and cook up a post to remind the crunchers to take it easy on the "Update" button. Thanks, CJSL Gotta keep crunching, there's a world to save !!! I looked in the FAQ and saw nothing relating to this ah maybe I dreamed I read the FAQ |
||
|
|
|