jbear

Anyone have any insight on this? At one point I ran the powerdown addon, it was removed awhile back as I was told it was no longer needed. When the reboot button is clicked, I assume it runs a command or script?, can I check to verify those commands and or scripts are present? If so, some guidance on where to look would be appreciated.

I have a problem that popped up earlier in the 6.3 BETA cycle, hoped it would get fixed when the FINAL came out, but no luck. Maybe it's specific to my configuration. This issue is when I STOP the array, then select the checkbox to reboot, then proceed to click the REBOOT button, nothing happens. Almost like there is nothing associated with this action. I end up having to SSH in, then reboot from the shell. I'm experiencing no other issues. Diagnostics attached. Feedback appreciated. Thanks. tower-diagnostics-20170206-1446.zip

Me too, file are moved to Output, but input files are not removed. I have to manual delete.

Noticed the same thing.

Anyone else use Headphones with the local Musicbrainz server docker? Headphones seems brutally slow using my local MusicBrainz server, if I query the same LOCAL Musicbrainz server directly via the web interface, it seems to be fairly quick. Headphones seems to pause on "(Album information for this artist is currently being loaded)" .. Any help is appreciated.

Anyone having any problems with NZBHydra, Sonarr and NZBGet ? Sonarr stopped working recently after updating NZBHydra, I noticed in the official NZBHydra release notes that Sonarr support was broken but then later fixed. Still not working for me. NZBHydra works fine on it's own, but when I point Sonarr to NZBHydra as an indexer, I get the following errors. NzbDrone.Core.Download.Clients.DownloadClientException: Failed to add nzb REMOVED 1080i HDTV DD2.0 MPEG2-TrollHD.nzb at NzbDrone.Core.Download.Clients.Nzbget.Nzbget.AddFromNzbFile (NzbDrone.Core.Parser.Model.RemoteEpisode remoteEpisode, System.String filename, System.Byte[] fileContent) <0x4102ada0 + 0x0026f> in <filename unknown>:0 at NzbDrone.Core.Download.UsenetClientBase`1[TSettings].Download (NzbDrone.Core.Parser.Model.RemoteEpisode remoteEpisode) <0x4102a2a0 + 0x00521> in <filename unknown>:0 at NzbDrone.Core.Download.DownloadService.DownloadReport (NzbDrone.Core.Parser.Model.RemoteEpisode remoteEpisode) <0x410296c0 + 0x00561> in <filename unknown>:0 at NzbDrone.Api.Indexers.ReleaseModule.DownloadRelease (NzbDrone.Api.Indexers.ReleaseResource release) <0x410293c0 + 0x000c1> in <filename unknown>:0 at NzbDrone.Api.Indexers.ReleaseModule.<.ctor>b__7_0 (System.Object x) <0x4101b6f0 + 0x0002b> in <filename unknown>:0 at (wrapper dynamic-method) System.Object:CallSite.Target (System.Runtime.CompilerServices.Closure,System.Runtime.CompilerServices.CallSite,System.Func`2<object, object>,object) at Nancy.Routing.Route+<>c__DisplayClass4.<Wrap>b__3 (System.Object parameters, CancellationToken context) <0x40f1d2f0 + 0x0014f> in <filename unknown>:0 Log from NZBGet ERROR Wed Aug 10 2016 18:56:02 Could not add collection REMOVED 1080i HDTV DD2.0 MPEG2-TrollHD.nzb to queue ERROR Wed Aug 10 2016 18:56:02 Error parsing nzb-file REMOVED 1080i HDTV DD2.0 MPEG2-TrollHD.nzb ERROR Wed Aug 10 2016 18:56:02 Error parsing nzb-file: Extra content at the end of the document ERROR Wed Aug 10 2016 18:56:02 Error parsing nzb-file: SYSTEM or PUBLIC, the URI is missing ERROR Wed Aug 10 2016 18:56:02 Error parsing nzb-file: SystemLiteral " or ' expected ERROR Wed Aug 10 2016 18:56:02 Error parsing nzb-file: Space required after the Public Identifier Works fine if I use one of my indexers directly in Sonarr, and use that instead of NZBHydra, NZBGet does it thing without any issues. That has been my workaround.

