Squid

Switch your scale from Celsius to Fahrenheit and back again. It should then work properly

Say what? So for a 2TB drive, I should keep 400MB empty? Any official documentation on this topic? The issue only happens when writing to an almost full drive. ReiserFS can take awhile to figure out where to put the contents. Reads are not affected. XFS is not affected to the same extent. My secondary server has <10 Gig free on each drive, and is all still ReiserFS

Doesn't matter to me at all. If you keep the URL the same and just change the contents everything picks it up the changes. If the URL changes then the thread will have the old icon (community repositories will get the new one). Its just more work on my end, and for something as minor as an icon change I may or may not get around to it - depending upon what my mood is at the time - as it is now I only check for new containers for each repo about once a month. New repositories get added all the time immediately, but new containers once a month - too much work to go through everyone's repo's and look for changes everyday. Half the reason why I started that plugin.

It was just a heads up... I actually would never notice during my updates to the thread if the url for the icon changed as long as the original url still worked.

As an aside, if you change the URL for the icon file, then the Popular Repositories Thread will also have to be updated . If you keep the same URL then nothing needs to be changed. Community Repositories won't have an issue either way. didn't you once say you'd be bored if everything worked as it should ? lol. yeah I did once say that sparklyballs... or should I say zzzzzzzzzzzsparklyballs

As an aside, if you change the URL for the icon file, then the Popular Repositories Thread will also have to be updated . If you keep the same URL then nothing needs to be changed. Community Repositories won't have an issue either way.

It looks like it first copies the file to a tmp file and then copies it back onto the user share to avoid that issue mv "$FILE" "$FILE.tmp" #ls -l "$FILE.tmp" mv "$FILE.tmp" "/mnt/user/$SHARE/$FILE" Haven't tested it though.

Apr 30 11:54:16 server kernel: ata6.00: cmd 25/00:00:60:2b:00/00:02:00:00:00/e0 tag 0 dma 262144 in Apr 30 11:54:16 server kernel: res 51/84:7f:e1:2b:00/84:01:00:00:00/e0 Emask 0x10 (ATA bus error) Apr 30 11:54:16 server kernel: ata6.00: status: { DRDY ERR } This error is in your log, along with a bunch of READ DMA EXT. It sounds like when you replaced a drive you may have inadvertently knocked a cable loose, and your 1TB samsung is having connection problems. It's still working, but has downgraded itself speed wise to be PIO instead of DMA. I've never seen the READ MULTIPLE EXT errors that are popping up, but I have a feeling that its because the drive is now in PIO mode. I would check the power and sata connections to the drive and at the mobo.

So you don't think the dashboard thumbs up / down is good enough? The auto update / ignore feature is dangerous. It lets you think the problem has been resolved, when it actually may be something you need to deal with. I saw a thread where they posted about a thumb's down, and then posted back a little later saying "never mind, it went back to thumb's up all by itself". You should at least have to read and acknowledge the error before it goes back into the watch for changes mode. When the thumb turns red there is also a notification created. A notification displayed on screen needs to be acknowledged, further it is stored in the archive for later perusal. Users can choose to comletely ignore all this, but the system does give all the necessary warnings. I think this is more about on initial boot up where it gives a red thumb for a minute and then turns green. Could be all solved if the attributes are saved from one boot to another.

Its in NerdPack

Thinking about it, you're probably going to have to put quotations around it ie: -e IP="$(ifconfig .....)"

doubt if there's a way through dockerMan, but from the command line you should be able to do something like: docker run -d --net="host" --name="couchpotato" -v /path/to/couchpotato/data:/config -v /path/to/downloads:/downloads -v /path/to/movies:/movies -v /etc/localtime:/etc/localtime:ro -e IP=$(ifconfig br0 | grep 'inet' | awk '{print $2}') -p 5050:5050 needo/couchpotato You're the expert on environment variables, but that should set the environment variable IP to be the IP address of br0 which should wind up equaling 192.168.xx.xx or whatever

I dislike the terminology of "highly discourage", and still being only useful for webGUI enhancement. There are a number of plugins that are impractical to program as a docker container (Docker Search & XML conversion) that could not be classified as a GUI enhancement, and yet are only practical as a plugin. (Although I try and avoid dependencies like the plague) While I completely understand trying to get away from application plugins and move those to docker containers (and have been encouraging the community as a whole to stop using application plugins), limiting ourselves to GUI enhancements is almost shooting yourself in the foot.

