LHC@home

I attempted to add a new workstation to this project. For my trouble, the BOINC Event Log shows:

Fetching configuration file from http://lhcathomeclassic.cern.ch/sixtrack/get_project_config.php

Project name does not yet show up in the list of attached BOINC projects. No files are being downloaded.

Any ideas?

We are having a look....Eric.

---

Apparently the get_project_config.xml was downloaded into the BOINC data directory but the process stalled there.

<?xml version="1.0" encoding="ISO-8859-1"?>
<project_config>
<name>LHC@home 1.0</name>
<master_url>http://lhcathomeclassic.cern.ch/sixtrack/</master_url>
<web_rpc_url_base>http://lhcathomeclassic.cern.ch/sixtrack/</web_rpc_url_base>
<local_revision>26051M</local_revision>
<web_stopped>0</web_stopped>
<min_passwd_length>6</min_passwd_length>
<sched_stopped>0</sched_stopped>
<platforms>
<platform>
<platform_name>i686-pc-linux-gnu</platform_name>
<user_friendly_name>Linux running on an Intel x86-compatible CPU</user_friendly_name>
</platform>
<platform>
<platform_name>i686-pc-linux-gnu</platform_name>
<user_friendly_name>Linux running on an Intel x86-compatible CPU</user_friendly_name>
<plan_class>pni</plan_class>
</platform>
<platform>
<platform_name>i686-pc-linux-gnu</platform_name>
<user_friendly_name>Linux running on an Intel x86-compatible CPU</user_friendly_name>
<plan_class>sse2</plan_class>
</platform>
<platform>
<platform_name>i686-pc-linux-gnu</platform_name>
<user_friendly_name>Linux running on an Intel x86-compatible CPU</user_friendly_name>
<plan_class>sse3</plan_class>
</platform>
<platform>
<platform_name>windows_intelx86</platform_name>
<user_friendly_name>Microsoft Windows (98 or later) running on an Intel x86-compatible CPU</user_friendly_name>
</platform>
<platform>
<platform_name>windows_intelx86</platform_name>
<user_friendly_name>Microsoft Windows (98 or later) running on an Intel x86-compatible CPU</user_friendly_name>
<plan_class>pni</plan_class>
</platform>
<platform>
<platform_name>windows_intelx86</platform_name>
<user_friendly_name>Microsoft Windows (98 or later) running on an Intel x86-compatible CPU</user_friendly_name>
<plan_class>sse2</plan_class>
</platform>
<platform>
<platform_name>windows_intelx86</platform_name>
<user_friendly_name>Microsoft Windows (98 or later) running on an Intel x86-compatible CPU</user_friendly_name>
<plan_class>sse3</plan_class>
</platform>
<platform>
<platform_name>windows_x86_64</platform_name>
<user_friendly_name>Microsoft Windows running on an AMD x86_64 or Intel EM64T CPU</user_friendly_name>
</platform>
<platform>
<platform_name>windows_x86_64</platform_name>
<user_friendly_name>Microsoft Windows running on an AMD x86_64 or Intel EM64T CPU</user_friendly_name>
<plan_class>pni</plan_class>
</platform>
<platform>
<platform_name>windows_x86_64</platform_name>
<user_friendly_name>Microsoft Windows running on an AMD x86_64 or Intel EM64T CPU</user_friendly_name>
<plan_class>sse2</plan_class>
</platform>
<platform>
<platform_name>windows_x86_64</platform_name>
<user_friendly_name>Microsoft Windows running on an AMD x86_64 or Intel EM64T CPU</user_friendly_name>
<plan_class>sse3</plan_class>
</platform>
<platform>
<platform_name>x86_64-pc-linux-gnu</platform_name>
<user_friendly_name>Linux running on an AMD x86_64 or Intel EM64T CPU</user_friendly_name>
</platform>
<platform>
<platform_name>x86_64-pc-linux-gnu</platform_name>
<user_friendly_name>Linux running on an AMD x86_64 or Intel EM64T CPU</user_friendly_name>
<plan_class>pni</plan_class>
</platform>
<platform>
<platform_name>x86_64-pc-linux-gnu</platform_name>
<user_friendly_name>Linux running on an AMD x86_64 or Intel EM64T CPU</user_friendly_name>
<plan_class>sse2</plan_class>
</platform>
<platform>
<platform_name>x86_64-pc-linux-gnu</platform_name>
<user_friendly_name>Linux running on an AMD x86_64 or Intel EM64T CPU</user_friendly_name>
<plan_class>sse3</plan_class>
</platform>
</platforms>
<ldap_auth/>
</project_config>

Thanks for the help; passed to admins. Eric.

---

Local admins say our side looks OK....
Say it should be a problem on your/client side.
Eric.

---

Well out of the six projects I frequent, this is the only one it won't join. I tried disabling antivirus and firewall with no joy...

Sorry about that; I'll try my "support" again......
Eric.

---

