Troubles on Linux


Advanced search

Message boards : Problems and Help : Troubles on Linux

1 · 2 · Next
Author Message
Sir Stooper
Send message
Joined: 29 Jun 13
Posts: 1
Credit: 63,544
RAC: 0
Message 11957 - Posted: 2 Aug 2013, 7:05:56 UTC

Hi all,

I have tried to run the project on my Linux machine (xubuntu 13.04 64-bit) but am having troubles. Every WU is failing. I am pretty new to linux and don't really know where to start. Each WU will produce an stderr with similar outputs:

<core_client_version>7.0.65</core_client_version> <![CDATA[ <message> process exited with code 247 (0xf7, -9) </message> <stderr_txt> ---------------------------- GLUE ---------------------------- Detected input arg: argv[0] is ../../projects/burp.renderfarming.net/blender_4.78_x86_64-pc-linux-gnu Setting basename to blender_4.78_x86_64-pc-linux-gnu from ../../projects/burp.renderfarming.net/blender_4.78_x86_64-pc-linux-gnu Detected input arg: argv[1] is blender Setting command to blender Detected input arg: argv[2] is -noaudio -y -b Setting preopts to -noaudio -y -b Detected input arg: argv[3] is -P clirender.py -- -F PNG -t 1 -f 732 0.0 0.0 1.0 1.0 Setting postopts to -P clirender.py -- -F PNG -t 1 -f 732 0.0 0.0 1.0 1.0 Detected input arg: argv[4] is --kill Setting no-progress threshold to 676000 Detected input arg: argv[5] is 676000 $Id: BOINCHandler.cpp 1278 2011-01-23 09:22:45Z jbk $ Initializing stdout redirection, all output from now on will be redirected to a file boinc_init_diagnostics() completed boinc_init_options() completed boinc_get_init_data() completed CPU performance profile completed: 2755780910.125072 fpops, 15575849119.731014 iops reported. p_c is 1375021464.851725 Mapping logical files to physical destinations: in => in out.zip => ../../projects/burp.renderfarming.net/ses0000001678frm0000000732prt00001_0_0 ./linux_zip_x64_r600 => ../../projects/burp.renderfarming.net/linux_zip_x64_r600 ./linux_unzip_x64_r600 => ../../projects/burp.renderfarming.net/linux_unzip_x64_r600 Unpacking archives: blender_4.78_x86_64-pc-linux-gnu.zip => ../../projects/burp.renderfarming.net/blender_4.78_x86_64-pc-linux-gnu.zip ../../projects/burp.renderfarming.net/linux_unzip_x64_r600 -o -d "." ../../projects/burp.renderfarming.net/blender_4.78_x86_64-pc-linux-gnu.zip...done CHMODing executable... CHMODing preloader executable... Creating worker... Worker constructing... Worker constructed. $Id: glue.cpp 1303 2011-02-18 08:10:43Z jbk $ $Id: BOINCHandler.cpp 1278 2011-01-23 09:22:45Z jbk $ $Id: Controller.cpp 1432 2012-04-15 13:36:53Z jbk $ $Id: ProgressMonitor.cpp 1278 2011-01-23 09:22:45Z jbk $ Executing ./blender_ld --library-path ./lib ./blender -noaudio -y -b in -P clirender.py -- -F PNG -t 1 -f 732 0.0 0.0 1.0 1.0 Child created. Worker thread started Worker thread monitor almost up. Worker thread monitor up. ./blender: error while loading shared libraries: __vdso_time: invalid mode for dlopen(): Invalid argument |[-->] Info: |child <13311> to stdout |0 - ./blender_ld |1 - --library-path |2 - ./lib |3 - ./blender --------------------------- Exception caught: Worker application apparently died prematurely Status: -9 --------------------------- Calling boinc_finish()... 00:14:24 (13289): called boinc_finish </stderr_txt> ]]>


It seems an error arises while loading shared libraries: __vdso_time

I would appreciate any help.

overkill
Send message
Joined: 12 Jun 08
Posts: 56
Credit: 922,628
RAC: 0
Message 11959 - Posted: 4 Aug 2013, 14:00:58 UTC

I'm having the same problem. I just built a new machine (Debian Jessie / 3.9.8-1 x86_64) and sure I'm missing something, but I can't figure out what.

I unzipped blender_4.78_x86_64-pc-linux-gnu.zip to try to run manually.

Using the command...
./blender_ld --library-path ./lib ./blender -noaudio -y -b file2265897 -P clirender.py -- -F PNG -t 1 -f 806 0.0 0.0 1.0 1.0

I only get...
./blender: error while loading shared libraries: __vdso_time: invalid mode for dlopen(): Invalid argument

'ldd blender_ld' shows "statically linked", which seems appropriate.
'ldd blender' shows the following...
linux-vdso.so.1 (0x00007ffffb358000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f4efe4bc000)
libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007f4efe21d000)
libSDL-1.2.so.0 => /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0 (0x00007f4efdf80000)
libGL.so.1 => /usr/lib/x86_64-linux-gnu/libGL.so.1 (0x00007f4efdc63000)
libGLU.so.1 => /usr/lib/x86_64-linux-gnu/libGLU.so.1 (0x00007f4efd9e4000)
libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007f4efd6a5000)
libXi.so.6 => /usr/lib/x86_64-linux-gnu/libXi.so.6 (0x00007f4efd495000)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007f4efd292000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f4efd08d000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f4efce71000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f4efcb69000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f4efc86a000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f4efc4be000)
/lib64/ld-linux-x86-64.so.2 (0x00007f4efe6e1000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f4efc2a8000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f4efc08f000)
libasound.so.2 => /usr/lib/x86_64-linux-gnu/libasound.so.2 (0x00007f4efbd98000)
libpulse-simple.so.0 => /usr/lib/x86_64-linux-gnu/libpulse-simple.so.0 (0x00007f4efbb93000)
libpulse.so.0 => /usr/lib/x86_64-linux-gnu/libpulse.so.0 (0x00007f4efb947000)
libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007f4efb735000)
libdirectfb-1.2.so.9 => /usr/lib/x86_64-linux-gnu/libdirectfb-1.2.so.9 (0x00007f4efb4b0000)
libfusion-1.2.so.9 => /usr/lib/x86_64-linux-gnu/libfusion-1.2.so.9 (0x00007f4efb2a5000)
libdirect-1.2.so.9 => /usr/lib/x86_64-linux-gnu/libdirect-1.2.so.9 (0x00007f4efb08d000)
libcaca.so.0 => /usr/lib/x86_64-linux-gnu/libcaca.so.0 (0x00007f4efafc0000)
libts-0.0.so.0 => /usr/lib/x86_64-linux-gnu/libts-0.0.so.0 (0x00007f4efadbc000)
libnvidia-tls.so.304.88 => /usr/lib/x86_64-linux-gnu/tls/libnvidia-tls.so.304.88 (0x00007f4efabb9000)
libnvidia-glcore.so.304.88 => /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.304.88 (0x00007f4ef87cf000)
libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f4ef85af000)
libpulsecommon-4.0.so => /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so (0x00007f4ef8341000)
libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x00007f4ef813c000)
libjson-c.so.2 => /lib/x86_64-linux-gnu/libjson-c.so.2 (0x00007f4ef7f31000)
libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007f4ef7cec000)
libslang.so.2 => /lib/x86_64-linux-gnu/libslang.so.2 (0x00007f4ef7955000)
libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 (0x00007f4ef7725000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x00007f4ef74fb000)
libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007f4ef72f7000)
libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007f4ef70f2000)
libX11-xcb.so.1 => /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1 (0x00007f4ef6eef000)
libICE.so.6 => /usr/lib/x86_64-linux-gnu/libICE.so.6 (0x00007f4ef6cd4000)
libSM.so.6 => /usr/lib/x86_64-linux-gnu/libSM.so.6 (0x00007f4ef6acd000)
libXtst.so.6 => /usr/lib/x86_64-linux-gnu/libXtst.so.6 (0x00007f4ef68c7000)
libwrap.so.0 => /lib/x86_64-linux-gnu/libwrap.so.0 (0x00007f4ef66bc000)
libsndfile.so.1 => /usr/lib/x86_64-linux-gnu/libsndfile.so.1 (0x00007f4ef6454000)
libasyncns.so.0 => /usr/lib/x86_64-linux-gnu/libasyncns.so.0 (0x00007f4ef624e000)
libattr.so.1 => /lib/x86_64-linux-gnu/libattr.so.1 (0x00007f4ef6049000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007f4ef6042000)
libnsl.so.1 => /lib/x86_64-linux-gnu/libnsl.so.1 (0x00007f4ef5e2a000)
libFLAC.so.8 => /usr/lib/x86_64-linux-gnu/libFLAC.so.8 (0x00007f4ef5bf8000)
libvorbisenc.so.2 => /usr/lib/x86_64-linux-gnu/libvorbisenc.so.2 (0x00007f4ef5728000)
libvorbis.so.0 => /usr/lib/x86_64-linux-gnu/libvorbis.so.0 (0x00007f4ef54fb000)
libogg.so.0 => /usr/lib/x86_64-linux-gnu/libogg.so.0 (0x00007f4ef52f4000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007f4ef50dc000)

Is there anything else I can check to see what I'm missing?

Is burp still 32 bit? I remember having to install ia32-libs in the past, but I don't think it's being used anymore(?).

Thanks for any help.

Profile Janus
Volunteer moderator
Project administrator
Avatar
Send message
Joined: 16 Jun 04
Posts: 4487
Credit: 2,094,806
RAC: 0
Message 11962 - Posted: 11 Aug 2013, 17:42:54 UTC - in response to Message 11959.

Looks like the link loader in the official BURP linux client may need upgrading.

Is there anything else I can check to see what I'm missing?

Does your native libs work with the Blender client that the server sent? Try:
./blender -noaudio -y -b file2265897 -P clirender.py -- -F PNG -t 1 -f 806 0.0 0.0 1.0 1.0
(without the blender_ld)

The next version of Glue will have a way to switch between loaders if the one provided doesn't work on a particular system. Right now, unfortunately, your only option may be to use the anonymous platform method.

Is burp still 32 bit? I remember having to install ia32-libs in the past, but I don't think it's being used anymore(?).

It should be 64-bit now. There's a funny feature where the server sometimes opportunistically sends out 32-bit apps to 64-bit systems to check if they perform better in that way but this sounds like something else.

JZD
Send message
Joined: 30 Dec 11
Posts: 89
Credit: 3,294,306
RAC: 7,178
Message 11964 - Posted: 11 Aug 2013, 20:39:57 UTC

Hello,

When I started here at BURP project, I used Mageia 2 and everything was fine. At the end of May, I went on Mageia 3 and have the same error as above. http://burp.renderfarming.net/result.php?resultid=7392824 So I went back to the second Mageia. http://burp.renderfarming.net/result.php?resultid=7449948 Unfortunately for a in November I will end official support for Mageia 2, so I switch to a supported Mageia 3, and so I have a project BURP quit because here I have bad results. Interestingly, this problem only occurs in BURP project and in other projects everything is fine.

JZD
Send message
Joined: 30 Dec 11
Posts: 89
Credit: 3,294,306
RAC: 7,178
Message 11965 - Posted: 11 Aug 2013, 20:47:17 UTC

Oh, I had to walk away from the computer and let the itemized contribution and I find that after sending the Janus has a comment. I'm sorry.

syll
Send message
Joined: 21 Jul 09
Posts: 5
Credit: 223
RAC: 0
Message 11966 - Posted: 11 Aug 2013, 20:54:31 UTC - in response to Message 11962.

Same problem here.

I've run this command :
./blender_4.78_x86_64-pc-linux-gnu -noaudio -y -b file2265897 -P clirender.py -- -F PNG -t 1 -f 806 0.0 0.0 1.0 1.0

And this is the result :

#######################################################################

----------------------------
GLUE
----------------------------
Detected input arg: argv[0] is ./blender_4.78_x86_64-pc-linux-gnu
Setting basename to blender_4.78_x86_64-pc-linux-gnu from ./blender_4.78_x86_64-pc-linux-gnu
Detected input arg: argv[1] is -noaudio
Setting command to -noaudio
Detected input arg: argv[2] is -y
Setting preopts to -y
Detected input arg: argv[3] is -b
Setting postopts to -b
Detected input arg: argv[4] is file2265897
Detected input arg: argv[5] is -P
Detected input arg: argv[6] is clirender.py
Detected input arg: argv[7] is --
Detected input arg: argv[8] is -F
Detected input arg: argv[9] is PNG
Detected input arg: argv[10] is -t
Detected input arg: argv[11] is 1
Detected input arg: argv[12] is -f
Detected input arg: argv[13] is 806
Detected input arg: argv[14] is 0.0
Detected input arg: argv[15] is 0.0
Detected input arg: argv[16] is 1.0
Detected input arg: argv[17] is 1.0
$Id: BOINCHandler.cpp 1278 2011-01-23 09:22:45Z jbk $
Initializing stdout redirection, all output from now on will be redirected to a file


#######################################################################

And in stderr.txt :

#######################################################################

