Welcome to MilkyWay@home

post milkyway_i686-pc-linux-gnu problems here


Advanced search

Message boards : Number crunching : post milkyway_i686-pc-linux-gnu problems here
Message board moderation

To post messages, you must log in.

1 · 2 · 3 · Next

AuthorMessage
ProfileTravis
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 30 Aug 07
Posts: 2046
Credit: 26,480
RAC: 0
10 thousand credit badge10 year member badge
Message 6426 - Posted: 22 Nov 2008, 13:04:45 UTC

Please post any problems with the 32 bit linux app here.
ID: 6426 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
barsanuphe

Send message
Joined: 19 Oct 08
Posts: 19
Credit: 1,463,876
RAC: 0
1 million credit badge10 year member badge
Message 6496 - Posted: 23 Nov 2008, 17:40:17 UTC - in response to Message 6426.  

any idea of when it will actually be available?
ID: 6496 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileTravis
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 30 Aug 07
Posts: 2046
Credit: 26,480
RAC: 0
10 thousand credit badge10 year member badge
Message 6500 - Posted: 23 Nov 2008, 17:54:13 UTC - in response to Message 6496.  
Last modified: 23 Nov 2008, 17:57:34 UTC

any idea of when it will actually be available?


We need to get a 32 bit linux machine to compile it on... I thought Dave had one but it's not looking like it. If anyone wants to compile the latest code for it and send us the binary we can make it available that way as well.

(update) I'm going to see if our linux system will let us compile 32 bit binaries, if so we can probably make it available today.
ID: 6500 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
barsanuphe

Send message
Joined: 19 Oct 08
Posts: 19
Credit: 1,463,876
RAC: 0
1 million credit badge10 year member badge
Message 6717 - Posted: 25 Nov 2008, 19:17:25 UTC

still no news?
ID: 6717 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileTravis
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 30 Aug 07
Posts: 2046
Credit: 26,480
RAC: 0
10 thousand credit badge10 year member badge
Message 6718 - Posted: 25 Nov 2008, 19:19:21 UTC - in response to Message 6717.  

still no news?


Not yet, neither of us have access to a 32 bit linux machine.
ID: 6718 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileTravis
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 30 Aug 07
Posts: 2046
Credit: 26,480
RAC: 0
10 thousand credit badge10 year member badge
Message 6719 - Posted: 25 Nov 2008, 19:19:21 UTC - in response to Message 6717.  

still no news?


Not yet, neither of us have access to a 32 bit linux machine.
ID: 6719 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileTravis
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 30 Aug 07
Posts: 2046
Credit: 26,480
RAC: 0
10 thousand credit badge10 year member badge
Message 6735 - Posted: 25 Nov 2008, 22:01:13 UTC - in response to Message 6719.  

Update to this -- We got some pre-compiled 32 bit linux boinc libraries, so we can just link our app to those and hopefully things should be peachy-keen. Hopefully have a 32bit linux app out tonight or tomorrow.
ID: 6735 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
barsanuphe

Send message
Joined: 19 Oct 08
Posts: 19
Credit: 1,463,876
RAC: 0
1 million credit badge10 year member badge
Message 6786 - Posted: 26 Nov 2008, 17:49:29 UTC

i'm testing it right now -- so far, no problem.
ID: 6786 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfilePhil
Avatar

Send message
Joined: 13 Feb 08
Posts: 1124
Credit: 46,740
RAC: 0
10 thousand credit badge10 year member badge
Message 6787 - Posted: 26 Nov 2008, 17:49:48 UTC
Last modified: 26 Nov 2008, 18:13:05 UTC

Got some nm_test25s and the 04 linux 32bit client.

Still have the checkpointing problem, client crashes on a restart.

[edit]Otherwise its finished a work unit correctly.[/edit]
ID: 6787 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileCori
Avatar

Send message
Joined: 27 Aug 07
Posts: 647
Credit: 27,592,547
RAC: 0
20 million credit badge10 year member badge
Message 6792 - Posted: 26 Nov 2008, 19:27:03 UTC
Last modified: 26 Nov 2008, 19:27:38 UTC

Errm, wrong thread... *grin*
Lovely greetings, Cori
ID: 6792 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profilespeedimic
Avatar

Send message
Joined: 22 Feb 08
Posts: 260
Credit: 57,387,048
RAC: 0
50 million credit badge10 year member badge
Message 6822 - Posted: 26 Nov 2008, 22:13:58 UTC

Just did my first new WU: nm_test11_75_1227466845_2 (app 0.4)

No problems - valid.

Although the stderr out doesn't look 'clean':
<core_client_version>6.2.12</core_client_version>
<![CDATA[
<stderr_txt>
Unrecognized XML in parse_init_data_file: computation_deadline
Skipping: 1227985432.136000
Skipping: /computation_deadline
Unrecognized XML in GLOBAL_PREFS::parse_override: mod_time
Skipping: /mod_time
Unrecognized XML in GLOBAL_PREFS::parse_override: max_ncpus_pct
Skipping: 100.000000
Skipping: /max_ncpus_pct
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0

</stderr_txt>
]]>