In your gitHub repo there seems to be missing the xml files for no-ip and mumble

Did you try this plugin? http://lime-technology.com/forum/index.php?topic=38879.0 I had a look at the dockerfile, and you'll have to add port 9000 to the template the plugin creates

You should probably post in Phaze's thread. He may miss this thread here

When you stop array, docker should stop all of the running containers, but it may take a bit (depending upon what they were doing), or if you have a putty session opened into the console and the current directory was set to something within /mnt it will be unable to stop the array. Initially, I wouldn't blame it on the plex docker. I have zero problems with it, and never stop it prior to stopping the array (or any of my other containers for that matter)

Try putting a slash in front of movies, tv shows etc on the container paths

You may want to look at global share settings and see if a drive is excluded. I can't remember if a when a drive is globally excluded if its contents will show up in a share

I have looked around but haven't found a guide to setting up a mysql server for Kodi on Unraid. Do you happen to have a link to a guide you used to set yours up? I am currently running unraid 6 15b, so I would be using mysql docker container. Thanks. If you search, I believe that there's a couple of threads about this. I think however that the easiest way would be to install the MariaDB docker container, and then follow the guide on Kodi's website (but use MySQL Workbench from your desktop to connect to the database to enter in the SQL commands) - That's how I did it.

When needo's plex starts up, it downloads the updated plex application (which may take a bit depending upon what else is going on), and then it still takes a bit for plex to get itself up and running.

Maybe post a picture up of the port mappings for both those containers. Also, it may take a bit for the UI to become active, as the containers may be downloading any updates, etc prior to launching the container

http://lime-technology.com/wiki/index.php/Upgrading_to_UnRAID_v6

It's a Docker Search plugin error. Different ways of looking at it. When I was testing the plugin, I only had minimal amounts of "my" templates in that folder, so never noticed that dockerMan doesn't always display the templates-user contents correctly when subfolders exist. I'll push an update out later tonight to move the storage from the sub-folder directly into the templates-user folder. That's exactly why you lost the templates, and the reason why I was storing them in the templates-user folder. EDIT: On my system, everything displays correctly until I actually add another unRaid template. That's when I get the second templates-user. Either way, I've already updated the plugin to avoid this issue in the future.

That's where you went wrong. You should be installing one of the Plex Docker images. Plugins are pretty much just for OS related stuff now, not really for "apps". That's not really true. App plug-ins are still prefectly acceptable and is more of a preference thing. Recomended Plugin for Plex or Recomended Docker for Plex Also have you consered Emby (Formerly Media Browser 3)? Emby has some features that Plex doesn't but also doesn't have the app enviroment that Plex has yet. Pro's and Con's, but the big pro IMO is that the developers actually care what people say, and provide feedback. The thing is, plugins are OS related things whether they are intended to be or not. That can have some unintended consequences. So on balance, I think the preference should be towards dockers unless you intend to affect the unRAID OS. The way that I look at it is that because plugins run directly on unRaid, whenever changes happen to unRaid, those changes directly affect the running of plugins. How many times when the version number of unRaid (eg: 6b10 to b11 to b12, 13, 14, 15, etc) has changed has this necessitated a change to the plugin? Docker does not have this problem. A docker container which worked on 6b6 is still going to work on 6b15, and still going to work on 6.0 Final, and 7b1 in the exact same manner as before. Currently for applications such as Plex, CP, Sab, etc it still is a personal preference as to whether you run the plugin version or the docker version. However, as time goes on plugins of this type are going to dwindle because of the potential of plugin A messing up how plugin B works, plugin A doesn't like unRaid X, etc. Docker avoids all of those problems because it effectively hides each app from each other and from the underlying OS (unRaid) while maintaining equivalent performance (albeit with slightly higher memory / disk usage) Things aren't perfect yet with the setup of docker however. Just as with plugins, you have to consider which ports to use, and additionally you now also have to set and choose which folders on your array to give them access to. It's this last point which I feel is what is the hangup on switching over to docker. Everything else is identical in terms of setup.