boinc_init_diagnostics() completed
22:56:49 (15028): Can't open init data file - running in standalone mode
boinc_init_options() completed
boinc_get_init_data() completed
CPU performance profile completed: 0.000000 fpops, 0.000000 iops reported. p_c is 0.000000
Mapping logical files to physical destinations:
in => in
out.zip => out.zip
./linux_zip_x64_r600 => ./linux_zip_x64_r600
./linux_unzip_x64_r600 => ./linux_unzip_x64_r600
Unpacking archives:
blender_4.78_x86_64-pc-linux-gnu.zip => blender_4.78_x86_64-pc-linux-gnu.zip
./linux_unzip_x64_r600 -o -d "." blender_4.78_x86_64-pc-linux-gnu.zip...done
CHMODing executable...
Creating worker...
Worker constructing...
Worker constructed.
$Id: glue.cpp 1303 2011-02-18 08:10:43Z jbk $
$Id: BOINCHandler.cpp 1278 2011-01-23 09:22:45Z jbk $
$Id: Controller.cpp 1432 2012-04-15 13:36:53Z jbk $
$Id: ProgressMonitor.cpp 1278 2011-01-23 09:22:45Z jbk $
Executing ./-noaudio -y in -b
Child created.
Worker thread started
Worker thread monitor almost up.
Worker thread monitor up.
Something returned from execvp: -1
---------------------------
Exception caught: Portability::POSIX::createChild(): execvp returned, indicating an error
Status: -8
---------------------------
terminate called after throwing an instance of 'Exception'
SIGABRT: abort called
Stack trace (12 frames):
[0x411c36]
[0x48dcf0]
[0x501cd5]
[0x4ad250]
[0x484a85]
[0x479156]
[0x479183]
[0x47823e]
[0x404ea0]
[0x409e3e]
[0x4a414e]
[0x4003a9]

Exiting...
|[-->] Info:
|child <15032> to stdout
|0 - ./-noaudio
|1 - -y
|2 - in
|3 - -b

---------------------------
Exception caught: Worker application apparently died prematurely
Status: -9
---------------------------
Calling boinc_finish()...
22:57:03 (15028): called boinc_finish

#######################################################################

overkill
Send message
Joined: 12 Jun 08
Posts: 56
Credit: 922,628
RAC: 0
Message 11967 - Posted: 12 Aug 2013, 14:09:22 UTC - in response to Message 11962.

Looks like the link loader in the official BURP linux client may need upgrading.

Does your native libs work with the Blender client that the server sent? Try:
./blender -noaudio -y -b file2265897 -P clirender.py -- -F PNG -t 1 -f 806 0.0 0.0 1.0 1.0
(without the blender_ld)

Janus.

Yes, it works fine if I don't use blender_ld (your command above).

Thanks for looking into it.

Profile Janus
Volunteer moderator
Project administrator
Avatar
Send message
Joined: 16 Jun 04
Posts: 4487
Credit: 2,094,806
RAC: 0
Message 11969 - Posted: 12 Aug 2013, 16:23:03 UTC

Ok thanks for the feedback - this is definitely something that will be fixed in the next release of the Linux client. I can't make any promises as to when the next release is going to happen because I'm a little low on dev time right now, but what has been posted so far is enough to find the issue at hand and fix it.

overkill
Send message
Joined: 12 Jun 08
Posts: 56
Credit: 922,628
RAC: 0
Message 12128 - Posted: 30 Nov 2013, 21:28:43 UTC

I just built a new machine and I'm having the same problems as before (in this thread). Running blender_ld only shows...
./blender: error while loading shared libraries: __vdso_time: invalid mode for dlopen(): Invalid argument

Yet when I don't use the loader, it runs fine.

My system is here (Debian Jessie 3.11.8-1 (2013-11-13) x86_64 GNU/Linux).

I've also recently setup a Debian Wheezy system which seems to work fine.

I'm guessing something is missing in the new (Jessie) system, but ldd shows the same as my other post. Everything looks ok to me.

Profile Janus
Volunteer moderator
Project administrator
Avatar
Send message
Joined: 16 Jun 04
Posts: 4487
Credit: 2,094,806
RAC: 0
Message 12133 - Posted: 1 Dec 2013, 9:55:27 UTC - in response to Message 12128.
Last modified: 1 Dec 2013, 10:00:20 UTC

Same problem still, the new kernels are not compatible with the old loader bundled with the current linux client.
If you feel creative you can run the "anonymous platform" mechanism, include the usual files but leave out the blender_ld file, this instructs the client to use native libs instead. This is also somewhat what the upcoming clients will do.

overkill
Send message
Joined: 12 Jun 08
Posts: 56
Credit: 922,628
RAC: 0
Message 12142 - Posted: 4 Dec 2013, 15:08:06 UTC - in response to Message 12133.

Thanks Janus.

I started messing with anonymous platform, but haven't had much luck. I first setup my app_info.xml file to only replace the blender.zip file, but boinc thought that was the executable and (of course) wouldn't run.

Now I've "replaced" blender_4.78_x86_64-pc-linux-gnu, infozip_license, linux_zip_x64_r600, linux_unzip_x64_r600, and blender_4.78_x86_64-pc-linux-gnu.zip. This is my current app_info.xml file... Documentation for this is rare and the only examples I can find are for seti (which only has one executable).

<app_info> <app> <name>blender</name> </app> <file_info> <name>blender_4.78_x86_64-pc-linux-gnu</name> <executable/> </file_info> <app_version> <app_name>blender</app_name> <version_num>478</version_num> <file_ref> <file_name>blender_4.78_x86_64-pc-linux-gnu</file_name> <main_program/> </file_ref> <file_ref> <file_name>infozip_license</file_name> </file_ref> <file_ref> <file_name>linux_zip_x64_r600</file_name> </file_ref> <file_ref> <file_name>linux_unzip_x64_r600</file_name> </file_ref> <file_ref> <file_name>blender_4.78_x86_64-pc-linux-gnu.zip</file_name> </file_ref> </app_version> <app_version> <app_name>blender</app_name> <version_num>999</version_num> <file_ref> <file_name>blender_4.78_x86_64-pc-linux-gnu</file_name> <main_program/> </file_ref> <file_ref> <file_name>infozip_license</file_name> </file_ref> <file_ref> <file_name>linux_zip_x64_r600</file_name> </file_ref> <file_ref> <file_name>linux_unzip_x64_r600</file_name> </file_ref> <file_ref> <file_name>blender_4.78_x86_64-pc-linux-gnu.zip</file_name> </file_ref> </app_version> </app_info>


I'm hacking my way through this, but getting confused with the multiple files. Currently waiting for workunits to see if this works.

Am I on the right track? Do I need to replace every file in the project folder, or just the ones I want to change (the .zip file)?

Any tips you can provide would be helpful.

Thanks.

Profile DoctorNow
Project donor
Avatar
Send message
Joined: 11 Apr 05
Posts: 392
Credit: 2,168,338
RAC: 3
Message 12143 - Posted: 4 Dec 2013, 17:35:27 UTC - in response to Message 12142.
Last modified: 4 Dec 2013, 17:56:45 UTC

As far as I can see, this should work - although I don't use Blender on Linux, but I have written an app_info for Windows recently, looks quite similar.
But I don't think you need the second block, the same stuff is standing there but only with another version_num. It may confuse the client.

Edit:
Sorry, forget my post. I didn't read first what problem you are referring to...
____________
Life is Science, and Science rules. To the universe and beyond
Proud member of BOINC@Heidelberg
My BOINC-Stats

Profile Janus
Volunteer moderator
Project administrator
Avatar
Send message
Joined: 16 Jun 04
Posts: 4487
Credit: 2,094,806
RAC: 0
Message 12144 - Posted: 5 Dec 2013, 14:46:51 UTC

A hint is that you can pretty much search for the app-info section of your client_state.xml and move some of that into it and just mess around with things that way.

Whatever you do. NEVER use a version number that doesn't match with the binary files. (ie. never use 999 with a binary file that should be 478), it is really, really, really (did I say "really"?) bad karma.

Be sure to post back if you figure it out, though - I'm sure other people are interested in trying out a native-libs client while waiting for that feature to be available in the official ones too.

tiwake
Send message
Joined: 17 Dec 13
Posts: 1
Credit: 0
RAC: 0
Message 12357 - Posted: 16 Feb 2014, 17:26:43 UTC - in response to Message 12144.

Has this been fixed yet?

overkill
Send message
Joined: 12 Jun 08
Posts: 56
Credit: 922,628
RAC: 0
Message 12383 - Posted: 25 Feb 2014, 14:50:29 UTC

The clients do not get updated very frequently. I managed to work around this by creating an Anonymous Client using the app_info.xml file.

If you're having this exact problem (client crashing on Debian Jessie), you can try what I did...

