magiin83

Yeah that's definitely way more than I'm trying to attempt to get this running, but I appreciate the info. I'll just stick with trakt for sync watched and deal with fast forwarding or whatever if I switch NUC's in different rooms when watching something mid-way.

Is this still the only method (whether it's working or not?) of having a headless sql database on unraid? I dont believe I ever got this fully setup months ago, and had a headache of a time trying to. I'd still love to get my 2 NUC's linked together with a mysql rather than just trakt watched status sync across. I remember trying to put this together with the advancedsettings and sources xml files, along with maraidb and this docker, kodi displayed as headless off unraid, but I could never get anything to properly sync to the other NAS. Is there a better method of headless these days? Doesn't seem this thread is active anymore or I would presume this was the go to.

Just want to say, thank you enormously for that well-written overview. I am starting this mysql database from scratch, and having never used mariadb or the headless docker before, I'm sure this description you gave will be very help, so I really greatly appreciate you explaining what needs to be done! Cheers!

I have been wanting to finally give this headless idea a go, and have read through this thread multiple times - regardless of user error, issues with the docker that seemed to occur around when 17 and 18.0 started to come about - is this docker currently functioning? I've never messed with any mysql database stuff before, but I'd like to start although it seems daunting at first. I do have 2 instances of kodi running, 1 on a main htpc that is used the most often, and another that isn't used more than 5x a month, so this seems like the best option rather than keeping that instance running 24/7. Between the setup details on linuxserver's git and the details posted a few posts ago with the xml details and what to use with the sources and advancedsettings, is there anywhere else I should be looking for details on getting this started?

Post your docker run command. Disregard, forgot nzbget scripts had to be in separate folders within scripts

Anyone having issues attempting to get nzbget to see the scripts directory? Cannot for the life of me get it to see anything within it, no clue why. It also never created the directory when nzbget was first setup, but regardless, made the dir 0755, and nobody:users, yet nothing inside it is detected on the PP script list.

Anyone able to import a movie once it's downloaded properly since the last update? For me files are just sitting in the complete folder, waiting to move, but since drone factory isn't functional yet, everything just sits doing nothing. Nevermind, seems this is already a known issue, and since Discordd and all the devs are extremely active, already received the answer from them.

Considering it's only about 2 weeks into its creation, it needs a lot more work... but what does work already is quite impressive for that short amount of time. Once imdbid searches start working versus simply by name, that'll be a huge game changer. I wouldn't call it a daily just yet, but day by day it's getting closer.

+1 for this. github for it with changes and updates is already quite impressive.

As I was just about to post the same info Nice job, LS folks!

Thank you for making this it's own thread, both of you were extremely helpful with the issue I was having, as I'm sure plenty of others have had/will continue to have as microsoft continues their direction of homegroups

So then does that mean there isn't anyone using unraid who's able to get a remote folder scan to work using couchpotato?

Just downloaded something in fact to test it out. Here's what happens with these settings: Remote folder scan enabled ONLY on Kodi: Get file details (System-video-file list) is enabled. CP's end: Kodi's end: Only a notification occurs, AND the spinup happens because kodi tries to find whatever dl'd at /media/________ fails, but still spins up trying.

I do, and it doesnt. Only remote folder scan setting enabled, all that happens on the kodi end is the notification about X being downloaded, there is no update of the library that happens. That below is all that occurs and shows on the kodi logs. So it tries to find that directory, it doesnt exist, nothing else happens. If full library and remote is enabled, it shows the full story: Attempts remote folder scan, cant find /media/______, fails, backs up to full library scan.

Correct. The issue is, that one latest movie is the only thing that isn't added to kodi's library, so it leads me to believe, it's spinning to detect that 1 folder change of that newest movie. The only thought I've had in changing this from happening is in kodi settings the System->video->file list->get file details and create thumbnails to off. This doesnt spin anything (Granted I could just have something else set up incorrectly, if everyone else using this doesn't get a drive to spin when the video library scan starts)

Just leave it to full library scan, it's pretty quick at doing it from what I recall when I was running XMBC/Kodi. That's correct, CP is sending the wrong path. I understand that full library scan works, and I normally would use it - but does that mean that no one is able to get remote folder scan to work using CP as a docker? It is very quick with full library scan, but that's not really the point - I'm essentially trying to get movies, as they finish downloading, to have all of the file details and meta info scraped in while the files are still on cache, however, with full library scan enabled in CP, kodi is running the scan, seeing the new movie on the array rather than the cache drive link, and spinning the drive the file will eventually be written to, to get those file details, codec, meta info, etc.

No, I don't run headless. Just kodi on an intelNUC, running Jarvis. This issue I've had happening going as far back as helix though.

Anyone able to help with the above question? I can move this to a general couchpotato thread and not specifically this docker if it'll help

This has been an issue of mine on and off for some time, that I've tried correcting and gotten no where with. This issue more than likely doesn't effect just this CP docker, but probably all CP dockers, although I may be completely wrong there and I've just been doing this setup incorrectly the whole time. As background: My docker paths: The issue of remote folder scan, with dockers, being the way it is: If I want to notify kodi, with ONLY the folder being updated (Ie. a movie downloads, I want that folder and ONLY that folder to be added so as to not do a complete folder scan in kodi), it seems that remote folder scan does not work. For example, on couch's end in the logs: and shown in Kodi's debug log: In other words, if I had CP's "Always do a full scan" enabled, it would revert to that, then pick up the movie but only by doing the full scan. So... how does one get remote scan (much like how sonarr sends a proper remote path notification to kodi) to work in couchpotato, without doing a full video scan? Has anyone ever been able to get this to work with CP as a docker? Does the CP setting for Default File Action need to change to Symlink or Link to get this to occur properly? It's never been clear exactly how those settings effect the files, but I always assumed that Move would be the logical answer seeing as you're moving it from the download area to the complete area on the array (although mover doesn't occur til later) To coincide with those question: Once kodi receives that notification of a new file, will the location it tries to scan (ie retrieve file details, meta info, etc) be from the cache drive or from the array? Any help would be insanely appreciated.

Fixing some other things, now that NZBGet source code has being migrated to GitHub. Oh awesome! I remember talk of hug saying he was planning that but didnt realize it would ever come to be true. Thanks for the update and thanks for all the hard work!

Has a fix been applied or was last nights git push for something else? Not trying to rush anything, just asking since I'm still getting the 404 error with that update, or are others experiencing a fixed ui?

Assuming that's what is causing this, yeah.

I believe this is gfjardim's own. I switched to his some months back. Hopefully he sees this thread, I should've probably checked prior to hitting the docker update button. This container used is a fork of needo's NZBGet, and offer always updated versions of NZBget</b>

I updated the docker from the docker update available, not from within the application. Still receiving that same 404 error after adding in the EDGE parameter, and also removing the container, image and config file, and then starting from scratch. Things are still being sent and downloading properly to it, but any webui attempt is just error. gfjardim?

Ok, so I'm at the point where this has spiraled out of control. Just so we're all on the same page: I upgraded to 6.0 a few days ago, that is literally all I've changed in terms of settings for unRAID. Cache dirs I applied a new user defined setting (-U 0) and thats it. Dockers have changed - filebot on and off. So right now, literally anything I do in terms of using sonarr, or CP, will spin up the drive it's downloading to. I havent' changed any parameters or volume mappings in months, or probably since I got my cache drive even longer than that. I realize this isn't really the thread to be posting this in, but I have absolutely no clue what's causing this or why it's all of a sudden started. Clearly it's not filebot anymore. These are my mappings: All are up to date and updated dockers. My cache_dirs settings are in the image attached. I've had inotifywait -mr -e access -e modify /mnt/disk2 monitoring the drive as things light up, bu tobviously because cache_dirs is enabled, it's an enormous amount of info getting thrown at it. Also, with it enabled, it seems like ANY change sent to the drive (being downloaded, etc) will spin the drive. Also, any time I try to access even just general /Movies list in shell or over windows samba, the drives will spin. I have no depth limit used. Everything should have been cached, so why is it acting like it's not? With cache_dirs off, this doesn't occur. I can browse shares, etc. and drives don't spin. Doesn't this sound like the exact opposite of what should be happening? Yes I should probably post this in the cache_dirs thread, and I plan to, but since this back and forth with you guys helping has been going on, I thought I'd update here as well.... this is racking my brain way too much.