Posts by Jnargus

log in
1) Message boards : Number crunching : Never-ending WU (Message 330)
Posted 14 Oct 2010 by Jnargus
WU http://wuprop.boinc-af.org/result.php?resultid=1036186 on computer http://wuprop.boinc-af.org/show_host_detail.php?hostid=6945 is doing the same thing. It is up to 56 hours and is 53.1% done. Unlike the rest of the people in this thread I am running Ubuntu with a Linux 2.6.32-25-generic-pae kernel on an i7 920 based machine with 3G of ram.

I will abort it as it has taken way to long and I would like to get some credit from this machine.
2) Message boards : Number crunching : Invalid WU's (Message 315)
Posted 26 Aug 2010 by Jnargus
I'm not sure what mscharmack is talking about but the machine I was having problems with was running 6 other projects. So the fact that this projects WUs were coming back invalid did not bother me in the least, and I did not consider it a waste of electricity in the least. (OK it bothered me enough to try to find out why they were coming back invalid and fix the problem.)

If mscharmack is running just this project on his computers that IS a waste of time and electricity as it will not give credit if no other projects are running. Besides this project does not award large amounts of credit per day anyway. You are much better off with just about any other project if all you want is credit.

I try to find projects that are doing something interesting that I like first and then I try to maximize credit after. All I need to really start bringing on the credit is a GPU but that will have to wait until I finish renovating my house.

jna
3) Message boards : Number crunching : Invalid WU's (Message 303)
Posted 22 Aug 2010 by Jnargus
Ca marche!

The file stderr.txt contains:

Utilisation du port 31415

after 15 minutes of runtime! Yay!

Merci beaucoup!
(la blonde de jna)
4) Message boards : Number crunching : Invalid WU's (Message 301)
Posted 21 Aug 2010 by Jnargus
Here is the result of the Telnet command:

telnet 127.0.0.1 31416
(UNKNOWN) [127.0.0.1] 31416 (?) : Connection refused

telnet 127.0.0.1 31415
<get_cc_status>
<boinc_gui_rpc_reply>
<cc_status>
<network_status>2</network_status>
<ams_password_error>0</ams_password_error>
<task_suspend_reason>0</task_suspend_reason>
<network_suspend_reason>0</network_suspend_reason>
<task_mode>2</task_mode>
<task_mode_perm>2</task_mode_perm>
<task_mode_delay>0.000000</task_mode_delay>
<gpu_mode>2</gpu_mode>
<gpu_mode_perm>2</gpu_mode_perm>
<gpu_mode_delay>0.000000</gpu_mode_delay>
<network_mode>2</network_mode>
<network_mode_perm>2</network_mode_perm>
<network_mode_delay>0.000000</network_mode_delay>
<disallow_attach>0</disallow_attach>
<simple_gui_only>0s</simple_gui_only>
</cc_status>
</boinc_gui_rpc_reply>

It just occured to me that I am using a non-standard port for Boinc. This is probably the cause of all the problems. I'm not sure if you want to fix your app to handle non-standard ports or not but I will wait for your reply before trying the standard port.

jna
5) Message boards : Number crunching : Invalid WU's (Message 298)
Posted 20 Aug 2010 by Jnargus
Started running WUs again and got the same error messages. This machine is running Debian sid and Linux kernel 2.6.32-5-686-bigmem. So there is something different about this machine that causes problems. Are there any ports that this application uses that I could be blocking that could cause this problem?

Thanks

jna
6) Message boards : Number crunching : Invalid WU's (Message 293)
Posted 18 Aug 2010 by Jnargus
OK, A few more details, The OS and kernel that are failing is Debian Sid and either kernel 2.6.32-trunk-686 (Debian 2.6.32-5) or 2.6.32-5-686 (Debian 2.6.32-20), both were used at various time and I'm not sure which was used when. Now this machine is running the 2.6.32-5-686-bigmem kernel so I will enable this project again and see what it does.

I will keep you informed of the progress.

jna
7) Message boards : Number crunching : Invalid WU's (Message 292)
Posted 18 Aug 2010 by Jnargus
This machine is running Debian linux I will get the exact details when I get home tonight and let you know what they are. I do know it is a very recent version of Debian.

Thanks.
8) Message boards : Number crunching : Invalid WU's (Message 288)
Posted 16 Aug 2010 by Jnargus
I tried a few of the newest WU's and got the same messages again. Can anyone help me figure this out?

Thanks