OK. I enabled all possible debug flags and tried joining again. Among the megabytes of garbage dumped on the screen is the following interesting-looking verbiage (the "***REMOVED***" is my editing). Note that when I attempt to join the project, I am using the "Existing User" option and specifying both my email address and password. Why it doesn't pass along my e-mail address in the lookup account request is beyond me.

26-May-2015 10:58:51 | | [gui_rpc] GUI RPC Command = '<boinc_gui_rpc_request><lookup_account> <url>http://lhcathomeclassic.cern.ch/sixtrack/</url> <email_addr></email_addr> <passwd_hash>***REMOVED***</passwd_hash> <ldap_auth>1</ldap_auth></lookup_account></boinc_gui_rpc_request>'
26-May-2015 10:58:51 | | [gui_rpc] GUI RPC reply: '<boinc_gui_rpc_reply><error>missing URL, email address, or password</error></boinc_gui_rpc_reply>'
26-May-2015 10:58:51 | | [gui_rpc] GUI RPC Command = '<boinc_gui_rpc_request><lookup_account_poll/></boinc_gui_rpc_request>'
26-May-2015 10:58:51 | | [gui_rpc] GUI RPC reply: '<boinc_gui_rpc_reply></boinc_gui_rpc_reply>'
26-May-2015 10:58:51 | | [gui_rpc] GUI RPC Command = '<boinc_gui_rpc_request><project_attach> <project_url>http://lhcathomeclassic.cern.ch/sixtrack/</project_url> <authenticator></authenticator> <project_name>LHC@home 1.0</project_name></project_attach></boinc_gui_rpc_request>'
26-May-2015 10:58:51 | | [gui_rpc] GUI RPC reply: '<boinc_gui_rpc_reply><error>Missing authenticator</error></boinc_gui_rpc_reply>'
26-May-2015 10:58:52 | | [gui_rpc] GUI RPC Command = '<boinc_gui_rpc_request><project_attach_poll/></boinc_gui_rpc_request>'
26-May-2015 10:58:52 | | [gui_rpc] GUI RPC reply: '<boinc_gui_rpc_reply><project_attach_reply> <error_num>0</error_num></project_attach_reply></boinc_gui_rpc_reply>'

OK; it turns out my admins are away (I found out the
hard way). Maybe we shall get some other advice or I'll
check again next week. Thanks for your perseverance! Eric.

---

edit: (Ok I just looked at your copy and I guess you are using the correct URL for LHC.......it did change a while back but you have the current one)

It is acting like you typed an error with either the email account or password.

Never seen that happen here unless it was a typo.

---

Volunteer Mad Scientist For Life

I am a practiced finger-fumbler :). But in this case I neither mistyped, nor misremembered, my email and password.

I am a practiced finger-fumbler :). But in this case I neither mistyped, nor misremembered, my email and password.

I reinstalled BOINC from scratch on that workstation. The 2nd time around, I get exactly the same thing as before.

For good measure, I just tried detaching another machine and tried to rejoin the project. It had no difficulty rejoining.

So whatever this is, it's related to the new workstation.

Further information... On the workstation that successfully rejoined the project, the lookup_account it sent was substantially different. The e-mail address was filled in and the password hash was NOT clear text (that I edited out in my report posted here).

Is this a Linux OS on a X86 ?



(or Windows like your other hosts)

Is this a clean installed OS on this host or have you used it for other projects? (since I see you mentioned running other projects)

I remember back in 2011 where some malware or trojan was causing problems with T4T......not quite the same as this but who knows these days.

As I recall it had to be scanned by a few different programs before it was found and fixed (I think it was causing problems with the Oracle VB there)

But if you have been able to already install projects like Atlas or vLHC and run them but not LHC......THAT makes no sense at all

---

Volunteer Mad Scientist For Life

It's Windows 7 SP1 just like all the other machines (except 1) I have running this project. It's currently running 5 other BOINC projects without any difficulty. Only joining LHC@HOME is a problem.

If there's a Trojan installed, it came straight from HP with their pre-installed OS.

Sorry Brian, my support reports:

"The problem reported by the user is not a server or BOINC service issue, as we cannot reproduce it. (I just successfully added a new computer with the BOINC client to Sixtrack.)"

I hope you get it sorted. Eric.

---

Hi Brian,
This might not work but might be worth a try:
Have a look in ProgramData/Boinc/Projects to see if there is a folder called lhcathomeclassic.cern.ch_sixtrack which should be there if your machine is attached but shouldn't be there if it's not. Something may have gotten corrupted in there on the first attempt and the debris isn't letting the attachment proceed. Delete it and try to attach again to see if it fixes the blockage. (The ProgramData folder is hidden so you might have to unhide it first)
Hope that's helpful.

FYI, there is no such subdirectory.

I just had the same happen to me when tried to add LHC to a new win 7 laptop. I used BOINC 7.4.42 64 bit and tried to add LHC as the first project without success. No error messages and nothing. This was from Boinc Manager.

Then I installed Efmer BoincTasks and attached first to Einstein@home successfully and then to LHC using BoincTasks. Now LHC attached just fine. So I was able to circumvent the problem. Which one did the trick, BoincTasks or attaching to Einstein first, I don' know.

---