local\ owenm 2015 - 08 - 27 23 : 57 : 55 : Deadline Launcher 7.2 2015 - 08 - 27 23 : 57 : 55 : deadlinelaunchernew is running 2015 - 08 - 27 23 : 57 : 55 : deadlinelauncher has exited, proceeding with self upgrade 2015 - 08 - 27 23 : 58 : 00 : Reading in bootstrap ini settings. For this reason, we recommend ensuring that access to log files is restricted to trusted users only.Ģ015 - 08 - 27 23 : 57 : 55 : BEGIN - mbp. Note that log files contain sensitive data in job info and output from render applications, such as names of projects, scenes, shots, etc.
Please see the section Access via API for more details. Alternatively, our API can be used to regularly ‘take a copy’ of any of the log reports and push them to an external location outside of Deadline. It is recommended to NOT redirect/pipe any Deadline logs to a remote location as this will stop job, task and slave reports from being visible in the Deadline Monitor panels. Under Configure Repository Options, various Application Data settings are available to control the deletion interval of application logs, maximum number of history entries per application and finally, if a high level of verbosity should be enabled for Slave, Pulse and Balancer (very useful for render job debugging). When exporting multiple reports, Deadline will automatically create a single zip file. Job, Slave, Event, Requeue log reports can easily be exported from Deadline and shared. The application logs are stored as flat *.log files, which makes it easy to zip up and send as a single package. It’s recommended to always provide log reports where applicable to Thinkbox when contacting for support. Typically, these logs will help to diagnose the root cause of an error (exception) in Deadline. You can stream, visualize, filter, analyze, copy, and export the logs via Deadline. Deadline provides logging in a number of areas.
0 kommentar(er)
