Squid

Delete advanced buttons.plg from config/plugins on the flash drive then reboot

Then you should check the logs of the containers in question and see if they've exited for some reason. Best I can say right now is that after the start of the array, they were running properly, because the autoupdate only stops a container that is running.

Biggest change (albeit rather minor in the grand scheme of things) are mobile device detection and options regarding the search bar focus Mobile Device detection *slightly* adjusts how the system works when running on a mobile device (currently how the resizing works when rotating, and the setting regarding search bar focus). Since the distinction between a mobile device and a computer can get rather blurred nowadays, the there is an option (below) to force on/off/auto the only change that this really affects for the end user. Search Bar Focus Previous behaviour was to have the search bar only in focus when entering the Apps tab, so you could immediately search without having to click in the bar. A new option is available in CA settings to allow you to adjust how the focus works: Automatic (default) - This keeps the search bar always in focus at all times so that no matter what you've done or clicked, you can always start banging away on the keyboard to have it begin to search. Automatic means that this feature is enabled from a desktop / laptop, but disabled on a mobile device (Some mobile devices do not like this and will continually scroll back to the top of the page when using CA) Always in focus - This forces the search bar to always be in focus. As stated, some mobile devices may have trouble with this. Never in focus - This is the previous behaviour, where the search bar is only in focus on the initial load of the Apps tab, and after clicking anything you will have to click into the search bar to type. Beyond that, some optimizations and fixes that nobody has noticed which means that either no-one uses CA or I'm just anal on this plug.

Additionally, I find it strange that docker.txt in the diags has a file length of zero bytes. Never really seen that before if docker is running.

Since I didn't have my diags from when this happened to me, and I'm unable to replicate my one-off issue under any circumstance I've thrown at it, I've got to tear apart yours: Right here: is a key. Your storj containers did start with the array. (And this is the point at which @bonienl and @limetech will stop caring, and I will start ? The update plugin stopped them May 5 11:02:12 Unraid-Server Docker Auto Update: Stopping Storj2 . May 5 11:03:54 Unraid-Server Docker Auto Update: Stopping Storj7 . May 5 11:04:14 Unraid-Server Docker Auto Update: Stopping Storj8 . May 5 11:04:34 Unraid-Server Docker Auto Update: Stopping Storj9 Ran the updates May 5 11:05:14 Unraid-Server Docker Auto Update: Installing Updates for heimdall hydra mariadb nextcloud nzbget plexrequests radarr Storj Storj1 Storj2 Storj3 Storj4 Storj5 Storj6 Storj7 Storj8 Storj9 Storj10 And then restarted them May 5 11:12:15 Unraid-Server Docker Auto Update: Restarting Storj2 . May 5 11:12:17 Unraid-Server Docker Auto Update: Restarting Storj7 . May 5 11:12:18 Unraid-Server Docker Auto Update: Restarting Storj8 . May 5 11:12:19 Unraid-Server Docker Auto Update: Restarting Storj9 So far as I can tell they did start up successfully.

Its up now. Must've been a temporary thing.

Same thing happened to me @bonienl with MariaDB, and I don't use autostart manager at all. I'll post diags later. And, autostart manager happens after emhttp does its starts and if the container is listed in the dynamix autostart file, then dynamix starts it.

logger this will appear in the syslog

logger command

Fixed in 6.5.2-rc1+

You can set CA Backup to not stop certain applications (Advanced Settings) before backing them up. Whether or not this affects the app in question depends. In my case, since there's no access to my db when the backup runs, I don't have any problems with leaving it running.

I used to run a secondary display via a USB adapter no problems. You won't however be able to set up the VM over the USB though. You'll have to do it all via VNC, and install the drivers etc. After that it should just work.

Yeah, that request has come up before, and running scripts at boot up is not something I want to support Sent from my SM-T560NU using Tapatalk

Actually, in retrospect I did say that. Rather than relying on the built-in css from dynamix, the preclear plugin redefines some css which does have an adverse effect on certain aspects of CA (ie: CA et al looks slightly different depending upon if Preclear is installed or not. And a uninstall is not enough to fix those problems - a reboot is necessary) I'm not a big believer of: Redefining stock elements of unRaid that can have an adverse effect on unRaid and/or other plugins Injecting code into every single page of unRaid's UI including plugins.

I've never said its harmful.

Are you using unRaid? docker compose does not come with it out of the box

Have another script run instead, and have that script run this one and fork it to the background #!/bin/bash /boot/scripts/myRealScript.sh &

Just a comment about this line. This should match the URL listed in the .plg file exactly (after any variable substitution) CA currently does a simple substitution of raw.github.com to rawgithubuser.com to try and alleviate any mismatches between the two. But, because there are numerous possible redirects and formats for the URL, mismatches may hinder the ability for CA to determine if the .plg is installed and CA will not follow the redirects to determine the actual URL of the .plg file because it slows everything down significantly. This is especially important if you have named the plugin identically to another plugin. In case you have different URLs listed in the .plg and in the .xml template that are not equivalent via the substitution listed above, I will ask (insists actually) that you change either the template or the .plg to match each other.

No issues with the .plgs that I'm aware of. The issue with both of them is that the url specified in the template doesn't match the URL specified in the plugin. I can work around that.

Not going to comment on your actual problem, but don't do this. Permissions on the appdata folder may or may not bear any relationship to what New Permissions sets them too. That's why Fix Common Problems includes a docker safe New Permissions tool that specifically excludes any changes to the appdata folder

Without knowing squat about owncloud, you're probably going to be better off utilizing either @dlandon's app or the official app instead of gfjardim's

Those are hidden metadata files created by your Mac. Safe to delete

Personally, if I heard this from a member of the Plex support team, I would bitch and complain to no end since Plex Inc does support running as a container, and whether or not its on unRaid is completely irrelevant.

Sooner rather than later.

The log is full and you haven't rebooted is the key. There's something wrong with the server and that has to be addressed first. The log filling up to 100% in a month plus is nowhere near correct