Anytime I abort a result from another project ( especially if that result is in progress) I get a computation error from working mw tasks.Gives the process got signal 11 stderr message. Heres a result (Dang Orbit and Cosmo)

---

Anytime I abort a result from another project ( especially if that result is in progress) I get a computation error from working mw tasks.Gives the process got signal 11 stderr message. Heres a result (Dang Orbit and Cosmo)

I've seen simliar behaviour, and it's not just MW WUs that get killed. For me, when it happens my firewall pops up to warn about unexpected inter-process messaging. If I allow it, I lose a WU, if I block it BOINC just sulks ;)

Only seen this on ancient BOINC versions (e.g. 5.10.7). Have never seen it on 5.10.28 (the newest version I run).

Looks like a 'kill' is being sent or propogated from the aborted task and clobbering the next thing in the chain.

Serves you right for running flaky projects ;)

Al.

Anytime I abort a result from another project ( especially if that result is in progress) I get a computation error from working mw tasks.Gives the process got signal 11 stderr message. Heres a result (Dang Orbit and Cosmo)

I've seen simliar behaviour, and it's not just MW WUs that get killed. For me, when it happens my firewall pops up to warn about unexpected inter-process messaging. If I allow it, I lose a WU, if I block it BOINC just sulks ;)

Only seen this on ancient BOINC versions (e.g. 5.10.7). Have never seen it on 5.10.28 (the newest version I run).

Looks like a 'kill' is being sent or propogated from the aborted task and clobbering the next thing in the chain.

Serves you right for running flaky projects ;)

Al.

hmmm...this sounds like a BOINC bug....are you running the latest client version? I don't see how other work can affect another project unless it's client related. You may want to report this to the BOINC developers.

---

Dave Przybylo
MilkyWay@home Developer
Department of Computer Science
Rensselaer Polytechnic Institute

Anytime I abort a result from another project ( especially if that result is in progress) I get a computation error from working mw tasks.Gives the process got signal 11 stderr message. Heres a result (Dang Orbit and Cosmo)

I've seen simliar behaviour, and it's not just MW WUs that get killed. For me, when it happens my firewall pops up to warn about unexpected inter-process messaging. If I allow it, I lose a WU, if I block it BOINC just sulks ;)

Only seen this on ancient BOINC versions (e.g. 5.10.7). Have never seen it on 5.10.28 (the newest version I run).

Looks like a 'kill' is being sent or propogated from the aborted task and clobbering the next thing in the chain.

Serves you right for running flaky projects ;)

Al.

hmmm...this sounds like a BOINC bug....are you running the latest client version? I don't see how other work can affect another project unless it's client related. You may want to report this to the BOINC developers.

Hi Dave- This only affects mw units running...no other projects...Einstein,Seti,Cosmo work doesn't error out.
Client being used is 5.10.8 because this is what the synaptic package manager gave me with Ubuntu....now if I could figure out how to upgrade it I would...but that is a whole different deal.

It also occurs on windows 5.10.13 so I thought this was a general issue,,,,

---

Anytime I abort a result from another project ( especially if that result is in progress) I get a computation error from working mw tasks.Gives the process got signal 11 stderr message. Heres a result (Dang Orbit and Cosmo)

I've seen simliar behaviour, and it's not just MW WUs that get killed. For me, when it happens my firewall pops up to warn about unexpected inter-process messaging. If I allow it, I lose a WU, if I block it BOINC just sulks ;)

Only seen this on ancient BOINC versions (e.g. 5.10.7). Have never seen it on 5.10.28 (the newest version I run).

Looks like a 'kill' is being sent or propogated from the aborted task and clobbering the next thing in the chain.

Serves you right for running flaky projects ;)

Al.

hmmm...this sounds like a BOINC bug....are you running the latest client version? I don't see how other work can affect another project unless it's client related. You may want to report this to the BOINC developers.

Hi Dave- This only affects mw units running...no other projects...Einstein,Seti,Cosmo work doesn't error out.
Client being used is 5.10.8 because this is what the synaptic package manager gave me with Ubuntu....now if I could figure out how to upgrade it I would...but that is a whole different deal.

It also occurs on windows 5.10.13 so I thought this was a general issue,,,,

That is really weird. Nothing you should do on another project should affect mw. I'll look into this.

---

Dave Przybylo
MilkyWay@home Developer
Department of Computer Science
Rensselaer Polytechnic Institute

