TheNyan

Members
 View Profile  See their activity

  • Posts

    10

  • Joined

  • Last visited

 Content Type 

Posts posted by TheNyan

    [Support] binhex - SABnzbdVPN

    in Docker Containers

    Posted

      

    On 11/18/2021 at 3:41 AM, francishefeng59 said:

    Hi, 

    After running a day, another problem came up. Once the internet connection was down or it lost connection after being idle for some time , it wouldn't re-establish connection even when the internet was up or tasks were imported waiting for being downloaded. I have to restart them manually. I've tried sabnzbdvpn and nzbgetvpn, all giving me the same issue. Privoxyvpn works ok. But I failed to find how to get them to work on privoxyvpn. Any idea?

     

    Part of the log after the internet is up:

    2021-11-18 10:44:31,537 DEBG 'start-script' stdout output:
    2021-11-18 10:44:31 TCP/UDP: Preserving recently used remote address: [AF_INET]23.19.87.116:1194
    2021-11-18 10:44:31 Socket Buffers: R=[212992->212992] S=[212992->212992]
    2021-11-18 10:44:31 UDP link local: (not bound)
    2021-11-18 10:44:31 UDP link remote: [AF_INET]23.19.87.116:1194

    2021-11-18 10:44:31,537 DEBG 'start-script' stdout output:
    2021-11-18 10:44:31 write UDP: Network is unreachable (code=101)
    2021-11-18 10:44:31 Network unreachable, restarting
    2021-11-18 10:44:31 SIGHUP[soft,network-unreachable] received, process restarting

    2021-11-18 10:44:31,538 DEBG 'start-script' stdout output:
    2021-11-18 10:44:31 OpenVPN 2.5.4 [git:makepkg/3f7a85b9aebe7be0+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Oct  5 2021
    2021-11-18 10:44:31 library versions: OpenSSL 1.1.1l  24 Aug 2021, LZO 2.10

    2021-11-18 10:44:31,538 DEBG 'start-script' stdout output:
    2021-11-18 10:44:31 Restart pause, 5 second(s)

     

    Hi everyone,

    i have the exact same problem. This was "fixed" by the user by routing through a privoxy container, but that cant be the only solution, right?

    After restarting the container, everything works fine (as long as downloads are active).

    If I add items to the queue after some idle time, it never reconnects. Just gets stuck in this restart loop.

    Anyone know how to fix this? It was 100% working like a year ago with the same setup.

    Thanks!

     

     

    APC UPS Network Management Card 2 SNMP

    in General Support

    Posted · Edited by TheNyan

    Well, did you enable modbus on the ups itself? I also did a firmware update on the ups with the apc software. Maybe thats needed.

    i have a apc smt750i and it works with the normal usb cable and modbus.

    You also have to disable and enable the ups deamon after changing that setting.

    My Servers Early Access Plugin

    in Announcements

    Posted

    Yup, same here (again)

    Uninstalled this after first having spin up problems (@squid linked my thread on page 18)

    Then reinstalled after it was fixed.

    Now its broken again.

    I´ll just stay away from this plugin until it isnt in beta anymore.

    But thats what beta is for, so all good.

    (SOLVED) 2 Disks wont spin down, others work fine? Whats going on?

    in General Support

    Posted · Edited by TheNyan

    Hey,

    im really confused. I have read that 6.9.2 has some spindown problems, but it used to work fine all the time from 6.9.2 release until now.

    Disk 1 (literally 100% empty) wont spin down at all. When i click spindown, it takes about 10 seconds and then it spins back up.

    Log shows this every time:

     

    Jun 9 19:23:44 Unraid emhttpd: spinning down /dev/sdd
    Jun 9 19:23:53 Unraid emhttpd: read SMART /dev/sdd

     

    Same thing happens with Disk 3, but 2 and 4 are fine and spin down normally.

    Why would spindown trigger smart? Is it really this "stupid"?

     

    Do i have to downgrade to 6.9.1? Cause its driving me mad.

     

    File activity shows nothing.

     

     

     

    EDIT:

    Uninstalled "my servers" after last update ruined it, problem fixed. Wasnt 6.9.2´s fault after all.