Maya 2018, Miarmy 6.5.21 and Deadline 10 ( Linux CentOS 7 }

[distephano]

We are renderING a crowd scene with Maya 2018 and Miarmy 6.5.21. A number of workstations are failing after loading the Miarmy plugin with a segmentation fault.  IT creates a crash report but the report is always empty.  Is there anywhere else we should be looking to find out what is causing this issue? Thanks


2019-01-14 23:11:38: 0: STDOUT: VLK found:
2019-01-14 23:11:38: 0: STDOUT: /opt/Basefount/Miarmy/maya/plug-ins/miarmy_key.txt
2019-01-14 23:11:38: 0: STDOUT: Basefount-dsbeuBmD9fnv0JksKXnaHFhcg9Lb4ZhI==
2019-01-14 23:11:38: 0: STDOUT: *******
2019-01-14 23:11:38: 0: STDOUT: Basefount Miarmy Unlimited Key.
2019-01-14 23:11:38: 0: STDOUT: *******
2019-01-14 23:11:38: 0: STDOUT: Welcome to Miarmy Pro Linux Version 6.5.21
2019-01-14 23:11:38: 0: STDOUT: Timestamp: /opt/Basefount/Miarmy/maya/plug-ins/miarmy_time.txt
2019-01-14 23:11:38: 0: STDOUT: licContents: 49258510403758160116001853==
2019-01-14 23:11:38: 0: STDOUT: remain days: 656
2019-01-14 23:11:42: 0: STDOUT: pymel.core : INFO : Updating pymel with pre-loaded plugins: svgFileTranslator, mayaHIK, vrayformaya, Turtle, GPUBuiltInDeformer, stereoCamera, AbcImport, lookdevKit, Type, deformerEvaluator, MiarmyProForMaya2018, retargeterNodes
2019-01-14 23:11:42: 0: STDOUT: Stack trace:
2019-01-14 23:11:42: 0: STDOUT: Writing crash report in /usr/tmp/render.20190114.2311.crash
2019-01-14 23:11:46: 0: STDOUT: Segmentation fault (core dumped)
2019-01-14 23:11:47: 0: WARNING: Monitored managed process MayaBatch is no longer running
2019-01-14 23:11:47: 0: Done executing plugin command of type 'Render Task'

[Yeah YANG]

Hello Distephano,

Is that possible use our newer version of 6.7.11?
We cannot tell if there is no more information. But maybe it caused by:
1. video card setup
2. linux version.

Would it be possible try to load miarmy on that machine which miarmy crash maya.

Cheers,
Yeah

[distephano]

Thanks Yeah,

Sorry for the late response. We upgraded all our workstations to 6.7.11 and this fixed the issue. Cheers!