Welcome to MilkyWay@home

Posts by GlennG

1) Message boards : News : Running Modfit on MilkyWay@home (Message 64763)
Posted 27 Jun 2016 by GlennG
Post:
With the current change, it appears that most of my linux machines (80 processors total) are now unusable.

<core_client_version>6.10.58</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)
</message>
<stderr_txt>
../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_1.36_x86_64-pc-linux-gnu: /lib64/libc.so.6: version `GLIBC_2.8' not found (required by ../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_1.36_x86_64-pc-linux-gnu)
../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_1.36_x86_64-pc-linux-gnu: /lib64/libc.so.6: version `GLIBC_2.7' not found (required by ../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_1.36_x86_64-pc-linux-gnu)
../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_1.36_x86_64-pc-linux-gnu: /lib64/libc.so.6: version `GLIBC_2.11' not found (required by ../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_1.36_x86_64-pc-linux-gnu)

</stderr_txt>
]]>

In years past, when problems like this occurred, compiling with static libraries appeared to solve the problem at the expense of making the applications slightly bigger.

Glenn
2) Message boards : News : Separation updated to 1.00 (Message 52861)
Posted 8 Feb 2012 by GlennG
Post:
All my tasks are failing with the new app.

<core_client_version>6.10.58</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)
</message>
<stderr_txt>
../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_separation_1.00_x86_64-pc-linux-gnu: /lib64/libc.so.6: version `GLIBC_2.7' not found (required by ../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_separation_1.00_x86_64-pc-linux-gnu)

</stderr_txt>
]]>


Did the makefile for the app change, because this was not an issue before.

I realize that my glibc is older, but things worked before, and I am not in a position to update them at this time.

3) Message boards : Number crunching : All my units erroring out... (Message 51955)
Posted 13 Dec 2011 by GlennG
Post:
Matt,

I have reset my linux boxes, but still get the following. Have the linux apps been updated??

