| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Unable to Download new Tasks - No close tag in scheduler reply[RESOLVED] |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 47
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Not real strange... assigned in those broken sched_reply tag transmissions, but since incomplete [this is like American football, where they're allowed like 4 attempts at a touchdown], you never got the actual task files as pegged by server [see Result Status page].
----------------------------------------[Edit 1 times, last edit by Former Member at Dec 18, 2013 1:57:13 PM] |
||
|
|
Mumak
Senior Cruncher Joined: Dec 7, 2012 Post Count: 477 Status: Offline Project Badges: 
|
Thanks for explanation. However, now it's again back to the error state.
---------------------------------------- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
You may want to up the buffer setting a bit. Tuvak logic here is, if a reply gets through, hopefully you get a few dozen, so there's no immediate pressing urgency for a next request... after success lower buffer setting again, or keep it higher.:D
|
||
|
|
Mumak
Senior Cruncher Joined: Dec 7, 2012 Post Count: 477 Status: Offline Project Badges:
|
I tried to raise the buffer, but that doesn't help. Since the server reply is broken, it doesn't get parsed at all, so no new tasks are accepted.
----------------------------------------I'm actually trying to set the buffer to minimum hoping that a smaller server reply (with less tasks) won't get broken on the packet boundary. Btw, when there's no work being sent from server, at least the finished tasks get reported... |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
That is good to know as Scribe 'deScribed' it as having to specifically set 'No new work' to get the 'Ready to Report's through. (not been in the situation yet, touch wood, to see how latest test clients act in the 'no closing tag' reply condition)
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I tried to raise the buffer, but that doesn't help. Since the server reply is broken, it doesn't get parsed at all, so no new tasks are accepted. I'm actually trying to set the buffer to minimum hoping that a smaller server reply (with less tasks) won't get broken on the packet boundary. Btw, when there's no work being sent from server, at least the finished tasks get reported... I told you how to fix it, why don't you do it? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Here there's the dilemma set: knreed wants as many copies mailed as possible of broken replies to get patterns, and you want to crunch uninterrupted, detach > add project in hopes it works. Think knreed would like copies mailed if after this sequence there's still failure.
----------------------------------------edit: Of course, if the geographical location makes a difference and once having mailed the sched* files, what more can one do... return to crunching ASAP, in whatever brute way possible ;? [Edit 1 times, last edit by Former Member at Dec 18, 2013 2:41:04 PM] |
||
|
|
Mumak
Senior Cruncher Joined: Dec 7, 2012 Post Count: 477 Status: Offline Project Badges:
|
I told you how to fix it, why don't you do it? 1. I want to gather as much information about this issue as possible. 2. I was searching for a less-radical solution. 3. In case the issue is on server-side and it gets fixed, I might be able to verify it. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Commendable [:thumbs up smiley]
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I told you how to fix it, why don't you do it? 1. I want to gather as much information about this issue as possible. 2. I was searching for a less-radical solution. 3. In case the issue is on server-side and it gets fixed, I might be able to verify it. Reasonable action  |
||
|
|
|