• Crashes since updating to v6.11.x for qBittorrent and Deluge users


    JorgeB
    • Closed

    EDIT: issue was traced to libtorrent 2.x, it's not an Unraid problem, more info in this post:

     

    https://forums.unraid.net/bug-reports/stable-releases/crashes-since-updating-to-v611x-for-qbittorrent-and-deluge-users-r2153/?do=findComment&comment=21671

     

     

    Original Post:

     

    I'm creating this to better track an issue that some users have been reporting where Unraid started crashing after updating to v6.11.x (it happens with both 6.11.0 and 6.11.1), there's a very similar call traced logged for all cases, e.g:

     

    Oct 12 04:18:27 zaBOX kernel: BUG: kernel NULL pointer dereference, address: 00000000000000b6
    Oct 12 04:18:27 zaBOX kernel: #PF: supervisor read access in kernel mode
    Oct 12 04:18:27 zaBOX kernel: #PF: error_code(0x0000) - not-present page
    Oct 12 04:18:27 zaBOX kernel: PGD 0 P4D 0
    Oct 12 04:18:27 zaBOX kernel: Oops: 0000 [#1] PREEMPT SMP PTI
    Oct 12 04:18:27 zaBOX kernel: CPU: 4 PID: 28596 Comm: Disk Tainted: P     U  W  O      5.19.14-Unraid #1
    Oct 12 04:18:27 zaBOX kernel: Hardware name: Gigabyte Technology Co., Ltd. Z390 AORUS PRO WIFI/Z390 AORUS PRO WIFI-CF, BIOS F12 11/05/2021
    Oct 12 04:18:27 zaBOX kernel: RIP: 0010:folio_try_get_rcu+0x0/0x21
    Oct 12 04:18:27 zaBOX kernel: Code: e8 8e 61 63 00 48 8b 84 24 80 00 00 00 65 48 2b 04 25 28 00 00 00 74 05 e8 9e 9b 64 00 48 81 c4 88 00 00 00 5b c3 cc cc cc cc <8b> 57 34 85 d2 74 10 8d 4a 01 89 d0 f0 0f b1 4f 34 74 04 89 c2 eb
    Oct 12 04:18:27 zaBOX kernel: RSP: 0000:ffffc900070dbcc0 EFLAGS: 00010246
    Oct 12 04:18:27 zaBOX kernel: RAX: 0000000000000082 RBX: 0000000000000082 RCX: 0000000000000082
    Oct 12 04:18:27 zaBOX kernel: RDX: 0000000000000001 RSI: ffff888757426fe8 RDI: 0000000000000082
    Oct 12 04:18:27 zaBOX kernel: RBP: 0000000000000000 R08: 0000000000000028 R09: ffffc900070dbcd0
    Oct 12 04:18:27 zaBOX kernel: R10: ffffc900070dbcd0 R11: ffffc900070dbd48 R12: 0000000000000000
    Oct 12 04:18:27 zaBOX kernel: R13: ffff88824f95d138 R14: 000000000007292c R15: ffff88824f95d140
    Oct 12 04:18:27 zaBOX kernel: FS:  000014ed38204b38(0000) GS:ffff8888a0500000(0000) knlGS:0000000000000000
    Oct 12 04:18:27 zaBOX kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Oct 12 04:18:27 zaBOX kernel: CR2: 00000000000000b6 CR3: 0000000209854005 CR4: 00000000003706e0
    Oct 12 04:18:27 zaBOX kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    Oct 12 04:18:27 zaBOX kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
    Oct 12 04:18:27 zaBOX kernel: Call Trace:
    Oct 12 04:18:27 zaBOX kernel: <TASK>
    Oct 12 04:18:27 zaBOX kernel: __filemap_get_folio+0x98/0x1ff
    Oct 12 04:18:27 zaBOX kernel: ? _raw_spin_unlock_irqrestore+0x24/0x3a
    Oct 12 04:18:27 zaBOX kernel: filemap_fault+0x6e/0x524
    Oct 12 04:18:27 zaBOX kernel: __do_fault+0x2d/0x6e
    Oct 12 04:18:27 zaBOX kernel: __handle_mm_fault+0x9a5/0xc7d
    Oct 12 04:18:27 zaBOX kernel: handle_mm_fault+0x113/0x1d7
    Oct 12 04:18:27 zaBOX kernel: do_user_addr_fault+0x36a/0x514
    Oct 12 04:18:27 zaBOX kernel: exc_page_fault+0xfc/0x11e
    Oct 12 04:18:27 zaBOX kernel: asm_exc_page_fault+0x22/0x30
    Oct 12 04:18:27 zaBOX kernel: RIP: 0033:0x14ed3a0ae7b5
    Oct 12 04:18:27 zaBOX kernel: Code: 8b 48 08 48 8b 32 48 8b 00 48 39 f0 73 09 48 8d 14 08 48 39 d6 eb 0c 48 39 c6 73 0b 48 8d 14 0e 48 39 d0 73 02 0f 0b 48 89 c7 <f3> a4 66 48 8d 3d 59 b7 22 00 66 66 48 e8 d9 d8 f6 ff 48 89 28 48
    Oct 12 04:18:27 zaBOX kernel: RSP: 002b:000014ed38203960 EFLAGS: 00010206
    Oct 12 04:18:27 zaBOX kernel: RAX: 000014ed371aa160 RBX: 000014ed38203ad0 RCX: 0000000000004000
    Oct 12 04:18:27 zaBOX kernel: RDX: 000014c036530000 RSI: 000014c03652c000 RDI: 000014ed371aa160
    Oct 12 04:18:27 zaBOX kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 000014ed38203778
    Oct 12 04:18:27 zaBOX kernel: R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000000
    Oct 12 04:18:27 zaBOX kernel: R13: 000014ed38203b40 R14: 000014ed384fe940 R15: 000014ed38203ac0
    Oct 12 04:18:27 zaBOX kernel: </TASK>
    Oct 12 04:18:27 zaBOX kernel: Modules linked in: macvlan xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net vhost vhost_iotlb tap tun veth xt_nat xt_tcpudp xt_conntrack nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter xfs md_mod kvmgt mdev i915 iosf_mbi drm_buddy i2c_algo_bit ttm drm_display_helper intel_gtt agpgart hwmon_vid iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables af_packet 8021q garp mrp bridge stp llc bonding tls ipv6 nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) x86_pkg_temp_thermal intel_powerclamp drm_kms_helper btusb btrtl i2c_i801 btbcm coretemp gigabyte_wmi wmi_bmof intel_wmi_thunderbolt mxm_wmi kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd
    Oct 12 04:18:27 zaBOX kernel: btintel rapl intel_cstate intel_uncore e1000e i2c_smbus bluetooth drm nvme nvme_core ahci i2c_core libahci ecdh_generic ecc syscopyarea sysfillrect input_leds sysimgblt led_class joydev nzxt_kraken2 intel_pch_thermal fb_sys_fops thermal fan video tpm_crb wmi tpm_tis backlight tpm_tis_core tpm acpi_pad button unix
    Oct 12 04:18:27 zaBOX kernel: CR2: 00000000000000b6
    Oct 12 04:18:27 zaBOX kernel: ---[ end trace 0000000000000000 ]---

     

    Another example with very different hardware:

    Oct 11 21:32:08 Impulse kernel: BUG: kernel NULL pointer dereference, address: 0000000000000056
    Oct 11 21:32:08 Impulse kernel: #PF: supervisor read access in kernel mode
    Oct 11 21:32:08 Impulse kernel: #PF: error_code(0x0000) - not-present page
    Oct 11 21:32:08 Impulse kernel: PGD 0 P4D 0
    Oct 11 21:32:08 Impulse kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI
    Oct 11 21:32:08 Impulse kernel: CPU: 1 PID: 5236 Comm: Disk Not tainted 5.19.14-Unraid #1
    Oct 11 21:32:08 Impulse kernel: Hardware name: System manufacturer System Product Name/ROG STRIX B450-F GAMING II, BIOS 4301 03/04/2021
    Oct 11 21:32:08 Impulse kernel: RIP: 0010:folio_try_get_rcu+0x0/0x21
    Oct 11 21:32:08 Impulse kernel: Code: e8 8e 61 63 00 48 8b 84 24 80 00 00 00 65 48 2b 04 25 28 00 00 00 74 05 e8 9e 9b 64 00 48 81 c4 88 00 00 00 5b e9 cc 5f 86 00 <8b> 57 34 85 d2 74 10 8d 4a 01 89 d0 f0 0f b1 4f 34 74 04 89 c2 eb
    Oct 11 21:32:08 Impulse kernel: RSP: 0000:ffffc900026ffcc0 EFLAGS: 00010246
    Oct 11 21:32:08 Impulse kernel: RAX: 0000000000000022 RBX: 0000000000000022 RCX: 0000000000000022
    Oct 11 21:32:08 Impulse kernel: RDX: 0000000000000001 RSI: ffff88801e450b68 RDI: 0000000000000022
    Oct 11 21:32:08 Impulse kernel: RBP: 0000000000000000 R08: 000000000000000c R09: ffffc900026ffcd0
    Oct 11 21:32:08 Impulse kernel: R10: ffffc900026ffcd0 R11: ffffc900026ffd48 R12: 0000000000000000
    Oct 11 21:32:08 Impulse kernel: R13: ffff888428441cb8 R14: 00000000000028cd R15: ffff888428441cc0
    Oct 11 21:32:08 Impulse kernel: FS:  00001548d34fa6c0(0000) GS:ffff88842e840000(0000) knlGS:0000000000000000
    Oct 11 21:32:08 Impulse kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Oct 11 21:32:08 Impulse kernel: CR2: 0000000000000056 CR3: 00000001a3fe6000 CR4: 00000000003506e0
    Oct 11 21:32:08 Impulse kernel: Call Trace:
    Oct 11 21:32:08 Impulse kernel: <TASK>
    Oct 11 21:32:08 Impulse kernel: __filemap_get_folio+0x98/0x1ff
    Oct 11 21:32:08 Impulse kernel: filemap_fault+0x6e/0x524
    Oct 11 21:32:08 Impulse kernel: __do_fault+0x30/0x6e
    Oct 11 21:32:08 Impulse kernel: __handle_mm_fault+0x9a5/0xc7d
    Oct 11 21:32:08 Impulse kernel: handle_mm_fault+0x113/0x1d7
    Oct 11 21:32:08 Impulse kernel: do_user_addr_fault+0x36a/0x514
    Oct 11 21:32:08 Impulse kernel: exc_page_fault+0xfc/0x11e
    Oct 11 21:32:08 Impulse kernel: asm_exc_page_fault+0x22/0x30
    Oct 11 21:32:08 Impulse kernel: RIP: 0033:0x1548dbc04741
    Oct 11 21:32:08 Impulse kernel: Code: 48 01 d0 eb 1b 0f 1f 40 00 f3 0f 1e fa 48 39 d1 0f 82 73 28 fc ff 0f 1f 00 f3 0f 1e fa 48 89 f8 48 83 fa 20 0f 82 af 00 00 00 <c5> fe 6f 06 48 83 fa 40 0f 87 3e 01 00 00 c5 fe 6f 4c 16 e0 c5 fe
    Oct 11 21:32:08 Impulse kernel: RSP: 002b:00001548d34f9808 EFLAGS: 00010202
    Oct 11 21:32:08 Impulse kernel: RAX: 000015480c010d30 RBX: 000015480c018418 RCX: 00001548d34f9a40
    Oct 11 21:32:08 Impulse kernel: RDX: 0000000000004000 RSI: 000015471f8cd50f RDI: 000015480c010d30
    Oct 11 21:32:08 Impulse kernel: RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000
    Oct 11 21:32:08 Impulse kernel: R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000000
    Oct 11 21:32:08 Impulse kernel: R13: 00001548d34f9ac0 R14: 0000000000000003 R15: 0000154814013d10
    Oct 11 21:32:08 Impulse kernel: </TASK>
    Oct 11 21:32:08 Impulse kernel: Modules linked in: xt_connmark xt_comment iptable_raw wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha xt_mark xt_nat xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs md_mod ip6table_filter ip6_tables iptable_filter ip_tables x_tables af_packet 8021q garp mrp bridge stp llc ipv6 mlx4_en mlx4_core igb i2c_algo_bit edac_mce_amd edac_core kvm_amd kvm wmi_bmof mxm_wmi asus_wmi_sensors crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel mpt3sas aesni_intel crypto_simd nvme cryptd ahci i2c_piix4 raid_class rapl k10temp i2c_core nvme_core ccp scsi_transport_sas libahci wmi button acpi_cpufreq unix [last unloaded: mlx4_core]
    Oct 11 21:32:08 Impulse kernel: CR2: 0000000000000056
    Oct 11 21:32:08 Impulse kernel: ---[ end trace 0000000000000000 ]---

     

    So they always start with this (end address will change):

     

    Oct 11 05:02:02 Cogsworth kernel: BUG: kernel NULL pointer dereference, address: 0000000000000076

     

    and always have this:

     

    Oct 11 05:02:02 Cogsworth kernel: Call Trace:
    Oct 11 05:02:02 Cogsworth kernel: <TASK>
    Oct 11 05:02:02 Cogsworth kernel: __filemap_get_folio+0x98/0x1ff

     

    The fact that it's happening to various users with very different hardware, both Intel and AMD, makes me think it's not a hardware/firmware issue, so we can try to find if they are running anything in common, these are the plugins I've found in common between the 4 or 5 cases found so far, these are some of the most used plugins so not surprising they are installed in all but it's also easy to rule them out:

     

    ca.backup2.plg - 2022.07.23  (Up to date)
    community.applications.plg - 2022.09.30  (Up to date)
    dynamix.active.streams.plg - 2020.06.17  (Up to date)
    file.activity.plg - 2022.08.19  (Up to date)
    fix.common.problems.plg - 2022.10.09  (Up to date)
    unassigned.devices.plg - 2022.10.03  (Up to date)
    unassigned.devices-plus.plg - 2022.08.19  (Up to date)

     

    So anyone having this issue try temporarily uninstalling/disabling these plugin to see if there's any difference.

    • Like 2
    • Upvote 1



    User Feedback

    Recommended Comments



    On 2/6/2023 at 3:47 PM, JesterEE said:

     

    Been running it continuously since my 11/18/2022 post. No issues.

     

     

    On 2/6/2023 at 3:54 PM, ShadyDeth said:

     

    I have had zero issues running this version since my posts were made.

     

    On 2/7/2023 at 5:08 PM, CiscoCoreX said:

    Hi,

     

    I have been running this version lscr.io/linuxserver/qbittorrent:libtorrentv1 since December 2022. Uptime over 35 days.
    For fun, I installed binhex latest bittorrent version, and the problem came back :(.

    Back to lscr.io/linuxserver/qbittorrent:libtorrentv1 

     

     

    19 hours ago, Shomil Saini said:

     

     

    Thanks everyone, I am migrating from binhex-deluge to linuxserver/deluge:2.1.1-r3-ls179 today. Fingers crossed.

     

    Cheers!

     

    Quick Update: Download speeds have dropped significantly from about 100Mbps to 40Mbps. Testing on Ubuntu latest torrent. Much slower on private trackers. Running via NordVPN. I have 3Gbps symmetrical fiber internet. Also, using ltConfig-2.0.0.egg with High Performance Seed Settings.

     

    Anyone have the same issue? I remember my speeds shooting up with the buggy update. I will take stability over speed but this is getting into turtle slow territory. I migth try transmission v4 that just dropped last night. Can't do qbit as it is not supported on the private tracker I use.

     

    Please feel free to provide your inputs.

    Cheers!

    Link to comment

    Hi Everyone,

    10 day Update: Running stable now, speed issues resolved after a restart.

    Using version: lscr.io/linuxserver/deluge:2.1.1-r3-ls179

    UNRAID Version: 6.11.5

     

    Cheers!

    • Like 1
    Link to comment
    8 minutes ago, sillstrybarn said:

    What version of qbit should I downgrade to? 

     

    Linuxserver provides an up to date version of qbittorrent with libtorrent V1, which will stop the issue.

     

    In the "Repository" section put: lscr.io/linuxserver/qbittorrent:libtorrentv1 

    Edited by ShadyDeth
    Link to comment
    13 minutes ago, ShadyDeth said:

     

    Linuxserver provides an up to date version of qbittorrent with libtorrent V1, which will stop the issue.

     

    In the "Repository" section put: lscr.io/linuxserver/qbittorrent:libtorrentv1 

    Thanks! 

     

    But would love to skip all the work with setting up another docker with VPN and privoxy and run qbit through that... But if that's what I have to do. 

    • Thanks 1
    Link to comment
    4 minutes ago, sillstrybarn said:

    Thanks! 

     

    But would love to skip all the work with setting up another docker with VPN and privoxy and run qbit through that... But if that's what I have to do. 

     

    FWIW I ended up just forcing my docker to stay on binhex/arch-qbittorrentvpn:4.3.9-2-01 and haven't had any issues

    Link to comment
    10 minutes ago, antiremy said:

     

    FWIW I ended up just forcing my docker to stay on binhex/arch-qbittorrentvpn:4.3.9-2-01 and haven't had any issues

    Maybe will try to rollback to that one first. Hoping it wont be a banned client on different sites...

    Link to comment

    Have been stay tuned on this issue and hopefully will have a fix for it...Using binhex/arch-qbittorrentvpn:4.3.9-2-01 as well.

    Link to comment

    I

    On 3/15/2023 at 4:15 AM, PzrrL said:

    Have been stay tuned on this issue and hopefully will have a fix for it...Using binhex/arch-qbittorrentvpn:4.3.9-2-01 as well.

    I went back to 4.3.9-2-01 and still have the same problem :( You're supposed to just type "binhex/arch-qbittorrentvpn:4.3.9-2-01" in the repository line, right?

    Link to comment
    3 minutes ago, Pjrezai said:

    You're supposed to just type "binhex/arch-qbittorrentvpn:4.3.9-2-01" in the repository line, right?

     

    Yes that is correct. I myself have switched from deluge to that version and It's been running fine for me.

     

    Have you ran diagnostics or logged your syslog to see if you're getting the same crash error or if it's something different causing the crash?

    Link to comment

    Well I'm giving it another shot, maybe it was just because when I downgraded I didn't reboot the server? I don't think that would have anything to do with it, but we will see.

    Link to comment

    This is definently the issue. Everything works but the webgui and DelugeVPN. 

    Had to SSH into unraid and run

     

    Quote

    /etc/rc.d/rc.docker restart

     

    to get the webgui to come back.

    Link to comment

    Thanks to @JorgeB, I just connected the dots on a server crash and Deluge on my 6.11.5 server.

     

    I see in the About screen in the Deluge GUI, it's at Deluge 2.1.1 with libtorrent 2.0.8.0.

     

    Are there any recommendations for binhex/arch-deluge users or do I need to start over with a different container?

    Link to comment
    9 hours ago, nraygun said:

    Thanks to @JorgeB, I just connected the dots on a server crash and Deluge on my 6.11.5 server.

     

    I see in the About screen in the Deluge GUI, it's at Deluge 2.1.1 with libtorrent 2.0.8.0.

     

    Are there any recommendations for binhex/arch-deluge users or do I need to start over with a different container?

    Never mind, I just setup qbittorrent 4.3.9-2-01.

     

    Now we wait.

    Link to comment

    arch-qbittorrentvpn:4.3.9-2-01 has been stable for quite a while now using the libtorrent 1.x library.

     

    Does anyone have an ETA on a patched libtorrent 2.x library?

    Link to comment

    Adding my logs here in case it is of any help to those tracking this issue.

     

    Background:

    Issues started with binhex-delugevpn docker roughly 1 week ago. Noticed call traces associated with the container in diagnostics. My docker containers update weekly so it was running with libtorrentv2 for a bit unless I'm mistaken.

     

    @binhex pointed this thread out to me. The issues here mirror my problems almost exactly.

     

    Interestingly, binhex-qbittorrentvpn was installed after deluge began locking up. So far it has not suffered the same fate despite running libtorrent 2.0.9. Downgrading binhex-delugevpn to libtorrentv1 does seem to have solved the issue.

     

     

    logs.zip

    Link to comment

    Well, I am late to the party. Not sure why I didn't experience this problem when the server was on 6.11.x, and the crashes only started after update to 6.12.x. My binhex-qbittorrentvpn container was running on latest tag and updated whenever there was a new one released.

     

    My host (6.12.2) GUI became unresponsive but all my docker services (except binhex-qbittorrentvpn) and VM were still functioning normal. After SSH in and kill the qbittorrent container process, the host GUI became available again. There were some error events logged in the syslog.

     

    Jul 9 01:58:04 Gandor kernel: CPU: 1 PID: 10534 Comm: qbittorrent-nox Tainted: P O 6.1.36-Unraid #1
    Jul 9 01:58:04 Gandor kernel: Call Trace:

     

    I tried switching over to hotio's qbittorrent-vpn docker, but I also saw related error to "qbittorrent-nox segfault" when stop/restart the container. I then switched over to hotio's qbittorrent-vpn "legacy" version, which uses libtorrent 1.2.x.

    I has not seen the segfault error message yet. I will keep this setup for the next month or so and report back any error if there is any.

    Edited by jfoxwu
    Link to comment

    For those wanting to stay on updated versions of bixhex releases, I see he did release libtorrentv1 versions of his apps. Change your repo's to the following.

     

    binhex/arch-qbittorrentvpn:libtorrentv1

     

    binhex/arch-delugevpn:libtorrentv1

     

    • Like 1
    Link to comment
    4 hours ago, ShadyDeth said:

    For those wanting to stay on updated versions of bixhex releases, I see he did release libtorrentv1 versions of his apps. Change your repo's to the following.

     

    binhex/arch-qbittorrentvpn:libtorrentv1

     

    binhex/arch-delugevpn:libtorrentv1

     

    Anybody using binhex/arch-qbittorrentvpn:libtorrentv1 with binhex/arch-radarr?

     

    I've been using binhex/arch-qbittorrentvpn:4.3.9-2-01 because of earlier issues with binhex/arch-radarr

     

    Link to comment

    A quick post on this, i see from the issue raised that several people are having zero crashes after updating to kernel 6.5, and as kernel 6.6 has just got the LTS approval i am hopeful unraid @SpencerJwill move to this new kernel in the future (6.13 perhaps?), which will finally put an end to this bug.


    https://github.com/arvidn/libtorrent/issues/6952#issuecomment-1719203595

    https://github.com/arvidn/libtorrent/issues/6952#issuecomment-1719224295
    https://github.com/arvidn/libtorrent/issues/6952#issuecomment-1770925098
    https://github.com/arvidn/libtorrent/issues/6952#issuecomment-1770936648

    • Like 1
    Link to comment

    I have been running binhex/arch-qbittorrentvpn:libtorrentv1 since suffering fairly frequent unraid crashes with the latest tag. It has been fine since the switchover. Should I still be running this or can I now move to binhex/arch-qbittorrentvpn:latest?

     

    Running 6.12.6

    Link to comment



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.