LHC@home

I have just spent about the last 6 hours straightening out my Accounts on all my Computers because it seems BURP was on the attack again and taking over all of the other Project Accounts ...

I managed to get everything straightened out again by getting rid of everything in the xml files that pertained to BURP and detaching all my computers from BURP ...

Sorry to say I had some major loss of WU's though, 2 CPDN WU's with about 200 hr's each done on them and 5 or 6 Pirate WU's waiting to be done. But I did manage to save and Report 15 finished Pirate WU's on 1 PC after I got it fixed again ... :)

> I have just spent about the last 6 hours straightening out my Accounts on all
> my Computers because it seems BURP was on the attack again and taking over all
> of the other Project Accounts ...
>
> I managed to get everything straightened out again by getting rid of
> everything in the xml files that pertained to BURP and detaching all my
> computers from BURP ...
>
> Sorry to say I had some major loss of WU's though, 2 CPDN WU's with about 200
> hr's each done on them and 5 or 6 Pirate WU's waiting to be done. But I did
> manage to save and Report 15 finished Pirate WU's on 1 PC after I got it fixed
> again ... :)

Which CC version are you using? It may be, that you have an outdated BOINC client (versions prior to 4.41 have caused such problems).

Happy crunching,

---

Which CC version are you using? It may be, that you have an outdated BOINC client (versions prior to 4.41 have caused such problems).
==========

All my problems began when I installed v4.44 on all my PC's, it started out with most of the Managers Freezing up after running a short while.

Then when I went back to v4.25 the Pirates, BURP & LHC Projects took turns taking over the other Accounts I was Attached to. I got it straightened out after 6 hr's of messing around with the xml files.

So far it hasn't happened again & I even re-installed v4.44 on just 1 PC this morning and it has run 5 hr's so far without freezing up ...

But the funny thing was as soon as I install the v4.44 the Pirates Project took over the LHC Account again, I fixed it right away & Pirates hasn't tried it again so far ... :/

What does "taking over the account" mean in this situation?

I'm sorry that you are experiencing problems while running BURP.

> What does "taking over the account" mean in this situation?
>
> I'm sorry that you are experiencing problems while running BURP.
==========

Janus, it means BURP either re-names an Account like LHC to BURP & re-names the LHC WU's to BURP WU's even though they are still LHC WU's. Then when you finish the newly re-named WU's from LHC or whatever Project you can't report them properly because the BOINC Manager doesn't recognize them as LHC WU's anymore & you can't get Credit for them either...

Also when a call goes in for more LHC or Pirate WU's the call gets routed through the BURP Project instead so you can't get anymore work either, I saw this in the xml files. The call was going out for more Pirate WU's but it was showing the call going through to the BURP Site instead of the Pirates Site.

Pirates@Home will do the same thing from time to time to the other Projects you are attached to. Heck, LHC@Home was even doing it for awhile ...

My 1 computer is still all screwed up & has been for 3 days now because of it. This morning I started deleting everything pertaining to BOINC on that Computer & going through the Registry getting rid of everything for BOINC. Hopefully by doing this it will straighten itself out ...

Ok, thank you.

At first glance it seems like a BOINC core client issue.
It will be looked into.

> > What does "taking over the account" mean in this situation?
> >
> > I'm sorry that you are experiencing problems while running BURP.
> ==========
>
> Janus, it means BURP either re-names an Account like LHC to BURP &
> re-names the LHC WU's to BURP WU's even though they are still LHC WU's. Then
> when you finish the newly re-named WU's from LHC or whatever Project you can't
> report them properly because the BOINC Manager doesn't recognize them as LHC
> WU's anymore & you can't get Credit for them either...
>
> Also when a call goes in for more LHC or Pirate WU's the call gets routed
> through the BURP Project instead so you can't get anymore work either, I saw
> this in the xml files. The call was going out for more Pirate WU's but it was
> showing the call going through to the BURP Site instead of the Pirates Site.
>
> Pirates@Home will do the same thing from time to time to the other Projects
> you are attached to. Heck, LHC@Home was even doing it for awhile ...
>
> My 1 computer is still all screwed up & has been for 3 days now because of
> it. This morning I started deleting everything pertaining to BOINC on that
> Computer & going through the Registry getting rid of everything for BOINC.
> Hopefully by doing this it will straighten itself out ...

