BOINC 4.43
22 May 2005 15:30:56 UTC
Topic 189217
(moderation:
I just installled BOINC version 4.43 after having 4.25 running with no problems at all. So, when I was checking it, it said the following, and I don't know what's going on with Einstein?? Can anyone explain to me, if I have a problem, what it might be, and how I solve it?? IF I have a problem!
I have manually updated the projects some times!
22-05-2005 12:54:28||Starting BOINC client version 4.43 for windows_intelx86
22-05-2005 12:54:28||Data directory: C:\Programmer\BOINC
22-05-2005 12:54:28|Einstein@Home|Computer ID: 56003; location: home; project prefs: home
22-05-2005 12:54:28|SETI@home|Computer ID: 722589; location: home; project prefs: home
22-05-2005 12:54:28||General prefs: from SETI@home (last modified 2005-04-06 22:34:16)
22-05-2005 12:54:28||General prefs: using separate prefs for home
22-05-2005 12:54:29||Remote control not allowed; using loopback address
22-05-2005 12:54:29|SETI@home|Resuming computation for result 04fe05aa.10289.10898.279820.165_1 using setiathome version 4.09
22-05-2005 12:54:29|Einstein@Home|Deferring computation for result H1_1077.5__1077.8_0.1_T06_Fin1_2
22-05-2005 12:54:30||schedule_cpus: must schedule
22-05-2005 13:54:29||schedule_cpus: time 3600.031250
22-05-2005 13:54:29|SETI@home|Pausing result 04fe05aa.10289.10898.279820.165_1 (removed from memory)
22-05-2005 13:54:29|Einstein@Home|Restarting result H1_1077.5__1077.8_0.1_T06_Fin1_2 using einstein version 4.79
22-05-2005 13:54:30||request_reschedule_cpus: process exited
22-05-2005 13:54:30||schedule_cpus: must schedule
22-05-2005 14:54:30||schedule_cpus: time 3600.062500
22-05-2005 14:54:30|SETI@home|Restarting result 04fe05aa.10289.10898.279820.165_1 using setiathome version 4.09
22-05-2005 14:54:30|Einstein@Home|Pausing result H1_1077.5__1077.8_0.1_T06_Fin1_2 (removed from memory)
22-05-2005 14:54:31||request_reschedule_cpus: process exited
22-05-2005 14:54:31||schedule_cpus: must schedule
22-05-2005 15:54:31||schedule_cpus: time 3600.046875
22-05-2005 15:54:31|SETI@home|Pausing result 04fe05aa.10289.10898.279820.165_1 (removed from memory)
22-05-2005 15:54:31|Einstein@Home|Restarting result H1_1077.5__1077.8_0.1_T06_Fin1_2 using einstein version 4.79
22-05-2005 15:54:32||request_reschedule_cpus: process exited
22-05-2005 15:54:32||schedule_cpus: must schedule
22-05-2005 16:54:32||schedule_cpus: time 3600.078125
22-05-2005 16:54:32|SETI@home|Restarting result 04fe05aa.10289.10898.279820.165_1 using setiathome version 4.09
22-05-2005 16:54:32|Einstein@Home|Pausing result H1_1077.5__1077.8_0.1_T06_Fin1_2 (removed from memory)
22-05-2005 16:54:33||request_reschedule_cpus: process exited
22-05-2005 16:54:33||schedule_cpus: must schedule
22-05-2005 17:13:08||request_reschedule_cpus: project op
22-05-2005 17:13:08||schedule_cpus: must schedule
22-05-2005 17:13:09|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
22-05-2005 17:13:11|Einstein@Home|Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi succeeded
22-05-2005 17:14:05||request_reschedule_cpus: project op
22-05-2005 17:14:05||schedule_cpus: must schedule
22-05-2005 17:14:06|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
22-05-2005 17:14:07|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
22-05-2005 17:26:04||request_reschedule_cpus: process exited
22-05-2005 17:26:04|SETI@home|Computation for result 04fe05aa.10289.10898.279820.165_1 finished
22-05-2005 17:26:04||schedule_cpus: must schedule
22-05-2005 17:26:04|SETI@home|Starting result 03fe05ac.27320.11760.497156.235_2 using setiathome version 4.09
22-05-2005 17:26:05|SETI@home|Started upload of 04fe05aa.10289.10898.279820.165_1_0
22-05-2005 17:26:09|SETI@home|Finished upload of 04fe05aa.10289.10898.279820.165_1_0
22-05-2005 17:26:09|SETI@home|Throughput 69976 bytes/sec
22-05-2005 17:26:45||request_reschedule_cpus: project op
22-05-2005 17:26:45||schedule_cpus: must schedule
22-05-2005 17:26:45|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
22-05-2005 17:26:46|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
BOINC 4.43
)
Ok, I see now that Einstein is running (at least!), but what does this
22-05-2005 17:13:11|Einstein@Home|Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi succeeded
22-05-2005 17:14:05||request_reschedule_cpus: project op
22-05-2005 17:14:05||schedule_cpus: must schedule
mean?????
4.43 has an entirely
)
4.43 has an entirely different client side scheduler than 4.25 did. You aren't going to always get work when you try to update a project because the CC is trying to make sure you don't blow past deadlines. If you are attached to multiple projects, you also may not see work from every project on your machine at the same time.
The request_reschedule_cpus: project op message means that you have just done something (such as updating a project) that causes the CPUs to recalculate debt.
4.43 has an entirely
)
4.43 has an entirely different client side scheduler than 4.25 did. You aren't going to always get work when you try to update a project because the CC is trying to make sure you don't blow past deadlines. If you are attached to multiple projects, you also may not see work from every project on your machine at the same time.
Ohh, thank you! This is a nice feature! I have set cache to 1 day, so I never have more than 2 Einstein and 3 Seti WU's at any time, sometimes less. This is good for us who don't have large cache's that we are not punished by people who keep their cache large and therefore return late! :-)
The request_reschedule_cpus: project op message means that you have just done something (such as updating a project) that causes the CPUs to recalculate debt.
Yes, I had just updated the projects! And, as I said earlier, my Einstein WU is crunching well! :-))))
Thanks!
EDIT: I thought the BBCode could be used here also? I just found out that the BBCode
EDIT: I thought the BBCode
)
EDIT: I thought the BBCode could be used here also? I just found out that the BBCode
4.43 has an entirely
)
4.43 has an entirely different client side scheduler than 4.25 did. You aren't going to always get work when you try to update a project because the CC is trying to make sure you don't blow past deadlines. If you are attached to multiple projects, you also may not see work from every project on your machine at the same time.
Or no work at all. Not that my CPU is twiddling its virtual thumbs. I must say that the CPDN unit is getting a lot of attention. All the attention even, as no other projects are downloading work, not even Einstein.
4.43 has an entirely
)
4.43 has an entirely different client side scheduler than 4.25 did. You aren't going to always get work when you try to update a project because the CC is trying to make sure you don't blow past deadlines. If you are attached to multiple projects, you also may not see work from every project on your machine at the same time.
Or no work at all. Not that my CPU is twiddling its virtual thumbs. I must say that the CPDN unit is getting a lot of attention. All the attention even, as no other projects are downloading work, not even Einstein.
Many of the projects seem to be out of commission at the moment.
Projects with a negative LT debt have gotten more than their share of work recently and are taking a break from work so that the other projects can catch up their resource share.
BOINC WIKI
Projects with a negative LT
)
Projects with a negative LT debt have gotten more than their share of work recently and are taking a break from work so that the other projects can catch up their resource share.
I have following LT debt:
Einstein@Home
long_term_debt -111051.375621
LHC@home
long_term_debt 153096.398403
SETI@home
long_term_debt -42045.022782
LHC is suspended, the others not.
For Seti and Einstein no WU's are downloaded although Boinc gives the message
24/05/2005 20:29:38||May run out of work in 4.00 days; requesting more
Is the 153096 LT debt for LHC responsible for this?
If yes, should Boinc in that case not take into consideration that LHC is suspended in order to be able to download WU's for Eistein and Seti?
Update.
After returning the result of 1 WU of Seti, having just only 1 left, Boinc downloaded 5 WU's for Einstein.
Greetings from Belgium
Thierry
Projects with a negative LT
)
Projects with a negative LT debt have gotten more than their share of work recently and are taking a break from work so that the other projects can catch up their resource share.
I have following LT debt:
Einstein@Home
long_term_debt -111051.375621
LHC@home
long_term_debt 153096.398403
SETI@home
long_term_debt -42045.022782
LHC is suspended, the others not.
For Seti and Einstein no WU's are downloaded although Boinc gives the message
24/05/2005 20:29:38||May run out of work in 4.00 days; requesting more
Is the 153096 LT debt for LHC responsible for this?
If yes, should Boinc in that case not take into consideration that LHC is suspended in order to be able to download WU's for Eistein and Seti?
Update.
After returning the result of 1 WU of Seti, having just only 1 left, Boinc downloaded 5 WU's for Einstein.
Yes, the positive debt for LHC is the culprit. Yes, it should take this into account, and a fix for this has been checked in.
You can reset LHC a couple of times to get one of the other projects to have a positive debt.
BOINC WIKI
Yes, the positive debt for
)
Yes, the positive debt for LHC is the culprit. Yes, it should take this into account, and a fix for this has been checked in.
You can reset LHC a couple of times to get one of the other projects to have a positive debt.
Thanks John for the update. Seems I was thinking in the right way. Let's have that update ASAP or otherwise a lot of people are going into problems.
And the trick worked, thanks.
Greetings from Beglium.
Greetings from Belgium
Thierry
JM7 has been saying that a
)
JM7 has been saying that a fix has been proposed for a couple of days now. Shame the powers that be do not see these issues as sufficiently important to release a developement release quickly, especially since this bug has such a large impact on the way BOINC obtains and crunches work. It's pretty crap for a recommended version. HURRY UP WITH THE NEXT DEV VERSION PLEASE!
Live long and crunch.
Paul
