Hmm… We’re definitely eating that progress data too. Usually that’s a good thing as it’ll cut down on log size, but we must not be doing the calculations properly.
Update: I did some quick digging and the only lines we should be supressing are those which contain this:
"Progress: ([0-9]+) %"
I don’t know how or why that’s being suppressed here.
Just so I have something more to go on, the main complaint is that you’re not getting progress information on the tasks when doing multiple frames per task, or would you want to see the output in the log?
If you look for “self.SuppressThisLine()”, that is where we’re excluding information from the Slave log. Feel free to try commenting them out to see if it makes a difference.
There’s a lack of progress report which is annoying but can be dealt with
The main problem is that there’s no catch on errors,
e.g. if a frame fails to write, it’s not failing the job
and actually getting full report is also good when trying to debug jobs acting weirdly
Also on top of that I had to add the following code at line 157 of FusionCmd.py plugin file
It so happens (at least in our setup) that Fusion sometimes exits with this error code while it succeeded renders, no clue why
elif exitCode == -1073741819:
return
We’re using Deadline 8.0.7.3
Edit ; Just saw 8.0.8.1 is out
Will try to upgrade today
/
8.0.8.1 rolled out on Repository/Pulse/Windows rendering
Windows/Linux Clients/Linux Rendering on their way
Issue still there for Fusion Winx64
Hmm. The strange thing here is that Deadline is catching some of the log, but not all of it.
The only guess I have for this is that maybe Fusion writes that output to STDERR and not STDOUT and somehow we’re not catching that like we always have. When you pasted the command line output, did you use the pipe option I sent along, or did you copy from the command prompt?
Also, this seems like it’s turning into one of those “call to troubleshoot” problems. Here’s what I want to do: (in case you’d rather run with it)
Take that command line run that gave all the output and feed it through the Command Line plugin in the Monitor
This would make sure it’s not a Fusion plugin problem. Depending on that, we’d investigate a different angle.
Try piping that render text to two different files:
We are using the comand line Fusion plugin. Normal plugin is not working at all.
Deadline receives a -1073741819 returncode which should refer to a memory problem but I think that is very unlikely. By adding this code in the checkexitcode() part the job continues.
The main problem is that Deadline is not receiving the standard exitcode but always receives a -1073741819 code
In the attached log you can see that I have some bad frames (I have to look into that later) which are caused by a input mov file.
The exitcode fusion throws is 10 which s great because it shows things went wrong. Deadline receives the -1073741819 code always. So my guess is that deadline is somehow not receiving a proper errorcode anymore.
If all renders are ok there is no problem but I want to detect the wrongly rendered frames.
The exit code hasn’t really gone wrong before this. I can only see possible problems if you have ‘render as user’ enabled in the user security settings.
I think we’ll need to include an option to ignore that exit code… Any issues with that idea from anyone?
I would have no problem with ignoring that exit code. But I would like to see the exitcode that fusion returned. There are already some exitcodes within the scripts that seems to be right (errorcode 10 for instance)
It would be helpfull if the ‘right’ exitcode will be used so we can see if a comp goes wrong.
Deadline has never used the wrong exit code before. At least not that I can remember. It’s built into the operating system, so not much can go wrong without ‘run as user’.
Can you try running it from the command line and then running “echo %ERRORLEVEL%” immediately after? That should show whatever the true exit code was from the application. The error code from the program output though might be entirely different. We could just look for the text “Auto-exiting with errcode (\d+)” and that would return the number from that line.
Sorry for the silence. The %errorlevel% is -1073741819. Always. I checked with a batch job. So the command line version of fusion probably only returns that code. Which is a shame. I have attached a somewhat edited output.txt of the command line output.
As you can see Fusion reports an exiting with code 0 but somehow it doesn’t. I also read that the errorcode -1073741819 might have something to do with the Open CL drivers but I installed the latest version of them but it made no difference.
I am not sure if you can get the verbose output and check for this part.
Render completed successfully at Thu 4:16PM - Total Time: 0h 0m 5.63s, Average: 1.41 seconds/frame
Auto-exiting with errcode 0
Cleanup licenses
I hope this can be solved because if something goes wrong now the tasks will still be flagged as complete.
Okay! I’ll make a Git issue for that and we’ll hopefully be able to get something out for you either in the 8.0 service pack or 8.1 (not sure which will be out next). As usual, I’ll try to report back once it’s been implemented.
It would be great if the team can also fix the normal (non commandline) plugin of Fusion. This has been mentioned before. The process is unable to kill the fuscript.exe becasue of a rights issue.
The output seems alright. I’d expect non-normal operations like warnings and errors to come through STDERR and the rest to go to STDOUT. The good news is Deadline mushes them both into the same stream handling functions, so for us it doesn’t matter much. The good news is that SP12 added the “Exit code -1073741819 is no longer treated as an error during rendering.”, so you should be in good shape with Fusion now in SP13. Are you getting new errors?
To be clear I only see the STDERR catched by deadline
The STDOUT is just nowhere to be found
this poses problem as there is no progress report, but the most problematic is that it’s not catching on errors because of that
So, after digging into our issue tracker this may have been caused by a bad auto-upgrade. Would you be able to uninstall and re-install Deadline? We’d want to clear out the ‘bin’ directory before re-installing. The guess is that there may be a bad DLL.
If that makes no difference, it might be related to a different problem that we’re working on this week.