That is really weird. Nothing you should do on another project should affect mw. I'll look into this.

Thanks Dave-It may be a Boinc problem but it seems to affect mw only from the 8 projects I actively run.

When aborting say a cosmo ...Boinc freezes for 10-15 seconds before the error ...if that helps.

---

There is an easy way to update your boinc client in Linux, it won't be as intergrated as the synaptic one but will work all the same. At the boinc site select all versions and then select the version you want to use,5.10.45 is the latest linux one. Download the client to your home directory, D/L should be a shell script. Now open a terminal and cd into your home directory. eg
cd /home/"homedirname" (don't used the quote marks)
now just run the boinc shell script eg for 5.10.45 it is as follows
sh boinc_ubuntu_5.10.45_x86_64-pc-linux-gnu.sh
NOTE that this is for the 64bit version so make sure you get the name right for your version if different. This command will create a directory in your home folder called BOINC. Now come the not intergrated bit. To run your new client(and it will be a new client not an update to the one installed already) open a new terminal. In your new BOINC directory there will be a file called "run_manager" which is a plain text file. drag that file into your open terminal and press return Boinc and Boinc manager should start up. Remember you MUST leave this terminal open while boinc is running so just minimise the terminal window don't close it. If for some reason draging the file into the terminal doesn't work the actual command to run it is
cd "/home/yourhomedir/BOINC" && exec ./boincmgr $@
type this in your terminal WITH the quotes and with the actual name of yourhomedir

There is an easy way to update your boinc client in Linux, it won't be as intergrated as the synaptic one but will work all the same. At the boinc site select all versions and then select the version you want to use,5.10.45 is the latest linux one. Download the client to your home directory, D/L should be a shell script. Now open a terminal and cd into your home directory. eg
cd /home/"homedirname" (don't used the quote marks)
now just run the boinc shell script eg for 5.10.45 it is as follows
sh boinc_ubuntu_5.10.45_x86_64-pc-linux-gnu.sh
NOTE that this is for the 64bit version so make sure you get the name right for your version if different. This command will create a directory in your home folder called BOINC. Now come the not intergrated bit. To run your new client(and it will be a new client not an update to the one installed already) open a new terminal. In your new BOINC directory there will be a file called "run_manager" which is a plain text file. drag that file into your open terminal and press return Boinc and Boinc manager should start up. Remember you MUST leave this terminal open while boinc is running so just minimise the terminal window don't close it. If for some reason draging the file into the terminal doesn't work the actual command to run it is
cd "/home/yourhomedir/BOINC" && exec ./boincmgr $@
type this in your terminal WITH the quotes and with the actual name of yourhomedir

Thanks for the directions mgpower0 :) I am saving the text for future reference,at this point I am going to leave as is (if it ain't broke don't fix it) because I have no real issues with the older client. ;)

---

There is an easy way to update your boinc client in Linux, it won't be as intergrated as the synaptic one but will work all the same. At the boinc site select all versions and then select the version you want to use,5.10.45 is the latest linux one. Download the client to your home directory, D/L should be a shell script. Now open a terminal and cd into your home directory. eg
cd /home/"homedirname" (don't used the quote marks)
now just run the boinc shell script eg for 5.10.45 it is as follows
sh boinc_ubuntu_5.10.45_x86_64-pc-linux-gnu.sh
NOTE that this is for the 64bit version so make sure you get the name right for your version if different. This command will create a directory in your home folder called BOINC. Now come the not intergrated bit. To run your new client(and it will be a new client not an update to the one installed already) open a new terminal. In your new BOINC directory there will be a file called "run_manager" which is a plain text file. drag that file into your open terminal and press return Boinc and Boinc manager should start up. Remember you MUST leave this terminal open while boinc is running so just minimise the terminal window don't close it. If for some reason draging the file into the terminal doesn't work the actual command to run it is
cd "/home/yourhomedir/BOINC" && exec ./boincmgr $@
type this in your terminal WITH the quotes and with the actual name of yourhomedir

Thanks for the directions mgpower0 :) I am saving the text for future reference,at this point I am going to leave as is (if it ain't broke don't fix it) because I have no real issues with the older client. ;)

On a completely different note, i think this is one of the main problems with streamlining Linux as a consumer friendly operating system. It's so hard for the average joe to install or do anything on the OS without any help.

---

Dave Przybylo
MilkyWay@home Developer
Department of Computer Science
Rensselaer Polytechnic Institute