John
9) Message boards : Cafe : Anybody home? (Message 253)
Posted 21 Jul 2010 by Jnargus
I check most days to see if anyone from the project has answered my question that I posted a month and half ago. But other than us two I think everyone else went home and forgot to turn the lights off. :-)
10) Questions and Answers : Unix/Linux : Invalid WU's (Message 250)
Posted 29 Jun 2010 by Jnargus
This machine (ID: 5522) is still producing the same result for all work units. If anyone out there has any idea I would appreciate hearing from you. In the mean time I will just disable this project on this machine and try to get some of my other machines running the latest version of BOINC to get them involved.

I am a little disappointed that no one from the project can offer any insight into this problem if they have even looked at this post.
11) Questions and Answers : Unix/Linux : Invalid WU's (Message 246)
Posted 16 Jun 2010 by Jnargus
I started three computers on this project and two are working just fine. The third, with computer ID: 5522, keeps getting marked "Completed, marked as invalid".

This is a partial list of the stderr out:
<core_client_version>6.10.17</core_client_version>
<![CDATA[
<stderr_txt>
GPIPE: write on a pipe with no reader
19:30:42 (2573): Interrogation impossible Broken pipe.
SIGPIPE: write on a pipe with no reader
19:30:43 (2573): Interrogation impossible Broken pipe.
SIGPIPE: write on a pipe with no reader
19:30:44 (2573): Interrogation impossible Broken pipe.

...

SIGPIPE: write on a pipe with no reader
07:33:03 (14831): Interrogation impossible Broken pipe.
SIGPIPE: write on a pipe with no reader
07:33:05 (14831): Interrogation impossible Broken pipe.
07:33:06 (14831): Deconnection impossible Transport endpoint is not connected.
07:33:06 (14831): Connection impossible Connection refused.
SIGPIPE: write on a pipe with no reader
07:33:06 (14831): Interrogation impossible Broken pipe.
SIGPIPE: write on a pipe with no reader

...

SIGPIPE: write on a pipe with no reader
07:43:03 (14831): Interrogation impossible Broken pipe.
SIGPIPE: write on a pipe with no reader
07:43:04 (14831): Interrogation impossible Broken pipe.
SIGPIPE: write on a pipe with no reader
07:43:05 (14831): Interrogation impossible Broken pipe.
07:43:06 (14831): Deconnection impossible Transport endpoint is not connected.
07:43:06 (14831): called boinc_finish

</stderr_txt>
]]>

Can someone explain what is going on here and if there is anything I should be doing my end to fix the problem. This computer is running several projects and only CPU WUs.
12) Message boards : Number crunching : Invalid WU's (Message 245)
Posted 14 Jun 2010 by Jnargus
I started three computers on this project and two are working just fine. The third, with computer ID: 5522, keeps getting marked "Completed, marked as invalid".

This is a partial list of the stderr out:
<core_client_version>6.10.17</core_client_version>
<![CDATA[
<stderr_txt>
GPIPE: write on a pipe with no reader
19:30:42 (2573): Interrogation impossible Broken pipe.
SIGPIPE: write on a pipe with no reader
19:30:43 (2573): Interrogation impossible Broken pipe.
SIGPIPE: write on a pipe with no reader
19:30:44 (2573): Interrogation impossible Broken pipe.

...

SIGPIPE: write on a pipe with no reader
07:33:03 (14831): Interrogation impossible Broken pipe.
SIGPIPE: write on a pipe with no reader
07:33:05 (14831): Interrogation impossible Broken pipe.
07:33:06 (14831): Deconnection impossible Transport endpoint is not connected.
07:33:06 (14831): Connection impossible Connection refused.
SIGPIPE: write on a pipe with no reader
07:33:06 (14831): Interrogation impossible Broken pipe.
SIGPIPE: write on a pipe with no reader

...

SIGPIPE: write on a pipe with no reader
07:43:03 (14831): Interrogation impossible Broken pipe.
SIGPIPE: write on a pipe with no reader
07:43:04 (14831): Interrogation impossible Broken pipe.
SIGPIPE: write on a pipe with no reader
07:43:05 (14831): Interrogation impossible Broken pipe.
07:43:06 (14831): Deconnection impossible Transport endpoint is not connected.
07:43:06 (14831): called boinc_finish

</stderr_txt>
]]>

Can someone explain what is going on here and if there is anything I should be doing my end to fix the problem. This computer is running several projects and only CPU WUs.




Home | My Account | Message Boards | Results


Copyright © 2020 Sebastien