| Info | Message |
|---|---|
| 1) Message boards : Questions and problems : Host id duplicated on two computers
Message 19478 Posted 14 Aug 2008 by Matt |
I'm pretty sure I just copied the account_*.xml files. |
| 2) Message boards : Questions and problems : Host id duplicated on two computers
Message 18904 Posted 29 Jul 2008 by Matt |
Hi folks, Recently, I set up a diskless Linux machine to crunch WUs for 4 BOINC projects. I also have a server (also running Linux) doing the same. Both are running BOINC 5.10.45 (as I need a version that does not have a GUI). When I got the diskless machine set up, I installed BOINC on it, and copied my account_*.xml files from my server's installation to the new workstation (as opposed to running BOINC to attach them, because BOINC gave me a little bit of trouble/crashes last time). A side effect that I've noticed is that both computers got assigned the same host ID. This doesn't seem to be a problem for 3 of the 4 projects I'm working on...CPDN, on the other hand, declared the WU that the server was working on as "client detached". I guess the questions I would ask here are: a) Does "client detached" mean what I think it does -- e.g., the computer running the work unit is no longer associated with the project, and therefore all WUs assigned to it are no longer valid? b) Is this actually caused by two computers sharing a host ID? c) If so, what's the solution? |
| 3) Message boards : Questions and problems : High Priority Help
Message 18903 Posted 29 Jul 2008 by Matt |
Wow...nice to actually hear from someone working on CPDN. The intent here wasn't to have one computer crunch the same work unit for five years before returning it. The intent was to be able to allow these computers crunch work units for more than just CPDN. As I said, one computer had already gotten to the point where it was ONLY crunching CPDN units (and at high priority), the other one seemed to be going in that direction (seeing as it was slower than the first). I guess I just chose 5 years at random as a length of time that would have been likely to solve the problem -- which it did. Realistically, I probably should turn their due dates back to what they were, as the machine may have trouble finishing it by the actual due date without the extra workload. |
| 4) Message boards : Questions and problems : High Priority Help
Message 18806 Posted 24 Jul 2008 by Matt |
I also have this problem -- I have two slower Linux machines set up (slow = one is a Pentium-MMX 233MHz, the other is an AMD K6-2 300MHz). When I attach to them with my BOINC manager, it says "Running, high priority" on whatever task it's working on. Now, the explanation Sekerob makes sense -- I'm attached to climateprediction.net on both machines. One machine is stuck doing a CPDN work unit, and the other, since it's freshly set up, is heading there after it gets done with it's SETI@home work unit. I've heard (from this post) that CPDN doesn't care about going over your deadline, so here's what I did. I'd appreciate it if someone double-checked me on this. I went into client_state.xml, went down to the section that had my CPDN work unit, and went into the key labelled "report_deadline", and added 157788000 to the number that was there (5 years * 365.25 days per year * 24 hours per day * 60 minutes per hour * 60 seconds per minute = 157,788,000), and restarted BOINC. It seems to have worked, as the BOINC manager now shows the work unit due in 2014 (instead of 2009), and it immediately downloaded a new S@H work unit and started working on that...except that it immediately started running the S@H work unit as high priority... |
Copyright © 2025 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.