omv5 (armbian) freezes when SABnzbd (docker) is unraring downloads

  • Hi.

    After i suceed in installing SABnzbd, omv5 now seems to have the same issue i experienced with dietpi before.


    When SABnzbd is unraring the downloaded files, the server freezes.
    Kodi is not able to playback files from the server when unraring starts.
    Kodi does not even find the shared nfs-folder from the server.


    omv5 does not crash. i mean i can login to the web-ui.

    In system information i can see, that the usages of cpu (4-5%) and ram (16-17% from 3,55GB). Looks ok.


    Unfortunately the performance statistics graphics are empty.
    Disks or File systems show only "Loading".


    syslogs look like this:

    Any ideas?

  • Any ideas?

    If your load is that high, it is probably doing a multi-threaded unrar and the storage it is doing that on is either slow or very busy. Faster storage or a faster server is about the only that will fix that.

    omv 5.5.17-3 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • If your load is that high, it is probably doing a multi-threaded unrar and the storage it is doing that on is either slow or very busy. Faster storage or a faster server is about the only that will fix that.

    i do not agree.

    i use an odroid n2 that is better than the odroid i had before and with that one before - i forget the name - i never had those issues.

    Same software, same external usb-hdd.


    Why do you mean "load is high"?
    The numbers that i posted are not that high?

  • i do not agree.

    Well, I gave you an educated guess based the information you gave me and 22 years as a Linux admin. A load of 18.2 on a system that has 6 cores (really only 4 usable max - I have an N2), means there are either lots of processes asking for cpu time and/or the I/O wait on the storage.

    Why do you mean "load is high"?

    Your 1 min load average is 18. Unless you have 18 cpus and fast storage, your load is high.

    The numbers that i posted are not that high?

    Syslog tells me otherwise. cpu percentage and ram use are only part of load on Linux.

    omv 5.5.17-3 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • Sorry, sounded more disrespectful than i meant it.
    ;)

    Ok, i did not see the load of 18.2 in the syslog?

    Good that i accidentally copied this part...
    :)

    But if you have an odroid n2, don't you think it should handle a little bit unraring?
    In htop there were only one core active with around 16%.


    Kodi does not find the nfs-shared-folder anymore.
    I rebooted but there is still possibility to access the nfs-shares.

  • But if you have an odroid n2, don't you think it should handle a little bit unraring?

    Yep. Are you sure it is unraring to and from the usb hard drive? If you open another session while it is unraring, what is the value of wa in the line of top that looks like:


    %Cpu(s): 1.7 us, 0.7 sy, 0.0 ni, 97.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st

    omv 5.5.17-3 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • Yep. Are you sure it is unraring to and from the usb hard drive? If you open another session while it is unraring, what is the value of wa in the line of top that looks like:


    %Cpu(s): 1.7 us, 0.7 sy, 0.0 ni, 97.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st

    First of all: THANK YOU FOR YOUR SUPPORT1


    I skipped to nzbget to see if the new SABnzbd is maybe the problem but had the same issues.


    The wa is around 32 while unraring.

  • Ok. Can you tell me more about this?
    "wa" means "waiting for I/O" so it is an issue with the external usb-disk?


    EDIT:
    I mentioned that the wa=32 does not change much, also when the unraring has ended.

    Another issue i have is, that the reboot does not work.
    I have to draw the powercable.
    Now - after you mentioned the I/O - i draw the USB-cable from the external hdd and the reboot happened!

    So it seems to be the external usb-hdd.

  • I watched the unraring process again:

    At the beginning unraring works with only 2-3 wa, but then the unrar-process in iotop diappears and the wa goes up to 31-33.

    Seems to crash or freeze here.
    The wa stays there and does not change anymore.


    What can i do?

  • "wa" means "waiting for I/O" so it is an issue with the external usb-disk?

    It might be. Do you see any drive errors in dmesg?


    What can i do?

    Try a different drive?

    omv 5.5.17-3 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!