Creditwise it's exactly the same as milksop's app on my Q9550.
(2x crunch-time -->> 2x the credit)


mic.


ID: 6822 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
barsanuphe

Send message
Joined: 19 Oct 08
Posts: 19
Credit: 1,463,876
RAC: 0
1 million credit badge10 year member badge
Message 6823 - Posted: 26 Nov 2008, 22:15:40 UTC
Last modified: 26 Nov 2008, 22:17:45 UTC

i just had some nm_test10 with following result:

Outcome Client error
Client state Downloading
Exit status -186 (0xffffffffffffff46)

<core_client_version>6.2.18</core_client_version>
<![CDATA[
<message>
WU download error: couldn't get input files:
<file_xfer_error>
<file_name>stars.txt</file_name>
<error_code>-224</error_code>
<error_message>file not found</error_message>
</file_xfer_error>

</message>
]]>


nm_test25 were fine.

edit: nm_test25 were fine but with same stdout as post above
ID: 6823 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
cwhyl

Send message
Joined: 11 Nov 07
Posts: 41
Credit: 1,000,181
RAC: 0
1 million credit badge10 year member badge
Message 6910 - Posted: 28 Nov 2008, 10:24:24 UTC
Last modified: 28 Nov 2008, 11:15:31 UTC

Got about 70 WUs, really quick: 00:11 instead of 04:53.
Seem to work fine but stderr out complains a bit:
stderr out

<core_client_version>5.10.45</core_client_version>
<![CDATA[
<stderr_txt>
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0

</stderr_txt>
]]>


Edit: oops..3 failed:


<core_client_version>5.10.45</core_client_version>
<![CDATA[
<message>
WU download error: couldn't get input files:
<file_xfer_error>
<file_name>astronomy_parameters_nm_test24.txt</file_name>
<error_code>-119</error_code>
<error_message>MD5 check failed</error_message>
</file_xfer_error>

</message>
]]>

Not with nm_test25 or nm_test26 though, they seem fine.
ID: 6910 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileConan
Avatar

Send message
Joined: 2 Jan 08
Posts: 105
Credit: 65,396,973
RAC: 0
50 million credit badge10 year member badge
Message 7108 - Posted: 1 Dec 2008, 9:37:01 UTC
Last modified: 1 Dec 2008, 10:32:39 UTC

Ok Travis, I have downloaded your new stock app to see how it is going, mainly as you are going to cease the 1.22 Op app anyway and I could not get work.

They run quite a bit longer than the Milksop 1.22 op app.
(I have had to be very quick to get the results, even then I only got a couple then they were gone).

The 'test' WU's run about twice as long as the Milksop app but the 'stripe' WU's run heaps longer and vary between different stripe versions (79; 86 etc).

Also the run time between Windows and Linux is still quite a bit different to each other on the same WU type. Windows is much faster, this was the case on the original stock app, Milksop's app and now your new app (v0.04).

AMD Opteron 285 Linux FC6....'stripe79_1' WU...3,652 sec, Op App..389 sec
AMD Opteron 285 Windows XP...'stripe79_1' WU...2,837 sec, Op App..351 sec

As you can see run times on near identical machines is slower with Linux.

(I have noticed some variation in the run times of 'stripe79' WU's, so maybe it is not as consistent as the previous work units).

The 'test' apps on my Linux machine run for about 910 sec on 'test26' and 920 sec on 'test27'.
On my Intel P4 2.53 the 'test25' work units run for about 1,269 sec, not much slower than my Opteron, which user to be twice as quick at doing a WU.

Maybe I need to learn how to compile source code on Linux ???

With the longer Work Units I have not had too much problem with the 8 WU limit per CPU.

Thanks Travis and Dave for all your hard work on this.

EDIT:-- Have just read another post (post is '20 work unit limit') about the difference in 'stripe79' and 'stripe79_1' and why they are not the same length.
ID: 7108 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileKSMarksPsych
Avatar

Send message
Joined: 9 Sep 07
Posts: 22
Credit: 320,035
RAC: 0
100 thousand credit badge10 year member badge
Message 7113 - Posted: 1 Dec 2008, 11:24:57 UTC

Just had one error out after 35 minutes.

Task ID 56879889
Name nm_stripe79_1_13099_1228123065_0
Workunit 57100851
Created 1 Dec 2008 9:17:50 UTC
Sent 1 Dec 2008 9:28:30 UTC
Received 1 Dec 2008 11:21:52 UTC
Server state Over
Outcome Client error
Client state Compute error
Exit status 255 (0xff)
Computer ID 36872
Report deadline 4 Dec 2008 9:28:30 UTC
CPU time 2143.636117
stderr out

<core_client_version>6.4.1</core_client_version>
<![CDATA[
<message>
process exited with code 255 (0xff, -1)
</message>
<stderr_txt>
Unrecognized XML in parse_init_data_file: computation_deadline
Skipping: 1228379223.600000
Skipping: /computation_deadline
Unrecognized XML in GLOBAL_PREFS::parse_override: mod_time
Skipping: /mod_time
Unrecognized XML in GLOBAL_PREFS::parse_override: max_ncpus_pct
Skipping: 100.000000
Skipping: /max_ncpus_pct
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
Unrecognized XML in parse_init_data_file: computation_deadline
Skipping: 1228379223.600000
Skipping: /computation_deadline
Unrecognized XML in GLOBAL_PREFS::parse_override: mod_time
Skipping: /mod_time
Unrecognized XML in GLOBAL_PREFS::parse_override: max_ncpus_pct
Skipping: 100.000000
Skipping: /max_ncpus_pct
Error reading into stream_integrals

</stderr_txt>
]]>

Validate state Invalid
Claimed credit 5.05409120118583
Granted credit 0
application version 0.04



This was after detaching/reattaching to get the stock app.
Kathryn :o)
The BOINC FAQ Service
The Unofficial BOINC Wiki
The Trac System
More BOINC information than you can shake a stick of RAM at.
ID: 7113 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profilecaspr
Avatar

