Beta 4 on Fedora 15 x64
So far in my testing, I’ve been running all my Deadline apps manually. After updating the repo to Beta 4, I decided to try out the client auto-update, so I ran deadlinelauncher (as root, to give it proper perms), and it appeared to update properly.
After this I launched the Monitor, which proceeded to emit the following error constantly (with no interval) until I killed it.
[code]reporting ‘Deadline Monitor 6.0 [v6.0.0.48930 R] - UnauthorizedAccessException: Access to the path "/var/log/Thinkbox/Deadline6/deadlinemonitor(ws-vm01)-2012-10’ via email…
ErrorLog.WriteExceptionLog() >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Date Stamp
CurrentDate: Wednesday, October 31, 2012
CurrentTime: 3:58:22 PM
Exception Details
UnauthorizedAccessException – Access to the path “/var/log/Thinkbox/Deadline6/deadlinemonitor(ws-vm01)-2012-10-31-0000.log” is denied.
Exception.Source: mscorlib
Exception.TargetSite: Void .ctor(String, FileMode, FileAccess, FileShare, Int32, Boolean, FileOptions)
Exception.Data: ( )
Exception.StackTrace:
at System.IO.FileStream…ctor (System.String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean anonymous, FileOptions options) [0x00000] in :0
at System.IO.FileStream…ctor (System.String path, FileMode mode, FileAccess access, FileShare share) [0x00000] in :0
at (wrapper remoting-invoke-with-check) System.IO.FileStream:.ctor (string,System.IO.FileMode,System.IO.FileAccess,System.IO.FileShare)
at FranticX.Diagnostics.Tracing.TraceLogWriter.GetCurrentLog (System.Boolean& logUpdated) [0x00000] in :0
at FranticX.Diagnostics.Tracing.TraceLogWriter.a () [0x00000] in :0
at FranticX.Diagnostics.Tracing.TraceLogWriter.a (System.Object A_0, System.Timers.ElapsedEventArgs A_1) [0x00000] in :0
ErrorReporting Watches
“Version”: v6.0.0.48930 R[String]
Trace2Cache:
0 Other Running Threads
Process Threads
Memory and CPU Stats
GC.TotalMemory: 14.863 MB
Environment.WorkingSet: 0 Bytes
ComputerSystem.TotalPhysicalMemory: 1.957 GB
ComputerSystem.FreePhysicalMemory: 1.355 GB
Application Information
Application.ExecutablePath: /usr/Deadline6/client/bin/deadlinemonitor.exe
Application.CurrentDirectory: /home/ruschn
Application.StartupPath: /usr/Deadline6/client/bin
Application.ProductName: Deadline Monitor 6.0
Application.ProductVersion: 6.0.0.48930 File.GetLastWriteTime( Application.ExecutablePath ): 10/31/2012 3:57:16 PM
Assembly Information (Executing)
ExecutingAssembly.CodeBase: file:///usr/Deadline6/client/bin/franticx.dll
ExecutingAssembly.Location: /usr/Deadline6/client/bin/franticx.dll
ExecutingAssembly.GlobalAssemblyCache: False File.GetLastWriteTime( ExecutingAssembly.Location ): 10/31/2012 3:57:16 PM
Assembly Information (Current)
CurrentAssembly.CodeBase: file:///usr/Deadline6/client/bin/franticx.dll
CurrentAssembly.Location: /usr/Deadline6/client/bin/franticx.dll
CurrentAssembly.GlobalAssemblyCache: False File.GetLastWriteTime( CurrentAssembly.Location ): 10/31/2012 3:57:16 PM
Thread Information
CurrentThread.Name: Threadpool worker
CurrentThread.Priority: Lowest
Operating System Information
Environment.OSVersion.Platform: Linux
Environment.OSVersion.Version: 2.6.43.8
.NET Platform Information
Environment.Version.Major: 4
Environment.Version.Minor: 0
Environment.Version.Build: 30319
Environment.Version.Revision: 1
Misc Environment Information
Environment.MachineName: ws-vm01
Environment.UserName: ruschn
Environment.SystemDirectory:
Environment.TickCount: 936797
Command Line
Environment.CommandLine: /usr/Deadline6/client/bin/deadlinemonitor.exe
Environment.CommandLineArgs[0]: /usr/Deadline6/client/bin/deadlinemonitor.exe
Current Call Stack
Environment.StackTrace: at System.Environment.get_StackTrace()
at FranticX.Diagnostics.Reporting.ErrorReporting.GetExceptionReport(System.Exception e, ErrorReportDetail detail)
at FranticX.Diagnostics.Reporting.ErrorReporting.WriteExceptionReport(System.Exception ex)
at FranticX.Diagnostics.Reporting.ErrorReporting.RecordException(System.Exception e)
at FranticX.Diagnostics.Tracing.TraceLogWriter.a(System.Object A_0, System.Timers.ElapsedEventArgs A_1)
at System.Timers.Timer.Callback(System.Object state)
at System.Threading.Timer+Scheduler.TimerCB(System.Object o)
email file reporting failed: Sender account in the SMTP settings is blank (System.Exception)
exception occurred while recording file: Sender account in the SMTP settings is blank (System.Exception)[/code]
It seems fairly benign, but the rate at which it emits these things does affect GUI performance slightly. More importantly, this seems to be solely the fault of the autoupdate process. After grabbing the exception, I ran the client installer manually (again, as root), after which the error no longer appears when the monitor is launched.
-Nathan