Problem with simultaneously starting Multicore CPU tasks has not been fixed yet!

Problem with simultaneously starting Multicore CPU tasks has not been fixed yet!

If two WUs start at the same time, in most cases one of the WU failes right at start and throws an calculation error, which is very inconveniant, if you have to start often times more than one WU at the same time (in my case up to 20 WUs on my 80 threads machine). Would like to hear some statement of the developer(s) or simply a bugfix within the WUs, because at the moment, I do not see any suitable work around. Don't think it's just your fault or mine, because several users have reported this issue for a while now.

Toni,

Here are two task numbers that started at the same time. Both failed.

17737243
17737150

Let me know if you need more info.

EDIT:

Here is a task that started by itself and failed.

17714391

Toni,

The "flock" command was found and asked for more arguments.

After a project reset, the following two tasks were started and both failed.

17737309
17737152

The following task was started by itself and failed.

17737252

What next?

with all my computers just the same... Toni, does it help if I give you by private message the remote control access credentials of one of my Linux machines, so you can test on your own?

Sometimes they work and sometimes not. If two or more WUs start at the same time, they all throw calculation errors. This was the state until now. But with the very new version you just released today, it seems like they are not working anymore at all. My operating system is Linux Mint 18.3 64 Bit with actual linux kernel. I installed boinc with "sudo apt-get install boinc". gcc-5 and g++-5 are installed; also python-support.

All errors on my VM (with 4 virtual core).

<message>
process exited with code 195 (0xc3, -61)
</message>
<stderr_txt>
16:29:25 (2940): wrapper (7.7.26016): starting
16:29:25 (2940): wrapper (7.7.26016): starting
16:29:25 (2940): wrapper: running /bin/bash (-c "flock /var/lib/boinc-client/projects/www.gpugrid.net/miniconda.lock ./miniconda-installer -b -u -p /var/lib/boinc-client/projects/www.gpugrid.net/miniconda")
Please run using "bash" or "sh", but not "." or "source"\n16:29:26 (2940): /bin/bash exited; CPU time 0.000000
16:29:26 (2940): app exit status: 0x1

All tasks exit with error:

When I tried to start two at the same time, one of them runs okay and the other one aborts.

Task id for the aborted work unit is 17714759
Work unit number for the aborted work unit is 13679491

Running version 3.20

Let me know if you need more info.

I have had libc6-dev already installed... Earlier I got a bunch of new WUs, but all failed after several minutes of calculation (~ 5 - 15 minutes).

Started two QC Wu's simultaneously using app version 3.20 and one failed with this stderr report:

<core_client_version>7.9.3</core_client_version>
<![CDATA[
<message>
process exited with code 195 (0xc3, -61)</message>
<stderr_txt>
13:45:21 (5569): wrapper (7.7.26016): starting
13:45:21 (5569): wrapper (7.7.26016): starting
13:45:21 (5569): wrapper: running /bin/bash (-c "flock /var/lib/boinc/projects/www.gpugrid.net/miniconda.lock ./miniconda-installer.sh -b -u -p /var/lib/boinc/projects/www.gpugrid.net/miniconda")
flock: failed to execute ./miniconda-installer.sh: Text file busy
13:45:30 (5569): /bin/bash exited; CPU time 0.000265
13:45:30 (5569): app exit status: 0x45
13:45:30 (5569): called boinc_finish(195)

</stderr_txt>
]]>

Machine is an AMD FX8350 at 4.1 GHz with Fedora 28 kernel 4.16.13 with both gcc and glibc-devel installed.

I had been running both my 8 core machines in 4 core mode and 2 concurrent QC WU's for several months with only one simultaneous start error the whole time but with no other project to compete for the CPU. I found that when running both WCG and QC CPU WU's, simultaneous starts occurred more frequently and unfortunately when it did happen, then failures would leap frog through the queue quickly and blacklist the computer from more work for a day.

Just got a couple of errors from last night's WUs version 3.20.

Here are the links:
https://www.gpugrid.net/result.php?resultid=17740487
https://www.gpugrid.net/result.php?resultid=17740592

All the rest ran fine.

^^ These seem connection errors (network down or so)

I have exactly the same problems so I dont think this is connection related.

Version 321 looks promising. Just finished two that started at the same time and they finished normally. Just started three at the same time and they are all processing as they should.

Success with two QC WU's simultaneous start using app 3.21. Both WU's happily crunching @ 1.098% completed so far.

