standard vray rendering has no problem. also vrlclient.xml is set correctly.
But an error of “ERR Cmdjob adapter: Process exit abnormally,Exit code is 1” will be produced if job is sent to Backburner Server on the same OS X machine.
My check of “backburnerServer.log” has reported the “V-Ray error: Could not obtain a license (61).”
It seems not to refer to vrlclient.xml, when processing by backburner server of OSX.
It says once again.
The usual VRay rendering has no problem. (BatchRender same.)
It is not a problem of blocking of firewall.
It is a problem only when doing a rendering by Backburner server.
I narrow down the cause of a problem.
When a license server is outside = backburner failure
When a license server is in local = backburner success
Therefore, when you do a rendering by Backburner server of OS X, refer only to the “localhost” license server for V-Ray.
checks by V-Ray for Maya version 2.25.01, revision 22390 from Sep 26 2012, 16:08:17 + OS X 10.6 + Maya 2012
Sorry for the delay.
We found that the “Sandboxing” option under Mac OSX 10.7 and later can restrict the Backburner to see all PC resources.
I hope our developers will find how to fix this soon.
The workaround that you can use for now is described below:
*> Create folder /usr/share/ChaosGroup and place inside this folder the vrlclient.xml file from $HOME/.ChaosGroup
*> Open file /etc/profile and add:
export VRAY_AUTH_CLIENT_FILE_PATH=/usr/share/ChaosGroup
*> Log Out and Log in
This issue is cropping up for me again in 3.1 after I had solved it long ago in 2.4 using the steps listed in this thread. Back burner will trigger the renderer on the render manager machine (which is also the vray license server), but will still gives “Cmdjob adapter: Process exit abnormally,Exit code is 1” on all of the render nodes.
I noticed under distributed rendering in the manual it says to change the line in /etc/profile to point to /Users/*user*/.ChaosGroup/vrlclient.xml. I’ve tried it this way as well, but it doesn’t resolve the issue.
Actually, I should say that DR works fine after editing /etc/profile again.
when I installed v-ray 3.1 on my nodes, the installer edited /etc/profile and added an additional “export VRAY_AUTH_CLIENT_FILE_PATH” line that pointed to “/Users/*user*/.ChaosGroup/vrlclient.xml”
This is apparently typed wrong. So, even if there is a file in that location, v-ray must expect that line to specify a directory and not a file. Running setvrlservice -dump resulted in an error saying it couldn’t access “Users/*user*.ChaosGroup/vrlclient.xml/vrlclient.xml”
Removing this newly added line, leaving the one that says “export VRAY_AUTH_CLIENT_FILE_PATH=”/usr/share/ChaosGroup"", and restarting resolved this problem.
EDIT: I should clarify. this solved DR not working. I still get an error when rendering via back burner.
Thank you for the update.
Would it be possible to send us the full log from the BB job to support@chaosgroup.com ?
Are you able to render a BB job using the Maya software renderer ?
I actually have a ticket opened already, just got a response today with some more troubleshooting steps after supplying my log. If they resolve the issue I’ll post them here.
Ok, I got a response from support that said to make a .plist file in /Library/LaunchDaemons that points to the /usr/share/ChaosGroup. I’m unclear on whether this is needed in addition to editing /etc/profile, but I have both at this point and now it works.
I did have to manually set the permissions/owner/group for the .plist files and then restart.
contents of .plist file should be
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<!-- This file was generated by the CHAOS GROUP installer. Please do NOT edit the file by yourself. -->
<plist version="1.0">
<dict>
<key>Label</key>
<string>setenv.chaos_group.VRAY_AUTH_CLIENT_FILE_PATH</string>
<key>ProgramArguments</key>
<array>
<string>/bin/launchctl</string>
<string>setenv</string>
<string>VRAY_AUTH_CLIENT_FILE_PATH</string>
<string>/usr/share/ChaosGroup</string>
</array>
<key>RunAtLoad</key>
<true/>
<key>ServiceIPC</key>
<false/>
</dict>
</plist>
edit: if you have to do this and you aren’t sure how to edit file permissions, there are two commands you need.
sudo chown root:wheel /Library/LaunchDaemons/*plist file you created*
sudo chmod 644 /Library/LaunchDaemons/*plist file you created*