Something odd just happened. LHC@home has renamed my CPDN project to LHC. My work unit is still there and running at the moment, but it\'s showing as a LHC project. It seems to have happened when LHC DL\'ed new work. It looks like it came in as lots of small parts that were combined into a couple WU\'s. I would copy what all it said, except.... I closed and reopened BOINC in the vain hope of getting it to reset itself correctly.

Also, CP had just sent in a trickle, but I am not sure about the timing on all these things.


Any ideas?
BOINC v 4.09
Win XP home
Intel P4 1.6 Ghz (Dell)

Eric
XY

OK, that was weird. I hit update project on the CPDN listing (which was showing as a second LHC listing) and it seems to have returned to normal.

Eric
XY

Look at this post:

<a href="http://climateapps2.oucs.ox.ac.uk/cpdnboinc/forum_thread.php?id=877&amp;PHPSESSID=8840bbb83977d1664dff4698de029584">Yikes! Cross project Contamination... </a>

It appears that maybe LHC admins are not as experienced at tweaking their BOINC servers. Your best bet is probably checking out LHC's forums for possible solutions.

<A HREF="http://lhcathome.cern.ch/forum_thread.php?id=414">LHC Cloobers CPDN</a>

<A HREF="http://www.geocities.com/dlihooya/logo/logo.htm"><IMG SRC="http://boinc.mundayweb.com/cpdn/stats.php?userID=64&amp;trans=off"></A>

You are lucky...

Update did nothing for me. I ended up resetting everything. :(

<a href="http://www.boinc.dk/index.php?page=user_statistics&amp;project=cpdn&amp;userid=355"><img border="0" height="80" src="http://355.cpdn.sig.boinc.dk?188"></a>

&gt; It appears that maybe LHC admins are not as experienced at tweaking their
&gt; BOINC servers. Your best bet is probably checking out LHC's forums for
&gt; possible solutions.

HeHe... Don't bother. They don't know what happened, and are saying it looks like a Core Client issue.

&gt; &gt; It appears that maybe LHC admins are not as experienced at tweaking
&gt; their
&gt; &gt; BOINC servers. Your best bet is probably checking out LHC's forums for
&gt; &gt; possible solutions.
&gt;
&gt; HeHe... Don't bother. They don't know what happened, and are saying it looks
&gt; like a Core Client issue.

Good to know. Funny this happens right after LHC came out with new applications/validator. I just reset LHC just in case until this is resolved.

<A HREF="http://www.geocities.com/dlihooya/logo/logo.htm"><IMG SRC="http://boinc.mundayweb.com/cpdn/stats.php?userID=64&amp;trans=off"></A>

&gt; &gt; &gt; It appears that maybe LHC admins are not as experienced at tweaking
&gt; &gt; their
&gt; &gt; &gt; BOINC servers. Your best bet is probably checking out LHC's forums
&gt; for
&gt; &gt; &gt; possible solutions.
&gt; &gt;
&gt; &gt; HeHe... Don't bother. They don't know what happened, and are saying it
&gt; looks
&gt; &gt; like a Core Client issue.
&gt;
&gt; Good to know. Funny this happens right after LHC came out with new
&gt; applications/validator. I just reset LHC just in case until this is
&gt; resolved.
&gt;
The BOINC developers believe that they have found the issue, and are working on a fix.
<a href="http://www.boinc.dk/index.php?page=user_statistics&amp;project=cpdn&amp;userid=13"><img border="0" height="80" src="http://13.cpdn.sig.boinc.dk?188"></a>

I posted this at SETI@home and LHC@home:

&gt; Argh! First one machine got nailed with this and now I've seen a second
&gt; machine fall prey to this bug. It's definitely a problem in the core client

Now, that said, this is all really easy to fix. And, yes, I mean really easy. A couple of minutes with the editor of your choice and your projects will be back to normal. Here's how to fix it:

1) Close BOINC
2) Make back-up copies of all your XML files to a safe directory
3) Open all account_*.xml files and edit the project name so that it is appropriate to the project URL
4) Open client_state.xml. Scroll through the file. Change your project name(s) that you corrected in the account files to match the URLs here, too. Note that the XML file contains project tags for each project. When you find an affected project, you'll see that there is app and file data that is inconsistent with that project. Delete these entries (including tags) from the file. Don't be shy (you made back-ups, right?) -- you can do it again in case you mess something up. Besides, your editor has undo.
5) Delete suspect files from incorrect project directories
6) Restart BOINC
7) It *might* be necessary to detach an orphan project. In my first attempt, I somehow wound up with an extra LHC@home on one machine. It showed 0 results, so I just detached it. My valid LHC@home entry remains fine.

I've fixed two machines so far and both are working fine now. LHC@home seems to be offering valid work again, so maybe the hiccoughs are short-lived. I'll check (and maybe fix) my third LHC@home-enabled machine as soon as the GUI un-freezes (it's a dual that's only got work for one slot at the moment).

I hope this helps, people. Click "It answered my question" now. ;)

trane