[[Support] binhex - Jackett]

7 minutes ago, schuu said:

what is this path used for, what were would be an ideal location?

That’s where you’re downloads folder is. Not useful for Sonarr and Radarr functionality, but useful if you want to manually trigger downloads via Jackett

[[Support] binhex - Sonarr]

Wondering if there’s any way to accomplish This using the current build of Binhex-Sonarr, basically I’d like to avoid needing to manually import episodes with TBA titles but I don’t see this option in the client. 
 

also thanks for all the great containers you provide!!
 

 

[[Support] binhex - qBittorrentVPN]

13 minutes ago, binhex said:

Q26:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

I was having the same issue this AM (proxy was set up on Radarr and Sonarr, not Jackett, and everything stopped working). 100% fixed via your FAQ linked above as I removed the config from Radarr and Sonarr and added HTTP Proxy settings to Jackett, directing it at the DelugeVPN container's proxy port, while also adding the Jackett port to Container Variable: ADDITIONAL_PORTS within Deluge's docker image settings.

 

Hope this helps someone else! And @binhex, you are incredible. Thank you for all you do for us!

[Log Filling Up Regularly]

Thanks @JorgeB will try that now and hope it solves the issue.

[Log Filling Up Regularly]

ChatNoir - thanks for spotting this! Any thoughts on how to fix? Sounds like I have a bunch of research to do. Hopefully the drive isn't dead... it's been in my cache pool for only 1.5 years but I guess the excessive write issue could have burnt it out.

 

Additionally I'd appreciate any insight you can offer as to whether this is a hardware issue (replace the NVME drive) or a software issue (nuke the cache, reformat, restore from backup).

 

I performed a BTRFS scrub (no errors) and also a filesystem check (output attached)

[Log Filling Up Regularly]

Currently running 6.8.3 and having a new and strange issue I can't figure out. Server had been running for multiple months with little to no issue, but recently every few days my log will fill up overnight (usually between 4:30AM - 5:00AM) which basically causes the server to cease to function (all dockers shut down except Plex, which ceases to function) and can only be fixed with a reboot. While the reboot fixes the issue, it keeps occurring and I'd like to fix it at the source.

 

All my dockers have the extra parameter: --log-opt max-size=50m --log-opt max-file=1

Currently my docker log rotation is on

I am no VMs

 

Below I've attached a couple of items I thought might help:

