Message boards :
Number crunching :
Another 'Sorry' thread (should we sticky one?)
Message board moderation
Author | Message |
---|---|
Woodgie Send message Joined: 6 Dec 99 Posts: 134 Credit: 89,630,417 RAC: 55 |
An apology to anyone relying on Hermes (6376517) to validate workunits but last night I did a dumb thing and updated BOINC. Hermes is a an old Mac OS X 10.6.8 Mac Mini (CoreDuo) and really didn't like BOINC 7.4.36 (couldn't start the daemon etc.) So I RTFM and rolled back to 7.2.42. The problem is, in rolling back I went and deleted the workunits it was crunching. Live and learn, huh? (also, 'stop and think' would have helped...) Sorry about that. ~W |
HAL9000 Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57 |
What is there to be sorry about? The previous work was flagged as Abandoned. Looks like all of that work has already gone out to a 3rd host to be processed with a few already returning their results. SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ |
Link Send message Joined: 18 Sep 03 Posts: 834 Credit: 1,807,369 RAC: 0 |
What is there to be sorry about? That's what I also ask myself every time I see such a "sorry thread". Shit happens. |
JanniCash Send message Joined: 17 Nov 03 Posts: 57 Credit: 1,276,920 RAC: 0 |
I think there is a slight difference between aborting (manually or automatic) tasks and leaving them hanging "in progress". In the former case they are reassigned to another system in a timely fashion. In the latter case they need to time out, which takes considerable time. I created one of those "in progress" hanging tasks myself by destroying a test VM before cleaning out the task list. Is there any way to abort that or is it better to just wait? http://setiathome.berkeley.edu/workunit.php?wuid=1657323561 |
HAL9000 Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57 |
I think there is a slight difference between aborting (manually or automatic) tasks and leaving them hanging "in progress". In the former case they are reassigned to another system in a timely fashion. In the latter case they need to time out, which takes considerable time. You could create a new VM with the same configuration and machine name. Then merge the two hosts. Once merged the new host would get the old task as a resend. Which could then be aborted. Or you can just let it time out. Which is normally what I do. As the merging of hosts is never guaranteed. SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ |
JanniCash Send message Joined: 17 Nov 03 Posts: 57 Credit: 1,276,920 RAC: 0 |
You could create a new VM with the same configuration and machine name. Then merge the two hosts. I'll give that a try. Since the original one that create the problem was a test deployment of an OVF template, this may actually work. Unless the MAC address of the machine is somehow part of the host identity. Thanks! |
JanniCash Send message Joined: 17 Nov 03 Posts: 57 Credit: 1,276,920 RAC: 0 |
You could create a new VM with the same configuration and machine name. Then merge the two hosts. It automagically merged the host and abandoned the taks. All good now. Thanks again. |
Woodgie Send message Joined: 6 Dec 99 Posts: 134 Credit: 89,630,417 RAC: 55 |
It automagically merged the host and abandoned the taks. All good now. This is what appears to have happened with Hermes. I was a bit confused when HAL9000 pointed out they'd been abandoned as I hadn't abandoned them, just deleted them from the machine. So they'll be re-assigned in a timely fashion, good. All's well that ends well then? ~W |
HAL9000 Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57 |
It automagically merged the host and abandoned the taks. All good now. I think the task status of "Abandoned" is a server side abort vs when you select Abort from the client the task status will be "Aborted by user". however knowing BOINC there could be 37 different triggers for those task status. SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.