JohanSF

Members
  • Posts

    122
  • Joined

  • Last visited

Posts posted by JohanSF

  1. 16 hours ago, Mrtj18 said:

    Im not sure this would help but in my situation, any time I rest my tvheadend docker I will need to rest my router, and vice versa. Or I would get massive buffering issues.

     

    The only way I can do days or weeks without having to go through with this, is to try my best to NOT rest my router. Of I don't rest my router constantly, tvheadend will play just fine

    I never reset my router or otherwise have trouble with that portion.

    5 hours ago, bucky2076 said:

    I would be interested to see how these adapters are configured inside tvheadend.

    Seems like a networking problem (DNS, DHCP) or something similar. Also how the users are configured too... 

    I use hdhomerun... and never have to reboot or reset. Very solid.

     

    Here's the adapter configuration (status period marked cause I was googling and that might be of interest):
    chrome_2023-04-06_08-45-13.thumb.png.c8248ee73a49c464a911392d3c421e4e.png

    Stream profiles (don't know if the relevant one is selected here):

    chrome_2023-04-06_08-37-19.thumb.png.b7c510ee47a9322797718fbfe935e231.png

    User settings:
    image.thumb.png.82b43a5ee1e2c6e01d5ebf7ebdb6b2ab.pngimage.thumb.png.bf9e4ca5568578d6ab21fbde15355b9c.pngimage.thumb.png.4a185dbe594d2161e6f4f846fabdb5d8.png

     

  2. I constantly have to restart the tvheadend docker container when I want to watch TV.

    When I simply try to tune a channel I usually get this:
    image.png.ee7f2bb0b7b6c2f6c40f80639a34c2f8.png

    tvheadend docker log when it doesn't work: https://pastebin.com/hU2e3rDc

     

    After restarting the tvheadend docker container it works perfectly until a while has passed with no watching, and it will need a restart again.

    tvheadend docker log while watching a stream: https://pastebin.com/B4GUSPyS

    DVB Driver Plugin:
    image.thumb.png.cbb1c3054d7699b3bbcd5c721f16be3e.png

     

    Container edit page:
    image.thumb.png.f09f6912d1d19c11db6faae5b1111150.png

     

    My device is a Hauppauge WinTV-quadHD and I'm using antennas container to route tvheadend:
    image.png.4a714fa623f5c2f625151e36034980bb.png

     

    Please let me know if there is anymore information I can post to help solve this issue. It is a huge pain to deal with this on a daily basis.

  3. My binhex-rtorrentvpn using PIA stops and starts every night when the mover runs. For the last couple of months it has been random if it was running when I woke up or not.

    For example I just restarted right now and get this:
    image.png.6f0ec63cc9a49060153445ef497951fc.png

    I can restart the container a minute later and then it will work - it seems completely random and this has been going on for more than a month now. Just haven't had the time to properly deal with it :( Now from reading your comments it seems like I'm not the only one.

    • Like 1
  4. Search has been broken for quite a while. Typing anything into the instant search field throws this error and the search does not execute:

    image.png.84f5e0a30f532b87b7ebf20e84635686.png

     

    I googled and found this:

    https://github.com/Novik/ruTorrent/issues/1989

     

    Maybe something needs to be updated in the container, or is this just on my end that I need to do something?
    Recreating the container did not fix it.

    Tried manually updating to the newer https://github.com/Micdu70/rutorrent-instantsearch, the one in the folder on my system was from 2010, but this did also not fix it.

    EDIT: It seems that the manual updating to the newer instantsearch plugin worked! :) maybe it was a cache issue after updating it.

  5. Hi all, I just installed two brand new drives to my LSI SAS2008 controller, but I'm not seeing them in unRaid. I can feel them running with the touch of a finger on the physical drives so it should not be a connection issue.

     

    The drives are both this model: WESTERN DIGITAL ULTRSTAR DC HC550 18TB 3.5 SAS SE 512MB 7200 WUH721818AL5204 INT

    This is the cable: https://www.av-cables.dk/diverse-sas-kabler/mini-sas-kabel-sff-8087-til-4-x-sas-29pin-sff8482-0-75.html

     

    I have searched both google and the forum here, and found this, but I am not sure if it is relevant for my case:

     

    Here you can see the card while booting:

    IMG_20200715_221723.thumb.jpg.4736f4f3d6995b1344a7da569814f6d8.jpg

     

    IMG_20200715_222133.thumb.jpg.ed2146ae9f80f051eadbfa7d53a6dc11.jpg

     

    The settings:

    JPEG_20200715_222319.thumb.jpg.7748de984469ba910abc1a65588a50bf.jpg

     

    SAS Topology (I tried with the cable plugged in to either SAS port:

    JPEG_20200715_223423.thumb.jpg.2368c8f538af047ad6116dabf2689e0c.jpg

     

    I use this SAS cable and it definitely feels high quality - my PSU is the RM 550x powering the drives via molex with no conversion:

    IMG_20200715_171046.thumb.jpg.adbdefafa06f82f3d8c76369e485e4c7.jpg

     

    Can you help me troubleshoot it?

     

    Kind Regards, Johan

    hal9000-diagnostics-20200715-2000.zip

  6. Yo, I am here because android apps nzb360 and Transdroid won't connect anymore after the last update.

     

    I saw what you changed and tried commenting out the two new lines. Everything works now except nzb360 still won't connect locally.

     

    I am not sure if I am even in the scope of people that can benefit from what you changed (and I don't quite understand it), as my apps were set to connect to a subdomain reverse proxy with basic auth set in the Letsencrypt docker container by Linuxserver, and locally to the localip:9080 with /RPC2 endpoint and without authentication.

  7. The largest one that I can see is 75 mb, that is the lidarr container. I remember that one was running with Debug log level and I had recently started using it more. But there are of course quite a lot that I cannot see.

  8. Most of them give "cannot read directory" "input/output error".
    Can't screenshot it right now as I'm not home though.

    For "--log-opt max-size=50m --log-opt max-file=1", is something missing in this command? those are only options.

  9. Hey GilbN, I searched about how to do that and found this way to increase the log size:

    However, I still get the docker error.
    I guess I will have to delete my docker image and do this:

    Unless someone here has another suggestion before I do that?

  10. To the devs:

    You can fix the Reverse Proxy issue by editing the file /etc/services.d/duplicati/run to the following (i.e. adding --webservice-allowed-hostnames=*):

    #!/usr/bin/with-contenv bash
    
    cd /app/duplicati || exit
    
     exec \
        s6-setuidgid abc mono Duplicati.Server.exe \
        --webservice-interface=any --server-datafolder=/config --webservice-allowed-hostnames=*

    See https://github.com/linuxserver/docker-duplicati/blob/master/root/etc/services.d/duplicati/run

    For now I use a mounted run file with this change.

    Edit: The best solution is to make it an environment variable in the docker container.

  11. I need access to put an asterisk in the the Hostnames option to make my reverse proxy working again.
    What I need looks like this:
    image.thumb.png.e2b11aee228f0291a128ed072fe10825.png

     

    But that is only possible if I can visit Duplicati via 127.0.0.1, how do I do that when it is inside this docker container?

    This means that as of now I only see this:
    image.thumb.png.ec921f14ecc42a3798bc3239bcc0d921.png

  12. Thank you for this.

     

    Yet doing 'ulimit -n 65536' on the host, I still get the error:

    max file descriptors [40960] for elasticsearch process is too low, increase to at least [65536]

    My guess now is that I have to do that command in the elasticsearch container, how can I pass it in the edit section of the docker container?


    EDIT: Add '--ulimit nofile=65536:65536' in the Extra Parameters field when you edit the docker container.

    • Like 1