Maya Batch Wait a long time before finishing the job completely

Soal GIVORD

unread,

Nov 16, 2023, 10:13:26 AM11/16/23

to Royal Render Knights Tavern

Hello,

we are using RR to execute mayabatch (opening scenes ,execute python in them, then save and close the scene)

The execution itself goes well, but when it finishes(2 to 5 min), the jobs waits an additional 5 or 6 minutes before changing its state to finished and releasing the client. And sometimes it waits indefinitely until the job crashes. (see attachments)

We are forcing the command to return exit code 0 if all went well and put a "sys.exit()" at the end of the python script to be sure.

Do you have a clue on what could make the job waiting so long before finishing?

Thanks a lot

Soal

long_wait.png

long_wait_2.png

RR, Schoenberger

unread,

Nov 16, 2023, 11:20:07 AM11/16/23

to rrKn...@googlegroups.com

Hi

Please see the bottom of your screenshots.

RR warns that not all processes that have been started have been closed yet.

We have already got reports that this happens on some sites, but not all.

I assume that in some environments these tools are started with the system and not when Maya is started.
Or the license type is different and they close.

Anyway, we have added a workaround for our Maya scripts:

We terminate these tools after Maya finished.

ADSSO is terminated in RR for over a year.

ADPCLIENTSERVICE and AdskLicensingAgent will be terminated with the next RR update.

I assume you have created your own render config for Maya scripts?

Please edit your render config and after

CommandLine= <CheckExitCode> <FN>

add these lines:

CommandLine= "<rrBin64>rrKillWait" 1 ADSSO -this

CommandLine= "<rrBin64>rrKillWait" 1 ADPCLIENTSERVICE -this

CommandLine= "<rrBin64>rrKillWait" 1 AdskLicensingAgent -this

regards,
Holger Schönberger

Please use the rrKnights Tavern
or our support system for new questions.

Soal GIVORD

unread,

Nov 17, 2023, 4:36:51 AM11/17/23

to Royal Render Knights Tavern

Hello,

the config file was in fact E01__ExecuteOnce.cfg, but after applying those 3 lines it works like a charm!

Thanks a lot

Best regards

RR, Schoenberger

unread,

Nov 17, 2023, 5:04:50 AM11/17/23

to rrKn...@googlegroups.com

Ok, so you are writing a batch/shell file.

If you have some time you could test an other way.

Open the scene file in Maya, then choose menu RRender “Pick python script to execute”.

RR takes care of opening the file as it does with any render job.

Then executes your python script within the scene.

Or course this a test only.
I assume you have some pipeline tool that creates the .bat files.
Which could be modified to use the same submission as this test.

Damien KERAUDREN

unread,

Nov 27, 2023, 12:24:38 PM11/27/23

to Royal Render Knights Tavern

Hey, just popping by regarding this issue, we have the same problem on our maya 2024 renders

here is the renderer log

Nov 27. 17:30.03| NEW {X3D } job received 23-103,40
Nov 27. 17:30.03| {X3D } Job Received: {X3D } test2|Maya|--s _v|t_2024_low_cpu_dkeraudren_v001 (Preview 1040-1120,40)
Nov 27. 17:30.03| {X3D } Rendering to: C:\RR_localdata\renderout\A\rendu\dkeraudren\069-069_rendu_test_2024_low_cpu_dkeraudren_v001\masterLayer\beauty\camera1_069-069_rendu_test_2024_low_cpu_dkeraudren_v001_masterLayer_beauty. copy to:\\storf\diskf\test2\069-069\3d\images\
Nov 27. 17:30.03| {X3D } Auto-version change.
Job: 2024.010000000000000
Client cfg: 2020.000000000000000 (C:\Program Files\Autodesk\Maya2020\bin\Render.exe)
Searching for 'C:\Program Files\Autodesk\Maya*\bin\Render.exe'
Nov 27. 17:30.03| {X3D } Starting 1 Job instances... {X3D } test2|Maya|--s _v|t_2024_low_cpu_dkeraudren_v001 (System Memory: Available/Free: 126173MB System Cache: 296MB Kernel: 1553MB)
Nov 27. 17:30.04| rrClient app memory usage: 298 MB.
Nov 27. 17:30.04| {X3D } Job Started
Nov 27. 17:30.33| ******* Sending client status '{X3D } Rendering Job 1040-1120,40' userIdle: 11285*******
Nov 27. 17:35.17| WRN {X3D } Render process finished, but there are still render processes (1 min.)
Nov 27. 17:35.17| cCommand: Show process tree from rrUnknown ( send by 'UnclosedProcesses' )
Nov 27. 17:35.17| {X3D } ########## Job Processes ################
Nov 27. 17:35.17| {X3D } 2 Processes (17:35.15)
PID: 8072 CPU:0.0c Mem: 26 Name:ADSKIDENTITYMANAGER.EXE (PPID:%5)
PID: 2416 CPU:0.0c Mem: 45 Name:ADSSO.EXE (PPID:%5)
Total CPU:0.0c Mem: 71
-------------------------------------------------------------------------------

