|
1)
Message boards :
Number crunching :
Wrong applications sent to my computer?
(Message 27509)
Posted 8 Jun 2015 by Brian Priebe Post: Also, under BOINC Manager, "Projects", LHC@Home has not been added. Sounds like a carbon copy of what I just went through with a new workstation. The 'solution', kindly provided by Harri Liljeroos, was to join Einstein@Home first. Whatever that process did allowed me to join LHC@Home successfully afterward. |
|
2)
Message boards :
Number crunching :
Cannot Join New Host for Existing Account?
(Message 27496)
Posted 4 Jun 2015 by Brian Priebe Post: Thanks very much for this heads-up. That is the most bizarre thing I've ever heard. And it works! Join Einstein@Home first then join LHC@Home. |
|
3)
Message boards :
Number crunching :
Cannot Join New Host for Existing Account?
(Message 27491)
Posted 3 Jun 2015 by Brian Priebe Post: FYI, there is no such subdirectory. |
|
4)
Message boards :
Number crunching :
Cannot Join New Host for Existing Account?
(Message 27487)
Posted 30 May 2015 by Brian Priebe Post: 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. |
|
5)
Message boards :
Number crunching :
Cannot Join New Host for Existing Account?
(Message 27484)
Posted 29 May 2015 by Brian Priebe Post: 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). |
|
6)
Message boards :
Number crunching :
Cannot Join New Host for Existing Account?
(Message 27483)
Posted 29 May 2015 by Brian Priebe Post: 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. |
|
7)
Message boards :
Number crunching :
Cannot Join New Host for Existing Account?
(Message 27481)
Posted 29 May 2015 by Brian Priebe Post: I am a practiced finger-fumbler :). But in this case I neither mistyped, nor misremembered, my email and password. |
|
8)
Message boards :
Number crunching :
Cannot Join New Host for Existing Account?
(Message 27478)
Posted 26 May 2015 by Brian Priebe Post: 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>' |
|
9)
Message boards :
Number crunching :
Cannot Join New Host for Existing Account?
(Message 27476)
Posted 26 May 2015 by Brian Priebe Post: 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... |
|
10)
Message boards :
Number crunching :
Cannot Join New Host for Existing Account?
(Message 27473)
Posted 23 May 2015 by Brian Priebe Post: 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> |
|
11)
Message boards :
Number crunching :
Cannot Join New Host for Existing Account?
(Message 27471)
Posted 23 May 2015 by Brian Priebe Post: 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? |
|
12)
Message boards :
Number crunching :
Sixtrack has heartbeat failure -- hangs
(Message 26849)
Posted 4 Oct 2014 by Brian Priebe Post: And thanks for the prompt reaction to push things back towards the "normal" direction. |
|
13)
Message boards :
Number crunching :
Sixtrack has heartbeat failure -- hangs
(Message 26844)
Posted 4 Oct 2014 by Brian Priebe Post: We are seeing many many disk limit exceeded so maybe SixTrack is in Just checked all the slot directories. Total disk usage for any of them is between 335MB and 415MB. These WUs appear to have the new 500MB disk space limit per BOINC_TASK_STATE.XML. |
|
14)
Message boards :
Number crunching :
Sixtrack has heartbeat failure -- hangs
(Message 26843)
Posted 4 Oct 2014 by Brian Priebe Post: Tasks checkpoint to disk at most every 600 seconds Did this several years ago across the BOINC form. The disks were threatening to melt :). |
|
15)
Message boards :
Number crunching :
Sixtrack has heartbeat failure -- hangs
(Message 26842)
Posted 4 Oct 2014 by Brian Priebe Post: SIXTRACK is definitely in a loop. These handful of WUs have been restarting themselves at intervals all night. The BOINC error log is littered with reports of the form below. I will have to reset I guess... 04-Oct-2014 01:43:22 | LHC@home 1.0 | Task w-b3_16000_job.HLLHC_b3_16000.0732__30__s__62.31_60.32__15_17__5__35.2942_1_sixvf_boinc7819_1 exited with zero status but no 'finished' file 04-Oct-2014 01:43:22 | LHC@home 1.0 | If this happens repeatedly you may need to reset the project. 04-Oct-2014 01:43:22 | LHC@home 1.0 | Task w-b3_14000_job.HLLHC_b3_14000.0732__27__s__62.31_60.32__17_19__5__10.5883_1_sixvf_boinc7103_0 exited with zero status but no 'finished' file 04-Oct-2014 01:43:22 | LHC@home 1.0 | If this happens repeatedly you may need to reset the project. 04-Oct-2014 01:43:22 | LHC@home 1.0 | Task w-b3_10000_job.HLLHC_b3_10000.0732__28__s__62.31_60.32__17_19__5__17.6471_1_sixvf_boinc7367_1 exited with zero status but no 'finished' file 04-Oct-2014 01:43:22 | LHC@home 1.0 | If this happens repeatedly you may need to reset the project. 04-Oct-2014 01:43:22 | LHC@home 1.0 | Task w-b3_18000_job.HLLHC_b3_18000.0732__13__s__62.31_60.32__13_15__5__21.1765_1_sixvf_boinc3514_0 exited with zero status but no 'finished' file 04-Oct-2014 01:43:22 | LHC@home 1.0 | If this happens repeatedly you may need to reset the project. 04-Oct-2014 01:43:22 | LHC@home 1.0 | Task w-b3_18000_job.HLLHC_b3_18000.0732__13__s__62.31_60.32__13_15__5__19.4118_1_sixvf_boinc3513_0 exited with zero status but no 'finished' file 04-Oct-2014 01:43:22 | LHC@home 1.0 | If this happens repeatedly you may need to reset the project. 04-Oct-2014 01:43:22 | LHC@home 1.0 | Task w-b3_18000_job.HLLHC_b3_18000.0732__13__s__62.31_60.32__13_15__5__14.1177_1_sixvf_boinc3510_1 exited with zero status but no 'finished' file 04-Oct-2014 01:43:22 | LHC@home 1.0 | If this happens repeatedly you may need to reset the project. 04-Oct-2014 01:43:22 | LHC@home 1.0 | Task w-b3_8000_job.HLLHC_b3_8000.0732__27__s__62.31_60.32__11_13__5__84.7061_1_sixvf_boinc6955_0 exited with zero status but no 'finished' file 04-Oct-2014 01:43:22 | LHC@home 1.0 | If this happens repeatedly you may need to reset the project. 04-Oct-2014 01:43:22 | LHC@home 1.0 | Task w-b3_8000_job.HLLHC_b3_8000.0732__27__s__62.31_60.32__11_13__5__17.6471_1_sixvf_boinc6917_0 exited with zero status but no 'finished' file 04-Oct-2014 01:43:22 | LHC@home 1.0 | If this happens repeatedly you may need to reset the project. 04-Oct-2014 01:43:22 | LHC@home 1.0 | Task w-b3_8000_job.HLLHC_b3_8000.0732__27__s__62.31_60.32__17_19__5__3.52942_1_sixvf_boinc7059_0 exited with zero status but no 'finished' file 04-Oct-2014 01:43:22 | LHC@home 1.0 | If this happens repeatedly you may need to reset the project. 04-Oct-2014 01:43:22 | LHC@home 1.0 | Task w-b3_8000_job.HLLHC_b3_8000.0732__27__s__62.31_60.32__15_17__5__88.2355_1_sixvf_boinc7057_0 exited with zero status but no 'finished' file 04-Oct-2014 01:43:22 | LHC@home 1.0 | If this happens repeatedly you may need to reset the project. 04-Oct-2014 01:43:22 | LHC@home 1.0 | Task w-b3_8000_job.HLLHC_b3_8000.0732__27__s__62.31_60.32__15_17__5__37.0589_1_sixvf_boinc7028_0 exited with zero status but no 'finished' file 04-Oct-2014 01:43:22 | LHC@home 1.0 | If this happens repeatedly you may need to reset the project. 04-Oct-2014 01:43:22 | LHC@home 1.0 | Task w-b3_8000_job.HLLHC_b3_8000.0732__27__s__62.31_60.32__15_17__5__17.6471_1_sixvf_boinc7017_1 exited with zero status but no 'finished' file 04-Oct-2014 01:43:22 | LHC@home 1.0 | If this happens repeatedly you may need to reset the project. |
|
16)
Message boards :
Number crunching :
Sixtrack has heartbeat failure -- hangs
(Message 26827)
Posted 4 Oct 2014 by Brian Priebe Post: A number of recent WUs processed to 90%+ then hung with time remaining showing "---". The SIXTRACK executable is showing as still running but not consuming any CPU time. STDERR.TXT in the various slot directories all shows reports that the heartbeat was not detected. If you shut down BOINC and restart it, the process will restart from the last checkpoint then do exactly the same thing all over again. 00:04:04 (11060): No heartbeat from client for 30 sec - exiting 01:11:10 (4228): No heartbeat from client for 30 sec - exiting 01:43:52 (8532): No heartbeat from client for 30 sec - exiting 01:49:31 (8276): No heartbeat from client for 30 sec - exiting This has happened to the following WUs so far: w-b3_6000_job.HLLHC_b3_6000.0732__26__s__62.31_60.32__13_15__5__35.2942_1_sixvf_boinc6769_1 w-b3_16000_job.HLLHC_b3_16000.0732__30__s__62.31_60.32__15_17__5__35.2942_1_sixvf_boinc7819_1 w-b3_10000_job.HLLHC_b3_10000.0732__28__s__62.31_60.32__17_19__5__17.6471_1_sixvf_boinc7367_1 w-b3_18000_job.HLLHC_b3_18000.0732__13__s__62.31_60.32__13_15__5__21.1765_1_sixvf_boinc3514_0 w-b3_18000_job.HLLHC_b3_18000.0732__13__s__62.31_60.32__13_15__5__19.4118_1_sixvf_boinc3513_0 |
|
17)
Message boards :
Number crunching :
Error while Computing
(Message 26779)
Posted 3 Oct 2014 by Brian Priebe Post: I am starting to see a fairly large number of Error while Computing task failures. So am I. Now nearly 45% of all tasks. This is a massive waste of computing resources. Time for No New Tasks... |
©2024 CERN