It is possible to eradicate a container completely. So if you can't there are only 2 options: 1. There's a bug 2. You're doing something wrong Thank You.

Its not 6.2, but the way that docker works, completely normal. Image layers are shared between containers. If its already there, being used by another app, then it won't redownload it. No, it's because the container is auto-updating at startup... Thanks for the feedback guys, I was able to get NZBHydra working with Sonarr with the help of the guys over at git-hub, workaround, but at least it works. I did find it interesting that I couldnt wipe the container, I suppose that is another question, and possibly not appropriate in this thread. Thanks again. So if there is a bug, then you need to post instructions on how to recreate the problem and then problems get fixed. Otherwise the only one who has benefit from this is yourself, which defeats the purpose of beta testing. Not sure why I would post an NZBHydra (Sonarr Integration) bug on an Unraid forum ? Really not related to why I posted in the first place, I was wondering if it was possible to eradicate a container, leaving no traces behind, ie downloading from scratch. If there are those interested in NZBHydra / Sonarr issue, you can look here. https://github.com/theotherp/nzbhydra/issues/301?_pjax=%23js-repo-pjax-container

Its not 6.2, but the way that docker works, completely normal. Image layers are shared between containers. If its already there, being used by another app, then it won't redownload it. No, it's because the container is auto-updating at startup... Thanks for the feedback guys, I was able to get NZBHydra working with Sonarr with the help of the guys over at git-hub, workaround, but at least it works. I did find it interesting that I couldnt wipe the container, I suppose that is another question, and possibly not appropriate in this thread. Thanks again.

Tried that, no orphaned containers

I'm trying to COMPLETELY delete a Docker so I can re-install from scratch. I've done this many times in the past, with no issues. Stop Docker Container Remove Appdata folder Remove Docker container and Image Problem is when I attempt to re-install, it says image already exists, and uses the existing image. I want it download a VIRGIN image, as if it were the first time installing the docker, it appears to me as if nothing is downloading. Reason is, I updated this particular docker (NZBHydra/Linuxserver) via the update from WITHIN the NZBHydra web interface, which went fine. Unfortunately, this update has a bug when using with Sonarr, and I want to revert back to the version which was installed originally. I've never had an issue doing this in the past. If I'm not making any sense, I apologize Thanks.

Seems like no matter how many times I try and update the Binhex-Madsonic docker, it still displays Update Ready. Even though it clearly appears to have updated. Never had an issue in the past, so I'm not sure if this is related to B22. Thanks. tower-diagnostics-20160610-1428.zip

Upgrade done, so far so good Thanks. LT

I usually just use Chome on Windows 7 x64. What client are you using? OpenPHT or Plex Media Player? You don't necessarily have to use another computer, just try another client. I can keep my OpenPHT on Mac paused for as long as I want without issue. The only problem may be that unRAID has spun my disks down during that time and requires a bit more time to spin back up before the video will fully resume. Other clients sometimes kick me out of the pause after a while if its being transcoded... really is quite client-dependent (which would have little or nothing to do with this Docker container).

Was set for /mnt/user, switch to /mnt/cache same problem. Doesn't work either way. Put movie on pause, walk away for a few minutes, come back press play, and the cursor spins, hit X to menu, then play again ... Seems like some kind of player issue. ... Will try another PC to make sure.. Out of curiosity, how is your /config folder passed? as /mnt/user/appdata/plex... or as /mnt/cache/appdata/plex...

Plex not resuming after pausing, resuming not properly started from the last spot. Anyone else having issues with either of these of late. Seemed like these issues started in the last couple weeks.

Go back to stable version ? Wait for next beta maybe ? It seems LT has been working on the next beta for awhile, been mostly quiet, so maybe they are still having issues reproducing some of these issues in their lab. Hardware: ----------- CPU: Intel i7 3930k4.3GHz Motherboard: Asus P9X79-Pro Graphics1: NVIDIA Geforce 210 (for Unraid) Graphics2: NVIDIA GTX980ti (Main gaming VM) Graphics3: NVIDIA GTX750ti (Guest gaming VM) SSD1: Samsung_SSD_850_EVO_250GB_S21PNXAG319699H SSD2: KINGSTON_SV300S37A120G (Main SSD Guest VM) ParityHDD: Seagate_ST3000DM001_3TB HDD1: WDC_WD20EZRX-00D8PB0_2TB HDD2: Seagate_ST2000DM001-1CH164_2TB HDD3: SAMSUNG_HD103SJ_1TB

