I am attempting to run this headless on ubuntu server 21.04 and I get the error
Command: ./blender -noaudio -b --python ~/.config/blender/2.80/scripts/addons/crowdrender/src/py_3_7/serv_int_start.py -- -t "server_int_proc"
Blender 2.80 (sub 75) (hash f6cb5f54494e built 2019-07-29 17:17:04) /run/user/1000/gvfs/ non-existent directory Read prefs: /home/jacob/.config/blender/2.80/config/userpref.blend found bundled python: /home/jacob/blender-2.80-linux-glibc217-x86_64/2.80/python Crowd Render Server Interface Process ready Traceback (most recent call last): File "/home/jacob/.config/blender/2.80/scripts/addons/crowdrender/src/py_3_7/serv_int_start.py", line 72, in <module> server_interface = crowdrender.src.py_3_7.server_interface AttributeError: module 'crowdrender.src' has no attribute 'py_3_7' Blender quit
I tried with blender 2.80, 2.82, and 2.83 and get the same error on all of them no matter what version of python I choose (in the code above I used py_3_7, but I also used 8 and 9). This is with crowdrender V0.3.1. The system python version is 3.9.5 although I don't think that matters. Any suggestions?
My question was answered by somebody else a lot faster than I thought. Here is their response copy and pasted: This change to the packaging of the addon caused the command to change slightly to
./blender -noaudio -b --python ~/.config/blender/2.80/scripts/addons/crowdrender/src/cr/serv_int_start.py -- -t "server_int_proc"
also consider your circumstances for the other options -p false - if you're using a virtual machine from a cloud provider, you may not want to permanently store it in your crowdrender account as if you do, each time you use a vm from a cloud provider, you'll get a different vm and they'll start to pile up in your account. -ak - called the access key, if you setup multiple vm's on your own servers, best give them each a unique access key. This can be literally anything, but its important if you're using containerisation or vms on your own hardware since if you do, chances are the hardware id of those vm's containers could be the same, which totally prevents you from connecting to more than on of them at once, defeating the purpose of using our software. -ct - authorisation token of your Crowdrender cloud account. Using this allows the vm's / containers to post to your cloud account on our servers when they are alive. This means you'll actually be able to see which of them are alive and able to be used and which are offline (or just not posting cause they're not logged in).
Hi Jacob, yeah, that was me :) I help out with the gist and moderate this forum too. Just curious did this work?