Jomo

Members
  • Posts

    15
  • Joined

  • Last visited

Posts posted by Jomo

  1. I am completely lost. I started getting errors with Sonarr and Radarr after my server ran a backup and update last night. I am assuming it has to do with the stuff in the recommended post but I'm not sure especially since it sounds like I should have had problems after restart/update last week... Anyway, the issues I am having:

    1) binhex-delugevpn says "version: not available"

    2)Sonarr give errors "Unable to communicate with deluge. Unable to write data to the transport connection: The socket has been shut down."
    3)Radarr gives error "Unable to communicate with Deluge. An error occurred while sending the request. Unable to read data from the transport connection: Connection reset by peer.: '<LAN Deluge ip>/json'

    4)None of the indexers work for Sonarr or Radarr
    5)NZBHydra, every indexer says "Error while communicating with indexer <indexer>. Server returned: java.net.SocketException: Connection reset" (Note: honestly this stuff is so complicated and it has been a while since I've set it up. I have no idea how any of it works anymore. I am not even sure if NZBHydra is even connected to the VPN and if so where/how that was set up)

    I tried fixing according to the posts: I edited binhex-deluge, the line that says "VPN_INPUT_PORTS" has value: "8989, 7878"
    Where 8989 and 7878 are the ports for Sonarr and Radarr are on. I tried also going through sonarr and radarr and editing "settings > Download Clients > Host" and changing it to "localhost" but then when I hit "test" I get an error  "Unable to connect" . Also note that if I leave it as my LAN Ip instead of localhost, it gives an error "Unable to connect to Deluge"

    EDIT:

    Looks like some how privoxy got turned off. Which, tbh, I am not 100% certain I had it on. But I followed SpaceInvdader's video in the past and it said to turn it on so I assume that is what I had. Turning it on fixed Hydra's issue and also changed the errors I get in Sonarr/Radarr. Now it gives a timeout instead of "Unable to connect to Deluge" when I test with LAN ip in the host.

    EDIT 2:
    I have now added NZBHydra's, SABnzbd's, and jackett's port to the "VPN_OUTPUT_PORTS", (so that is now equal to "8080,5076,9117"). That seems to have fixed the issue with the indexers not working with Sonarr and Radarr. Additionally inside settings -> download client, I changed the host from the  192.... ip to the 172.... ip for Deluge (but NOT for SAB, that is still the 192... address) That has caused both Sonarr and Radarr to test successful for deluge. So now the only remaining problem that I know of is the "not available" version for delugeVPN. But I mean, at the same time, I basically button mashed through this thing. I have no idea why any of that did anything or if there are other issues I am missing. I don't understand at all.

    EDIT 3:
    I read up on the FAQ more and that combined with what I got working, I think I understand now. Seems I ended up basically doing the solution given in Q27. Accessed LAN applications from something going through the VPN by adding those application ports to the VPN_OUTPUT_PORTS. I suppose I could have gotten deluge to work without changing to 172 in download clients by simply including it in the export list too. (Though I have no idea why the change to 172 worked also). I see now that I COULD have used the solution in Q26 and simply added the 192 address to ignore list under proxy. And I also didn't need to add  anything to the import or output list. (And indeed, I changed to this and it works)

    I do still have the problem of it showing as not available for version number. Additionally, I still don't really know why hydra wasn't working when privoxy was off, I can't seem to find anything that is making it go through it. ALSO it seems to me that I don't actually have anything using the VPN proxy except the deluge itself, and I wonder if I should have more stuff going through it, like SAB and if so, how...

     

    EDIT 4:
    It no longer says version: not available. I dunno why, seems to have fixed during one of the restarts when I removed input and outputs in favor of using the ignore address in the proxy settings for Sonarr/Radarr solution.

     

    EDIT 5:
    Ah ha, and now I have found where Hydra was connected. Hidden "advanced" setting, where Proxy is set. And I've set jackett to go through it now too.

  2. On 10/30/2020 at 8:30 AM, DZMM said:

    Thanks deleted.

     

    I'm going to go and read up first on how the auth thing works again and implement from scratch.  I did this ages ago following an online guide and I can't remember how I did it, so I guess it's time for a refresher.

    Did you figure this out? I am having the same problem

  3. This is what I got:

    Note that since yesterday, I unassigned the drive, ran the parity sync with my other parity drive just fine, and then I started a preclear of this drive to see if that got any errors too, so far no but it is still on the preread (~19 hours later, 91% done...)

    Quote

    smartctl 7.0 2018-12-30 r4883 [x86_64-linux-4.19.41-Unraid] (local build)
    Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org

    === START OF INFORMATION SECTION ===
    Vendor:               HITACHI
    Product:              H7230AS60SUN3.0T
    Revision:             A6C0
    Compliance:           SPC-4
    User Capacity:        3,000,592,982,016 bytes [3.00 TB]
    Logical block size:   512 bytes
    Rotation Rate:        7200 rpm
    Form Factor:          3.5 inches
    Logical Unit id:      0x5000cca03e2602ec
    Serial number:        001237RNX1ND        YVGNX1ND
    Device type:          disk
    Transport protocol:   SAS (SPL-3)
    Local Time is:        Tue Jun 25 09:23:33 2019 EDT
    SMART support is:     Available - device has SMART capability.
    SMART support is:     Enabled
    Temperature Warning:  Enabled
    Read Cache is:        Enabled
    Writeback Cache is:   Disabled

    === START OF READ SMART DATA SECTION ===
    SMART Health Status: OK

    Current Drive Temperature:     33 C
    Drive Trip Temperature:        85 C

    Manufactured in week 37 of year 2012
    Specified cycle count over device lifetime:  50000
    Accumulated start-stop cycles:  63
    Specified load-unload count over device lifetime:  600000
    Accumulated load-unload cycles:  1878
    Elements in grown defect list: 1073

    Vendor (Seagate Cache) information
      Blocks sent to initiator = 22452280036950016

    Error counter log:
               Errors Corrected by           Total   Correction     Gigabytes    Total
                   ECC          rereads/    errors   algorithm      processed    uncorrected
               fast | delayed   rewrites  corrected  invocations   [10^9 bytes]  errors
    read:          0   986464         0    986464   22970810     776960.878           2
    write:         0 10885558         0  10885558    3123961     244165.631           0
    verify:        0        0         0         0   19274899         35.033           0

    Non-medium error count:        0

    SMART Self-test log
    Num  Test              Status                 segment  LifeTime  LBA_first_err [SK ASC ASQ]
         Description                              number   (hours)
    # 1  Background long   Completed                   -   43862                 - [-   -    -]

    Long (extended) Self-test duration: 27182 seconds [453.0 minutes]

    Background scan results log
      Status: scan is active
        Accumulated power on time, hours:minutes 43878:57 [2632737 minutes]
        Number of background scans performed: 266,  scan progress: 91.56%
        Number of background medium scans performed: 266

       #  when        lba(hex)    [sk,asc,ascq]    reassign_status
       1 43807:33  000000015198c1d1  [3,11,0]   Require Write or Reassign Blocks command
       2 43720:18  00000000e9fbe684  [3,11,0]   Reassigned by app, has valid data
       3 43720:18  00000000e9fbde52  [3,11,0]   Reassigned by app, has valid data

    Protocol Specific port log page for SAS SSP
    relative target port id = 1
      generation code = 20
      number of phys = 1
      phy identifier = 0
        attached device type: SAS or SATA device
        attached reason: loss of dword synchronization
        reason: unknown
        negotiated logical link rate: phy enabled; 6 Gbps
        attached initiator port: ssp=1 stp=1 smp=1
        attached target port: ssp=0 stp=0 smp=0
        SAS address = 0x5000cca03e2602ed
        attached SAS address = 0x500304800020a127
        attached phy identifier = 7
        Invalid DWORD count = 1388
        Running disparity error count = 1311
        Loss of DWORD synchronization = 344
        Phy reset problem = 0
        Phy event descriptors:
         Invalid word count: 1388
         Running disparity error count: 1311
         Loss of dword synchronization count: 344
         Phy reset problem count: 0
    relative target port id = 2
      generation code = 20
      number of phys = 1
      phy identifier = 1
        attached device type: no device attached
        attached reason: unknown
        reason: power on
        negotiated logical link rate: phy enabled; unknown
        attached initiator port: ssp=0 stp=0 smp=0
        attached target port: ssp=0 stp=0 smp=0
        SAS address = 0x5000cca03e2602ee
        attached SAS address = 0x0
        attached phy identifier = 0
        Invalid DWORD count = 0
        Running disparity error count = 0
        Loss of DWORD synchronization = 0
        Phy reset problem = 0
        Phy event descriptors:
         Invalid word count: 0
         Running disparity error count: 0
         Loss of dword synchronization count: 0
         Phy reset problem count: 0

     

  4. Now that it is about 70% done, the speed has drastically dropped again.

     

    Also, I am unable to check the results of the SMART test for the drive with errors, it is just spinning at "Last SMART test results".

    Guessing at this point I just need to remove the drive and just deal with one parity drive for now.