I had an app_info.xml file set up to run "lunatics" optimized applications but wanting to update the stock setiathome_v7 executable, and hoping to pick up the astropulse version 6.07 executable, I renamed the app_info.xml file then drained out all the work units, terminated and restarted boincmgr, and did a "reset project". I get the following error:
your app_config.xml file refers to an unknown application 'astropulse_v6'
Here is the app_config.xml file ---
<app_config>
<app>
<name>setiathome_v7</name>
<max_concurrent>7</max_concurrent>
<gpu_versions>
<gpu_usage>0.33</gpu_usage>
<cpu_usage>0.1</cpu_usage>
</gpu_versions>
</app>

<app>
<name>astropulse_v6</name>
<max_concurrent>3</max_concurrent>
<gpu_versions>
<gpu_usage>0.33</gup_usage>
<cpu_usage>0.1</cpu_usage>
</gpu_versions>
</app>
</app_config>

What's up?? If I don't have a usable version of astropulse_v6 isn't the current version supposed to be downloaded "automatically" when the app_info.xml file is not present? I do have an nvidia GPU installed that was previously running the "lunatics" _x41g_ code.
Or maybe just tell me what files I should delete before doing a "reset project" in order to reload all the usable applications. (For Linux x86_64 with a CUDA capable Nvidia GPU)

---

It seems that BOINC is still seeing the app info file.

---

BOINC WIKI

I renamed the app_info.xml (see below) so there isn't any "app_info.xml" in the directory.

gene64:> pwd
/home/gene/BOINC/projects/setiathome.berkeley.edu
gene64:> ls *.xml
app_config.xml back-app_info.xml
gene64:>

Is a previous app_info.xml preserved in client_state or some other file exchanged between host and server ?? Yes, I am puzzled by inconsistent error messages labeled as from app_info.xml when I have tried to do things in app_config.xml that are not supported in parsing that file.

Somewhere long ago I think I saw a forum message describing what files (in the project/setiathome.berkeley.edu directory to delete if one wanted to reinitialize the whole setup. Is there a way to do that?

---

Well no, your error message doesn't mention app_info.xml, but app_config.xml
Have you tried already, to temporarily remove the app_config.xml file as well, to then do a project reset, wait for BOINC to download all the necessary applications, and then put the app_config.xml file back?

BOINC checks at start-up what's available, so when it then finds an app_config.xml file, but not the science application that's mentioned in the app_config.xml file, it will flag that and throw a message about it.

It's just as you having not enough money in your account, but money will come in later in the day. When you then try to pay with a debit card before this money is in, you can't pay, and you'll get a message that you don't have enough money in the account. Doesn't matter that 10 minutes later there's trillions in there, at the moment you needed it, it wasn't there.

And on top of that, Astropulse tasks aren't always available. Since the science application is only downloaded at the moment that work is actually appointed to you, it can take quite a while before the Astropulse application gets downloaded. At this moment, there is no Astropulse work.

---

I'll try removing the app_config.xml and a reset project.
I think I tried that before but it's easy enough to do again and wait a few days for Astropulse jobs to appear. I am a bit uncertain, though, whether I will get 32-bit Astropulse stock instead of the 64-bit CUDA Astropulse that I really want.
I can see that the CONFIG.xml doesn't accept settings that should be in INFO.xml but the informative message is not clear; eg. when I put in a <app-version> element I see the following in the Event Log (and also in the stdoutdae.txt) --
----
14-Feb-2014 16:15:03 [---] Re-reading cc_config.xml
14-Feb-2014 16:15:03 [---] Not using a proxy
14-Feb-2014 16:15:03 [---] log flags: file_xfer, sched_ops, task, unparsed_xml
14-Feb-2014 16:15:03 [SETI@home] Found app_config.xml
14-Feb-2014 16:15:03 [SETI@home] Unparsed line in app_info.xml: app_version
14-Feb-2014 16:15:03 [SETI@home] Unparsed line in app_info.xml: app_version
14-Feb-2014 16:15:03 [SETI@home] Your app_config.xml file refers to an unknown application 'astropulse_v6'. Known applications: 'setiathome_v7'
----
i.e. in lines 5 & 6 the message refers to "app_info.xml". (???)
...
This app_config.xml was not the one quoted in the OP but just an example, to clarify, what I was seeing that seemed to point to an app_info.xml file.
O.K., here we go with a reset project...

---

Well, if you want <app_version> to be recognized by BOINC, you need to use 7.2.39
7.2.33 doesn't support it on app_config.xml.

7.2.39 just became the new recommended yesterday, so is available from the BOINC download page (Berkeley version).

Why it said app_config.xml first, then switched to app_info.xml to then switch back to app_config.xml, I don't know. May have been a bug in 7.2.33

See if it behaves differently with 7.2.39 first.

---

Re: boinc 7.2.39 -- In browsing the forum I saw references to features not in the (then) current 7.2.33 that _were_ available in the 7.2.34, ..36, ..38 versions but I was given to understand that the even number versions were developmental versions not recommended for public use. O.K., thanks for the heads up on the new 7.2.39 release. I sure hope the documentation on the syntax for the .xml file has been updated to correspond to what is supported in the .39 version.
Re: remove app_config.xml -- that seemed to work. No message regarding "unknown application" since, of course, there was NO app_config.xml file! Normal 7.01 apps downloaded (for x86_64 platform) and by just good luck a few hours later the 6.07 Astropulse (nvidia) apps also loaded and work units followed.
Now, I guess, I'm unclear what the role of the app_config.xml file really is. If things run without it is it just for fine tuning the resource allocation? I'll go look in the Number Crunching forum for more guidance on the content of the app_config.xml file. I know there's a help file on app_config.xml somewhere, if I can just remember where it was.

---

I know there's a help file on app_config.xml somewhere, if I can just remember where it was.

Here:
app_config.xml

Most people use the file to run more than one task per GPU (<gpu_usage>.5</gpu_usage> for 2 tasks)
and/or to auto-free a CPU core when some type of GPU task is running (<cpu_usage>1.0</cpu_usage>)

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

Re: boinc 7.2.39 -- In browsing the forum I saw references to features not in the (then) current 7.2.33 that _were_ available in the 7.2.34, ..36, ..38 versions but I was given to understand that the even number versions were developmental versions not recommended for public use.

To elaborate on that, it is the minor version that is important in determining if a release is an alpha or development release vs. a supported release.

For example, anything in the 7.2.x range is usually considered safe. However, anything in the 7.3.x range will be developmental. The 7.4.x will be the next minor release with features from 7.3.x.

So versions like 7.2.39 / 7.2.33 are still in an even-numbered minor version and are safe for full release.

O.K., downloaded boinc 7.2.39 and will switch to it "soon." I want to drain my work unit queue; not strictly necessary, I suppose, but I want to create an app_config.xml and app_info.xml file to use with it so I feel better doing that from a clean start.
The boinc client configuration documentation is helpful but assumes more detailed knowledge of boinc/seti than I have. For example, one item in the app_config file is the <plan_class> and the "helpful" explanation for this is that this is where one supplies the "plan_class" of the application...
Oh, well, Q&A is not the best venue to pursue this any further. Thanks for the help here and I'll go browse, and post, in the main forums.
..
Edit: ..and I forgot about the BOINC forums, too...

---