Debug plugin running through service (Windows)

We are using the Deadline service to run under a different user than the one logged in.

We are developing a plugin, which is built on the CommandLine plugin, to render CelAction through. The plugin is working when not using the Deadline service, but I don’t get how to debug it when I can’t see what is happening.
I’ve tried using the same command lines the plugin report in a Render log, and this works fine.

Anyone got any tips on how to debug this?

Hello,

You should be able to see the slave log by using the monitor’s ‘connect to slave log…’ feature. You said it runs outside of Deadline, but can you advise what happens when it runs inside Deadline? If you can share more info that would be great.

Hey Dwight,

Here are two videos showing the plugin running with and without service mode;

Without service mode; https://youtu.be/mLTYXMppzxs
With service mode; https://youtu.be/pofN61RfB_k

CelAction does not output anything to the terminal, which is not Deadline’s fault, just a design implementation from CelAction. So the render logs are the same for both with and without service mode;

[code]=======================================================
Log

2016-08-01 09:41:25: BEGIN - 061-KUVIRA\render.farm
2016-08-01 09:41:25: 0: Start Job timeout is disabled.
2016-08-01 09:41:25: 0: Task timeout is disabled.
2016-08-01 09:41:25: 0: Plugin rendering frame(s): 11-20
2016-08-01 09:41:25: 0: INFO: Stdout Redirection Enabled: True
2016-08-01 09:41:25: 0: INFO: Stdout Handling Enabled: True
2016-08-01 09:41:25: 0: INFO: Popup Handling Enabled: True
2016-08-01 09:41:25: 0: INFO: QT Popup Handling Enabled: False
2016-08-01 09:41:25: 0: INFO: WindowsForms10.Window.8.app.* Popup Handling Enabled: False
2016-08-01 09:41:25: 0: INFO: Using Process Tree: True
2016-08-01 09:41:25: 0: INFO: Hiding DOS Window: True
2016-08-01 09:41:25: 0: INFO: Creating New Console: False
2016-08-01 09:41:25: 0: INFO: Running as user: render.farm
2016-08-01 09:41:25: 0: INFO: Executable: “K:\development\tools\celaction\v3.888\CelAction2D.exe”
2016-08-01 09:41:25: 0: INFO: Argument: “y:\projects\testing\shots\sh001\animation\publish\sh001.animation.v016.scn” -a -s 11 -e 20 -d “y:/projects/testing/renders/img/sh001/animation/v016/scene” -x 1920 -y 1080 -r “y:/projects/testing/renders/img/sh001/animation/v016/scene/scene.v016.png” -= AbsoluteFrameNumber=on -= PadDigits=4 -= ClearAttachment=on
2016-08-01 09:41:25: 0: INFO: Startup Directory: “K:\development\tools\celaction\v3.888”
2016-08-01 09:41:25: 0: INFO: Process Priority: BelowNormal
2016-08-01 09:41:25: 0: INFO: Process Affinity: default
2016-08-01 09:41:25: 0: INFO: Process is now running
2016-08-01 09:41:31: 0: INFO: Process exit code: 0

=======================================================
Details

Date: 08/01/2016 09:41:31
Frames: 11-20
Job Submit Date: 08/01/2016 09:10:45
Job User: toke.jepsen
Average RAM Usage: 15942451 (1%)
Peak RAM Usage: 31703040 (1%)
Average CPU Usage: 8%
Peak CPU Usage: 10%
Used CPU Clocks: 3871
Total CPU Clocks: 48380

=======================================================
Slave Information

Slave Name: 061-KUVIRA
Version: v7.2.1.0 R (f3c20b064)
Operating System: Windows 7 Professional (SP1)
Running As Service: Yes
Machine User: render.farm
IP Address: 192.168.145.36
MAC Address: 1C:6F:65:C3:6C:86
CPU Architecture: x64
CPUs: 8
CPU Usage: 26%
Memory Usage: 4.4 GB / 16.0 GB (27%)
Free Disk Space: 128.436 GB
Video Card: NVIDIA GeForce GTX 570
[/code]

Have you tried running the service with the optional checkbox enabled: “Allow Service to Interact with desktop”:
howtogeek.com/school/using-w … o/lesson8/
(Please note limitations if you are running Windows 8 compared to Windows 7 OS).

If that doesn’t help, then some applications simply don’t work when being run as a service and although Deadline software runs quite happily as a service, we do need the application in question being executed to also support being run in this way.

That did actually work:) But after consulting our IT guys, it is too much of a security risk:(

CelAction wasn’t designed to run as a service, and can’t render without opening its interface.

We’re accepting that we can’t run it through a service now, and planning our farm accordingly.