I also see as well. And I don't throttle. Isn't this basically the "no heartbeat" message in a different format? I've never found a resolution to this.
Actually, I think your problem is a different one still:
This is all about not being able to get the S5R3 (!!) app files.
Strange...Did you use the "dual run" app_info.xml file posted in this forum, but maybe forgot to download the apps in question? Do you have an app_info.xml file installed? Does the problem persist if you remove it?
CU
Bikeman
Yeah, I tried running dual, but really messed it up. So I detached and reattached to the project. I get this message on both Einstein and CPDN units.
If you press the "Update" button in BOINC manager while E@H is selected in the projects window (in advanced view), the result files would be uploaded for us to see. Currently only the "Download error units" are visible in the database.
Well, it's been running for about 28 hr 28 min, 78.871% complete from a BOINC Mgr view with about 7 hr 38 min to completion. BOINC LogX thinks it has about 8 hrs 55 min left to go. I'm running a HT machine so I have an Einstein unit paired up with a CPDN unit. There's been some pauses on the Einstein to push through a few SETI units. I've seen this message pop up more than once on each of the projects over the past few days. When I was doing some testing for SETI Astropulse and suspending everything except that one wu, then I didn't notice getting that message. But I hate having to run that way. I don't mind if it takes a bit longer to do the work, especially since it seems that in most cases the wu's do validate. It's just a bit aggravating seeing those messages when I know the proposed solution doesn't change a thing. In the older versions of the BOINC Mgr, it was labeled as the no heartbeat message.
Thanks Jord. Didn't think I was alpha though... But maybe I am???? ;-)
I saw this on 5.10.45 and now seeing it on 6.2.14 (which I had loaded in that brief moment in time that it was an official version). I can't track down the messages to anything else on the machine (scans, etc). It may happen once a day per project. But then again, it may go a few days without me seeing it.
Also, looking at the OP's messages, I don't see it nearly that frequently on mine. Basically, I'll see it then I'll see the restart, then a few hours or so later, I'll see the wu complete.
Thanks Jord. Didn't think I was alpha though... But maybe I am???? ;-)
If you mean about the PM, it's just so he doesn't get any emails... ;-)
Quote:
Also, looking at the OP's messages, I don't see it nearly that frequently on mine. Basically, I'll see it then I'll see the restart, then a few hours or so later, I'll see the wu complete.
Frequent enough if you see it happen more than once, or at least once per task. More than I see it at least.
...It may happen once a day per project. But then again, it may go a few days without me seeing it...
Do you happen to use Internet time servers to automatically adjust your PC time? If so, just ignore the messages. It's not a project specific problem, it's caused by boinc's heartbeat mechanism to check if the application is still working. If it doesn't respond for longer than 30 seconds, boinc assumes that it's "dead" and drops the process. Unfortunately, that also happens when the PC clock is adjusted in the "wrong" direction. Just yesterday I saw this happen to einstein and seti simultaneously. It occurred exactly when the PC clock was adjusted, so I ignored it.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
Here's a link to the wu 104183560. It finally finished.
Gundolf - yes, I do have my machine set up to synch for time. Looks like I'm using time.windows.com instead of using time.nist.gov. And it's scheduled to happen once a week. I don't think the timing of the corresponds to what I'm seeing in messages (because it happened on different days - like 24 hrs later). Digging through the messages, it looks like it happened on Saturday, Sunday and Monday. But I haven't seen it resurface since.
Guess I won't worry about it. But I've noticed on several boards that people are seeing this.
RE: RE: I also see as
)
Yeah, I tried running dual, but really messed it up. So I detached and reattached to the project. I get this message on both Einstein and CPDN units.
Wendy
Check the BOINC Wiki for help
I see. If you press the
)
I see.
If you press the "Update" button in BOINC manager while E@H is selected in the projects window (in advanced view), the result files would be uploaded for us to see. Currently only the "Download error units" are visible in the database.
CU
Bikeman
result still has about 7 hrs
)
result still has about 7 hrs to go before it's finished....
Wendy
Check the BOINC Wiki for help
RE: result still has about
)
Oh, so it's running fine now ... ok, I'll keep my fingers crossed.
CU
Bikeman
Well, it's been running for
)
Well, it's been running for about 28 hr 28 min, 78.871% complete from a BOINC Mgr view with about 7 hr 38 min to completion. BOINC LogX thinks it has about 8 hrs 55 min left to go. I'm running a HT machine so I have an Einstein unit paired up with a CPDN unit. There's been some pauses on the Einstein to push through a few SETI units. I've seen this message pop up more than once on each of the projects over the past few days. When I was doing some testing for SETI Astropulse and suspending everything except that one wu, then I didn't notice getting that message. But I hate having to run that way. I don't mind if it takes a bit longer to do the work, especially since it seems that in most cases the wu's do validate. It's just a bit aggravating seeing those messages when I know the proposed solution doesn't change a thing. In the older versions of the BOINC Mgr, it was labeled as the no heartbeat message.
Make sense?
Wendy
Check the BOINC Wiki for help
I sent off the problem to the
)
I sent off the problem to the developers and the BOINC alpha email list.
David just answered:
So, if you're an alpha, git. ;-)
Thanks Jord. Didn't think I
)
Thanks Jord. Didn't think I was alpha though... But maybe I am???? ;-)
I saw this on 5.10.45 and now seeing it on 6.2.14 (which I had loaded in that brief moment in time that it was an official version). I can't track down the messages to anything else on the machine (scans, etc). It may happen once a day per project. But then again, it may go a few days without me seeing it.
Also, looking at the OP's messages, I don't see it nearly that frequently on mine. Basically, I'll see it then I'll see the restart, then a few hours or so later, I'll see the wu complete.
Wendy
Check the BOINC Wiki for help
RE: Thanks Jord. Didn't
)
If you mean about the PM, it's just so he doesn't get any emails... ;-)
Frequent enough if you see it happen more than once, or at least once per task. More than I see it at least.
RE: ...It may happen once a
)
Do you happen to use Internet time servers to automatically adjust your PC time? If so, just ignore the messages. It's not a project specific problem, it's caused by boinc's heartbeat mechanism to check if the application is still working. If it doesn't respond for longer than 30 seconds, boinc assumes that it's "dead" and drops the process. Unfortunately, that also happens when the PC clock is adjusted in the "wrong" direction. Just yesterday I saw this happen to einstein and seti simultaneously. It occurred exactly when the PC clock was adjusted, so I ignored it.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
Here's a link to the wu
)
Here's a link to the wu 104183560. It finally finished.
Gundolf - yes, I do have my machine set up to synch for time. Looks like I'm using time.windows.com instead of using time.nist.gov. And it's scheduled to happen once a week. I don't think the timing of the corresponds to what I'm seeing in messages (because it happened on different days - like 24 hrs later). Digging through the messages, it looks like it happened on Saturday, Sunday and Monday. But I haven't seen it resurface since.
Guess I won't worry about it. But I've noticed on several boards that people are seeing this.
Wendy
Check the BOINC Wiki for help