Summary

Title:Maya SegFaulting on farm render
Category:Crash/Critical
Status:Closed
Posted By:it.accounts@pukekopictures.com ( Pukeko IT )
Date Created:23 March 2022

Problem

Description:

Since updating Maya and Ornatrix, maya is segfaulting on the farm. You should be able to see from the deadline log that it just finishes reading the scenefile. 

I've tried to include all the relavent logs that I can, but I'm not sure how to get more. 

Rendering a scene that does not use Ornatrix renders without issue. However it is worth noting that a successful render also generates the errors logged on line 129-183 of deadlineSlaveLog.txt and thus I am currently discounting them

We are using:

Maya2022v3

Ornatrix 3.3.5.30081

Redshift 3.0.66

CentOS7

 

This has changed from:

Maya2020v3

Ornatrix 3.2.8

Redshift 3.0.58

 

Thanks. 

 

Steps to Reproduce:
 

Attached Files:

>deadlineSlaveLog.txt (19775 bytes), >maya.log (8930 bytes), >OrnatrixMaya2022.log (56922 bytes),

Hello,

Thank you for the logs. We will investigate this and get back to you soon. 

Jeordanis Figuereo (Product Designer. EPHERE Inc.)

I can't find anything in the provided log files that points to Ornatrix, or could help in any way.

Which was the previous version that worked?

Does the crash happen when you render locally?

Can you try deleting the directory Module/OrnatrixMaya2022/plug-ins/procedurals and the file Module/OrnatrixMaya2022/bin/libEphere.Ornatrix.so and see if the crash persists?

 

Ivan Kolev (Software Developer, EPHERE Inc.)

E-mail: ivan.kolev at ephere dot com

Discord: ikolev

I was worried that might be the case. 

Version 3.2.8 was the previous one that worked with maya 2020v3

So far no, however we have only rendered locally on Windows. We have a linux farm and only have the Windows workstations licensed. I'll see about either getting the license transferred for testing, or getting another to test locally. 

Crash still persists with those files gone. What does that tell you?

Sorry for asking about your previous version, you had already provided that in your report.

Those files are part of new features that should go to V4 and only cause problems in V3 (especially with Maya 2022), they will be removed in the next V3 stable build.

But if it's not them, then the problem will be harder to track down.

Can we exclude Deadline from the setup? Maybe try to run MayaBatch manually on a render node? This might also provide a crash dump file in /tmp

And I see multiple errors about missing plugins in your maya.log , don't these otherwise cause problems too?

 

Ivan Kolev (Software Developer, EPHERE Inc.)

E-mail: ivan.kolev at ephere dot com

Discord: ikolev

Hi Ivan, thanks for the suggestions. 

I ran mayabatch as: ./render.bin -proj <PROJECT_PATH> <.MB_PATH>

The results are attached, please note that one is with 3.3.5, and one is with a fresh install of 3.3.6. They are also slightly different, the 3.3.5 one complains about the missing binary as we tried earlier.

Those other missing plugins don't seem to no, we can otherwise render out just fine. 

 

Thanks, 

Doug


Attached Files:

>localMayaRenderLog.txt (5400 bytes), >localMayaRenderLog2.txt (5308 bytes),

There isn't much info in this log.

Can you check the /tmp directory? There might be an OrnatrixMaya2022.log file, and maybe some crash .dmp files (though I'm not sure in what directory Maya puts crash dumps).

Other than that, I can only suggest providing to us a stripped version of the crashing scene. Maybe see if it crashes with another renderer (Redshift version has changed too), or switch back the Redshift version.

Ivan Kolev (Software Developer, EPHERE Inc.)

E-mail: ivan.kolev at ephere dot com

Discord: ikolev

Hi Ivan, 

We have gone through checking everything, making sure there isn't a basic setup issue somethere. The only real thing that's changed is the filepaths are all valid and mapping correctly now.

I'm happy to report it's now not crashing and we are getting images out. Unfortunately there is no hair/fur. I've attached the latest log that shows this behaviour, there is still several missing plugin errors at the start. 

Is there anything that we could try to get hair rendering?

 

Thanks,

Doug


Attached Files:

>DeadlineOutputLog.txt (210270 bytes),

It looks like Redshift doesn't process the Ornatrix hair in the scene for some reason.

The module that takes care for that is called ornatrix_redshift.so / .dll and should be present somewhere in the Redshift installation. For example on Windows that is "C:\ProgramData\Redshift\Plugins\Maya\2022\nt-x86-64\extensions\ornatrix_redshift.dll". You may check first that you have that.

Then, you can check if Redshift renders hair on Linux in a very basic scene. Without a separate Linux license you could make a basic scene on Windows and send it over to Linux to render on the command line with MayaBatch. Or, you could open Maya on Linux and grab the Ornatrix license from the Windows machine by telling the Ornatrix authorization dialog to connect to it (by IP or machine name on the local network). Of course, firewalls should not prevent traffic on the port used by our license server, which is 39373, and the license should not be currently in use on the Windows machine.

If a basic scene does render properly on Linux, then the problem is related to the scene and we'll be only able to help if we get a (stripped down as much as possible) version of it.

If the basic scene doesn't render hair, then I suggest you try to find the combination of Redshift and Ornatrix versions that works. I'll check here too if latest Redshift works with latest Ornatrix on Linux. You may also contact Maxon about it, it's likely that the problem is related to Redshift's new version (and Maya 2022 may be related too).

Ivan Kolev (Software Developer, EPHERE Inc.)

E-mail: ivan.kolev at ephere dot com

Discord: ikolev

I confirmed that Redshift 3.0.66 doesn't render Ornatrix hair on Linux in Maya 2022.

I also remembered that we had a similar report about this some time ago. We'll notify Redshift about it.

 

Ivan Kolev (Software Developer, EPHERE Inc.)

E-mail: ivan.kolev at ephere dot com

Discord: ikolev

Thanks for that Ivan. 

We updated to Redshfit 3.5.01 which was just released in hopes that it would contain a fix. Unfortunately it does not seem to. 

I've attached the test fuzzy ball scene used, just incase there is an issue with how we are setting it up. 

 

Thanks


Attached Files:

>FurryBall_Test.mb (154288 bytes),

We had a response from Maxon, the next version of Redshift will include this fix.

Ivan Kolev (Software Developer, EPHERE Inc.)

E-mail: ivan.kolev at ephere dot com

Discord: ikolev