Bug 671288

That's really strange, I'm running the same without any problems. Have you done a new setup or is it an old configuration that stopped working. Would you try restarting the tasks?

Tried restarting the client - no joy.
Tried detaching/reattaching the project - no joy.

Found this post http://www.worldcommunitygrid.org/forums/wcg/viewthread_thread,28642 

on "BOINC: [error] App version has unsupported platform xxxxxxxxxx" 

and did what is said, placing the cc_config.xml file in /var/log/boinc. Currently there is now one task running, so fingers crossed.

Thanks
Joe

PS. WCG has a limit on number of daily downloads, so my search for a solution may have busted that, i.e. only one task running may be perfectly OK.

Good news, 

boinc seems to be running OK, work units being requested, processed and validated by WCG. 

I think you can close the issue. 

Whether the documentation/installation should reflect the change to cc_config.xml I leave up to you as package owner.

I was having the same problem and Google found this.  I took a look for that line in the existing boinc files.  I was able to see the line that forum entry spoke of on one computer but not another.  I have no idea why it showed up in one place but not the another.  

In Summary:
the line:
<alt_platform>i686-pc-linux-gnu</alt_platform>
exists in /var/lib/boinc/client_state.xml for fedora.
Mine exists between the <newer_version> node and the <proxy_info> node.
I tried changing the file with boinc-client stopped.  Nothing good came of it. 

I think that I had registered the PC name with boinc with a 32-bit OS, now that I upgraded to 64-bit with the same name, there is sadness.  I think that boinc or WCG controls the PC config file and that the problem is their issue. Its not a big deal, though... 

Thank you Joe for posting your findings!

Jason,

I'm not sure about the file name/location. 

On my x86_64 Fedora 14, the file is /var/lib/boinc/cc_config.xml and contains

<?xml version="1.0" encoding="ISO-8859-1" ?>
<cc_config>
   <log_flags>
      <task>1</task>
      <file_xfer>1</file_xfer>
      <sched_ops>1</sched_ops>
      <checkpoint_debug>1</checkpoint_debug>
   </log_flags>
   <options>
      <alt_platform>i686-pc-linux-gnu</alt_platform>
   </options>
</cc_config>

==== EOF ====

AFAIK it has to be in that location.

But I agree it should be sorted out by the authors/packing not by users on an ad hoc basis. You need to restart the boinc-client after modifying cc_config.xml.

My system has been happily processing work units for the past week or so. So I guess it just a matter of tidying up the solution.

Joe,

not sure what I can do here:

- I cannot reproduce this
- looking into build logs, there is always i686-pc-linux-gnu as an alternate platform detected properly for x68_64 builds.

Can you still reproduce the issue (= if you remove the cc_config.xml)? If yes, could you please pack /var/lib/boinc/*.xml and attach here?

Thank you,
Milos

Milos,

I deleted cc_config.xml, and it ran OK. [OK only tried for a few minutes, but it was working]

I erased boinc-client, boinc-manager packages. Cleared out /var/lib/boinc abd /var/log/boinc*.

Installed boinc-client, boinc-manager packages, connected to WCG and it downloaded some stuff and finally said:

07-Feb-2011 19:47:47 [World Community Grid] [error] App version has unsupported platform i686-pc-linux-gnu
07-Feb-2011 19:47:47 [World Community Grid] [error] No application found for task: i686-pc-linux-gnu 611 ; discarding

Which is where we came in ...

I've attached the current .xml files.

Joe

Created attachment 477493 [details]
Contents of /var/lib/boinc/*.xml on failure to start

Comment on attachment 477493 [details]
Contents of /var/lib/boinc/*.xml on failure to start

Fresh install after connecting to project.

Joe, can you still reproduce? If so, can you please also attach /var/log/boinc* files?

Hi Milos,

Good and bad news.

Firstly, I am now running F15:
[root@neon log]# uname -a
Linux neon.aleph.org.uk 2.6.40.3-0.fc15.x86_64 #1 SMP Tue Aug 16 04:10:59 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

I did a complete re-installation of boinc-client and boinc-manager. Please note I removed all boinc files from /var by hand after the packages were removed.

Some tasks are running OK. (Only been up a short while).

However, there are still boinc error reports:
29-Aug-2011 11:57:23 [World Community Grid] [error] App version has unsupported platform i686-pc-linux-gnu
29-Aug-2011 11:57:23 [World Community Grid] [error] No application found for task: i686-pc-linux-gnu 640 ; discarding

I have attached the full log.

Additionally, selinux is not happy, about read/write to nvidiactl, file attached.

Hope that Helps
Joe

Created attachment 520364 [details]
/var/log/boinc.log

Created attachment 520365 [details]
selinux error report on boinc startup

I have the same problem.

my steps:
1. installed fedora 15 x64 from DVD on KVM virtual host. (hypervisor also F15 x64)
2. run:
'sudo yum -y update' on guest OS
'sudo yum -y install boinc-client boinc-manager'
3. logged into boinc-manager and enter account info.
4. in "Message" tab a receive the same:

"
[World Community Grid] [error] App version has unsupported platform i686-pc-linux-gnu
[World Community Grid] [error] No application found for task: i686-pc-linux-gnu 611 ; discarding
"

Nothing calculates. 

Do U need any additional info from me?

forgot, SELinux disabled. firewall is ok. Guest OS connect to internet via NAT.

I repeated all commands with 32 bit version of Fedora 15. It's work fine from the box.
It's seems to be an x64 issue. Can I do some tests on this x64 OS to identify problem?

I am using Fedora 16 64-bit and was having the same problem with the "unsupported platform error". I followed the advice to create a cc_config.xml file in the /var/lib/boinc directory and add an alternative platform xml tagset from this link:

http://www.worldcommunitygrid.org/forums/wcg/viewthread_thread,28642

I issued a "service boinc-client restart" as root and it immediately fetched 2 new tasks and is compiling them now.

my /var/lib/boinc/cc_config.xml file contains the following:

<cc_config>
  <log_flags> <task>1</task> <file_xfer>1</file_xfer>
    <sched_ops>1</sched_ops> <checkpoint_debug>1</checkpoint_debug>
  </log_flags>
  <options>
    <alt_platform>i686-pc-linux-gnu</alt_platform>
  </options>
</cc_config>

Perhaps this file should be added by default to the 64-bit boinc package?

I am having this problem too.
Fedora 16 and WCG project 6.10.58

That workaround from WCG does not work.
I have opened a new thread about that
https://secure.worldcommunitygrid.org/forums/wcg/viewthread_thread,32171

I was able to reproduce this issue on RHEL 6 (via scientific linux). 

2.6.32-131.21.1.el6.x86_64 #1 SMP Tue Nov 22 14:15:09 CST 2011 x86_64 x86_64 x86_64 GNU/Linux

I suspect the problem is related to installing a version from the boinc website. This may have an interaction with the version from EPEL.

Removing all *boinc* from the filesystem and re-installing from EPEL resolved it for me.

No it is not related to installing a version from the boinc website, because I have installed it from Fedora repositories

I think this bug:
- it is a WCG project bug
OR
- it should be fixed on upstream

This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping