trurl

Thank you VERY much for this! I was excited to see that previous guaranteed lockup behavior wasn't causing the lockup once I set this parameter. Then all of a sudden after repeated testing it locked up again---looking at the cores from the webgui dashboard page I saw that core 6 was reporting 100% (almost no activity on the other cores) and I had specified Plex to use 0-5....which leads me to the point I had configured Crashplan to use 6&7 and enabled it after extensive testing. So reality is I'm looking at a crashplan issue and would have never arrived there without your assistance. I know I had lockups with Plex being the only active docker previously but with this --cpuset-cpus variable I'm able to avoid having the lockups that plagued me as long as I don't have Crashplan running at the same time. Plex cpu0-5 and nothing else: no lockups Crashplan 6-7 and Plex 0-5: 100% on core6 and lockup Thanks! Maybe you need to let unRAID have a core.

The same as anything else, in your router.

You can add --delete to rsync to delete files from the target that don't exist on the source.

You must let unRAID do the format of any drive that is part of the array, so removing it isn't what you want to do. If you have already added it, and started the array, then unRAID is probably offering to format it right now, if it hasn't already done so. And it is probably XFS since that it the default for array drives in V6. If for some reason you have already formatted it to a different filesystem, stop the array, click on the drive to go to its settings page, and change the format. Then unRAID will format it when you start the array. Not only does unRAID have to format any drive it will use, but formatting a drive (a fairly quick operation, since it is just writing a small amount of metadata that represents the empty filesystem) that is already in the array will also update parity, so no parity sync is required.

Make sure you check package version compatibility. You might take a look and see what versions of packages the NerdTools plugin installs.

I have removed the plugin and rebooted. We'll see if it happens again tonight.

I was just composing this when you posted your announcement about the new version. Got this email from the daily cron after the auto-update to the new preclear version. I wasn't even using the plugin at the time and in fact, haven't used it in months. I assume your plugin is to blame due to the mention of "tor" and it is the only thing that changed overnight.

Post your docker run command or a screenshot of your docker showing the volume mappings. EDIT - I see you already did on your other thread.

I think the point of that note is that if it is already an XFS formatted drive, then the step where you format it to XFS will not happen. And in fact, before you formatted it to XFS it wasn't.

QFT

I'm certainly not the best for scripting. If you search (see How to Search in my sig) for script/notify you will see other examples of people using notify. The main thing I don't know is how you intend to produce the log file you want to include in the email, and that is going to be something that is specific to your use.

Not at all what was asked for

Possibly you have more than one share with the same name, except for upper/lower case. Post a screenshot of your User Shares page, or just post your diagnostics.

Sometimes when I first start Plex and go to its webUI, it will not find the server either. Signing out and back in again fixes it for me.

Sounds to me like maybe the permissions on the share were set wrong somehow, and creating a new share then renaming it resulted in a share that didn't have those permissions.

See the github link in the first post for instructions on how to select a plex version.

Make a script that does whatever you want. In the script, include the notify at the end so that when you run the script, you get the notification. Call the script from the .cron file. Done

See here for example.

Basically, a template is just a way of saving the stuff you put in the Add/Update Container form, and the stuff in the Add/Update Container form is just a way of specifying what to put in the docker run command. The docker service takes care of the rest in the standard docker ways.

Have you read the Docker FAQ? Thank you for the link. Yes, I have had a look through these although didn't cover my main questions (or I wasn't asking the right questions). I think part of the problem is that version 6.2 has brought in some awesome improvements but these are still very new. I am new too so don't know anything about the background. Yes, there is a lot to learn. In case you haven't already, you might also take a look at the How to Search sticky link in my sig.

Have you read the Docker FAQ?

Means you need to read the Docker FAQ And see search tips in my sig

yes for certain. x.x.x.xxxx-xxxxxxx Can it be manually updated with the file I've downloaded an be sure I won't lose my database / library? How else can i troubleshoot this? Thanks. If you remove the container and then add it again you should be able to look at the log for that docker and see whether or not it is downloading the correct version. Not vastly experienced with dockers. The only times i've removed plex is for a complete rebuild. Do I risk loosing the library, or when I re install will it pick right up where it is now? A few steps to make sure the right version goes back? Your plex library is in your appdata. You can add it back in Community Applications - Previous Apps. Then after it starts you can look at its log to watch it download from plex.

yes for certain. x.x.x.xxxx-xxxxxxx Can it be manually updated with the file I've downloaded an be sure I won't lose my database / library? How else can i troubleshoot this? Thanks. If you remove the container and then add it again you should be able to look at the log for that docker and see whether or not it is downloading the correct version.

Are you sure you're using the full version number? Look at reply 936 on this thread.