Event Log Excerpt:

Thu 07 Jun 2018 07:22:04 AM MST | GPUGRID | task m0000000638_2278bdac_n00020-SDOERR_QMML50-0-1-RND5957_0 resumed by user
Thu 07 Jun 2018 07:22:04 AM MST | GPUGRID | task m0000000643_5ed133e9_n00020-SDOERR_QMML50-0-1-RND3172_0 resumed by user
Thu 07 Jun 2018 07:22:05 AM MST | GPUGRID | Starting task m0000000638_2278bdac_n00020-SDOERR_QMML50-0-1-RND5957_0
Thu 07 Jun 2018 07:22:05 AM MST | GPUGRID | Starting task m0000000643_5ed133e9_n00020-SDOERR_QMML50-0-1-RND3172_0

^^ These seem connection errors (network down or so)

Network can affect computation after the WU is already downloaded?

Yes. WUs check the latest version of conda packages/libraries right after start (from conda cloud).

Today I have had three successful simultaneous starts and returns without error on two different FX8350 machines. As far as I am concerned, this bug has been resolved at least for the Fedora distro.

Haven't gotten a single error with version 3.21 and it's been running all day. What did you change?

No more error, but a strange behaviour.
Remanining time for every wus are over 20h, but wus are crunched in 40/50 minutes...

Didn't get any response from my post in the cpu tasks thread.

How do you get the cpu tasks? I tried and failed. Is the QC app still considered a Test app? That was the only Preference toggle I didn't select.

Did you check: use CPU as well? You might not have allowed it.

No it is not necessary to check BETA tasks. I do not have checked it either, but I do get QC tasks.

Yes CPU was checked for use both places and the QC app. Didn't get any QC tasks both time I tried. Just gpu tasks. The scheduler request was for both cpu and gpu work. I know there is plenty of cpu tasks to farm out. Couldn't explain why I didn't get any work. I'll have to try again without gpu work checked I guess.

Yes CPU was checked for use both places and the QC app. Didn't get any QC tasks both time I tried. Just gpu tasks.

Thanks for the reply. I don't know. It worked a couple of months ago when the QC app and tasks first showed up. I was crunching both gpu and cpu at the same time. I know that shutting off a gpu request will probably work just to get some of the new QC tasks along with the latest 3.21 app.

I was just wondering how well the app works now with concurrent starts.

I was just wondering how well the app works now with concurrent starts.

My threadripper this night crunched 50 WU's, no issues. Good job :)

Not an important thing, but are you planning to implement separate badges for CPU points?

Hello, I just got a new error with v3.21. Does anyone have any idea what could be causing it?

Task is available below:
http://www.gpugrid.net/result.php?resultid=17764870

Yes CPU was checked for use both places and the QC app. Didn't get any QC tasks both time I tried. Just gpu tasks. The scheduler request was for both cpu and gpu work. I know there is plenty of cpu tasks to farm out. Couldn't explain why I didn't get any work. I'll have to try again without gpu work checked I guess.

At risk of stating trivialities: did you check in the log if by chance it's a matter of disk space (either allocated to boinc, or actually free)? QC tasks are unusually demanding on disk space.

Anyway: thanks for trying to make it work :)

Hello, I am having issues with a new Ubuntu 18.04 installation. I have installed the necessary packages but I am still getting errors. Can you let me know what the issue is? Errors linked below

http://www.gpugrid.net/results.php?hostid=480159&offset=0&show_names=0&state=5&appid=

Lots of things don't work the same in 18.04 the way they did on 16.04. I figure the change in GTK and Python is the base cause of why compute doesn't work the same.

Hello, I am having issues with a new Ubuntu 18.04 installation. I have installed the necessary packages but I am still getting errors. Can you let me know what the issue is? Errors linked below

http://www.gpugrid.net/results.php?hostid=480159&offset=0&show_names=0&state=5&appid=

Have you carried over the boinc dir from a previous installation?

In any case, try resetting the project.

CPU tasks do not fail on my HP laptop with SuSE Leap 42.3 which is constantly updated by SuSE. They fail instead on my SUN workstation, also with SuSE Linux 42.3 which is not updated by SuSE, I don't know why. On the other hand, GPU tasks run on the GTX 750 Ti board on the SUN, giving me huge credits.
Tullio

Can you try installing python-support (if not already?)

I am under the impression that the WUs failing with segmentation fault is the root cause, and other errors are consequences.