Send message
Joined: 22 Mar 08
Posts: 90
Credit: 501,728
RAC: 0
500 thousand credit badge10 year member badge
Message 7114 - Posted: 1 Dec 2008, 11:32:03 UTC
Last modified: 1 Dec 2008, 11:33:01 UTC

Thanks Conan! I was going to run my windoz down and check #'s on Linux but I guess since you've already done it I'll stick with Windoz!
A clear conscience is usually the sign of a bad memory



ID: 7114 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profilemindc

Send message
Joined: 9 Jul 08
Posts: 7
Credit: 11,070,991
RAC: 0
10 million credit badge10 year member badge
Message 7115 - Posted: 1 Dec 2008, 11:43:50 UTC - in response to Message 7114.  

And what with linux machines with gcc libs older than 4.2.0?

cheers
mindc
ID: 7115 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileTravis
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 30 Aug 07
Posts: 2046
Credit: 26,480
RAC: 0
10 thousand credit badge10 year member badge
Message 7118 - Posted: 1 Dec 2008, 12:33:23 UTC - in response to Message 7113.  

Just had one error out after 35 minutes.

Task ID 56879889
Name nm_stripe79_1_13099_1228123065_0
Workunit 57100851
Created 1 Dec 2008 9:17:50 UTC
Sent 1 Dec 2008 9:28:30 UTC
Received 1 Dec 2008 11:21:52 UTC
Server state Over
Outcome Client error
Client state Compute error
Exit status 255 (0xff)
Computer ID 36872
Report deadline 4 Dec 2008 9:28:30 UTC
CPU time 2143.636117
stderr out

6.4.1

process exited with code 255 (0xff, -1)


Unrecognized XML in parse_init_data_file: computation_deadline
Skipping: 1228379223.600000
Skipping: /computation_deadline
Unrecognized XML in GLOBAL_PREFS::parse_override: mod_time
Skipping: /mod_time
Unrecognized XML in GLOBAL_PREFS::parse_override: max_ncpus_pct
Skipping: 100.000000
Skipping: /max_ncpus_pct
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
Unrecognized XML in parse_init_data_file: computation_deadline
Skipping: 1228379223.600000
Skipping: /computation_deadline
Unrecognized XML in GLOBAL_PREFS::parse_override: mod_time
Skipping: /mod_time
Unrecognized XML in GLOBAL_PREFS::parse_override: max_ncpus_pct
Skipping: 100.000000
Skipping: /max_ncpus_pct
Error reading into stream_integrals


]]>

Validate state Invalid
Claimed credit 5.05409120118583
Granted credit 0
application version 0.04



This was after detaching/reattaching to get the stock app.


There's an issue with checkpointing v0.4 and lower, this should be fixed with version 0.6

ID: 7118 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ebahapo
Avatar

Send message
Joined: 6 Sep 07
Posts: 66
Credit: 596,734
RAC: 108
500 thousand credit badge10 year member badge
Message 7138 - Posted: 1 Dec 2008, 16:52:28 UTC - in response to Message 7108.  

AMD Opteron 285 Linux FC6....'stripe79_1' WU...3,652 sec, Op App..389 sec
AMD Opteron 285 Windows XP...'stripe79_1' WU...2,837 sec, Op App..351 sec

As you can see run times on near identical machines is slower with Linux.

It might be because Linux manages power differently from Windows, running BOINC applications at a slow CPU frequency in order to save energy. See more details here.

HTH

ID: 7138 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ebahapo
Avatar

Send message
Joined: 6 Sep 07
Posts: 66
Credit: 596,734
RAC: 108
500 thousand credit badge10 year member badge
Message 7140 - Posted: 1 Dec 2008, 16:56:45 UTC - in response to Message 7115.  

And what with linux machines with gcc libs older than 4.2.0?

Is it too much to ask that the application be linked with the GCC option -static-libgcc in order to avoid this issue?

TIA

ID: 7140 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
1 · 2 · 3 · Next

Message boards : Number crunching : post milkyway_i686-pc-linux-gnu problems here

©2019 Astroinformatics Group