I had the freeze problem again @ the completion of an Einstein WU, but again I had the kernel_task eating away at about 70% - 80% of my cpu processes. Is this just me for has anyone else noticed a kernel_task cycle drain?
I have also experienced a hang occurance at the end of the processing of a WU. After Suspend, Quit and Restart, the corresponding result could be uploaded, and I got normal credit for it.
This was on my PowerBook G4, runing OSX.3.9, BOINC 4.43, E@H 0.11, screensaver enabled, crunching for E@H only.
JJ
I had the freeze problem again @ the completion of an Einstein WU, but again I had the kernel_task eating away at about 70% - 80% of my cpu processes. Is this just me for has anyone else noticed a kernel_task cycle drain?
I've had this happen but only when browsing, not in reference to BOINC. It was something to do with a security program but seems to have stopped happening since the last update.
The auto restart thing seems like a reasonable solution ( with the caveat that C@H might lose up to 15 Min of work if it happens at the wrong time). Let everyone know how this works for you.
Not working the way it is supposed to. It shutsdown, but won't restart. I'll play with it some more, but in the meantime I think I'll have to check the MacNN forums to find out how to setup a chronjob again. There is a simple way to have it do a restart at a specified time(s), with reliability. I just don't remember how to do it. That would handle the freeze problem for the time being till the fix is available. As it is now, my iMac G5 shuts down and just stays off.
And so the beta saga continues..... Not complaining though, after all I volunteered.
As I will be travelling the next week, I have a smal script running in a terminal:
while sleep 43200 ; do
for i in `ps aux | grep -v grep | grep einstein | awk '{print $2}'`; do
kill -QUIT $i;
done;
done
This kills the running einstein processes every 12 hours, regardless of hanging or not. Einstein should then be restarted by the client, just giving a message "exited with zero status but no finished file". Adjust the sleep time so that normally a single Result isn't interrupted more than one time.
Two items to report:
1) I've been running both the iBook and the PowerBook for almost 48 hours now with my "connect to" set to .000005 days (roughly 1/2 second). So far, I still have not had the hang that I've had in the past, where the system is using most of the cpu.
2) This WU has had three results reported back; two of the results received credit, but mine received 0.0 credits. In the result for this WU, mine shows no errors in the std error out, but still gives me nothing for credit. The time it took to compute was the same as all my others, no hangs, etc...
Here's the MenuBar log for this WU:
2005-08-08 20:05:30 [Einstein@Home] Starting result w1_1019.0__1019.1_0.1_T04_S4hA_0 using einstein version 0.11
2005-08-08 21:05:31 [---] schedule_cpus: time 3600.052981
2005-08-08 22:05:31 [---] schedule_cpus: time 3600.057360
2005-08-08 23:05:31 [---] schedule_cpus: time 3600.078918
2005-08-09 00:05:31 [---] schedule_cpus: time 3600.006506
2005-08-09 01:05:31 [---] schedule_cpus: time 3600.015533
2005-08-09 02:05:31 [---] schedule_cpus: time 3600.054898
2005-08-09 03:05:31 [---] schedule_cpus: time 3600.017179
2005-08-09 04:05:31 [---] schedule_cpus: time 3600.038998
adding: w1_1019.0__1019.1_0.1_T04_S4hA_0_0 (deflated 65%)
2005-08-09 04:27:54 [---] request_reschedule_cpus: process exited
2005-08-09 04:27:54 [Einstein@Home] Requesting 0.42 seconds of work
2005-08-09 04:27:54 [Einstein@Home] Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
2005-08-09 04:27:54 [Einstein@Home] Computation for result w1_1019.0__1019.1_0.1_T04_S4hA_0 finished
2005-08-09 04:27:54 [---] schedule_cpus: must schedule
2005-08-09 04:27:54 [SETI@home] Resuming result 09my04ab.8123.17536.1022174.228_3 using setiathome version 4.30
2005-08-09 04:27:55 [Einstein@Home] Started upload of w1_1019.0__1019.1_0.1_T04_S4hA_0_0
2005-08-09 04:27:57 [Einstein@Home] Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi succeeded
2005-08-09 04:27:57 [---] request_reschedule_cpus: files downloaded
2005-08-09 04:27:57 [---] schedule_cpus: must schedule
2005-08-09 04:27:57 [SETI@home] Pausing result 09my04ab.8123.17536.1022174.228_3 (left in memory)
2005-08-09 04:27:57 [Einstein@Home] Starting result w1_1019.0__1019.2_0.1_T04_S4hA_0 using einstein version 0.11
C the result for that work unit came back as invalid. For whatever reason, your results did not match those of the other two work units. This has happened to me on rare occasion as well. Sooner or later it happens to everyone. It is one of the characteristics of BOINC. You will not get credit for a work unit that is not in consensus with others.
This is a safeguard to prevent some of the cheating that occurred previously in some projects as a result of individuals overclocking their systems for credit, but sacrificing quality science. Even though you were not cheating, for whatever reason (perhaps just a random error in calculations) did not come back sound. I wouldn't worry about it as long as it only occurs very occasionally. Once in a great while a work unit just won't qualify as a scientifically valid result. Out of hundreds of work units, I have had this occur with less then 1/2 of 1 percent. It is a sacrifice we all make on rare occasions, for the good of the science. If it occurs with frequency, it may indicate a problem with your machine that requires some corrective maintenence. The long term effect on total credit is not even noticable.
This really has nothing to do with the Beta, but I am curious about it. Why are the report deadlines listed as UTC on the stats page for BOINC applications and in local time on the BOINC Manager screen? It would seem to me that the UTC should be used in all cases. UTC is used to eliminate the confusion from times zones and daylight saving time variations so why is that feature not used in BOINC?
Just wondering
Phil
We Must look for intelligent life on other planets as,
it is becoming increasingly apparent we will not find any on our own.
I had the freeze problem
)
I had the freeze problem again @ the completion of an Einstein WU, but again I had the kernel_task eating away at about 70% - 80% of my cpu processes. Is this just me for has anyone else noticed a kernel_task cycle drain?
The freeze/hang bug is still
)
The freeze/hang bug is still there with the Mac Client 0.11, using Boinc 4.43 OS 10.3.9, Power Mac G5, CPUs: 2, 1.8 GHz, 1.25 GB
WU w1_1111.5__1111.5._0.1_T04_S4hA_0
restarting Boinc helps sometimes
Boinc Bug: copy & paste of messages doesn't work
Boinc Bug: While Boinc window is open, OS switches to english
thalasso
Special Off Topic Team
I have also experienced a
)
I have also experienced a hang occurance at the end of the processing of a WU. After Suspend, Quit and Restart, the corresponding result could be uploaded, and I got normal credit for it.
This was on my PowerBook G4, runing OSX.3.9, BOINC 4.43, E@H 0.11, screensaver enabled, crunching for E@H only.
JJ
RE: I had the freeze
)
I've had this happen but only when browsing, not in reference to BOINC. It was something to do with a security program but seems to have stopped happening since the last update.
RE: The auto restart thing
)
Not working the way it is supposed to. It shutsdown, but won't restart. I'll play with it some more, but in the meantime I think I'll have to check the MacNN forums to find out how to setup a chronjob again. There is a simple way to have it do a restart at a specified time(s), with reliability. I just don't remember how to do it. That would handle the freeze problem for the time being till the fix is available. As it is now, my iMac G5 shuts down and just stays off.
And so the beta saga continues..... Not complaining though, after all I volunteered.
Team MacNN - The best Macintosh team ever.
As I will be travelling the
)
As I will be travelling the next week, I have a smal script running in a terminal:
This kills the running einstein processes every 12 hours, regardless of hanging or not. Einstein should then be restarted by the client, just giving a message "exited with zero status but no finished file". Adjust the sleep time so that normally a single Result isn't interrupted more than one time.
BM
BM
Thanks Bernd. I'll give
)
Thanks Bernd. I'll give that a try.
Team MacNN - The best Macintosh team ever.
Two items to report: 1) I've
)
Two items to report:
1) I've been running both the iBook and the PowerBook for almost 48 hours now with my "connect to" set to .000005 days (roughly 1/2 second). So far, I still have not had the hang that I've had in the past, where the system is using most of the cpu.
2) This WU has had three results reported back; two of the results received credit, but mine received 0.0 credits. In the result for this WU, mine shows no errors in the std error out, but still gives me nothing for credit. The time it took to compute was the same as all my others, no hangs, etc...
Here's the MenuBar log for this WU:
2005-08-08 20:05:30 [Einstein@Home] Starting result w1_1019.0__1019.1_0.1_T04_S4hA_0 using einstein version 0.11
2005-08-08 21:05:31 [---] schedule_cpus: time 3600.052981
2005-08-08 22:05:31 [---] schedule_cpus: time 3600.057360
2005-08-08 23:05:31 [---] schedule_cpus: time 3600.078918
2005-08-09 00:05:31 [---] schedule_cpus: time 3600.006506
2005-08-09 01:05:31 [---] schedule_cpus: time 3600.015533
2005-08-09 02:05:31 [---] schedule_cpus: time 3600.054898
2005-08-09 03:05:31 [---] schedule_cpus: time 3600.017179
2005-08-09 04:05:31 [---] schedule_cpus: time 3600.038998
adding: w1_1019.0__1019.1_0.1_T04_S4hA_0_0 (deflated 65%)
2005-08-09 04:27:54 [---] request_reschedule_cpus: process exited
2005-08-09 04:27:54 [Einstein@Home] Requesting 0.42 seconds of work
2005-08-09 04:27:54 [Einstein@Home] Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
2005-08-09 04:27:54 [Einstein@Home] Computation for result w1_1019.0__1019.1_0.1_T04_S4hA_0 finished
2005-08-09 04:27:54 [---] schedule_cpus: must schedule
2005-08-09 04:27:54 [SETI@home] Resuming result 09my04ab.8123.17536.1022174.228_3 using setiathome version 4.30
2005-08-09 04:27:55 [Einstein@Home] Started upload of w1_1019.0__1019.1_0.1_T04_S4hA_0_0
2005-08-09 04:27:57 [Einstein@Home] Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi succeeded
2005-08-09 04:27:57 [---] request_reschedule_cpus: files downloaded
2005-08-09 04:27:57 [---] schedule_cpus: must schedule
2005-08-09 04:27:57 [SETI@home] Pausing result 09my04ab.8123.17536.1022174.228_3 (left in memory)
2005-08-09 04:27:57 [Einstein@Home] Starting result w1_1019.0__1019.2_0.1_T04_S4hA_0 using einstein version 0.11
C
[/url]
Join Team MacNN
C the result for that work
)
C the result for that work unit came back as invalid. For whatever reason, your results did not match those of the other two work units. This has happened to me on rare occasion as well. Sooner or later it happens to everyone. It is one of the characteristics of BOINC. You will not get credit for a work unit that is not in consensus with others.
This is a safeguard to prevent some of the cheating that occurred previously in some projects as a result of individuals overclocking their systems for credit, but sacrificing quality science. Even though you were not cheating, for whatever reason (perhaps just a random error in calculations) did not come back sound. I wouldn't worry about it as long as it only occurs very occasionally. Once in a great while a work unit just won't qualify as a scientifically valid result. Out of hundreds of work units, I have had this occur with less then 1/2 of 1 percent. It is a sacrifice we all make on rare occasions, for the good of the science. If it occurs with frequency, it may indicate a problem with your machine that requires some corrective maintenence. The long term effect on total credit is not even noticable.
Team MacNN - The best Macintosh team ever.
This really has nothing to do
)
This really has nothing to do with the Beta, but I am curious about it. Why are the report deadlines listed as UTC on the stats page for BOINC applications and in local time on the BOINC Manager screen? It would seem to me that the UTC should be used in all cases. UTC is used to eliminate the confusion from times zones and daylight saving time variations so why is that feature not used in BOINC?
Just wondering
Phil
We Must look for intelligent life on other planets as,
it is becoming increasingly apparent we will not find any on our own.