Belisaire Earl
Belisaire Earl
About Me
Connect
LOCATION
Not Specified
ウェブサイト
Houdini Engine
Availability
Not Specified
Recent Forum Posts
ShotGrid nodes do not work with Server Type: Service 2024年8月23日12:09
Ah, that's a shame.
The shared server method if I'm not mistaken spawns one actual server per input task, and processes then the queries for each input task, which is not really optimized for Shotgrid (Flow, whatever ^^)
At least that is the conclusion I have when I see Nx3 tasks spawning at the begin server block for N input tasks.
I was hoping that the service would allow us to process requests from 1 single connection point and avoid flooding the Shotgrid server, as I often have hundreds of inputs.
Thanks for the update in any case.
Cheers,
Beli
The shared server method if I'm not mistaken spawns one actual server per input task, and processes then the queries for each input task, which is not really optimized for Shotgrid (Flow, whatever ^^)
At least that is the conclusion I have when I see Nx3 tasks spawning at the begin server block for N input tasks.
I was hoping that the service would allow us to process requests from 1 single connection point and avoid flooding the Shotgrid server, as I often have hundreds of inputs.
Thanks for the update in any case.
Cheers,
Beli
ShotGrid nodes do not work with Server Type: Service 2024年8月23日10:22
Hello,
Just adding in that I have the same exact issue (Houdini 20.5.332), and am hoping that there is a solution, as I would prefer using the service then the sharedserver.
Beli.
Just adding in that I have the same exact issue (Houdini 20.5.332), and am hoping that there is a solution, as I would prefer using the service then the sharedserver.
Beli.
TOP / Deadline Scheduler - H19.5.493 - Tasks going missing 2023年4月6日4:12
Hello,
I've been running into an issue with TOPs for a couple days and have been debugging it. FYI I have this support request on Discord as well.
Basically what is happening is that I am unable to get all of the tasks to be processed by Deadline. Some of the "Task append" commands are having no effect on the deadline job and I have no logs to look at
I activated Verbose and I see the task files being generated and the line indicating that the scheduler is appending the tasks
Here is the log file that is output from the Houdini Console
(See attached log.txt)
Here is another example job sent. I specified not more than 5 tasks at a time, and it seems that it is trying to send several of the append commands before the job is submitted in Deadline.
And if I do it remotely on the farm for example (Using Submit Job) :
It seems to think everything is done correctly, but still an incorrect result... Very weird!
I finally found an error message on the scheduler node itself. Unsure what to do with it though, but will continue searching. So far, I have seen a few topics about deadline configuration but nothing that seems to be a match for my issues.
Any ideas would be appreciated.
For info, I am using Deadline 10.2.0.10
The variable %DEADLINE_PATH% is correctly setup.
I am not using any custom version of the PDGDeadline plugin
I have only tweaked the "Tasks Batch" values, as well as activated "Verbose Logging"
Plugin and Repository paths are default
A text transcripion of the error message (for seaches):
Thank you,
Beli.
I've been running into an issue with TOPs for a couple days and have been debugging it. FYI I have this support request on Discord as well.
Basically what is happening is that I am unable to get all of the tasks to be processed by Deadline. Some of the "Task append" commands are having no effect on the deadline job and I have no logs to look at
I activated Verbose and I see the task files being generated and the line indicating that the scheduler is appending the tasks
Here is the log file that is output from the Houdini Console
(See attached log.txt)
Image Not Found
Here is another example job sent. I specified not more than 5 tasks at a time, and it seems that it is trying to send several of the append commands before the job is submitted in Deadline.
And if I do it remotely on the farm for example (Using Submit Job) :
2023-04-05 18:13:59: 0: STDOUT: 18:13:58 Submitting 5 tasks: 1,2,3,4,5 2023-04-05 18:13:59: 0: STDOUT: 18:13:58 Appending frame range: 1,2,3,4,5 2023-04-05 18:13:59: 0: STDOUT: 18:13:59 Submitting 5 tasks: 6,7,8,9,10 2023-04-05 18:13:59: 0: STDOUT: 18:13:59 Appending frame range: 6,7,8,9,10 2023-04-05 18:14:00: 0: STDOUT: 18:14:00 Submitting 5 tasks: 11,12,13,14,15 2023-04-05 18:14:00: 0: STDOUT: 18:14:00 Appending frame range: 11,12,13,14,15 2023-04-05 18:14:00: 0: STDOUT: 18:14:00 Submitting 5 tasks: 16,17,18,19,20 2023-04-05 18:14:00: 0: STDOUT: 18:14:00 Appending frame range: 16,17,18,19,20 2023-04-05 18:14:01: 0: STDOUT: 18:14:01 Submitting 5 tasks: 21,22,23,24,25 2023-04-05 18:14:01: 0: STDOUT: 18:14:01 Appending frame range: 21,22,23,24,25 2023-04-05 18:14:02: 0: STDOUT: 18:14:01 Submitting 5 tasks: 26,27,28,29,30 2023-04-05 18:14:02: 0: STDOUT: 18:14:01 Appending frame range: 26,27,28,29,30 2023-04-05 18:14:02: 0: STDOUT: 18:14:02 Submitting 5 tasks: 31,32,33,34,35 2023-04-05 18:14:02: 0: STDOUT: 18:14:02 Appending frame range: 31,32,33,34,35 2023-04-05 18:14:03: 0: STDOUT: 18:14:02 Submitting 5 tasks: 36,37,38,39,40 2023-04-05 18:14:03: 0: STDOUT: 18:14:02 Appending frame range: 36,37,38,39,40 2023-04-05 18:14:03: 0: STDOUT: 18:14:03 Submitting 5 tasks: 41,42,43,44,45 2023-04-05 18:14:03: 0: STDOUT: 18:14:03 Appending frame range: 41,42,43,44,45 2023-04-05 18:14:04: 0: STDOUT: 18:14:04 Submitting 4 tasks: 46,47,48,49 2023-04-05 18:14:04: 0: STDOUT: 18:14:04 Appending frame range: 46,47,48,49
I finally found an error message on the scheduler node itself. Unsure what to do with it though, but will continue searching. So far, I have seen a few topics about deadline configuration but nothing that seems to be a match for my issues.
Any ideas would be appreciated.
For info, I am using Deadline 10.2.0.10
The variable %DEADLINE_PATH% is correctly setup.
I am not using any custom version of the PDGDeadline plugin
I have only tweaked the "Tasks Batch" values, as well as activated "Verbose Logging"
Plugin and Repository paths are default
A text transcripion of the error message (for seaches):
Failed to submit new tasks: 142,143. Error: Index was outside the bounds of the array. (System.IndexOutOfRangeException) thinkbox deadline
Thank you,
Beli.