From: Greg Ercolano <erco_mlist@(email surpressed)>
Subject: [Q+A] Maya 2017 error: This application failed to start because it
   Date: Fri, 11 Nov 2016 16:45:31 -0500
Msg# 2408
View Complete Thread (1 article) | All Threads
Last Next
> We switched from Maya 2014 to Maya 2017, and are now getting this error
> when submitting the Maya 2017 jobs:
> ----------------------------------------------------------------------------------
> Starting "/usr/autodesk/maya2017/bin/maya"
> 
> This application failed to start because it could not find or load the Qt platform plugin "minimal" in "".
> 
> Reinstalling the application may fix this problem.
> Abort (core dumped)
> ----------------------------------------------------------------------------------
> We modified our submit script to point to 2017, and all that looks OK, but the renders fail.
>
> We configured Rush to force run all renders as the single user "render", (we don't have centralized
> user accounts with LDAP).
>
> We found we could ssh into the node as the user "render" and replicate the error,
> but if we ssh in as root and run the render, it works fine. We compared the environment
> variables between "render" and "root" and decided that wasn't the problem, and if we make
> the maya Render executable setuid root, that doesn't fix it either.

	OK, after using strace to track this down, we found out the cause was
	the contents of the $HOME/maya directory was causing the error.

	So the solution was to rename away the ~render/maya directory to something else,
	then the renders ran fine. So while ssh'ed in as the user "render":

		mv ~/maya ~/.junk

	..and from then on the renders ran OK.

	It seemed like even though the ~/maya directory has subdirs that have version specific
	subdirs (2014 vs. 2017), somehow the 2017 dir still had paths pointing to 2014.

	It was great that you could replicate all this from ssh, finding that it worked
	in the "root" account, but failed in the "render" account.. that really led us
	to the solution quickly, as typically differences between accounts boils down to:

		o Environment variables
		o Permissions
		o Home directory

	We ruled out the first two pretty quickly, and ended up with the last one as being
	the culprit, since Maya likes to look for and create files in the user's home directory,
	even when network rendering.
	

Last Next