Follow BoincTasks on Twitter Facebook Visit our website here.BoincTasks cloud login is working again
Started by Pepo, October 26, 2011, 07:39:27 AM
0 Members and 1 Guest are viewing this topic.
Quote from: idahofisherman on November 03, 2011, 08:35:00 PMIs there a time limit for missed?
Quote from: 3216842 on November 04, 2011, 11:56:04 AMHello to all and congratulation for this great software.I have a little annoying problem with BT: When stopping BONIC client via menu, BT comes to a little freeze and after ~15-20 sek. BT shows up an error message "The BOINC client couldn't be shut down". Further ~10 sek. later the client and after this all running tasks/WUs stops (in this order) :-( .This behavior i watched in BT 1.23/.24/.25. Running XP Pro SP3, BOINC 6.12.34, BOINC Manager is not running.Log:04 November 2011 - 12:18:00 Shut down BoincTasks ---- The BOINC client is shutting down04 November 2011 - 12:18:30 Shut down BoincTasks ---- The BOINC client has shut down04 November 2011 - 12:18:30 Shut down BoincTasks ---- Der BOINC-Client konnte nicht beendet werden04 November 2011 - 12:18:30 Connect ---- The connection was lost, because the client stoppedHope for a fix.__W__
Quote from: 3216842 on November 04, 2011, 11:56:04 AMWhen stopping BONIC client via menu, BT comes to a little freeze and after ~15-20 sek. BT shows up an error message "The BOINC client couldn't be shut down". Further ~10 sek. later the client and after this all running tasks/WUs stops (in this order) :-(
Quote from: fred on November 04, 2011, 12:30:57 PMThe reason may be [...] a failure on the client itself to properly shut down.
Quote from: Pepo on November 04, 2011, 01:32:58 PMI do not remember anymore, how responsive the client was, while it was waiting for unresponsive tasks to finish, until finally killed them. This could have been the 20-30 sec. communication delay.
Quote from: fred on November 04, 2011, 12:30:57 PMI will fix the freeze on the main program, while it's waiting for the client to shut down.Der BOINC-Client konnte nicht beendet werden. : Means the client is still running even as it's ordered to shut down.The reason may be a running BOINC Manager that restarted the client. Or a failure on the client itself to properly shut down.This is by no means a BT problem.
Quote from: 3216842 on November 04, 2011, 10:07:47 PM- shuting down BOINC client from BOINC Manager is no problem and works fast (no matter running/not running any tasks), so i don't think this is a problem of the Client to shutdown ?!
Quote from: Pepo on November 04, 2011, 11:26:16 PMMaybe a side note - recent BOINC versions appear as shutting down very fast - in reality, as soon as the Manager gets a notification from the client that "it understood it should shut down", it simply disappears in nirvana. The client then slowly tries to finishing the tasks, while noone is aware and bothers anymore
Quote from: 3216842 on November 05, 2011, 01:22:02 AMThe shutdown over the BOINC Manager is much faster than the shutdown over BT.
Quote from: fred on November 05, 2011, 09:49:49 AMLets see how you like 1.26.
Quote from: idahofisherman on November 03, 2011, 08:35:00 PMThis seems to have fixed the cpu problem, but now I have increased "Missed" instead of Report OK.
Quote from: fred on November 06, 2011, 06:35:16 PMThis is an example:11777 PrimeGrid 06-11-2011 19:16 Computation for task llrCUL_104726483_4 finished 11779 PrimeGrid 06-11-2011 19:16 Started upload of llrCUL_104726483_4_0 11781 PrimeGrid 06-11-2011 19:16 Sending scheduler request: To report completed tasks. 11783 PrimeGrid 06-11-2011 19:16 Scheduler request completed PrimeGrid 6.09 Cullen (LLR) llrCUL_104726483_4 03d,15:44:09 (02d,04:17:26) 06-11-2011 19:17 06-11-2011 19:17 MissedMissed by 1 second As you can see the upload->ready->gone is within 1 second. So this is quite impossible the catch. At least not with extreme overhead.
Quote from: Pepo on November 06, 2011, 11:11:35 PMUnfortunately, Fred, I can personally not see it - your example is not that obvious, it is missing ":seconds" in the time values
5298 PrimeGrid 07.11.11 10:48:18 [checkpoint] result LLR_SGS_107255402_0 checkpointed 5301 PrimeGrid 07.11.11 10:49:07 Computation for task LLR_SGS_107255402_0 finished 5302 PrimeGrid 07.11.11 10:49:07 Starting task LLR_SGS_106902280_0 using llrTPS version 609 5303 PrimeGrid 07.11.11 10:49:08 Started upload of LLR_SGS_107255402_0_0 5304 PrimeGrid 07.11.11 10:49:10 Finished upload of LLR_SGS_107255402_0_0 5305 PrimeGrid 07.11.11 10:49:15 Sending scheduler request: To report completed tasks. 5307 PrimeGrid 07.11.11 10:49:18 Scheduler request completed: got 0 new tasks
PrimeGrid LLR_SGS_107255402_0 00:31:58 (00:26:39) 07.11.11 10:49:14 07.11.11 10:51:19 Reported: OK
5387 PrimeGrid 07.11.11 11:11:08 Computation for task LLR_SGS_106902280_0 finished 5390 PrimeGrid 07.11.11 11:11:10 Finished upload of LLR_SGS_106902280_0_0 5393 PrimeGrid 07.11.11 11:11:15 Scheduler request completed: got 0 new tasks PrimeGrid LLR_SGS_106902280_0 00:22:00 (00:21:09) 07.11.11 11:11:14 07.11.11 11:12:55 Reported: OK 5475 surveill@home 07.11.11 11:29:14 Computation for task wu_1320320103_162664_0 finished 5476 surveill@home 07.11.11 11:29:15 Started upload of wu_1320320103_162664_0_data 5479 surveill@home 07.11.11 11:29:17 Finished upload of wu_1320320103_162664_0_data 5480 surveill@home 07.11.11 11:29:21 Sending scheduler request: To report completed tasks. 5482 surveill@home 07.11.11 11:29:22 Scheduler request completed: got 0 new tasks surveill@home wu_1320320103_162664_0 00:16:13 (00:00:02) 07.11.11 11:29:21 07.11.11 11:31:29 Reported: OK
Quote from: Pepo on November 07, 2011, 10:50:09 AMOn the machine, History sampling is set to 4-10 seconds. Why the delay? If some task gets "missed", its timestamp is immediately (i.e. 1-5 sec.) after noticing it was gone.