2.0.8.1 issue on Linux

Support
1

I got the notification of the update from 2.0.7 to 2.0.8 and let it do the update. Then I told it to run one of my backups, that usually runs 20 minutes. It’s over an hour now and still showing starting backup. mono-sgen is at 100% cpu.

Help!

Here are the logs:

May 11, 2024 12:50 PM: Request for http://localhost:8200/api/v1/serverstate/?lasteventid=18285&longpoll=true&duration=299s gave error
System.Threading.ThreadAbortException: Thread was being aborted.
at (wrapper managed-to-native) System.Threading.WaitHandle.Wait_internal(intptr*,int,bool,int)
at System.Threading.WaitHandle.WaitOneNative (System.Runtime.InteropServices.SafeHandle waitableSafeHandle, System.UInt32 millisecondsTimeout, System.Boolean hasThreadAffinity, System.Boolean exitContext) [0x00044] in <533173d24dae460899d2b10975534bb0>:0
at System.Threading.WaitHandle.InternalWaitOne (System.Runtime.InteropServices.SafeHandle waitableSafeHandle, System.Int64 millisecondsTimeout, System.Boolean hasThreadAffinity, System.Boolean exitContext) [0x00014] in <533173d24dae460899d2b10975534bb0>:0
at System.Threading.WaitHandle.WaitOne (System.Int64 timeout, System.Boolean exitContext) [0x00000] in <533173d24dae460899d2b10975534bb0>:0
at System.Threading.WaitHandle.WaitOne (System.Int32 millisecondsTimeout, System.Boolean exitContext) [0x00019] in <533173d24dae460899d2b10975534bb0>:0
at Duplicati.Server.EventPollNotify.Wait (System.Int64 eventId, System.Int32 milliseconds) [0x00042] in <30a34d71126b48248d040dda634ddad9>:0
at Duplicati.Server.WebServer.RESTMethods.RequestInfo.LongPollCheck (Duplicati.Server.EventPollNotify poller, System.Int64& id, System.Boolean& isError) [0x00119] in <30a34d71126b48248d040dda634ddad9>:0
at Duplicati.Server.WebServer.RESTMethods.ServerState.GET (System.String key, Duplicati.Server.WebServer.RESTMethods.RequestInfo info) [0x0000c] in <30a34d71126b48248d040dda634ddad9>:0
at Duplicati.Server.WebServer.RESTHandler.DoProcess (Duplicati.Server.WebServer.RESTMethods.RequestInfo info, System.String method, System.String module, System.String key) [0x00146] in <30a34d71126b48248d040dda634ddad9>:0
May 11, 2024 12:50 PM: Reporting error gave error
System.ObjectDisposedException: Can not write to a closed TextWriter.
at System.IO.StreamWriter.Flush (System.Boolean flushStream, System.Boolean flushEncoder) [0x00008] in <533173d24dae460899d2b10975534bb0>:0
at System.IO.StreamWriter.Flush () [0x00006] in <533173d24dae460899d2b10975534bb0>:0
at Duplicati.Server.WebServer.RESTHandler.DoProcess (Duplicati.Server.WebServer.RESTMethods.RequestInfo info, System.String method, System.String module, System.String key) [0x003bc] in <30a34d71126b48248d040dda634ddad9>:0
May 11, 2024 12:50 PM: Request for http://localhost:8200/api/v1/serverstate?longpoll=true&lasteventid=18285&format=json&duration=5m gave error
System.Threading.ThreadAbortException: Thread was being aborted.
at (wrapper managed-to-native) System.Threading.WaitHandle.Wait_internal(intptr*,int,bool,int)
at System.Threading.WaitHandle.WaitOneNative (System.Runtime.InteropServices.SafeHandle waitableSafeHandle, System.UInt32 millisecondsTimeout, System.Boolean hasThreadAffinity, System.Boolean exitContext) [0x00044] in <533173d24dae460899d2b10975534bb0>:0
at System.Threading.WaitHandle.InternalWaitOne (System.Runtime.InteropServices.SafeHandle waitableSafeHandle, System.Int64 millisecondsTimeout, System.Boolean hasThreadAffinity, System.Boolean exitContext) [0x00014] in <533173d24dae460899d2b10975534bb0>:0
at System.Threading.WaitHandle.WaitOne (System.Int64 timeout, System.Boolean exitContext) [0x00000] in <533173d24dae460899d2b10975534bb0>:0
at System.Threading.WaitHandle.WaitOne (System.Int32 millisecondsTimeout, System.Boolean exitContext) [0x00019] in <533173d24dae460899d2b10975534bb0>:0
at Duplicati.Server.EventPollNotify.Wait (System.Int64 eventId, System.Int32 milliseconds) [0x00042] in <30a34d71126b48248d040dda634ddad9>:0
at Duplicati.Server.WebServer.RESTMethods.RequestInfo.LongPollCheck (Duplicati.Server.EventPollNotify poller, System.Int64& id, System.Boolean& isError) [0x00119] in <30a34d71126b48248d040dda634ddad9>:0
at Duplicati.Server.WebServer.RESTMethods.ServerState.GET (System.String key, Duplicati.Server.WebServer.RESTMethods.RequestInfo info) [0x0000c] in <30a34d71126b48248d040dda634ddad9>:0
at Duplicati.Server.WebServer.RESTHandler.DoProcess (Duplicati.Server.WebServer.RESTMethods.RequestInfo info, System.String method, System.String module, System.String key) [0x00146] in <30a34d71126b48248d040dda634ddad9>:0
May 11, 2024 12:50 PM: Reporting error gave error
System.ObjectDisposedException: Can not write to a closed TextWriter.
at System.IO.StreamWriter.Flush (System.Boolean flushStream, System.Boolean flushEncoder) [0x00008] in <533173d24dae460899d2b10975534bb0>:0
at System.IO.StreamWriter.Flush () [0x00006] in <533173d24dae460899d2b10975534bb0>:0
at Duplicati.Server.WebServer.RESTHandler.DoProcess (Duplicati.Server.WebServer.RESTMethods.RequestInfo info, System.String method, System.String module, System.String key) [0x003bc] in <30a34d71126b48248d040dda634ddad9>:0

2

Did it ever run longer, like reported? There have been prior reports of high CPU usage, typically with mono.
Battle plan for migrating to .Net8 will get off of mono and .NET Framework, but the work is still in progress.

After more time, is the 12:50 PM log output the only one? Also view About → Show log → Live → Profiling.

Is that 100% of one core? I think Windows Task Manager would only say 100% if one got all cores up there.

What other activity (if any) can you spot with whatever you use for tools? Any disk I/O visible, for example?

3

My mistake, I had two different backups, one that is short and one that is long. I thought I was testing 2.0.8 on the short one, but I actually was testing the long one, which did end up finishing as usual on 2.0.8. Subsequently, I have tested several more backups on several different Linux machines, and they work on 2.0.8 just as they did on 2.0.7

1 Like