binhex

Community Developer
  • Posts

    7880
  • Joined

  • Last visited

  • Days Won

    37

Report Comments posted by binhex

  1. 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
  2. 1 hour ago, sundown said:

    Looks like you have a new build of qbittorrent out on the same day that qbittorrent themselves released v4.5.0

    no coincidence, my builds are auto triggered by upstream releases.

     

    1 hour ago, sundown said:

    Assuming your latest build is leveraging their 4.5 release, should those of us on your release be relatively secure in reverting back to "latest"?

    no, the upstream build is still using libtorrent 2.x as can be seen from the qbittorrent web ui:-

    image.png.30f90251a1444f0a35d2587252ac54ec.png

  3. An interesting read regards THP, which looks to be triggering the crash:- https://blog.nelhage.com/post/transparent-hugepages/

     

    if you are feeling brave then you can try the following to disable THP which SHOUILD then prevent the crash without the need to downgrade libtorrent:-

     

    drop to 'terminal' for unraid (not the containers console) and copy and paste the following:-

     

    echo '# temporarily disable hugepages to prevent libtorrent crash with unraid 6.11.x' >> /boot/config/go
    echo 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' >> /boot/config/go
    echo 'echo never > /sys/kernel/mm/transparent_hugepage/defrag' >> /boot/config/go

    then reboot your system, and then run the following to confirm THP is disabled:-

     

    grep -i HugePages_Total /proc/meminfo # output should be 0
    cat /proc/sys/vm/nr_hugepages # output should be 0

     

    from the article linked above this MAY actually increase your performance!, or at the very worst you may see a 10% drop in performance (depends on usage).

     

    keep in mind the above is a temporary hack, libtorrent/kernel/app will no doubt resolve this issue at some point, im simply posting this as a workaround for now, so you will then need to remove the above from your go file and reboot to reverse this hack.

    • Like 3
    • Thanks 5
    • Upvote 2
  4. 2 minutes ago, sundown said:

    I didn't catch the older version of qbittorrent reset my cache directory and moved over 2TB off of long term storage and on to NVME cache drives, that I had to then move back..

    indeed, take heed of my warning posted earlier above:-

    WARNING you may see loss of some configuration when rolling back due to changes in qbittorrent between v4.3.x and 4.4.x

    it was the same issue going from 4.3.x to 4.4.x, loss of some (not all) configuration.

  5. 17 minutes ago, Altwazar said:

    Maybe this is some bug in kernel that exposed by libtorrent.

    you might be onto something there.

     

    17 minutes ago, Altwazar said:

    Swapped to entirely different hardware (cpu,motherboard,memory,hdd) and only recompiling qbittorrent with 1.2 version solved this.

    interesting!.

     

    just as a fyi i am drinking my own champagne here so i also do use qbittorrentvpn (latest) on unraid 6.11.3, and although i did get one crash earlier on its been rock solid for me since, so its not triggering the bug for all users, perhaps based on torrent load perhaps or hardware configuration.

  6. 1 hour ago, JesterEE said:

    and it's an application error rather than a kernel error!

    question is though, if it really is purely an application error (libtorrent bug) then why is the crash not seen in unraid 6.9.x?, i'm not saying its unrelated to libtorrent, just saying it could still be related to kernel/docker changes that are making the libtorrent bug more pronounced - keep in mind qbittorrent has been using libtorrent 2.x for my image since Jan 10th 2022, no reported issues until 6.111.x series came out.

     

    qbittorrentvpn users - if you are using my image and are seeing the crash then try rolling back to tagged image '4.3.9-2-01' this will be using libtorrent 1.x - WARNING you may see loss of some configuration when rolling back due to changes in qbittorrent between v4.3.x and 4.4.x

     

    • Like 1
  7. Now reached the heady heights of 14 days uptime, no crashes since the below changes:-

    https://forums.unraid.net/bug-reports/stable-releases/crashes-since-updating-to-v611x-r2153/?do=findComment&comment=21225

     

    i do torrent a fair bit (probably shifted around 1.5TB of data), 2 vm's running and actively used and i have not changed my daily usage of the server, so for now at least it SEEMS stable for me, time will tell i guess.

     

    p.s. I am not saying the above is THE fix, simply that it works for MY system.

    • Like 1
  8. On 10/12/2022 at 4:44 PM, binhex said:

    As you can probably see from my list of plugins i only have the following installed from your list of commonly installed plugins, which does shorten the list quite a lot, although i am only a metric of 1 so far so take it with a large pinch of salt 🙂


    community.applications.plg - 2022.09.30 (Up to date)
    unassigned.devices.plg - 2022.10.03 (Up to date)
    unassigned.devices-plus.plg - 2022.08.19 (Up to date)

     

    I am loathed to uninstall CA for obvious reasons, but i have nuked UD, so we shall see what happens.

     

    On 10/13/2022 at 11:14 AM, binhex said:

    i was using macvlan for one docker container, but have switched it to ipvlan now.

     

    @ich777 thanks for the pm.

    no crashes for me since doing the above, uptime 4 days 20 hours and counting, so MAYBE (a big maybe) it is related to Unassigned Devices (uninstalled after first (and only) crash as mentioned above), luckily for me i don't rely on UD, i only had it installed as i was previously playing with pre-clear on a USB connected drive.

  9. As you can probably see from my list of plugins i only have the following installed from your list of commonly installed plugins, which does shorten the list quite a lot, although i am only a metric of 1 so far so take it with a large pinch of salt 🙂


    community.applications.plg - 2022.09.30 (Up to date)
    unassigned.devices.plg - 2022.10.03 (Up to date)
    unassigned.devices-plus.plg - 2022.08.19 (Up to date)

     

    I am loathed to uninstall CA for obvious reasons, but i have nuked UD, so we shall see what happens.

  10. Add me to the list of users affected by this, i was running 6.9.2 without issue for months at a time, i took the plunge on release of 6.11.1 and upgraded on 10th Oct, its now 12th Oct and i have identical symptoms to this post (apart from NO hardware changes for me in years):- https://forums.unraid.net/topic/129456-unraid-kernel-crashing-after-611-upgrade/

     

    Sadly for me, even attempting to generate diagnostics from the cli (web ui not accessible) did not complete, leaving me with no option but to attempt a soft reboot, which hung so hard reset it is. This then allowed me access to the web ui and i have dumped the list of plugins on my system (see below).

     

    hardware spec
    Mobo:- ASUS ROG STRIX X470-F Gaming
    PSU:- Seasonic SSR-750PD2 Prime Ultra 750 W
    CPU:- AMD 3900X
    RAM:- 2 x Corsair CMK32GX4M2A2666C16 (64GB)
    Cache (appdata/vm):- Samsung 970 EVO Plus 1 TB (NVME)
    Cache (downloads):- Samsung 500 GB 860 EVO
    GPU:- Nvidia Quadro P2000 (Plex duties)
    RAID Controllers:- 2 x IBM M1015 (cross flashed to IT mode)

     

    plugins installed

    CA Auto Turbo Write Mode
    Support Thread    Andrew Zawadzki    2022.09.16      up-to-date    

    CA Auto Update Applications
    Support Thread    Andrew Zawadzki    2021.09.24      up-to-date    

    Community ApplicationsSupport Thread
    Andrew Zawadzki    2022.09.30      up-to-date    

    ** Dynamix Auto Fan Control
    Support Thread    Bergware/gfjardim    2022.09.16      up-to-date    

    Dynamix Cache Directories
    Support Thread    Bergware    2020.08.03      up-to-date    

    GPU Statistics
    Support Thread    b3rs3rk    2022.02.22      up-to-date    

    ** Nerd Tools
    Support Thread    dmacias72    2021.08.11      up-to-date    

    Nvidia Driver
    Support Thread    ich777    2022.10.05      up-to-date    

    ** Unassigned Devices
    Support Thread    dlandon    2022.10.03      up-to-date    

    ** Unassigned Devices Plus
    Support Thread    dlandon    2022.08.19      up-to-date 

     

     ** = now removed in hope of better stability.

     

    I guess i will let you know in a few days whether the system is still up or crashed again, if crashed i shall be doing a binary split on the plugins still installed.