So I'm hoping someone can shed some light on this problem. It might be too specific to our pipeline but I'll throw it out there in case anyone has any ideas.
Our renders kept crashing on the farm. We're using Qube as our render manager and vray as our renderer. We're rendering a scene with yeti hair. It gave us these errors and fail:
[Mon Feb 24 17:09:52 2014] Yeti 1.3.1: ERROR pgLicenseCheck - License system failed trying to checkout a license from 5053@192.168.1.6;C:/ProgramData/PeregrineLabs/rlm/ with error: All licenses in use (-22)
And
[Mon Feb 24 17:03:07 2014] Peregrine Log System 1.3.1: ERROR Can't open log file c:\yeti_log.txt
We narrowed the problem down one single attribute at a time. We traced the problem to a vray velocity pass. If we deleted the velocity pass in our render layers it didn't give us these errors anymore and would render without any problems. As soon as we added it back in the yeti error would happen again.
Can anyone think of ANY reason why adding a velocity pass would create those yeti errors? What makes it even stranger is that I know we've used velocity passes with yeti before and not had any problems. I mean, how would a velocity pass even have anything to do with yeti licenses?
Just throwing it out there. Thanks in advance!
Our renders kept crashing on the farm. We're using Qube as our render manager and vray as our renderer. We're rendering a scene with yeti hair. It gave us these errors and fail:
[Mon Feb 24 17:09:52 2014] Yeti 1.3.1: ERROR pgLicenseCheck - License system failed trying to checkout a license from 5053@192.168.1.6;C:/ProgramData/PeregrineLabs/rlm/ with error: All licenses in use (-22)
And
[Mon Feb 24 17:03:07 2014] Peregrine Log System 1.3.1: ERROR Can't open log file c:\yeti_log.txt
We narrowed the problem down one single attribute at a time. We traced the problem to a vray velocity pass. If we deleted the velocity pass in our render layers it didn't give us these errors anymore and would render without any problems. As soon as we added it back in the yeti error would happen again.
Can anyone think of ANY reason why adding a velocity pass would create those yeti errors? What makes it even stranger is that I know we've used velocity passes with yeti before and not had any problems. I mean, how would a velocity pass even have anything to do with yeti licenses?
Just throwing it out there. Thanks in advance!
Comment