djismgaming

I'm having this same behavior. The owner:group change to sshd:sshd.

Hi team, I've been hammering the server a little more than usual these past 2 days under 6.12.3. Setting up a lancache VM Saw mentions of macvlan traces on the Fix Common Problems plugin So I changed the docker network to ipvlan, although I do have the 2nd NIC fix applied since before those traces appeared, no biggie. So far Uptime 2 days 11 hours 57 minutes! We got past the 1 day mark now! And I see the possible 6.12.4 has a fix for macvlan traces and a possible revert to the usual macvlan with a single br0 link! These seem to be good times. I'll keep it as it is for now until 6.12.4 drops or a crash/shutdown happens. I deem this one as resolved for now. 😉

Hi, Local syslog server activated and the remote setup using the trickery option: Logging to file local to Unraid server Using a bit of trickery Will attach here the logs upon getting a crash/shutdown.

Hi team, I've tried 3 times the upgrade to 6.12 on my hardware. Each time on every 6.12.x release. On each I get no more than hours or 1 day of uptime. On each I've been reverting to the previous 6.11.5 which gives a lot of uptime (24 days before today's upgrade ☺️ that's a really good version!). I know I don't have the normal hardware for unRAID: Mac mini Late 2012 i7-3615QM CPU @ 2.30GHz 16 GiB DDR3 Almost all array drives are connected via USB. USB NIC for br0 (eth0) Built-In NIC for br1 (tg3, eth1 for VMs and Docker only) Took this diagnostic after the latest unattended and unclean shutdown happened Today. I was not around when it happened. Any input will be greatly appreciated. ☺️ I have currently set 2 of the 3 VMs (created but not running VMs for some months now) to br1 as the other was set. Let's hope it does something even though the 3 VMs are off by default. mini-diagnostics-20230822-0022.zip

If you get to the screen, you could also right-click on the screen to reload the obsidian application if it's closed for some reason.

I re-installed from scratch and it's working. It does show a white screen while loading the obsidian application but only for 2-3 seconds on my old Intel® Core™ i7-3615QM CPU @ 2.30GHz Mac mini Late 2012

Application Name: tracker-add Application Site: https://hub.docker.com/r/andrewmhub/transmission-tracker-add Docker Image Repository: https://hub.docker.com/r/andrewmhub/transmission-tracker-add Github: https://github.com/AndrewMarchukov/tracker-add Please post any questions/issues relating to this docker you have in this thread. If you need help but are not using unRAID, then please do not post here, instead head to the application's GitHub repository and open an issue there. This application can automatically add extra trackers to your torrents. The list provided in the template adds trackers by IP. You can change the list to any list available online or your own published one. How good it works depends on the torrent being downloaded. I've had some have much more speed than without adding the trackers but other have not seen any change. YMMV 😉

Indeed, the only change is the image being used and the inclusion of the PUID and GUID options as this last image makes use of that. It makes it easier to modify data inside the vault from outside the obsidian-remote container. This also makes it possible to have a local Obsidian installation pointing to the same Vault on the server, from a PC/mobile phone on the network.

Application Name: Obsidian Application Site: https://obsidian.md/ Docker Image Repository: https://hub.docker.com/r/braintobytes/obsidian-remote Github: https://github.com/BraintoByte/obsidian-remote Please post any questions/issues relating to this docker you have in this thread. If you need help but are not using unRAID, then please do not post here, instead head to the application's GitHub repository and open an issue there. Obsidian is a powerful knowledge base on top of a local folder of plain text Markdown files. NOTES: - When creating a vault, place it under '/vaults' dir, located in the root of the container (inside Obsidian). - This docker image allows you to run THE LATEST VERSION OF OBSIDIAN in a docker container and access it via your web browser. The original project was from sytone/obsidian-remote and it seemed deprecated as it was not running the latest version of Obsidian as this one does. SECURITY: - By no means this is secure for public exposure, it's full of security holes and RDP tricks that can be used against you, so if you do download it and run it, don't expose to the public interwebs! Do not expose this to the web unless you secure it with something like Authelia or a similar authentication process and know what you are doing!!

I changed the image to braintobytes/obsidian-remote. That image has the same configuration (it's a fork of sytone/obsidian-remote) but uses a python script to download the latest Obsidian version upon image creation. Check the Dockerfile for the update steps if reference is needed. This configuration is also missing the usual PUID=99 and PGID=100 variables for writing files in good permissions for the share, just in case you encounter issues while accessing the files from another Obsidian installation in your PC.

I see it worked! Thanks!

Thanks so much! All input is really appreciated. I've pushed the change to the repo now. I've made the addition here in the template: <Shell>sh</Shell> <Privileged>true</Privileged> <PrivilegedReq>true</PrivilegedReq> Should I remove the <Privileged> one? Or keep it?

Application Name: mbpfan Application Site: https://github.com/bplein/mbpfan Docker Image Repository: https://hub.docker.com/r/bplein/mbpfan Github: https://github.com/linux-on-mac/mbpfan Please post any questions/issues relating to this docker you have in this thread. If you need help but are not using unRAID, then please do not post here, instead head to the application's GitHub repository and open an issue there. PLEASE READ THIS, IMPORTANT TO MAKE THE CONTAINER WORK WITH YOUR MAC *** Must run as a privileged container *** Containerized mbpfan (for Macs running Linux, to control fans) NOTE: the executable in the container was compiled by bplein from https://github.com/linux-on-mac/mbpfan. Uses the Ubuntu repository version of https://github.com/linux-on-mac/mbpfan Need to create a configuration file with the following contents and mount it in the container as a volume in the container under /etc/mbpfan.conf: File contents of /mnt/user/appdata/mbpfan/mbpfan.conf (example on a Late 2012 i7 Mac mini, my unraid server) [general] # see https://ineed.coffee/3838/a-beginners-tutorial-for-mbpfan-under-ubuntu for the values min_fan_speed = 1800 # put the *lowest* value of "cat /sys/devices/platform/applesmc.768/fan*_min" max_fan_speed = 5500 # put the *highest* value of "cat /sys/devices/platform/applesmc.768/fan*_max" low_temp = 55 # try ranges 55-63, default is 63 high_temp = 66 # try ranges 58-66, default is 66 max_temp = 87 # take highest number returned by "cat /sys/devices/platform/coretemp.*/hwmon/hwmon*/temp*_max", divide by 1000 polling_interval = 7 # default is 7 seconds Edited March 22, 2023 by @djismgaming (initial post)

Glad to be of help

Finally found the culprit in the testing. In the notes on the container template there is this line: - Once that's setup you'll need to configure Deluge to allow remote RPC connections: - Open up core.conf in your Deluge configuration folder - set "allow_remote": true That was my issue on testing. Can you check if you followed that step? Remember to stop the deluge container while doing this change in the file. After the change, then start the container. It works now with the linuxserver image. Before, I was getting all these "connection refused" in storm's logs: