thestraycat

Hi guys, i have a weird issue with Radarr/Sonarr and the drone factory not picking up folder for processing (not sure if it's even still ment to be working as there was talk of depreciating it?) My paths are set as below in unraid: Sonarr (Unraid config) /downloads --> /mnt/user/appdata/downloads/sonardrone/ Radarr (Unraid config) /downloads --> /mnt/user/appdata/downloads/radardrone/ And within Radarr/Sonarr GUI, under dronefactory, there set as follows: Sonarr Drone Factory (Sonarr GUI) /downloads/sonardrone/ Radarr Drone Factory (Radarr GUI) /downloads/radardrone/ Everything's on the same server (192.168.1.125) and i'm fresh out of ideas! nothing in the logs corresponding to anything useable! I threw some attachments in to show, i can browse to the folders from within Radar and Sonar and can see the folders of films waiting to be processed but for some reason nothing happens when i manually trigger the dronefactory? Does the config look right to you? I'm starting to think the feature has been quietly depreciated... Can you see anything strange in the screenshots below?

Hi guys, I'm having some strange permission issues with Sonarr. When sonarr creates files in the shares i have created. it creates the files as: Owner Name: nobody Group Name: users sonarr is set with defaults as far as i can tell: Set permissions = Yes File CHMOD mask: 0644 Folder chmod mask: 0755 however from a windows machine i cant edit the files it creates: "you require permission from Unix user\nobody to make changes to this file." Any ideas? I've checked the file permissions from unraid for files being created by Couchpotato and the files show up the same as they do for files created by sonarr (ownername = nobody | Group Name = users) And files editted from windows created by couchpotato edit fine. From windows the couchpotato files look like this: Security tab on a file shows: Everyone - Read & Execute, Read, Write, Special permissions greyed nobody - Read & Execute, Read, Write, Special permissions greyed users - Read & Execute, Read, Write, Special permissions greyed however in sonarr they look like this: Everyone - Read nobody - Read, Write users - Read The shares look identical from within Unraid any ideas why NTFS/ACL's arn't being set properly? i've tried setting sonarr as Set permissions = Yes File CHMOD mask: 0777 Folder chmod mask: 0777 and Set permissions = No File CHMOD mask: 0777 Folder chmod mask: 0777 Am i ment to be specifying the following values within sonarr with "99" & "100" or anything? chown user chown group

Hmmm anyone else getting the problem when they click on "customization" all of the formatting breaks and the container cant recover even after a reboot? Tried it twice now from blowing away the container and deleting the persistant storage and reinstalling... WEIRD.

Anyone had any luck running it with apache reverse proxy?

Would love to have a convenient self-contained MediaWiki container if anyone fancies having a go... I run this particular container on my standalone docker host without issue... but have no idea of how to get it over to Unraid. Think it probably just needs redirecting to install in /appdata https://hub.docker.com/r/appcontainers/mediawiki/~/dockerfile/

Ah right thanks for the confirmation - Anyone else get it? Or am i on my own with it...

Just noticed this error in the logs when i turn off the container? Is it to be expected? Nov 6 17:10:13 MediaServer kernel: transmission-da[26536]: segfault at 48 ip 0000556061c5ee19 sp 00002ae9ef40b9e8 error 4 in transmission-daemon[556061c2e000+72000]

Any chance i can get a screenshot of your container config?

Anyone having a problem making changes to transmission that save for example adding a blocklist URL or changing values? Even when i edit the settings.json file with the container off and then turn the container on it still overwrites the settings which i believe is standard practice for the transmission daemon... But should i be turning off the transmission service with the container on, editting the settings.json file in the /defaults folder (in the container) and then enabling the service? I thought with there being a copy of settings.json kept in the appdata/transmission folder (outside the container) i should have been able to modify there?

I did my tests on a completely different docker host with no previous install of SABnzBD... Everythings fine until i tick "Download all par2 files" and restart. Then i lose the greyed out multicore tick. Even when i untick "Download all par2 files" and restart the greyed out multicore tick dosn't return, have a sneaking suspicion that making ammendments to any of the related PAR options would do the same...

@SparklyBalls Just did the exact same test as yourself following your vid letter for letter... got the same result as you. However, when i turn on "download all par2 files" under 'settings -> switches' I experience the issue i reported, i lose the greyed out tick. Can you see if it's the same your end? EDIT: Strangely when i remove the tick from "Download all par2 files" the tick under "Enable Multicore PAR2" dosn't come back either!

Sorry I mean the parameter in my screenshot. I have par2 and ionice parameters set in sabnzbd but sabnzbd complains of problems with my par2 parameters (which should be valid if it is indeed using multicore as these parameters force multicore) I was under the impression that if sab found a compatible multicore par2 executable it would have put a tick in the greyed out box for multicore as well? If anyone is running the latest pull of this container can they see how there's shows up under settings -> switches?

That's great do you know if the version of par2 you guys have used in this container can use the switch in my pic? Sent from my Nexus 5 using Tapatalk

Hi guys, Love your containers, and see that you've mentioned previously in the thread that PAR2 Multicore should be enabled as part of this container however when i browse the default skin and check my PAR2 settings there is NO tick in the greyed out enable multicore par2... Is this to be expected? And if it is enabled and this is related to PAR2 not being recognized as there are there any default PAR2 parameter settings that are being used straight out the box? i'm getting PAR2 switch error using the following:

+1 for iSCSI for mounting Hyperspin to windows clients... It's the only way to host content remotely to hyperspin...

Hi guys, I'm running the latest container of linuxserver.io's sabnzbd... i just wanted to ask whether it was nomal that the "Enable Multicore Par2" option was greyed out?? I read earlier in the thread that the multicore par2 was included in this container? I've entered the "Extra PAR2 Parameters" as -t+ but was concerned that if the enable multicore par2 option was greyed out it wouldnt be using it?? I've checked in unraid's dashboard whether all cores are in use during a verify and unpack and they seem to be (although there not maxed) Is there an easy way to confirm?