New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error with Debian mono 5.18 #3620

Open
achims311 opened this Issue Jan 22, 2019 · 12 comments

Comments

Projects
None yet
4 participants
@achims311
Copy link

achims311 commented Jan 22, 2019

  • I have searched open and closed issues for duplicates.

Environment info

  • Duplicati version: 2.0.4.5-1
  • Operating system: Debian unstable (mono 5.18)
  • Backend: all/none

Description

when starting duplicati it always generates a crash.
using the duplicati-server manually (not via systemd) I get the following stacktrace

Steps to reproduce

  1. update to latest debian mono packages (version 5.18)
  2. duplicati-server --log-level=debug --log-file=/tmp/dupli
  • Actual result:
    Unable to start up, perhaps another process is already running?
    Error message: System.InvalidOperationException: object_op ---> System.BadImageFormatException: Method has no body
    at System.IO.CoreFX.FileSystemWatcher.StartRaisingEvents () [0x00024] in :0
    at System.IO.CoreFX.FileSystemWatcher.StartRaisingEventsIfNotDisposed () [0x0001c] in :0
    at System.IO.CoreFX.FileSystemWatcher.set_EnableRaisingEvents (System.Boolean value) [0x0002a] in :0
    at (wrapper remoting-invoke-with-check) System.IO.CoreFX.FileSystemWatcher.set_EnableRaisingEvents(bool)
    at System.IO.CoreFXFileSystemWatcherProxy.m__0 (System.IO.CoreFX.FileSystemWatcher internal_fsw, System.IO.FileSystemWatcher fsw) [0x00048] in :0
    at System.IO.CoreFXFileSystemWatcherProxy.Operation (System.Action4[T1,T2,T3,T4] map_op, System.Action2[T1,T2] object_op, System.Object handle, System.Action2[T1,T2] cancel_op) [0x001d3] in <a9a08e39ba304bd0a84c49bd158dfc02>:0 --- End of inner exception stack trace --- at System.IO.CoreFXFileSystemWatcherProxy.Operation (System.Action4[T1,T2,T3,T4] map_op, System.Action2[T1,T2] object_op, System.Object handle, System.Action2[T1,T2] cancel_op) [0x001f8] in :0
    at System.IO.CoreFXFileSystemWatcherProxy.StartDispatching (System.Object handle) [0x00007] in :0
    at System.IO.FileSystemWatcher.Start () [0x00024] in :0
    at System.IO.FileSystemWatcher.set_EnableRaisingEvents (System.Boolean value) [0x00049] in :0
    at (wrapper remoting-invoke-with-check) System.IO.FileSystemWatcher.set_EnableRaisingEvents(bool)
    at Duplicati.Server.SingleInstance..ctor (System.String basefolder) [0x000ee] in :0
    at Duplicati.Server.Program.RealMain (System.String[] _args) [0x00307] in :0

  • Expected result:
    no stack trace..

Screenshots

Debug log

log-file exists, but is empty

@Pectojin

This comment has been minimized.

Copy link
Member

Pectojin commented Jan 23, 2019

Sounds like the same issue as #3572.

If you can downgrade to mono 5.16 that may fix your issue.

The Duplicati docker image is running Debian 8.11 with Mono 5.16.0.179, for reference.

@achims311

This comment has been minimized.

Copy link
Author

achims311 commented Jan 23, 2019

Yes you are right, the stracktrace is the same.
Interesting is thediff, for macOS not even 5.16 is working fine, but in debian it is.
Unfortunatly 5.16 never migrated to testing, and unstable only has 5.18 now, so switching back to 5.16 will be quite difficult(possible with the snapshops, but..)

@drwtsn32x

This comment has been minimized.

Copy link
Contributor

drwtsn32x commented Jan 24, 2019

I've also been hit by this with Duplicati 2.0.4.5.

I run Debian testing and mono was recently upgraded to 5.18.0.240, along with three or four dozen related supporting packages. I'm not even sure it's possible for me to go back to the version I had before.

Any ideas?

@Pectojin

This comment has been minimized.

Copy link
Member

Pectojin commented Jan 24, 2019

Mono's own repo is my best guess.

As far as I could tell they have every release available.
https://www.mono-project.com/download/stable/#download-lin-debian

@drwtsn32x

This comment has been minimized.

Copy link
Contributor

drwtsn32x commented Jan 24, 2019

Doesn't look like their repository has packages specifically for Debian testing (buster / 10). I see Debian 9 (stretch) and some older ones.

@drwtsn32x

This comment has been minimized.

Copy link
Contributor

drwtsn32x commented Jan 24, 2019

Ok I tested with Debian 9/stretch packages and it worked on Debian testing/10/buster.
I installed mono 5.16.

@achims311

This comment has been minimized.

Copy link
Author

achims311 commented Jan 25, 2019

I "only" found these as vs-strech.
So which version did you really install (exact version number)?
something like "5.??.0.????-0xamarin4+debian9b1"

@drwtsn32x

This comment has been minimized.

Copy link
Contributor

drwtsn32x commented Jan 25, 2019

I installed 5.16.0.220-0xamarin4+debian9b1. This is the version that is automatically selected by apt when you do the following:

First I removed and purged mono 5.18 and all related packages that were previously installed.

Then I added this to my apt sources (note that this targets 5.16 specifically):
deb https://download.mono-project.com/repo/debian stable-stretch/snapshots/5.16 main

Also I set up pinning to give preference to the packages from this source, otherwise the standard Debian repo will "win" since it has a newer version available:

Package: *
Pin: origin download.mono-project.com
Pin-Priority: 600

After you do that, if you do an apt install mono-runtime it will install the 5.16.XXXXX version.

@achims311

This comment has been minimized.

Copy link
Author

achims311 commented Jan 28, 2019

Some thing did not work out yet with this set-up but I worked around it by "holding" certain packages.

But, now I've got he first debian software package which requires 5.18 to get installed.
Sure I could start building this package locally or find any other workaround, but still I think the bug is still open, this software does not work under the latest debian packages (5.18)

@drwtsn32x

This comment has been minimized.

Copy link
Contributor

drwtsn32x commented Jan 28, 2019

Yeah you might have to Hold the 5.16 packages if you are trying to install something else that requires 5.18. I'm guessing the "pinning" trick doesn't work in that case. I am not in that situation so haven't run into it myself.

I think it's agreed here that Duplicati should be made compatible with 5.18. Or maybe mono 5.18 behavior is actually a bug and will be fixed in a future version of Mono.

@achims311

This comment has been minimized.

Copy link
Author

achims311 commented Jan 29, 2019

Who could confirm on which side the issue is on mono or duplicati side?

@warwickmm warwickmm added the mono label Feb 2, 2019

@warwickmm

This comment has been minimized.

Copy link
Contributor

warwickmm commented Feb 22, 2019

Possibly related:

mono/mono#12557

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment