maya 2015 / vray 2.4 license error

[thekraken]

Greetings,

I just deployed an environment for maya 2015 / vray 2.4 (02) on our renderfarm (osx 10., as we are still working on maya 2013.

While working on maya everything is fine, and I can launch interactive renders, but I get a license error on the renderfarm.

To be exact, the vrscene generation (Render -r vray -noRender) works like a charm, but the render command itself fails (vray -sceneFile …) :

[2015/Jan/23|12:19:58] error: Could not obtain a license (0).

License server is set at boot time (setvrlservice -server=vray-licences) and enforced through VRAY_AUTH_CLIENT_FILE_PATH environment variable, it's exactly the same configuration for maya 2013 / vray 2.4 so I can't figure out what's happening … should I upgrade our dongle in any way to support maya 2015 ?

In the meantime, is this a correct workflow, that is, generating vray scenes on the renderfarm with maya batches and then rendering these scenes. I'm not sure to understand this thread :
http://forums.chaosgroup.com/showthr...s-in-licensing

Just want to be sure that we're not doing anything illegal, and that generating vray scenes won't require interactive licenses when upgrading to vray 3.

Thanks in advance, and best new year wishes !

[Svetlozar Draganov]

We confirm that no V-Ray license update is required for using V-Ray 2.0 for Maya 2015.

It seems like you have everything set up correctly for the licensing. However we would recommend to double-check V-Ray client license settings on the render-farm, verifying that the render nodes can access V-Ray license server and have the settings properly set. You can easily to that by opening a web-browser on the render-farm machines and accessing V-Ray license server.

Please let us know do you use a render-manager for submitting the jobs and if so which one.

[thekraken]

Hi Svetlozar, thanks for your answer,

To be sure it wasn't a "farm related" issue I just launched the render command on my workstation and got the same behavior.

I also tried with direct IP to exclude dns issues, anyway, http://vray-licences:30304 is up and running, showing our 4 vray4maya and 40 standalone licences, and port is accessible according to nmap scans.

We use Tractor to dispatch jobs, so basically I build job descriptions with our in-house api and commands are detached with python execvp calls. I don't think it's related to tractor since executing the command in my terminal will just give the same result.

And this error code is strange, doesn't "0" means "everything went fine" ?

[Svetlozar Draganov]

Thank you very much for the clarification.
Would it be possible to contact us at support@chaosgroup.com and include a link to this thread - we may need to run a remote session in order to resolve the issue.

[Svetlozar Draganov]

Regarding the question bellow:

Just want to be sure that we're not doing anything illegal, and that generating vray scenes won't require interactive licenses when upgrading to vray 3.

In V-Ray 3.x it is required to have Interface license in order to render or export *.vrscenes.