GLIBC problems on Linux


Advanced search

Message boards : Problems and Help : GLIBC problems on Linux

Author Message
wigyori
Send message
Joined: 5 Jan 16
Posts: 3
Credit: 370,174
RAC: 0
Message 14344 - Posted: 17 Mar 2016, 14:17:53 UTC

Hi,

I'm running GPUgrid on a Debian Wheezy x64 box with a GTX950 (ID: 69067). Recently I've started getting missing GLIBC compat errors as below:

Worker thread monitor up.
./blender: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by ./lib/libX11.so.6)
./blender: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.15' not found (required by ./lib/libX11.so.6)
|[-->] Info:

(Example job ID is 9068925.)

$ strings /lib/x86_64-linux-gnu/libc-2.13.so |grep GLIBC
GLIBC_2.2.5
GLIBC_2.2.6
GLIBC_2.3
GLIBC_2.3.2
GLIBC_2.3.3
GLIBC_2.3.4
GLIBC_2.4
GLIBC_2.5
GLIBC_2.6
GLIBC_2.7
GLIBC_2.8
GLIBC_2.9
GLIBC_2.10
GLIBC_2.11
GLIBC_2.12
GLIBC_2.13
GLIBC_PRIVATE
GNU C Library (Debian EGLIBC 2.13-38+deb7u10) stable release version 2.13, by Roland McGrath et al.
$

Can the apps be updated to support these *cough* legacy systems? (If I were to install a native blender, in Wheezy that'd be 2.63a-1+deb7u1.)

Thanks,
-w-

Profile Janus
Volunteer moderator
Project administrator
Avatar
Send message
Joined: 16 Jun 04
Posts: 4483
Credit: 2,094,806
RAC: 0
Message 14346 - Posted: 17 Mar 2016, 20:26:47 UTC
Last modified: 17 Mar 2016, 20:33:08 UTC

Thanks for the "strings" trick, didn't know that one. I'm a little surprised to see that Wheezy ships with a libc from early 2011, 2.22 should have been out by the time - 2.23 was released a couple of weeks ago.
If you install Blender (the old version, don't worry it will not actually be used) through your repository and then make a file in the project directory of BOINC called "native" you may be able to run the client already through the use of native libraries. Or it may break and still not work - but it is worth a shot if you haven't tried it.

See The Linux Sticky in the Client forum for more info.

wigyori
Send message
Joined: 5 Jan 16
Posts: 3
Credit: 370,174
RAC: 0
Message 14347 - Posted: 18 Mar 2016, 12:15:32 UTC

Yeah - wheezy is kind of the "oldstable" while jessie is the "current stable", so it's indeed a bit rusty already, its initial release was back in 2013.

Anyway, I'll give a go for the "native" trick and see how it goes. :)

Thanks,
-w-

wigyori
Send message
Joined: 5 Jan 16
Posts: 3
Credit: 370,174
RAC: 0
Message 14348 - Posted: 18 Mar 2016, 13:29:06 UTC - in response to Message 14346.

OK, the "native" did the trick, at least the WUs are starting up. However, it doesn't seem to use the GPU (at least based on the nvidia-smi output) - is this varying from task to task?

Thanks,
-w-

Profile Janus
Volunteer moderator
Project administrator
Avatar
Send message
Joined: 16 Jun 04
Posts: 4483
Credit: 2,094,806
RAC: 0
Message 14350 - Posted: 19 Mar 2016, 11:47:07 UTC
Last modified: 19 Mar 2016, 12:12:22 UTC

Yes, the only GPU support we have right now is for cycles tasks and it is very experimental and is only run very occasionally. The hope is to ramp it up once the first few issues have been ironed out - it seems like a good platform for rendering.


Post to thread

Message boards : Problems and Help : GLIBC problems on Linux