Has there been any official comments from LT after this post ? Just curious if I missed anything as to the general status and progression until the next beta hits. More curious than anything else ..

Is the Flickr-uploader working for you ? Do you have a pro account, or just a normal Flickr account ? I've installed this docker, got my key and secret, edited the uploadr.ini (key, secret, files_dir edited), cut and pasted the URL from the log and authorized, docker seems to start etc., but nothing seems to be uploading. I will double check my path etc.

Switch to NZBGet and never look back Thanks for the feedback. I've been waiting for my parity to rebuild since last night before trying any of your suggested changes. However, while the parity was rebuilding I did slowly start enabling dockers and monitored their effect on the load of the system. I went in thinking Plex would be a huge load on the system, but in the end I was able to load all dockers except Sabnzbd. Once the parity rebuilt, I enabled Sabnzbd and the load went through the roof and the web ui stopped responding. Sniffing around while that happened, I noticed that for some reason I was unable to read (ls) the Incomplete folder (on disk 7, not user share) that Sabnzbd was also trying to read from when it hung. After a reboot I started a btrfs scrub on the drive in question to make sure it wasn't an FS error that was causing Sabnzbd to lock up, which would in turn took out the web ui. So while the jury is still out until the scrub is finished (i'm 1TB into a 3 TB drive), it seems that if I don't run the Sabnzbd docker then all is well. My server was stable enough to rebuild dual 4TB parity drives in about 15 hours without Sabnzbd running. Interestingly, as a test I've created an Ubuntu JEOS 14.04 VM and installed Sabnzdbd there. It has been happily running stable for the last hour or so, even with the host server load staying above 15 on the system. So it's almost as though Docker is choking when Sabnzbd would have a lot to process, but KVM keeps chugging along. I would have the thought with less overhead in Docker it would perform better. So, again thanks for the suggestions, but I'm reluctant to try them at the moment as things are somewhat stable, with everything at least working. I still need figure my way through the various combinations of technologies, but in the end it is amazing what this one box is doing. It's: - a 73 TB media server - a 9 TB ZFS RAID5 server with Samba and 3 years and counting of Windows Previous Versions for all my documents, family photos, etc. - a downloading powerhouse (Sabnzbd, Sonarr, FlexGet, etc) - a CrashPlan offsite backup enabler for my 9TB of critical data above, plus selected media (thanks to the 9p passthrough) I've consolidated multiple machines into this thing and thanks to KVM, passthrough, 9p, virtio and all the other Linux and Unraid goodness its running on less electrical power, less equipment and more then adequate performance for home use. I know I sound like an infomercial/fanboy, but it really is awesome when you step back and think about it (and when everything works! lol). So, good job LT/volunteers/open source communities!

Been on 6.2 Beta 21 for about 24 hours, ran full parity check, 0 errors. Updated dockers one by one, really nothing to report. Everything on the surface is working just as it did under 6.1.9, have not reviewed any logs looking for problems. All is well. Great job on 6.2. I use most of the dynamix plugins, 2 VM and 12 Dockers. Biggest pain in the *** was having to update each docker due to the docker API update Nothing other than updating them Lol, I think he was expecting more given the "biggest pain in the ass" comment.

Looks like Zoneminder 1.29.1 is out, what is the best way to upgrade ? Wasn't sure if I need to wait until you updated the docker, or if there was another way. Thanks. Great to hear is working. Let me know if you find any other bugs

LOL, true ... I've read through the first beta's release notes, and it didn't sound like there was anything major to do. His response did throw me off a bit I use most of the dynamix plugins, 2 VM and 12 Dockers. Biggest pain in the *** was having to update each docker due to the docker API update Nothing other than updating them Lol, I think he was expecting more given the "biggest pain in the ass" comment.

What did you have to do to each Docker after the upgrade ? I use most of the dynamix plugins, 2 VM and 12 Dockers. Biggest pain in the *** was having to update each docker due to the docker API update

Are you using Plugin's ? Dockers ? VM's ?