• -sm /var/log/* output
• All Diagnostics files (strangely my  syslog doesn't have any entries after ~2:00AM)
• Mover Settings
• Mover Tuning Settings
• The notification I received from Fix Common Problems telling me the log was full
• SSD Trim Settings

 

Thanks in advance for the help Unraid community!

Diagnostics.zip

[Docker Image Utilization]

Thank you Squid, really appreciate the help.

[Docker Image Utilization]

Will this blow up everything/settings/etc.? Or will I simply need to make sure all dockers are configured the same way as before?

[Docker Image Utilization]

Thank you, I'll add that to all my containers and report back if it doesn't work. Is there any way to tell from what I posted which docker was creating the gigantic log?

 

Assuming this does work, what's the easiest way to shrink the docker.img file down to a more reasonable 35GB or so? Or is it not worth it?

[Docker Image Utilization]

Forgot to be more specific in previous post, the exact same 45G file showed up in response to du -ah /var/lib/docker/containers/ | grep -v "/$" | sort -rh | head -60, so I followed up by using the same find /var/lib/docker/containers/ -type f -name "*.log" -delete that seemed to work (temporarily) yesterday. These two commands were run before I posted the output of the php command.

[Docker Image Utilization]

Seems like the problem is not fixed as I had to go through the same process todaySee above for results for the php command

[Docker Image Utilization]

Been driving myself a bit crazy trying to determine what is filling up my Docker.img - I've already increased the size of the image way more than I should have and am still struggling (91% of a 65GB image file). I've attached the results of the container size button on the docker tab, the results of running docker system df -v, and would much appreciate any help you could offer.

In my search to determine the culprit here, I ran this command du -ah /var/lib/docker/containers/ | grep -v "/$" | sort -rh | head -60 which resulted in the following

 

I then ran find /var/lib/docker/containers/ -type f -name "*.log" -delete which seems to have deleted the 45G files from the above picture, but the docker image utilization hasn't changed. I'm pretty desperate for help at this point.

 

Edit: literally the moment I was about to submit this topic, the docker image utilization went to <15%. So less urgent, but curious about the following.

• Was deleting the gigantic logs above the fix? How can I avoid these files growing so large in the future? Alternatively, any thoughts as to why this magically was fixed? The only other thing I did was turn off all my dockers (and turn them back on after utilization was under control)
• I gather my docker image file is WAY to big, and could be problematic. What should I do here in order to preserve all my dockers/settings as is?

[[Support] binhex - Plex Pass]

4 minutes ago, binhex said:

ahh yep i see the issue, so TRANS_DIR is NOT a volume mapping, its an environment variable, this is used to define what the path is to your transcode folder INSIDE of the container, its not supposed to be a mapping to your hosts file system (as in unraid). 

 

so what should it be i hear you say, well looking at what you are trying to achieve you could simply set TRANS_DIR to /config/Transcode that will then map via /config share to host path of /mnt/user/appdata/binhex-plexpass/Transcode (or something similar, depends if you customised the path for /config).

 

 

Thank you! The docker container appears to be working correctly now, really appreciate the help.

[[Support] binhex - Plex Pass]

35 minutes ago, binhex said:

this sounds like you maybe struggling with the concept of volume mappings with docker containers, have a read Q4 to Q7. from the following link:-

https://forums.unraid.net/topic/44108-support-binhex-general/?tab=comments#comment-433612

 

to debug your issue a bit further can you left click the plex icon and select edit, then choose "advanced view" from the top right and then screenshot the whole thing and post the screenshots here, its most likely a volume mapping not defined correctly.

Thanks so much for replying back - I just read over the attached link (thanks for providing the resource), and can't figure out exactly how I've messed with the volume mapping up. Below I've attached screenshots of everything I see in the advanced view.

[[Support] binhex - Plex Pass]

Hey Binhex - thanks so much for your work. I use 6 of your dockers regularly and they are fantastic! I'm hoping you can help me with an issue I'm having with the Plexpass docker...I'm pretty much an unRAID/Docker novice (just built my first set up a few weeks ago) so I imagine it's a pretty simple thing.

 

I set up the docker via CA, changed the settings for media and transcode directories, and can't get anything to launch. I see that it says it doesn't have access to mnt/user (which doesn't make sense to me, I gave it access), and mnt/user/Transcode also definitely exists. Any ideas?

Log for: binhex-plexpass.pdf

[Large Amount of Reads/Writes to Boot USB]

Thank you! Very happy to join the unRAID ranks.

 

I just hit "new config" before adding my parity and data disks, and the flash is reading <100 reads/writes, so I think I'm safe. Now to wait for the parity sync to run and I can get started in earnest!

[Large Amount of Reads/Writes to Boot USB]

https://drive.google.com/open?id=1Xu5SGd7LocrV6jWHr-NGi_fxDaGxApfd

[Large Amount of Reads/Writes to Boot USB]

Hope this is the right forum to post in, I'm brand new to unRAID. Just set up my first array last night, and so far there have been 4k reads from the boot USB and 45k writes. This doesn't feel normal based on what I know about how the OS is supposed to operate, or am I missing something?

 

The only things I've been doing so far is pre clearing drives before adding to the array and installing/configuring some plugins.

[New To unRAID Looking for Build Critique]

The goal is to use this as a NAS storage server that mostly runs Plex (3 simultaneous transcodes max, 5-7 simultaneous direct play max)/Sonarr/Radarr/Tautulli and some other dockers. I have a few 8TB WD Reds in my current set up - I would also need to figure out how to migrate things over and reformat those drives to add. I guess I should also mention this will be my first custom build. Would appreciate any comments that could either make this a better build, cooler(?), or save me some money.

 

CPU: Intel - Core i3-8100 3.6 GHz Quad-Core Processor  ($118.89 @ OutletPC) 
Motherboard: Asus - TUF Z370 Pro Gaming ATX LGA1151 Motherboard  ($154.99 @ B&H) 
Memory: G.Skill - Aegis 8 GB (1 x 8 GB) DDR4-2133 Memory  ($48.89 @ OutletPC) 
Storage: Samsung - 860 Evo 250 GB 2.5" Solid State Drive  ($52.99 @ Newegg Business)  - to be used as a cache drive
Case: Phanteks - Enthoo Pro M Tempered Glass (Black) ATX Mid Tower Case  ($108.98 @ Newegg) 
Power Supply: EVGA - SuperNOVA G2 750 W 80+ Gold Certified Fully-Modular ATX Power Supply  ($79.99 @ Amazon) 
Wired Network Adapter: TP-Link - TG-3468 PCI-Express x1 1000 Mbit/s Network Adapter  ($15.89 @ OutletPC) 
Total: ~$580.62

 

PCPartPicker part list: https://pcpartpicker.com/list/cWzFhy
Price breakdown by merchant: https://pcpartpicker.com/list/cWzFhy/by_merchant/

 

Thanks in advance. Looking forward to being a part of this community.