One of my rigs has been trashing all the v7 WUs. Below is the Stderr output

<core_client_version>7.0.64</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code -108 (0xffffff94)
</message>
]]>

The same setup on the other rigs is working fine. Any guidance please.

ERR_FOPEN -108 system fopen The file is "open" and in use by another process, or write access to the file cannot be obtained.

hm, virus scan running in that directory?

---

- Performance is not a simple linear function of the number of CPUs you throw at the problem. -

ERR_FOPEN -108 system fopen The file is "open" and in use by another process, or write access to the file cannot be obtained.

hm, virus scan running in that directory?

The rig is running Bitdefender, and although it didnt detect anything with the file, I have not put the entire directory under exclusions and restarted the system. It downloaded a fresh batch of v7 CPU files, eight of which got trashed within seconds, while the second batch seems to be crunching fine, till now. All of those WUs show the following Stderr output

<core_client_version>7.0.64</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code -1073741790 (0xc0000022)
</message>
<stderr_txt>
setiathome_v7 7.00 DevC++/MinGW/g++ 4.5.2
libboinc: 7.1.0

Work Unit Info:
...............
WU true angle range is : 0.407771
Optimal function choices:
--------------------------------------------------------
name timing error
--------------------------------------------------------
v_BaseLineSmooth (no other)
v_vGetPowerSpectrumUnrolled 0.000056 0.00000

</stderr_txt>
]]>
______________

Looks like the servers finally figgered out 5.0 was not the way to go on my 295 rig.
Now all 2.3 tasks in the cache.

---

"Time is simply the mechanism that keeps everything from happening all at once."

ERR_FOPEN -108 system fopen The file is "open" and in use by another process, or write access to the file cannot be obtained.

hm, virus scan running in that directory?

The rig is running Bitdefender, and although it didnt detect anything with the file, I have not put the entire directory under exclusions and restarted the system. It downloaded a fresh batch of v7 CPU files, eight of which got trashed within seconds, while the second batch seems to be crunching fine, till now. All of those WUs show the following Stderr output

<core_client_version>7.0.64</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code -1073741790 (0xc0000022)
</message>
<stderr_txt>
setiathome_v7 7.00 DevC++/MinGW/g++ 4.5.2
libboinc: 7.1.0

Work Unit Info:
...............
WU true angle range is : 0.407771
Optimal function choices:
--------------------------------------------------------
name timing error
--------------------------------------------------------
v_BaseLineSmooth (no other)
v_vGetPowerSpectrumUnrolled 0.000056 0.00000

</stderr_txt>
]]>

0xc0000022 is STATUS_ACCESS_DENIED with the following description: "{Access Denied} A process has requested access to an object but has not been granted those access rights."

You might want to double check what that AV is doing.

Since some of the tasks do manage to start and then die to that error another possibility is that you have permissions problems in the project directory and/or in slots directory. Check those too.

edit: That same computer is having problems with Einstein (host there) tasks too. The error there is:

The system cannot find the file specified.
(0x2) - exit code 2 (0x2)

hmmmm, one big disaster for now. Errored out more than 400 tasks pfff

Way to go for me was just totally uninstall Boinc, re-install and run stock for now. Seti is throwing all sorts of versions my way which some error out too like the opencl 6.04 AP which my videocard doesn't even support.

Ah well, when a working optimized installer comes out I'll try again. a thread will surely come up on the board when it's there.

---

This workunit could be in trouble,

http://setiathome.berkeley.edu/workunit.php?wuid=1256003580

Cheers.

It appears that the maximum run time setting of V7 units may be set a bit tight.

For install and testing purposes. I started V7 crunching running only one unit per GPU. When I was happy all was working properly I switched back to 2 per GPU.

As a result of this I trashed 60 odd units with -177 errors, all timing out after ~250 seconds. There has been no errors with units downloaded since that batch.

I thought the timeout was 10x the expected run time but these failures were only 2x ?

T.A.

You might want to double check what that AV is doing.

Since some of the tasks do manage to start and then die to that error another possibility is that you have permissions problems in the project directory and/or in slots directory. Check those too.

edit: That same computer is having problems with Einstein (host there) tasks too. The error there is:

The system cannot find the file specified.
(0x2) - exit code 2 (0x2)

This is really strange as this is my main rig and has had no changes in it. The issue began after the v7 release. I have now reset the rig and tuned down the AV scans. File and folder permissions are all ok. The system has downloaded a fresh batch of WUs along with the executables, seems to be crunching along. Will report back later.

I repeat here part of a discussion started in the news forum

1) All the Stock v7 GPU apps are Lunatics apps now!
2) You did go and enable 'SETI@home v7: yes' in your project preferences didn't you?
3) No, you copy and paste it from one of the posts in Number Crunching, and edit it to your requirements.

1: great! But Only GPU? Why not CPU Too? Sooner or Later?
2: NO, I didn't. Now I've done it on project page and I'v done "update" on the host 25 min ago. Nothing, untill now. Have I to reset again or have I only to wait?
3: What do you mean with (mine) requirements?

I have found this:

Make a new text file named app_config.xml and have this in the contents

<app_config>
<app>
<name>setiathome_v7</name>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>.04</cpu_usage>
</gpu_versions>
</app>
</app_config>


and this

<app_config>
<app> <name>setiathome_enhanced</name>
<max_concurrent>6</max_concurrent>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>0.04</cpu_usage>
</gpu_versions>
</app>
</app_config>

... ad many others ....
Where can I find instructions to build different files?

As I understand I will have V6 and V7, both GPU and CPU.
On some Hosts I run only one GPU task, on three ones I run two.

Thanks in advance for any clear answer

---

I repeat here part of a discussion started in the news forum

1) All the Stock v7 GPU apps are Lunatics apps now!
2) You did go and enable 'SETI@home v7: yes' in your project preferences didn't you?
3) No, you copy and paste it from one of the posts in Number Crunching, and edit it to your requirements.

1: great! But Only GPU? Why not CPU Too? Sooner or Later?
2: NO, I didn't. Now I've done it on project page and I'v done "update" on the host 25 min ago. Nothing, untill now. Have I to reset again or have I only to wait?
3: What do you mean with (mine) requirements?

1) No, Lunatics CPU apps won't become Stock apps (not at present anyway), it'll be too complicated project side making sure each app only goes to the right host, better to have a single app as Stock that covers all bases,
Lunatics has supplied improvements to the Stock v7 CPU app, it now does more function tests than 6.03 and choices the functions that are fastest, so it is faster than the old 6.03 app, especially on AVX hosts,
it also uses a newer fftw dll giving a further ~10% speedup.
2) Most of your hosts are running anonymous platform with Setienhanced v6 apps in them, you can't get v7 work until until either you update your app_info's with v7 apps, or you revert to Stock.
3) Depends on how many total tasks you want to run at once, and how many total GPU tasks you want to run at once, so your requirements, Edit the app_config.xml as you see fit,
But it's pointless setting a v7 app_config entry if you can't do v7 work, see answer 2.

Where can I find instructions to build different files?

What do you mean by that? are you after the source code and instructions for building applications or Boinc?, or how to do a app_config.xml?

Claggy

answer to claggy 1375285

1) clear
2) I have renamed app_inf in two hosts (one yesterday [6334665] and the other hours ago [5381180]) reverting to stock but no V7 at all. Only V6 of different types. Of course I have restard Boinc and reset project. Preferences are "SETI@home v7: yes". I usually walk step by step. If something works I extend to all hosts. I' still waitng to know if I have only to wait or if I have some mistake.
3)for CPU max can be all CPUS, for GPUS it depends from GPU type. I known which GPU is able to run 1 or 2 task, with the previous lunatics apps. I think it should be the same with new one, correct? Does exist some page showing us how to write a good app_config.xml?

---

answer to claggy 1375285

1) clear
2) I have renamed app_inf in two hosts (one yesterday [6334665] and the other hours ago [5381180]) reverting to stock but no V7 at all. Only V6 of different types. Of course I have restard Boinc and reset project. Preferences are "SETI@home v7: yes". I usually walk step by step. If something works I extend to all hosts. I' still waitng to know if I have only to wait or if I have some mistake.
3)for CPU max can be all CPUS, for GPUS it depends from GPU type. I known which GPU is able to run 1 or 2 task, with the previous lunatics apps. I think it should be the same with new one, correct? Does exist some page showing us how to write a good app_config.xml?

2) Host 6334665 has had plenty of v7 work. Host 5381180 has already got a whole shitload of work allocated to it, including 75 Astropulse v6 tasks, you'll have to get those resent, and crunched before you'll start getting Seti v7 tasks.

3) It is not CPU max, it is max_concurrent, that is GPU & CPU, if you put that as 4, and put gpu_usage as 0.5 you'll run two on the GPU and two on the CPU (a total of four), As with all Boinc configuration, it is in the Wiki: Client configuration

Claggy

It appears that the maximum run time setting of V7 units may be set a bit tight.

For install and testing purposes. I started V7 crunching running only one unit per GPU. When I was happy all was working properly I switched back to 2 per GPU.

As a result of this I trashed 60 odd units with -177 errors, all timing out after ~250 seconds. There has been no errors with units downloaded since that batch.

I thought the timeout was 10x the expected run time but these failures were only 2x ?

T.A.

The timeout is 10x the server estimate of runtime, the splitters still set that 10x factor. Maybe the reason it looks like 2x on your systems is because you're running BOINC 6.10.x so duration_correction_factor (DCF) affects your local run time estimates. For those running BOINC 7.x the local estimate matches the server estimate because DCF is disabled.

                                                                  Joe

One WU finished waiting for validation.

http://setiathome.berkeley.edu/result.php?resultid=3023153356

Will keep an eye one things.

Much appreciated here :) Dr Ivan mentioned, buried amidst the chaos, that he's going to have a look for x41zc update needs, and Urs provided some helpful starting suggextions.

Seems 41g works OK, so far no errors and only a few inconclusive.

http://setiathome.berkeley.edu/results.php?hostid=6636133&offset=0&show_names=0&state=0&appid=11

Well hope you and Ivan get the x41zc update working :)

2) Host 6334665 has had plenty of v7 work. Host 5381180 has already got a whole shitload of work allocated to it, including 75 Astropulse v6 tasks, you'll have to get those resent, and crunched before you'll start getting Seti v7 tasks.

3) It is not CPU max, it is max_concurrent, that is GPU & CPU, if you put that as 4, and put gpu_usage as 0.5 you'll run two on the GPU and two on the CPU (a total of four), As with all Boinc configuration, it is in the Wiki: Client configuration

Claggy

2) Ok, Now (this morning, at my time) I see them too.
3) Ok, everything is clear, now. I will read that page.
Thanks

---

answer to claggy 1375285

1) clear
2) I have renamed app_inf in two hosts (one yesterday [6334665] and the other hours ago [5381180]) reverting to stock but no V7 at all. Only V6 of different types. Of course I have restard Boinc and reset project. Preferences are "SETI@home v7: yes". I usually walk step by step. If something works I extend to all hosts. I' still waitng to know if I have only to wait or if I have some mistake.
3)for CPU max can be all CPUS, for GPUS it depends from GPU type. I known which GPU is able to run 1 or 2 task, with the previous lunatics apps. I think it should be the same with new one, correct? Does exist some page showing us how to write a good app_config.xml?

2) Host 6334665 has had plenty of v7 work. Host 5381180 has already got a whole shitload of work allocated to it, including 75 Astropulse v6 tasks, you'll have to get those resent, and crunched before you'll start getting Seti v7 tasks.

3) It is not CPU max, it is max_concurrent, that is GPU & CPU, if you put that as 4, and put gpu_usage as 0.5 you'll run two on the GPU and two on the CPU (a total of four), As with all Boinc configuration, it is in the Wiki: Client configuration

Claggy

Claggy are you saying I can get even the cpu to double up on how many it does with Lunatics ?
Or you talking stock v7

Currently my Quaddy does max of 4 ..so I can get it to do 8 ?
if so now I get why my Rac doesn't show upwards of 9000 I've been expecting 20000 or close to that

---

Claggy are you saying I can get even the cpu to double up on how many it does with Lunatics ?

In the past running more than 1 WU per CPU core has always resulted in a signifcant reduction in processing done.
With a GPU running 2 or 3 at a time just takes the GPU utilisation up to 100%, which is what a CPU core runs at when processing a WU.

---

Grant
Darwin NT

Claggy are you saying I can get even the cpu to double up on how many it does with Lunatics ?

In the past running more than 1 WU per CPU core has always resulted in a signifcant reduction in processing done.
With a GPU running 2 or 3 at a time just takes the GPU utilisation up to 100%, which is what a CPU core runs at when processing a WU.

Umm so no then ? I already have the GPU doing 3

I also checked my app_info file and it does not have

<app_config>
<app>
<name>uppercase</name>
<max_concurrent>1</max_concurrent>
<gpu_versions>
<gpu_usage>.5</gpu_usage>
<cpu_usage>.4</cpu_usage>
</gpu_versions>
</app>
</app_config>

the example from Bionic page you put up Claggy

I could not figure out thou if this is stock
seeing as it's not in my xml file I just leave it till I read up some more thanks thou Grant

---

Claggy are you saying I can get even the cpu to double up on how many it does with Lunatics ?

In the past running more than 1 WU per CPU core has always resulted in a signifcant reduction in processing done.
With a GPU running 2 or 3 at a time just takes the GPU utilisation up to 100%, which is what a CPU core runs at when processing a WU.

Umm so no then ? I already have the GPU doing 3

I also checked my app_info file and it does not have

the example from Bionic page you put up Claggy

I could not figure out thou if this is stock
seeing as it's not in my xml file I just leave it till I read up some more thanks thou Grant

Not app_info.xml, But app_config.xml, different files doing different things, app_info.xml specifies what apps Boinc should run via anonymous platform, app_config.xml puts limits on how many from a app name that can run at once,
enables other projects to run an instance or two, again you can specify how many of their apps names you want to run at once, So rather than Boinc 7 flipping between projects as the priorities change, it runs work from each constantly.

Claggy

Hi, as suggested I have prepared an app_config.hml file for hosts in which GPU I want to run 2 intances.

Here is my file

<app_config>
    <app>
    <name>setiathome_v7</name>
    <gpu_versions>
       <gpu_usage>0.5</gpu_usage>
       <cpu_usage>.4</cpu_usage>
    </gpu_versions>
</app>
<app>
    <name>astropulse_v6</name>
    <gpu_versions>
       <gpu_usage>0.5</gpu_usage>
       <cpu_usage>0.4</cpu_usage>
    </gpu_versions>
    </app>
</app_config>

As I can see, it' working.
In one hosts now I see two
SETI@home 6.04 AstroPulse v6 (opencl_nvidia_100) running
and in the other I see two
SETI@home 7.00 SETI@home v7 (cuda50) Running

Same file in both host.
But in both host I'v got the message : app setiathome_v7 not found in app_config.xml

---