Posts by solverworld

1) Message boards : BOINC client : Getting same hostid with different EC2 instances (Message 76205)
Posted 1 Mar 2017 by solverworld
Post:
Thanks, I think the problem was that I did not completely remove the hostid references, so the new instance started with the previous hostid. There is a file int the boinc/spot directory that contains the cpid/hostid that I needed to remove.

So, following HAL9000's advices, for future reference, here is what worked for me:

1. Turn off the autostart of boinc; stop boinc from running
2. Remove all xml files with reference to hostid and host_cpid - including client_state.xml, slots/?/init_data.xml. Used 'grep -r hostid' to find all references.
3. Create a new AMI from the AWS console from that instance.
4. Launch a new spot request of whatever size instance at a good price. Make sure to select 'do not delete on termination' and 'persistent request'. The persistent request allows the instance to be brought back if it gets terminated when the spot prices goes above your bid price and then goes back down. There are 2 ways to do a spot request, and it seems that selecting your AMI and then doing Actions->Spot request
let's you make a persistent request and makes it an instance request, rather than a fleet request.
5. ssh into the new instance and perform /etc/init.d/boinc start (or whatever method you set up to start boinc). You should make it autostart if you plan on having it restart with price fluctuations:
$sudo chkconfig --add boinc
$sudo chkconfig boinc on.
6. It is possible that making boinc autostart in step 2 before making the AMI would be a better solution so that you do not have to do step 5, but I wanted to keep control for now.

Thanks
2) Message boards : BOINC client : Getting same hostid with different EC2 instances (Message 76185)
Posted 28 Feb 2017 by solverworld
Post:
Thanks.
How do I remove the configuration once it has been configured? Just delete the boinc user home directory (/var/lib/boinc)?
Or do a remove projects ("boinccmd --project www.primegrid.com detach")?

This could work, where I could create a first-time configure script that logs into an instance and attaches to a project that would persist over reboots. Since I plan on doing Spot Instances on Amazon, they might go away and come back based on spot pricing for instances.

Edit: I checked and the 2 machines have the same host_cpid, which is probably why they are getting the same hostid. The cpid is supposed to be based on a hash of IP address, among other things, and the 2 machines have different (internal and external) IP addresses, so not sure how they got the same cpid. Is it because it was assigned from the first AMI (when first configured) and never recalculated?
3) Message boards : BOINC client : Power consumption vs. Total credits for different platforms (Message 76171)
Posted 27 Feb 2017 by solverworld
Post:
Seems like a good comparison, assuming you calculated Watt-hours properly (5V times current times hours). Your USB power supplies are probably 80+ percent efficient. You could check with a kill-a-watt meter or similar device that would tell you the power drawn at the AC plug. Your power going into the phone is not exactly the power being used to process data - the difference is going into charging/discharging the battery - you might run the test long enough to be sure you aren't charging the battery (or discharging it).

I believe the numbers because ARM is a pretty efficient processor (and why Intel has had trouble getting into mobile device market), and your laptop is pretty old.
4) Message boards : BOINC client : Getting same hostid with different EC2 instances (Message 76170)
Posted 27 Feb 2017 by solverworld
Post:
I have created a Amazon AMI that starts up boinc and processes work. This works fine. The problem is that when I try to launch another instance with the same AMI (to double processing work), the new instance gets the same hostid as the previous one, which causes problems with aborted jobs, etc.

I have tried: stopping boinc using /etc/init.d/boinc and then deleting client_state.xml and other files that contain hostid. When boinc is restarted, it comes back with the same hostid.

I would really like a way of resetting all work to zero and preventing the client from getting new tasks, then making an AMI image from that such that each launch of a new instance from that image will get a new hostid and start getting new tasks to process.

I am working with www.primegrid.com if that makes a difference.



Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.