I run BOINC on a small network server with an Opteron processor, under Linux (Fedora 17). My setup meets the requirements for running CPDN, and any of the models as far as I can see (disc space, processor speed, memory). However when trying to download work I get a message that no work is available, and also that my computer isn't suitable for the project.

Is there a a processing requirement I have missed, or a setting I need to change?

David

---

That's perfectly normal, as there is no work right now on the server: link. The work comes out sporadically. If you leave network activity enabled in BOINC you may catch a reissued task.

As to why you're receiving some message saying your machine isn't suitable--I can't see why: your processors and memory all seem up to the standards. Maybe check to see if you have the 32-bit compatiblity libraries installed: link.

Thanks for your note. So CPDN is running in 32bit - I'll install the i686 libraries & see what happens. (I know there is a lack of work at the moment, but the 'not suitable' message was irritating.) I have CPDN running on my desktop machine, but that has the i686 libraries installed for other things, and I hadn't spotted the difference.

(I don't think any compatibility libraries are needed - there are none on my desktop. So when I'm sure it's all running, I'll update the wiki.)

---

There's a sticky post at the top of this Linux section about the need for the 32 bit libraries.

---

Backups: Here

(I don't think any compatibility libraries are needed - there are none on my desktop. So when I'm sure it's all running, I'll update the wiki.)

I can assure you they are. We've had post after post of people with PCs crashing cpdn tasks because of the lack of such libraries on 64 bit Linux. After installing the libraries, their PCs were able to complete cpdn tasks.

Now I'm not sure why Boinc isn't even trying to download tasks. I've seen it before and it may have something to do with the 32bit libraries, but there must be different symptoms with different distributions/installs, depending on what libraries are installed as part of the base distribution, and what additional 32bit libraries might be installed as part of some optionally installed packages. It gets complicated.

I don't think any compatibility libraries are needed...

I think the confusion arises because someone installs a new operating system and then soon after installs something that pulls in 32-bit libraries--like Adobe Reader. Then they install BOINC and everything runs splendidly. "Who are these geeks who wail about 32-bit libraries?", they think. But the person who installs BOINC right after a new install will crash all 32-bit tasks until the cows come home. Later the two meet in a bar and get in fist-fight over it; worse they're Americans with concealed-carry permits (yes, there are states which allow guns in bars).

At least with distribution packages the BOINC people should make the 32-bit libraries a dependency. Lives may be at stake.

I have a 64-bit Opteron processor and have 32-bit Linux installed on it. But it also runs a VirtualBox and a 64-bit Solaris OS on it running SETI@home and another VirtualBox with Test4Theory@home from CERN.
Tullio

---

Thanks for your note but I think the confusion is that my emphasis was on compatibility but the responses have been about 32-bit libraries.

From running CPDN over the last week or so I agree entirely that it needs 32-bit libraries to run. But it looks as if these can be the stock libraries for whatever distribution & kernel you have installed. There is nothing particularly unusual about this, as you say these are pulled in for all sorts of programs. (It would help if they were routinely identified as a dependency for BOINC. It looks like you need libstdc++, libc, gcc & zlib.)

However, with respect, compatibility libraries are entirely different. These are libraries from a previous version which have to be used because the program won't run with the newer libraries. They should only be a temporary fix, and are a potential source of security problems or instability. The library suggested in the link on the Wiki is from GCC 3.3.4 (? from 2004), the current version is 4.7.2 (from last Sept).

I'll keep running CPDN, without compatibility libraries & report back.

---

I think that the real confusion is that Belfry used the word compatibility, and then you did.

To be sure about this, what's required are all libraries needed to run 32 bit versions of programs.
As well as for the general running of the climate program, (several files/libs), at least one is needed just for each of:
displaying graphics (using the Show graphics button), and
collecting up all of the small, progress files, so that they can be zipped for return to the project.

Where the library files come from, and what version they are, (provided they meet the minimum version needed by the project's compiler), is of no importance.

---

Backups: Here

I see what you are saying RhiOwGwil. The wiki is advice about installing certain rpms for running 32bit applications on 64bit linux, trying to cover all bases for just about any 32bit application. It's certainly possible (probable?) that not every one of those suggested rpms is necessary specifically for cpdn.

However, I never did a test, rpm by rpm, on a clean install of 64 bit linux to see which of those suggested rpms weren't needed to stably run cpdn.