Jump to content

Cpt. Chaz

Members
  • Posts

    220
  • Joined

  • Last visited

Posts posted by Cpt. Chaz

  1. For anyone that finds this post in the future, i solved my issue too thanks to backups of my flash drive.

     

    • rebuild docker image, then with the service disabled,
    • navigate to backups -> /config/plugins/dockerMan/templates-user 
    • then copy the docker xml's from backup location to the actual flash drive -> /config/plugins/dockerMan/templates-user
    • Then start docker service, go to CA, previously installed apps and the list should be repopulated for reinstallation
    • Like 1
  2. On 1/30/2020 at 10:32 AM, Squid said:

    3 reasons for nothing to show up under previous apps

     

    - Docker isn't enabled (There should be a big banner across the top of the screen)

    - Everything is already installed

    - You've also deleted the contents of /config/plugins/dockerMan/templates-user on the flash drive

    @Squid I may be in this boat - what happens if one somehow deleted the dockerman templates-user?

     

    I've already tried restoring from CA-AppData Backup, and no luck. I have all the appdata still in tact. i've deleted and tried recreating the docker image, still no luck. happy to post logs if necessary. Thanks in advance

  3. On 3/30/2020 at 5:46 PM, strayedcables said:

    Decided to go the Seedbox route, using ultraseedbox that comes with OpenVPN, but it sounds like i dont really need to set up a VPN at all for seedboxing

    that's correct, no vpn necessary. 

     

    which plan did you go with, and what client did you decide to use? i've also got an ultraseedbox and really like it so far.

  4. I know eth0 is down, that’s what I’m trying to resolve. They’re bonded now because it just happened to be one of the things I tried during troubleshooting. It didn’t resolve the eth0 problem, I just didn’t want to stop the array again to undo it since it didn’t seem to make a difference either way. But even if the nics aren’t bonded, lan still works, eth0 shows down. 
     

    if you’d like to see screenshots or logs of different configurations here, or even a specific one, I’d be happy to oblige. Thanks for the time 

  5. If sab is writing to the array instead of cache, that's most likely the source of the problem. Are you using sonarr/radarr too? If so, have sab set to download to cache, then sonarr/radarr will move the completed files to the array, keeping the cache clear.

     

    If you're not using sonarr/radarr, is there any reason you can't clear the cache using Mover more often? for example, sab writes to cache, mover is invoked say, every 8 hours, then files are moved to the array.

     

    would either of these work?

  6. Hello all! Thanks for taking the time to read here - with the lockdown happening, I figured this was a good time to do some maintenance.

     

    My issue is not high priority per se, as i'm not really having any operational issues here (although i couldn't get pfsense vm working and i suspect this is the cause). On my network settings, i'm getting an error in red at the bottom of the page:

     

    Interface Ethernet Port 0 is down. Check cable!

     

    This all started after i switched machines last year, i went from a desktop sff pc to a Dell R720 server, so essentially went from only have 1 nic to 4. On the new r720, it came with a SAS HBA assigned to ports 0,1, while regular 1gb ethernet is assigned to ports 2,3. I had gone into the idrac settings on the dell itself and tried to disable the sas controller, hoping unraid would just assign port 0 to the ethernet port i'm actually using. This didn't work though. Currently, i have ethernet plugged into port 2 with seemingly full functionality, minus the error.

     

    I had gone into the network settings a while back (somewhere around 6.7.9 and 6.8) and tried troubleshooting with different settings and never had any luck resolving it. i've attached screen shots and logs, if anyone cares to take a look, would be much appreciated getting this sorted. Thanks in advance!

     

    kal-el-diagnostics-20200325-1018.zip

    Interface eth0.png

    Interface eth1-3.png

    Interface Rules and Routes.png

  7. i ran nord for ages on the delugevpn docker per SI's video. but you should know, nord does not support port forwarding, so while your downloads will work fine, you won't be able to seed/upload with nord. i finally switched to PIA using one of the port forwarding config files, and been working fine ever since.

    • Like 1
  8. On 3/16/2020 at 11:30 AM, Cpt. Chaz said:

    @binhex Ok. according to nord's website, they don't support this. unless you know a way around it, looks like i may be looking for a new provider. unfortunate, because i've been loving the new nordlynx (wireguard) for adblocking on my phone.

    threw some PIA config files in the docker, and i'm off to the races.

    • Like 1
  9. On 3/13/2020 at 4:29 PM, binhex said:

    No port forwarding on nordvpn will be your issue.

    Sent from my CLT-L09 using Tapatalk
     

    @binhex Ok. according to nord's website, they don't support this. unless you know a way around it, looks like i may be looking for a new provider. unfortunate, because i've been loving the new nordlynx (wireguard) for adblocking on my phone.

  10. has anyone else had any trouble seeding torrents using nordvpn with this container? i have no issues downloading, but for whatever reason my seeds will only go for kb/s for roughly a minute or less, if at all. i have all the original files sitting in completed download folder just fine. webui not reporting any errors. I do have upnp enabled in my apple router.

  11. is it possible this nginx error could be related to the same one im experiencing? erros look different, but nginx seems to be a common denominator. i havent found a solution yet either. could try rolling back to 6.7 and see... but i never had any problems before 6.8 either, and no other major changes since the upgrade aside from wireguard install / use. 

     

     

  12. ok, nope, that wasn't the problem after all.

     

    server locked up again. wasn't able to use the diagnostic tool to capture the syslog, used terminal again to capture "syslog.txt" and i also ran a short tail and exported it "tail syslog.txt". Attached below.

     

    The tail output was running with docker service disabled, so this should disable nginx, right? I could try restarting in safe mode, but i don't know how to reproduce this problem. It just happened out of the blue again. i'm seeing

    # Jan 17 16:27:00 Kal-El nginx: 2020/01/17 16:27:00 [crit] 4850#4850: ngx_slab_alloc() failed: no memory
    # Jan 17 16:27:00 Kal-El nginx: 2020/01/17 16:27:00 [error] 4850#4850: shpool alloc failed
    # Jan 17 16:27:00 Kal-El nginx: 2020/01/17 16:27:00 [error] 4850#4850: nchan: Out of shared memory while allocating channel /var. Increase nchan_max_reserved_memory.

    over and over. nginx should be disabled with letsencrypt docker closed, right? and out of shared memory? getting out of my depth here, but with 192gb of ram, only ever getting up to 7-8% utilization with no more than i have running, seems strange. it says to "increase nchan_max_reserved_memory". should i do that? if so, how?

     

    It also seems i'm not alone, but they had no resolution it looks like here.

     

    edit: i also increased vm dirty ratios a few days ago per this and it obviously made no difference.

    tail syslog.txt.zip syslog.txt.zip

  13. On 1/12/2020 at 7:05 PM, Cpt. Chaz said:

    PS radarr V3 May have file analysis functionality which would render this whole exercise moot. Might also be worth looking into. 

     

    Couldn't stop thinking about this, so I tested it. Radarr V3 (aphrodite) does do a media file analysis unlike V2. Upgrading would solve the naming / upgrade issue. I'm still testing V3 alongside V2 before i fully commit because i've heard it's still buggy, but tbh so far it's working surprisingly well for me.

  14. Thanks guys, i'll give those a shot and report back.

     

    Off topic for a second, but, @johnnie.black i feel compelled to tell you how much i like your handle and avatar. not sure if you're familiar with Christopher Hitchens or not, but you might find this short youtube clip of general interest. "The best blended scotch in the history of the world..."

  15. Unraid 6.8.0

     

    Hi guys,

     

    This past saturday, out of the blue, i noticed the dashboard on my server wasn't showing any cpu stats... then i noticed none of my docker stats were working, then realized my syslog was at 100%. The whole system seemed very slow and unresponsive. Fix Common Problems showed nothing out of sorts, and the dockers themselves (plex for example) all seemed to be working fine. I tried to use the diagnostics zip tool and even that wouldn't work - unresponsive. I used terminal to capture the syslog to flash manually - the wiki said it would be ready to post to forums using this method, but if it's not anonymized let me know and i'll take it down straight away. this log file is below, titled "syslog-2020-01-11.zip". Clean reboot, everything seemed to return to normal.

     

    Fast forward a couple days to just a few short moments ago, i logged in to find my syslog back up to 77%. FCP still not showing any problems. diagnostic zip tool worked this time, so i snagged the logs and have attached them below as well. file is "kal-el-diagnostics-20200113-1320.zip". I glanced at the logs from today and saw a few red lines, but unfortunately the rest is greek to me. 

     

    I have a couple of suspicions... i installed folding@home last week, even with cpu and memory parameters, it caused problems so i uninstalled (no good deed... lol). other possibility is i have a semi permanent wireguard connection now with other remote unraid server. but that's been setup for weeks now with no issues (until now i guess). other than that, I can't think of any changes that might be the culprit, really don't know where to start. Thanks in advance

     

    -Chaz

     

    kal-el-diagnostics-20200113-1320.zipsyslog-2020-01-11.zip

     

  16. Radarr and Sonarr handle media files differently. Sonarr actually inspects the files and determines whether it’s x264 or x265. Radarr (at least V2) does not. It’s imperative to have radarr rename the files (not folders) with the media tag like so:

     

    {Movie Title} ({Release Year}) -{Quality Title}-{Mediainfo Videocodec}

     

    this will output a (Plex compatible) file name like:

     

    Batman (1992) -Bluray-1080p-x265

     

     

    so if you don’t have this tag set but you have a x265 profile, it will re download the file from a source with a x265 tag if it senses a file change ie from unmanic. 
     

    so add the file tag under the radarr settings. Then you’ll need to rename all the movies in your library to apply the naming scheme, which can be done with radarr or filebot. Then, when unmanic converts “Batman (1992) -Bluray-1080p-x264” to x265, you’ll need to manually change it to 

     

    Batman (1992) -Bluray-1080p-x265

     

    radarr will then see it meets the quality profile and won’t attempt to redownload (assuming other quality profile criteria is met). 
     

    PS radarr V3 May have file analysis functionality which would render this whole exercise moot. Might also be worth looking into. 

     

    • Thanks 1
×
×
  • Create New...