1. Stop the boinc client...
/etc/init.d/boinc-client stop
2. Go to the burp project folder...
/var/lib/boinc-client/projects/burp.renderfarming.net
3. Unzip the blender_4.78_x86_64-pc-linux-gnu.zip file and delete the "lib" folder and all it's contents.
4. Rezip into the same filename (blender_4.78_x86_64-pc-linux-gnu.zip)
5. Create an app_info.xml file with the following contents...

<app_info> <app> <name>blender</name> </app> <file_info> <name>blender_4.78_x86_64-pc-linux-gnu</name> <executable/> </file_info> <file_info> <name>infozip_license</name> <executable/> </file_info> <file_info> <name>linux_zip_x64_r600</name> <executable/> </file_info> <file_info> <name>linux_unzip_x64_r600</name> <executable/> </file_info> <file_info> <name>blender_4.78_x86_64-pc-linux-gnu.zip</name> </file_info> <app_version> <app_name>blender</app_name> <version_num>478</version_num> <api_version>7.1.0</api_version> <plan_class>mt</plan_class> <flops>1933209103.303349</flops> <avg_ncpus>1.000000</avg_ncpus> <max_ncpus>1.000000</max_ncpus> <file_ref> <file_name>blender_4.78_x86_64-pc-linux-gnu</file_name> <main_program/> </file_ref> <file_ref> <file_name>infozip_license</file_name> <open_name>infozip_license</open_name> </file_ref> <file_ref> <file_name>linux_zip_x64_r600</file_name> <open_name>linux_zip_x64_r600</open_name> </file_ref> <file_ref> <file_name>linux_unzip_x64_r600</file_name> <open_name>linux_unzip_x64_r600</open_name> </file_ref> <file_ref> <file_name>blender_4.78_x86_64-pc-linux-gnu.zip</file_name> <open_name>blender_4.78_x86_64-pc-linux-gnu.zip</open_name> </file_ref> </app_version> </app_info>


5. Restart Boinc.
/etc/init.d/boinc-client start

Once you get a task, it should start rendering with "Anonymous Platform" instead of "Blender v4.78"

If you have problems (like I did), you may need to detach & re-attach to the project while making these changes.

JZD
Send message
Joined: 30 Dec 11
Posts: 89
Credit: 3,294,306
RAC: 7,178
Message 12424 - Posted: 13 Mar 2014, 21:22:55 UTC - in response to Message 12383.

According to the instructions I got this error.
http://burp.renderfarming.net/result.php?resultid=7777402

Javier Alfonso
Send message
Joined: 25 Apr 14
Posts: 1
Credit: 0
RAC: 0
Message 12805 - Posted: 3 Jun 2014, 14:33:46 UTC - in response to Message 12424.

Any news on this? Haven't updated yet?

funkydude
Send message
Joined: 23 Dec 13
Posts: 275
Credit: 2,478,281
RAC: 0
Message 12806 - Posted: 3 Jun 2014, 15:13:32 UTC - in response to Message 12805.
Last modified: 3 Jun 2014, 15:20:42 UTC

Any news on this? Haven't updated yet?


Several issues were discussed in this thread, which are you experiencing?

If you're having issues getting BURP running successfully on Linux, try native mode. Discussed here: http://burp.renderfarming.net/forum_thread.php?id=2312

Basically creating a directory called "native". You should also make sure you have all the required libraries installed, the easiest way to do this is install the actual Blender software.

edit: I looked up your logs, and indeed, you need to enable "native" mode for them to render properly. Create a directory called "native" in /var/lib/boinc-client/projects/burp.renderfarming.net/

from terminal:
cd /var/lib/boinc-client/projects/burp.renderfarming.net/
sudo mkdir native

Install Blender from the Ubuntu software center.

funkydude
Send message
Joined: 23 Dec 13
Posts: 275
Credit: 2,478,281
RAC: 0
Message 12905 - Posted: 25 Jun 2014, 11:58:57 UTC - in response to Message 12806.

It appears that instead of reading the response to your post and acting on it, you are continually bombarding the server with errored results. I guess that's one approach to take...

Profile PlainText s.r.o.
Send message
Joined: 11 Apr 07
Posts: 95
Credit: 3,505,542
RAC: 0
Message 13316 - Posted: 9 Oct 2014, 11:15:17 UTC

Hi. Is this problem still here? I have connected two new PC to project with brand new and fresh ubuntu instalation and they got computation error with status -9... Have a look at one of them: http://burp.renderfarming.net/results.php?hostid=64016

I would like to have them working, because I like burp and because they have nothing beter to do now (it will chenge probably in month).

1 · 2 · Next
Post to thread

Message boards : Problems and Help : Troubles on Linux