Nov 27. 17:37.20| WRN {X3D } Render process finished, but there are still render processes (3 min.)
Nov 27. 17:37.20| cCommand: Show process tree from rrUnknown ( send by 'UnclosedProcesses' )
Nov 27. 17:37.20| {X3D } ########## Job Processes ################
Nov 27. 17:37.20| {X3D } 2 Processes (17:37.18)
PID: 8072 CPU:0.0c Mem: 26 Name:ADSKIDENTITYMANAGER.EXE (PPID:%5)
PID: 2416 CPU:0.0c Mem: 45 Name:ADSSO.EXE (PPID:%5)
Total CPU:0.0c Mem: 71
-------------------------------------------------------------------------------

Nov 27. 17:39.19| WRN {X3D } Render process finished, but there are still render processes (5 min.)
Nov 27. 17:39.19| cCommand: Show process tree from rrUnknown ( send by 'UnclosedProcesses' )
Nov 27. 17:39.19| {X3D } ########## Job Processes ################
Nov 27. 17:39.19| {X3D } 3 Processes (17:39.16)
PID: 2416 CPU:0.0c Mem: 45 Name:ADSSO.EXE (PPID:%5)
PID:11132 CPU:0.0c Mem: 8 Name:ADPCLIENTSERVICE.EXE (PPID:%5)
PID:11140 CPU:0.0c Mem: 10 Name:CONHOST.EXE (PPID:%5)
Total CPU:0.0c Mem: 63
-------------------------------------------------------------------------------

Nov 27. 17:41.17| WRN {X3D } Render process finished, but there are still render processes (7 min.)
Nov 27. 17:41.17| cCommand: Show process tree from rrUnknown ( send by 'UnclosedProcesses' )
Nov 27. 17:41.17| {X3D } ########## Job Processes ################
Nov 27. 17:41.17| {X3D } 3 Processes (17:41.15)
PID: 2416 CPU:0.0c Mem: 45 Name:ADSSO.EXE (PPID:%5)
PID:11132 CPU:0.0c Mem: 8 Name:ADPCLIENTSERVICE.EXE (PPID:%5)
PID:11140 CPU:0.0c Mem: 10 Name:CONHOST.EXE (PPID:%5)
Total CPU:0.0c Mem: 63
-------------------------------------------------------------------------------

Nov 27. 17:43.20| WRN {X3D } Render process finished, but there are still render processes (9 min.)
Nov 27. 17:43.20| cCommand: Show process tree from rrUnknown ( send by 'UnclosedProcesses' )
Nov 27. 17:43.20| {X3D } ########## Job Processes ################
Nov 27. 17:43.20| {X3D } 2 Processes (17:43.18)
PID:11132 CPU:0.0c Mem: 9 Name:ADPCLIENTSERVICE.EXE (PPID:%5)
PID:11140 CPU:0.0c Mem: 10 Name:CONHOST.EXE (PPID:%5)
Total CPU:0.0c Mem: 19
-------------------------------------------------------------------------------

Nov 27. 17:43.27| {X3D } Render task done.

Here is the corresponding job log part :

R270| ' 17:32.18 rrMaya : Frame #1120 done. Frame Time: 0:00:41.673776 h:m:s.ms

R271| ' 17:32.18 rrMaya : Render done

R272| ' 17:32.18 rrMaya : .

R273| ' 17:32.18 rrMaya : ...

R274| ' 17:32.18 rrMaya : .....

R275| ' 17:32.18 rrMaya : ..end..

R276|

R277|

R278| >"C:\Program Files\RoyalRender\lc64\rrCheckexitcode.exe" 0 0 0 1040

R279| ++____________________________________________________________________________________________________

0| ++ Nov 27. 17:32.21 Render executable closed ____________________________________________________

1| ++ Royal Render checks the return code of the executable or the OS _______________________________

2| ++ Executable returned 0 (0x0) as exit code for frame 1040 (jobthread 0). ________________________

3| ++ Executable finished ___________________________________________________________________________

4| ++____________________________________________________________________________________________________

5| >"\\storr\diskr\RoyalRender\bin\win64\rrKillWait" 1 ADSSO true

6| ||rrKillWait|| wait 0.2s for ADSSO.EXE. thisProcessGroup.

7| ||rrKillWait|| this process group was started by ... (ID 7888 RRKILLWAIT.EXE)

8| ||rrKillWait|| parent of our process group starter ... (ID 10004 CMD.EXE)

9| ||rrKillWait|| no render app with same parent process found. Searching render apps without parent

10| ||rrKillWait|| found (with parent) ADSSO.EXE ID 2416 ppID 8072

11|

12| +++++++++++++++++++++++++ All commandlines executed +++++++++++++++++++++++++++++++++++

13| +++++ 17:32:21,75

14| +++++ Job ID: {X3D }

15| +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

16|

17|

18|

19|

20| Current time:Nov 27. 17:43.30

21| Total processing time: 00:13.27 h:m.s

22| Max memory usage: 4.0GB (of 127GB installed, total system usage at same time: 8.6GB. Nov 27. 17:32.13)

23| Max CPU usage: 100% 128.0 of 128 cores (total system usage at same time: 0.0. Nov 27. 17:30.23)

The interesting thing is that the issue is nor raising when kso is enabled because kso recall an abortProcesses() when it didn't close, is there a way to reproduce this behavior without kso enabled ?

RR, Schoenberger

unread,

Nov 27, 2023, 12:44:10 PM11/27/23

to rrKn...@googlegroups.com

Hi

We have already added the ADPCLIENTSERVICE kill to the maya config file.
Unfortunately the current RR update took/takes a bit more time as we move from RR 9.0 to 9.1.

But the good news is that we are in the last steps of testing everything.
So it should be available this week.

Soal GIVORD

unread,

Apr 30, 2025, 6:59:27 AMApr 30

to Royal Render Knights Tavern

Hello,

i'm reviving this thread because even after putting extra commandlines to the ExecutOnce config, the jobs still freeze around 5 min before stopping completly.

I joined the config file capture and a sample of the log to this message.

Do you have any other trick to make Maya stop completely?

Thanks

Best regards

Soal

Capture d’écran 2025-04-30 113525.png

Capture d’écran 2025-04-30 113555.png

RR, Schoenberger

unread,

Apr 30, 2025, 8:11:11 AMApr 30

to rrKn...@googlegroups.com

I see the issue:

ADPClientService and AdskLicensingAgent are usually started by Maya directly.

But sometimes ADPClientService is started by AdskLicensingAgent.

Which means AdskLicensingAgent must be killed first.

We already fixed the order in which the processes are killed with RR 9.1.07.

I can see that you are using RR 9.1.12.

So either our Maya config files have not been updated because of a custom change

(In this case compare the config file to the one in the subfolder rr_original)
or you are using a custom config file which requires you to change the kill order.

PS:
Please note that your support&maintenance has expired.

Our system has already send a reminder to extend support&maintenance to contact@...box some time ago.

Soal GIVORD

unread,

Apr 30, 2025, 8:25:03 AMApr 30

to Royal Render Knights Tavern

Thanks a lot!

That was the trick i was looking for.

It works like a charm

About the support, we are aware of that and will probably extend it at some point.