../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_0.84_x86_64-pc-linux-gnu__mt: /lib64/libc.so.6: version `GLIBC_2.7' not found (required by ../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_0.84_x86_64-pc-linux-gnu__mt)

4) Message boards : Number crunching : Client rejecting WUs for no apparent reason (Message 49636)
Posted 27 Jun 2011 by GlennG
Post:
Removing the planclass item didn't solve it. I am still getting the following errors for some WUs and not others. If you have any other ideas, I don't want to keep rejecting any WUs, because I know that that puts strain on the Milky Database. My only other option would be to put my Linux boxes to other projects.

Milkyway@home	6/27/2011 2:48:19 PM	[error] No application found for task: i686-pc-linux-gnu 0 ; discarding	
5) Message boards : Number crunching : Client rejecting WUs for no apparent reason (Message 49512)
Posted 23 Jun 2011 by GlennG
Post:
I thought the same, but the app_info is working most of the time. If you can see a problem, please let me know.

<app_info>
<app><!-- std app for N-Body 0.62 mt 64bit -->
<name>milkyway_nbody</name>
<user_friendly_name>MilkyWay@Home nbody</user_friendly_name>
</app>
<file_info>
<name>milkyway_nbody_0.62_i686-pc-linux-gnu__mt</name>
<executable/>
</file_info>

<app_version>
<app_name>milkyway_nbody</app_name>
<version_num>62</version_num>
<plan_class>mt</plan_class>
<avg_ncpus>4</avg_ncpus>
<max_ncpus>4</max_ncpus>
<cmdline>--nthreads=4</cmdline>
<file_ref>
<file_name>milkyway_nbody_0.62_i686-pc-linux-gnu__mt</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>
6) Message boards : Number crunching : Client rejecting WUs for no apparent reason (Message 49509)
Posted 23 Jun 2011 by GlennG
Post:
I have recently noticed some errors on my Linux clients that only happen occasionally. The log below shows that the problem comes and goes.

1			6/23/2011 2:10:22 PM	Starting BOINC client version 6.6.41 for i686-pc-linux-gnu	
182	Milkyway@home	6/23/2011 3:17:07 PM	Sending scheduler request: To fetch work.	
183	Milkyway@home	6/23/2011 3:17:07 PM	Requesting new tasks	
184	Milkyway@home	6/23/2011 3:17:12 PM	Scheduler request completed: got 1 new tasks	
185	Milkyway@home	6/23/2011 3:17:12 PM	[error] No application found for task: i686-pc-linux-gnu 0 mt; discarding	
186	Milkyway@home	6/23/2011 3:18:17 PM	Sending scheduler request: To fetch work.	
187	Milkyway@home	6/23/2011 3:18:17 PM	Requesting new tasks	
188	Milkyway@home	6/23/2011 3:18:22 PM	Scheduler request completed: got 1 new tasks	
189	Milkyway@home	6/23/2011 3:18:22 PM	[error] No application found for task: i686-pc-linux-gnu 0 mt; discarding	
190	Milkyway@home	6/23/2011 3:19:27 PM	Sending scheduler request: To fetch work.	
191	Milkyway@home	6/23/2011 3:19:27 PM	Requesting new tasks	
192	Milkyway@home	6/23/2011 3:19:32 PM	Scheduler request completed: got 1 new tasks	
193	Milkyway@home	6/23/2011 3:19:32 PM	[error] No application found for task: i686-pc-linux-gnu 0 mt; discarding	
194	Milkyway@home	6/23/2011 3:23:41 PM	Computation for task de_nbody_orphan_test_2model_4_66751_1308833687_2 finished	
195	Milkyway@home	6/23/2011 3:23:41 PM	Starting de_nbody_orphan_test_2model_4_70890_1308841050_0	
196	Milkyway@home	6/23/2011 3:23:41 PM	Starting task de_nbody_orphan_test_2model_4_70890_1308841050_0 using milkyway_nbody version 62	
197	Milkyway@home	6/23/2011 3:23:42 PM	Sending scheduler request: To report completed tasks.	
198	Milkyway@home	6/23/2011 3:23:42 PM	Reporting 1 completed tasks, requesting new tasks	
199	Milkyway@home	6/23/2011 3:23:47 PM	Scheduler request completed: got 2 new tasks	
200	Milkyway@home	6/23/2011 3:24:44 PM	Computation for task de_nbody_orphan_test_2model_4_70644_1308840468_0 finished	
201	Milkyway@home	6/23/2011 3:24:44 PM	Starting de_nbody_orphan_test_2model_4_71045_1308841050_0	
202	Milkyway@home	6/23/2011 3:24:44 PM	Starting task de_nbody_orphan_test_2model_4_71045_1308841050_0 using milkyway_nbody version 62	
203	Milkyway@home	6/23/2011 3:24:52 PM	Sending scheduler request: To report completed tasks.	
204	Milkyway@home	6/23/2011 3:24:52 PM	Reporting 1 completed tasks, requesting new tasks	
205	Milkyway@home	6/23/2011 3:24:57 PM	Scheduler request completed: got 1 new tasks	


In a 7 minute period 3 WUs were dropped and 3 WUs were accepted.

Is the problem with the client, my app_info, or the WUs themselves?

I know the client is old, but it has never given me problems before, and I don't have the ability to update all of the libraries on my three systems to those required for newer clients.

Any Ideas?
7) Message boards : Number crunching : Validation Errors on LInux CPU WUs (Message 42594)
Posted 5 Oct 2010 by GlennG
Post:
Starting a short time ago, all of my WUs are running for 1 second and then being reported as failing validation. I haven't changed anything in forever. I am using an optimized linux app by Gispel, but that has been stable for many months. Any ideas??

Glenn
8) Message boards : Number crunching : No New Work (Message 40631)
Posted 24 Jun 2010 by GlennG
Post:
Using 6.10.18 and 6.10.19, no problems getting work everytime boinc reports finished tasks automatically or manually.


The problem is with machines that lost contact with MW enough times during yesterday's outage to cause BOINC to recheck the master file. One of my machines is fine, because it didn't timeout yesterday. All of the rest got into the "Fetching" state, and cannot get out because the <scheduler> </scheduler> information does not appear to be in the new project page.

9) Message boards : Number crunching : No New Work (Message 40615)
Posted 23 Jun 2010 by GlennG
Post:
Boinc keeps saying "Fetching Scheduler List", and then reschedules for 24 hours later.

Please help.

10) Message boards : Number crunching : No work being D/Led & no warning messages (Message 9576)
Posted 2 Feb 2009 by GlennG
Post:
Travis,

Logan is right. The real problems for those of us with fast machines are twofold.

1. The estimated duration for a WU, when it is published by the project is way too long (ex. the older WUs show up at around 22 hours after a reset on my machine) After several dozen wus have completed, the DCF has been reduced to the correct amount, but it is considered too low for BOINC to allow more work.

2. The new set of WUs started last week (I38 & I39) had estimated durations out of line with the other WUs. They were about 25% longer to crunch, but the published duration was about 2x.

People weren't seeing problem #1 because we were just above the theshold of the problem until the new WUs drove our DCFs down even lower.

My suggestion is that the published duration for each WU be cut by a factor of 10. That way the fast machines will still have reasonable DCF, and older, slower machines can have DCFs greater than 1.0. Also, try to make sure that each new set of WUs have duration estimates in line with other outstanding sets.

Glenn
11) Message boards : Number crunching : New faster application? (Message 8403)
Posted 15 Jan 2009 by GlennG
Post:
Your standard app can typically be found on a Windows PC in

C:\Program Files\BOINC\projects\milkyway.cs.rpi.edu_milkyway\milkyway_0.7_windows_intelx86.exe
12) Message boards : Application Code Discussion : What's needed to compile the app? (Message 8324)
Posted 14 Jan 2009 by GlennG
Post:
Petros & Speedimic,

The newly released windows apps are causing the following question:

What are we doing wrong on the Linux side??? ;-)

The windows apps appear to be approx 3x the performance of your best Linux releases. Is the windows compiler that much better? Or were there changes to the source code involved? (Inquiring minds and crunchers want to know!!)

Cheers,
Glenn
13) Message boards : Number crunching : Vote for the MilkyWay favicon! (Message 8198)
Posted 5 Jan 2009 by GlennG
Post:
I like #9 as well.

14) Message boards : Application Code Discussion : What's needed to compile the app? (Message 8108)
Posted 31 Dec 2008 by GlennG
Post:
No Joy. The 4.1 app brings me back to 22 minutes per WU.

Glenn
15) Message boards : Application Code Discussion : What's needed to compile the app? (Message 8098)
Posted 31 Dec 2008 by GlennG
Post:
Petros

Great job. My WU times have dropped from 22 mins with your old app to mid 16's for the new one. Keep squeezing.

Glenn
16) Message boards : Application Code Discussion : What's needed to compile the app? (Message 7819)
Posted 17 Dec 2008 by GlennG
Post:
Mic,

For the record, Yes.

Linux xxxxx 2.6.9-78.0.5.ELsmp #1 SMP Wed Sep 24 05:40:24 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux

Thanks again.
17) Message boards : Application Code Discussion : What's needed to compile the app? (Message 7798)
Posted 16 Dec 2008 by GlennG
Post:
No Joy. Thanks anyway

Glenn


Can't open init data file - running in standalone mode
SIGSEGV: segmentation violation
Stack trace (10 frames):
[0x80701b6]
[0xffffe500]
[0x80d1e51]
[0x80d82a7]
[0x809ddcf]
[0x8057bd1]
[0x804825b]
[0x804844c]
[0x80925fa]
[0x8048151]

Exiting...
18) Message boards : Application Code Discussion : What's needed to compile the app? (Message 7795)
Posted 16 Dec 2008 by GlennG
Post:
Sure. Post them up somewhere, and I will give them a whirl.

Processor Features: 64bit simd [x86] cmov mmx sse sse2 sse3 ssse3 sse4.1 vmx lm lahf_lm tm tm2 eist

Glenn




©2022 Astroinformatics Group