with 5.14 mono, jackett fails to connect to torrent sites

[sparklyballs]

Thanks, team linuxserver.io

using :latest pull of jackett.

docker inspect -f '{{ index .Config.Labels "build_version" }}' jackett
Linuxserver.io version:- v0.10.903-ls11 Build-date:- 2019-03-06T10:07:14+00:00

docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/jackett
Linuxserver.io version:- v0.10.903-ls11 Build-date:- 2019-03-06T10:07:14+00:00

# mono -V
Mono JIT compiler version 5.14.0.177 (tarball Mon Aug  6 09:13:43 UTC 2018)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
    TLS:           __thread
    SIGSEGV:       altstack
    Notifications: epoll
    Architecture:  amd64
    Disabled:      none
    Misc:          softdebug
    Interpreter:   yes
    LLVM:          yes(3.6.0svn-mono-/)
    GC:            sgen (concurrent by default)

docker version and host information:

docker info
Containers: 28
 Running: 28
 Paused: 0
 Stopped: 0
Images: 26
Server Version: 18.09.3
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: e6b3f5632f50dbc4e9cb6288d911bf4f5e95b18e
runc version: 6635b4f0c6af3810594d2770f662f34ddc15b40d
init version: fec3683
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.15.18-11-pve
Operating System: Debian GNU/Linux 9 (stretch)
OSType: linux
Architecture: x86_64
CPUs: 32
Total Memory: 62.86GiB
Name: proxmox
ID: FZSK:WGVO:N675:IX5T:TSXA:MVTA:HFZR:TKQ6:XU2Z:X7IH:5MBZ:PF2Q
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false
Product License: Community Engine

WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled

uname -a
Linux proxmox 4.15.18-11-pve #1 SMP PVE 4.15.18-34 (Mon, 25 Feb 2019 14:51:06 +0100) x86_64 GNU/Linux

host is proxmox (debian) latest community version.

after an unknown period of time , all of my torrent sites fail with the following message in the webui.

the log is full of bajillions of stacktrace messages, sample below...

--- End of stack trace from previous location where exception was thrown ---
  at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker+<InvokeNextResourceFilter>d__23.MoveNext () [0x0009f] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
--- End of stack trace from previous location where exception was thrown ---
  at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow (Microsoft.AspNetCore.Mvc.Filters.ResourceExecutedContext context) [0x0001b] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
  at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Next (Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker+State& next, Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker+Scope& scope, System.Object& state, System.Boolean& isCompleted) [0x00840] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
  at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker+<InvokeFilterPipelineAsync>d__18.MoveNext () [0x0002f] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
--- End of stack trace from previous location where exception was thrown ---
  at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker+<InvokeAsync>d__16.MoveNext () [0x0012e] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
--- End of stack trace from previous location where exception was thrown ---
  at Microsoft.AspNetCore.Builder.RouterMiddleware+<Invoke>d__4.MoveNext () [0x001cb] in <6092a16d93814eba828b517a2b132f80>:0
--- End of stack trace from previous location where exception was thrown ---
  at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware+<Invoke>d__6.MoveNext () [0x00384] in <427697fe42b7459ba5302fb76d339d3b>:0
--- End of stack trace from previous location where exception was thrown ---
  at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware+<Invoke>d__7.MoveNext () [0x0043e] in <f352e566abf6421e87eafbcf57a0b237>:0
--- End of stack trace from previous location where exception was thrown ---
  at Jackett.Server.Middleware.CustomExceptionHandler+<Invoke>d__3.MoveNext () [0x0008a] in <0906f7e0790f445ba4d1e9d6fcb7f88d>:0

restarting the container "fixes" the issue, but so far it has reverted to being broken again 3 times in the last 2 days.

[sparklyballs]

relevant section of my docker-compose file.

  jackett:
    image: linuxserver/jackett
    container_name: jackett
    volumes:
      - $APPDATA_VALUE/jackett:/config
      - $APPDATA_VALUE/jackett/downloads:/downloads
      - $APPDATA_VALUE/torrent-watch:/downloads
    ports:
      - 9117:9117
    environment:
      - PGID=$PGID_VALUE
      - PUID=$PUID_VALUE
      - TZ=$TZ_VALUE
    restart: $RESTART_VALUE

[thelamer]

New builds of jackett are shifting to .net core. We should really emphasise gettting that out the door vs playing musical chairs with mono .

[sparklyballs]

it's just swapping one set of microsoft problems for another with .net core

[thelamer]

Can you vet the preview tag here https://hub.docker.com/r/lsiodev/jackett/tags

Your rubber stamp would be extremely helpful in getting this out the door.

[sparklyballs]

i don't like it pulling pre-release versions

unless the current releases are available with .net core , it's something that perhaps should wait until they do.

[thelamer]

Yeah we are just lacking testers j0hnny is the only one with a Jackett setup churning and burning daily. I understand it is not a fix for this particular issue, just a bit of hopeful foreshadowing .

[ghost]

The .NET Core version of Jackett is now at general release and is now the recommended way to run Jackett. Even though its Microsoft have found it to be solid unlike Mono. I use the linuxserver jackett image daily and the change to the preview tag was seamless, all settings and indexers worked as before. As a user I wouldn't have known anything had changed https://github.com/Jackett/Jackett/issues/4824

[aptalca]

@flightlevel that is great to know, thanks

[aptalca]

@flightlevel just a heads up, the jackett image latest tag has been migrated to use .net core. We also added a development tag to pull the pre-releases from github. So you can switch back to linuxserver/jackett ;)

[ghost]

Thanks @aptalca , great work from the LinuxServer team!