AWS Thinkbox Discussion Forums

[10.0.10.3] AfterEffect CC2018 failing task after the task is already completed

Hello,

we have a bug with after effect CC2018.
Images are rendered successfully but the end of task is going error.

Any idea ?
Thanks
-p-

docs.thinkboxsoftware.com/produ … d-meanings

Are you running out of RAM? is that for a sequence and can you use smaller chunks?

The fact is : images are rendered & saved correctly.
The bug is ‘only’ on the end of task.

Oof. Well, that’s fun.

You could change the plugin to not care about errors after we’ve seen the success message:

    def HandleStdoutError( self ):
        # If the render was successful, there's no reason to fail the task
        if self.RenderSuccess:
            return
    
        if "auto-save" in unicode(self.GetRegexMatch(0)).lower(): # This was an autosaving issue, so it was not necessarily a critical error
            self.LogWarning( "After Effects auto-save was unsuccessful" )
        else:
            self.FailAERender( self.GetRegexMatch(0) )

You’d replace the current code in “[repo]/plugins/AfterEffects/AfterEffects.py”. If that works, I can make a push to fix that…

DL 10.0.10.3 introduced more debug logging in AE, so I would be interested in seeing a few example job log reports here before making judgement call on what might be the root cause of this false-positive exit at render end.

Most errors looks like this : (french version)

I’ll try to change the AfterEffect.py.
Thanks

after changing the .py file, i’ve still got errors, mainly 2 types :

Some task fails then finished, some slaves works than fail… so instable.
It’s an heavy job, is could be a RAM problem… but still can’t understand why the frames are rendered & saved correctly but the task still fail.

On finished jobs, it looks like there’s a check of the files. Could it come from it ?

Hmm. “fin de la composition” is supposed to trip the value I’m using…

I wonder if it is now failing on the “FailWithoutFinishedMessage”… Can you enable that as well? It’s in the plugin config and is labelled “Fail Without Finished Message”. If you’re rendering quicktimes this may cause some trouble though.

This is a difficult issue to work around. :S

Alright.

I’ve comment the CheckExitCode and return a true

Now all the task are rendered correctly, have a error but complete the task :

An error might be still present, but it looks like we can work for the moment :slight_smile:

Sorry I didn’t prioritize getting the render working… I was too focused on solving it the “right way”.

Can you attach your existing AfterEffects.py file here? I would like to make sure we’re properly matching for the French “fin de la composition” message. I’d rather other people not hit the same problem.

Here it is. Just zipped it, because .py is not allowed
AfterEffects.7z (8.04 KB)

After few test, it looks like it comes from the swap.

We’ve send the same job, on a swapping machine (already loaded stuff) and on a free ram machine, and the free one just completed the job normally.

Does it comes from the windows settings or deadline can’t handle a final check if no RAM is available ?

-p-

Deadline cannot currently use free RAM in it’s dequeuing decisions. You can great a group or limit for a certain amount of total memory, but if there is an unexpected lack of memory on the machine you will run into the same problem.

Was the problem with the types of machines which took the job, or was Deadline using too much memory?

Hello,

i’m re-opening this thread because we are entering our full production with after effect.

We still have errors on jobs, but the frames are rendered correctly.
I’ve watch during rendering, and it doesn’t seems to be a RAM problem, the slave was ~50% RAM utilisation.

I’ll take any idea :slight_smile:
Thanks
-p-

2018-04-23 12:49:25: 0: STDOUT: PROGRESS: Taille finale : 2078 x 858 2018-04-23 12:49:25: 0: STDOUT: PROGRESS: Profil : - 2018-04-23 12:49:25: 0: STDOUT: PROGRESS: Action post-rendu : Aucune 2018-04-23 12:49:25: 0: STDOUT: PROGRESS: 2018-04-23 12:49:44: 0: STDOUT: PROGRESS: 00004 (1) : 19 Secondes 2018-04-23 12:49:55: 0: STDOUT: PROGRESS: 00005 (2) : 11 Secondes 2018-04-23 12:49:55: 0: STDOUT: PROGRESS: 23/04/2018 12:49:55 : fin de la composition sXXpXXXX. 2018-04-23 12:49:55: 0: STDOUT: PROGRESS: Temps total écoulé : 38 Secondes 2018-04-23 12:50:12: 0: INFO: Checking for file "C:\Users\JDU\Documents\ae_render_only_node.txt" 2018-04-23 12:50:12: 0: INFO: Attempting to delete "C:\Users\JDU\Documents\ae_render_only_node.txt" to allow After Effects to run in the workstation environment 2018-04-23 12:50:12: 0: STDOUT: aerender ERROR Une connexion existante a dû être fermée par l’hôte distant. 2018-04-23 12:50:12: 0: STDOUT: : Unable to receive at line 316 2018-04-23 12:50:12: 0: Done executing plugin command of type 'Render Task'

[code]=======================================================
Error

aerender ERROR Une connexion existante a d¹ Ûtre fermÚe par lÆh¶te distant.
à Deadline.Plugins.PluginWrapper.RenderTasks(String taskId, Int32 startFrame, Int32 endFrame, String& outMessage, AbortLevel& abortLevel)

=======================================================
Type

RenderPluginException

=======================================================
Stack Trace

à Deadline.Plugins.SandboxedPlugin.d(DeadlineMessage aqg)
à Deadline.Plugins.SandboxedPlugin.RenderTask(String taskId, Int32 startFrame, Int32 endFrame)
à Deadline.Slaves.SlaveRenderThread.c(TaskLogWriter agy)[/code]

It’s weird that it’s throwing a TCP-based error there. Are you using the AE render-only mode, or are these render machines fully licensed?

“Forcibly closed” makes me think firewall, but that’s unlikely if the render started properly.

yea we are rendering in workstation mode, all slave are licenced properly.

For your information, i’ve re-tweak the HandleStdoutError so we can continu working, but it seems the probleme is in here.

[code] def HandleStdoutError( self ):
# If the render was successful, there’s no reason to fail the task
if self.RenderSuccess:
return

    if "auto-save" in unicode(self.GetRegexMatch(0)).lower(): # This was an autosaving issue, so it was not necessarily a critical error
        self.LogWarning( "After Effects auto-save was unsuccessful" )
    else:
        self.FailAERender( self.GetRegexMatch(0) )[/code]

AE is able to recover from “2018-04-23 12:50:12: 0: STDOUT: : Unable to receive at line 316”?! I haven’t seen AE carry on from that error before.

If that’s the case, we can just have Deadline skip over that error. Is this ‘auto-save’ a new error?

We could maybe parse the AE prefs file and disable the auto-save: helpx.adobe.com/after-effects/u … ences.html

While we’re in there, we should also throw an error if nodes have a remote share for their local cache. I spent three hours once fighting a lockup to discover that nodes were all using the same location and we’re deadlocking on the filesystem.

Hello,
it looks like we still have the problem

2018-06-07 15:58:56: 0: STDOUT: PROGRESS: 00000 (1) : 2 min, 4 sec 2018-06-07 15:59:43: 0: STDOUT: PROGRESS: 00001 (2) : 47 Secondes 2018-06-07 16:00:30: 0: STDOUT: PROGRESS: 00002 (3) : 47 Secondes 2018-06-07 16:01:17: 0: STDOUT: PROGRESS: 00003 (4) : 47 Secondes 2018-06-07 16:02:05: 0: STDOUT: PROGRESS: 00004 (5) : 47 Secondes 2018-06-07 16:02:52: 0: STDOUT: PROGRESS: 00005 (6) : 47 Secondes 2018-06-07 16:03:38: 0: STDOUT: PROGRESS: 00006 (7) : 46 Secondes 2018-06-07 16:04:24: 0: STDOUT: PROGRESS: 00007 (8) : 47 Secondes 2018-06-07 16:05:11: 0: STDOUT: PROGRESS: 00008 (9) : 47 Secondes 2018-06-07 16:05:59: 0: STDOUT: PROGRESS: 00009 (10) : 47 Secondes 2018-06-07 16:05:59: 0: WARNING: TEST PINGUS SUCCESS 2018-06-07 16:05:59: 0: STDOUT: PROGRESS: 07/06/2018 16:05:59 : fin de la composition sXXpXXXX. 2018-06-07 16:05:59: 0: STDOUT: PROGRESS: Temps total écoulé : 9 min, 10 sec 2018-06-07 16:06:12: 0: WARNING: TEST PINGUS ERROR 2018-06-07 16:06:12: 0: STDOUT: aerender ERROR Une connexion existante a dû être fermée par l’hôte distant. 2018-06-07 16:06:12: 0: STDOUT: : Unable to receive at line 316 2018-06-07 16:06:13: 0: INFO: Process exit code: -1073741819 2018-06-07 16:06:13: 0: Done executing plugin command of type 'Render Task'

I’ve added print message in the afterEffect.py and it looks like that even after passing in HandleRenderSuccess() the slaves goes inot the HandleStdoutError() anyway, and return an error.

Privacy | Site terms | Cookie preferences