Strange Rendering error (vray, yeti and qube)

[evanerichards]

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!

[bigbossfr]

Are you sur it is a VRay problem ?
Because the first error is a Yeti license error (all licenses from Yeti are used)

[evanerichards]

Well I'm not 100% sure, but the only thing we have to do in order for the exact same scene file to start rendering properly is to delete the velocity pass.

That's what I mean when I said that it is weird. Why would the velocity pass possibly have any effect on the yeti licenses?

[bigbossfr]

But perhaps, when you deleted the velocity pass, 1 license from Yeti was free...

[evanerichards]

Well, we've got a lot of licenses of yeti so it seems like that couldn't have been the issue.

[Svetlozar Draganov]

This looks more like Yeti issue than Vray - have you also contacted yeti-developers on that matter ?
Would it be possible to send us also this scene for investigation or it could be also stripped down version of the scene just make sure that the issue is still there.
Have you also tried to remove other render elements and keep the velocity one ?

[vlado]

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?

No idea whatsoever - it doesn't make much sense. Except if the renders were crashing and previous renders did not release the Yeti licenses. But then again, I thought Yeti didn't require render licences... very strange. As Svetlozar suggested, it would be very helpful if you can get us a reproducible case.

Best regards,
Vlado