Mocha OFX Plugin Nuke Render farm issues

Hello everyone!

We currently experiencing issues rendering with the Mocha Pro 2020.5 (v7.5.1) OFX plug-in in Nuke 11.3v2. We are using CentOs 7. If we have a Mocha Pro node in the scene and send it to the render farm we are running into this error:

QSocketNotifier: Can only be used with threads started with QThread
qt.qpa.xcb: could not connect to display 
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: minimal, offscreen, xcb.

The node just needs to be in the scene, the error will occur even when the node is not part of the current node tree. Rendering locally works with no issues. We suspect that it might be related to the fact that our render blades do not posses any graphic cards.

Does anybody has more information on this?


I will tag @martinb to flag this.

Hey @fabian.geisler how are you running the Nuke app on the headless systems?

This may be related to a limitation with mocha on a headless Linux server. Our plug-in is trying to connect to an X server at render time and not correctly handling the case where none is present.

On Centos 7 you may be able to use a virtual frame buffer on the render farm by running the Nuke app via:

xvfb-run /path/to/the/nuke/app

The default arguments for sleep and server are 3 and 99 respectively, which should help stop the problem from occurring.

If you run xvfb-run --help you can see these options.

Let me know if running via xvfb alleviates the problem.

Hi @martinb! Hi @maryp!

Thanks for getting back to me on this. Unfortunately your suggested workaround is does not work for us. Installing X server on our blades is too much for us atm. We will try to fool the blades to think they have a screen. There are some dummy plugs for HDMI and VGA. Will let you know how this goes.
Obviously it would be great, if you could alleviate this issue on your side or write a clear warning somewhere noticeable.
Thanks again!