You may be able to fix this more easily than that ...

Look in the client state XML file and look to see if the project name has been changed, if so, change it back. If there is more than one line in the scheduler list, delete all but the correct one. Restart BOINC ...

Here is what part of mine looked like when I was havnig trouble:

<project>
<master_url>http://einstein.phys.uwm.edu/</master_url>
<project_name>Einstein@Home</project_name>
<user_name>Paul D. Buck</user_name>
<team_name>Operation Einstein</team_name>
<user_total_credit>55565.766504</user_total_credit>
<user_expavg_credit>597.371863</user_expavg_credit>
<user_create_time>1106000202.000000</user_create_time>
<rpc_seqno>254</rpc_seqno>
<hostid>58618</hostid>
<host_total_credit>0.000000</host_total_credit>
<host_expavg_credit>0.000000</host_expavg_credit>
<host_create_time>0.000000</host_create_time>
<exp_avg_cpu>23351.044246</exp_avg_cpu>
<exp_avg_mod_time>1117059177.066874</exp_avg_mod_time>
<nrpc_failures>3</nrpc_failures>
<master_fetch_failures>0</master_fetch_failures>
<min_rpc_time>1117085812.090553</min_rpc_time>
<debt>0.000000</debt>
<resource_share>100.000000</resource_share>
<scheduler_url>http://predictor.scripps.edu/predictor_cgi/cgi</scheduler_url>
<scheduler_url>http://lhcathome-sched1.cern.ch/scheduler/cgi</scheduler_url>
<scheduler_url>http://predictor.scripps.edu/predictor_cgi/cgi</scheduler_url>
<scheduler_url>http://lhcathome-sched1.cern.ch/scheduler/cgi</scheduler_url>
<scheduler_url>http://lhcathome-sched1.cern.ch/scheduler/cgi</scheduler_url>
<scheduler_url>http://lhcathome-sched1.cern.ch/scheduler/cgi</scheduler_url>
<scheduler_url>http://lhcathome-sched1.cern.ch/scheduler/cgi</scheduler_url>
<scheduler_url>http://predictor.scripps.edu/predictor_cgi/cgi</scheduler_url>
<scheduler_url>http://lhcathome-sched1.cern.ch/scheduler/cgi</scheduler_url>
<scheduler_url>http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi</scheduler_url>
<code_sign_key>

---

You may be able to fix this more easily than that ...

Look in the client state XML file and look to see if the project name has been changed, if so, change it back. If there is more than one line in the scheduler list, delete all but the correct one. Restart BOINC ...
==========

Yup, I figured that out after fixing a few of my PC's the hard way Paul, I did that on the rest of them and it seemed to work ...

> Look in the client state XML file and look to see if the project name has been
> changed, if so, change it back. If there is more than one line in the
> scheduler list, delete all but the correct one. Restart BOINC ...

You don't even need to change the project name. All you need to do is make sure it has the correct scheduler URL. The next time it connects, the project name will be sorted out.

I saw this on the BURP news page.

"You are encouraged, although not forced, to upgrade your BOINC core client to version 4.41 or above - as this and later versions have several bugfixes aimed specifically at BURP."

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

Just had a similar problem, but it was the LHC account that dominated. My P4 2.8 cruncher, running 4.19 (yep I know it's old, but till now it was OK), with LHC, Einstein, CPDN and Predictor (no Burp). LHC had taken over the Predictor and CPDN settings.

A reset of the projects (with loss of WUs) solved it. Shame I didn't see the fix posted here to try first.

---