I have been running 4.45 since I first installed BOINC.
...
Are you sure about that? Forgive the arrogance, but unless I can't read the results page properly, you are using version 4.43. (example http://einsteinathome.org/task/8290642 under stderr out) I must retract my advice, however, as there is no version 4.45 for a Mac available for download (4.43 is the latest release version). I am afraid I can't comment on what will happen with the alpha release of BOINC, but I'd stick with the regular release version if I were you, as the ghost WU don't cause significant harm.
Nick
You are right it is 4.43 (highest release version for the Mac). I should have checked the version before I answered your post. In any case I have the most current version and have every since I started running BOINC. So the version is not the problem. I have checked everything I can on my end an have found nothing that could cause these issues. I would agree it is unlikely that the alpha 5.1 will solve the problem, but I though I might give it a shot.
In any case it is as though the server thinks it is downloading WUs to my system, and I never get them. In fact I can't even see any server requests in my logs that match the reported send dates and times listed in the results for the questionable WUs. Due to other project processing my system only completes about 1 or two WUs per day at best. The results page shows as many as 10-12 coming down in a single day. That just is not happening, and there must be some explanation.
Regards
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 am experiencing the same problem with my Mac as well (running 4.43). It is not isolated to Einstein either. I'm seeing similar behavior with ProteinPredictor as well. I'm hoping this does get fixed because I have run into situations where I can't retrieve more work units since I have met my daily quota (in this case all phantom units). This also unfortunately results in delayed project results since those work units will not be resent until after the deadline is past. I have not been able to get in a situation where I can get these lost results sent to me and I am not sure how one accomplishes that (i've done the reset, detach,etc. routines with no luck).
I am experiencing the same problem with my Mac as well (running 4.43). It is not isolated to Einstein either. I'm seeing similar behavior with ProteinPredictor as well. I'm hoping this does get fixed because I have run into situations where I can't retrieve more work units since I have met my daily quota (in this case all phantom units). This also unfortunately results in delayed project results since those work units will not be resent until after the deadline is past. I have not been able to get in a situation where I can get these lost results sent to me and I am not sure how one accomplishes that (i've done the reset, detach,etc. routines with no luck).
I too have seen this with ProteinPredictor. but with PP@H I have discovered it is caused by the server creating "phantom" computers. My research to date indicates that if the PP@H software thinks you have either lost contact with the project or in some way detached, it will create a new computer the next time you attach. But I have noticed that these Phantoms just appear. My system is humming along and then suddenly I start seeing these WUs that are not on my machine. When I check the PP@H site, sure enough I will have a new phantom computer. Now at PP@H the fix is to merge the phantoms with the real computer. But on E@H there is something else going on. the symptoms are the same except I do not see any phantom computers, so I have no way to fix it.
I have read that there is a bug in BOINC that is causing this somehow in the upload download cycle for E@H, but it seems to me that if that were true I would see it happening on CP@H and S@H and I don't. I am hoping that one of the E@H guys will chime in with a "detailed" explanation of what is happening and how we can fix it.
I agree with you that all of this causes bad effects in our local processing and I would really like to fix it.
Regards
Phil
We Must look for intelligent life on other planets as,
it is becoming increasingly apparent we will not find any on our own.
RE: RE: I have been
)
You are right it is 4.43 (highest release version for the Mac). I should have checked the version before I answered your post. In any case I have the most current version and have every since I started running BOINC. So the version is not the problem. I have checked everything I can on my end an have found nothing that could cause these issues. I would agree it is unlikely that the alpha 5.1 will solve the problem, but I though I might give it a shot.
In any case it is as though the server thinks it is downloading WUs to my system, and I never get them. In fact I can't even see any server requests in my logs that match the reported send dates and times listed in the results for the questionable WUs. Due to other project processing my system only completes about 1 or two WUs per day at best. The results page shows as many as 10-12 coming down in a single day. That just is not happening, and there must be some explanation.
Regards
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 am experiencing the same
)
I am experiencing the same problem with my Mac as well (running 4.43). It is not isolated to Einstein either. I'm seeing similar behavior with ProteinPredictor as well. I'm hoping this does get fixed because I have run into situations where I can't retrieve more work units since I have met my daily quota (in this case all phantom units). This also unfortunately results in delayed project results since those work units will not be resent until after the deadline is past. I have not been able to get in a situation where I can get these lost results sent to me and I am not sure how one accomplishes that (i've done the reset, detach,etc. routines with no luck).
RE: I am experiencing the
)
I too have seen this with ProteinPredictor. but with PP@H I have discovered it is caused by the server creating "phantom" computers. My research to date indicates that if the PP@H software thinks you have either lost contact with the project or in some way detached, it will create a new computer the next time you attach. But I have noticed that these Phantoms just appear. My system is humming along and then suddenly I start seeing these WUs that are not on my machine. When I check the PP@H site, sure enough I will have a new phantom computer. Now at PP@H the fix is to merge the phantoms with the real computer. But on E@H there is something else going on. the symptoms are the same except I do not see any phantom computers, so I have no way to fix it.
I have read that there is a bug in BOINC that is causing this somehow in the upload download cycle for E@H, but it seems to me that if that were true I would see it happening on CP@H and S@H and I don't. I am hoping that one of the E@H guys will chime in with a "detailed" explanation of what is happening and how we can fix it.
I agree with you that all of this causes bad effects in our local processing and I would really like to fix it.
Regards
Phil
We Must look for intelligent life on other planets as,
it is becoming increasingly apparent we will not find any on our own.