paperblankets

I'm on a temporary motherboard/cpu with fewer PCI-e slots while my motherboard is RMAed, I suspect quite a few plugins are angry about hardware changes (In particular a GPU is missing so it makes sense the plugin is unhappy I guess).

Fresh diags after reboot ms-diagnostics-20240403-1053.zip `/mnt/user` is still linked, and the server is not manifesting errors at the moment. I'm mostly posting the diags in case they are useful for resolving the root issue. I will follow up if I notice any more issues, let me know if I can provide any useful info.

Here are some fresh diagnostics. I just got this error for the first time (that I'm aware of). ms-diagnostics-20240403-1014.zip

I removed the old user scripts. I also found weird behavior in the unraid frigate template, setting `NVIDIA_VISIBLE_DEVICES` is not respected by the image, but using `CUDA_VISIBLE_DEVICES` works as expected.

Is there a way I can re-prioritize the gpu order in nvidia-smi? ~# nvidia-smi Mon Mar 4 07:50:18 2024 +-----------------------------------------------------------------------------------------+ | NVIDIA-SMI 550.54.14 Driver Version: 550.54.14 CUDA Version: 12.4 | |-----------------------------------------+------------------------+----------------------+ | GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |=========================================+========================+======================| | 0 NVIDIA GeForce RTX 3090 On | 00000000:01:00.0 Off | N/A | | 0% 37C P2 96W / 350W | 1164MiB / 24576MiB | 2% Default | | | | N/A | +-----------------------------------------+------------------------+----------------------+ | 1 NVIDIA RTX A5000 On | 00000000:82:00.0 Off | Off | | 30% 33C P8 6W / 230W | 2435MiB / 24564MiB | 0% Default | | | | N/A | +-----------------------------------------+------------------------+----------------------+ What I am actually trying to do: I would like to use the A5000 before the 3090 for containers (but I want to be able to use the 3090 when I need to) I am using this user script to bring power states down hourly, but what I really need is for my containers to prefer the A5000. Right now I pass through NVIDIA_VISIBLE_DEVICES-ALL to each container, if I pass through a GUID list with the A5000 first would that impact priority? Thanks for letting me pick your brains.

If this is the first time setting up Plex: I think your container was restarted (or otherwise interrupted) during it's first run, and the database failed to initialize properly. Deleting /config (or pointing to a new directory) should allow Plex to initialize SQL properly. Alternatively if /config is mounted somewhere strange you may need to set the mount to a different type, or it could be a permissions issue.

It has been added there as well

During backup I get a version of this error for a few containers: ... [24.02.2024 03:32:23][❌][unmanic] '/tmp/unmanic' does NOT exist! Please check your mappings! Skipping it for now. ... But I have that, and the other failing directories in my global exclusion list. Is there a config tweak I should be doing to ignore these tmp paths? Thanks for maintaining and working on the backup plugin!

I'm not sure if this will help some of you with APC 3000 hardware. After enabling ModBus (On the UPS, and in settings) I HAD to physically disconnect the USB cable before nominal power rendered. I bet I wasted hours trying permutations of things, and in the end that's all I had to do.

To add to ConnerVTs post above, you can also configure an application on zero trust to only be accessible on your cloudflare gateway (vpn). https://community.cloudflare.com/t/bypass-login-page-when-warp-client-active/376061/11 I can't speak to the overall security or risk of misconfiguration in zerotrust, but that would give you fully 'tunneled' communication.

Container request for a vpn version of tubesync of https://github.com/meeb/tubesync/blob/main/Dockerfile

I have ruled out this being DNS related (at least internal DNS). Verbose logging it is.

Based on that I think waiting for a stable 3.0 sounds reasonable even if that's a month out. I can check for a more verbose error option in the container (I have a vague memory of a path flag that increases the verbosity of some of the service logging). I could also go to static IPs to rule out DNS as well. That's maybe where I should start.

Hi @KluthR! Thanks for your work on the new plugin. I see a v3 is coming soon and could wait for that if thats best, or test it if you think what I'm about to bring up might already be addressed. I have some containers that fail to restart after backup. Frigate is one this happens with consistently. I believe this happens because of the extra options this container is started with. The container starts with Extra Parameters: `--runtime=nvidia --shm-size=5G`, which, by itself is not to crazy. But it also has a coral AI/TPU (device) passed in. The weird thing, is the backup thinks the container starts successfully from what I see. ... [08.04.2023 03:00:13] Stopping frigate-nvidia... done! (took 4 seconds) ... [08.04.2023 04:08:32] Starting frigate-nvidia... (try #1) done! but the container just stops right after starting (In this case, I started it myself at 11:29): [2023-04-08 04:08:36] frigate.app INFO : Starting Frigate (0.10.1-83481af) Starting migrations [2023-04-08 04:08:36] peewee_migrate INFO : Starting migrations There is nothing to migrate [2023-04-08 04:08:36] peewee_migrate INFO : There is nothing to migrate [2023-04-08 11:29:36] frigate.app INFO : Starting Frigate (0.10.1-83481af) 23-04-08 11:29:36] peewee_migrate INFO : There is nothing to migrate [2023-04-08 11:29:36] frigate.app INFO : Output process started: 227 [2023-04-08 11:29:36] ws4py INFO : Using epoll ... I really don't know why this is happening, but thought I would share some of the weird in case something jumps out, or someone else is experiencing the same issues. Maybe causes: My DNS server (a container) might be down, maybe frigate is silently erroring trying to access cameras. If it is that the DNS server container has not started yet, is there a quick solution to this? Like a pre start script that starts my DNS server container. I have not tried that since I thought the backup script would error trying to start the DNS server when it was already started. Thanks for any thoughts or ideas, and the work to improve the backup plugin.

It was the username I could not figure out, but admin worked. 🙌

HI there, for PhotoPrism, what is the default user? I can't seem to initially login. I'm using the internal database in your image. text error warn system array login time="2022-11-06T12:31:34-06:00" level=info msg="PhotoPrism® needs your support!" time="2022-11-06T12:31:34-06:00" level=info msg="Visit https://photoprism.app/membership to learn more." time="2022-11-06T12:31:34-06:00" level=info msg="migrate: executing pre migrations" time="2022-11-06T12:31:34-06:00" level=info msg="migrate: executing main migrations" time="2022-11-06T12:31:34-06:00" level=info msg="webdav: /originals/ enabled, waiting for requests" time="2022-11-06T12:31:34-06:00" level=info msg="webdav: /import/ enabled, waiting for requests" time="2022-11-06T12:31:34-06:00" level=info msg="server: tls disabled" time="2022-11-06T12:31:34-06:00" level=info msg="server: listening on 0.0.0.0:<port> [4.706171ms]" started 221105-jammy as root (amd64-prod) init: updating filesystem permissions PHOTOPRISM_DISABLE_CHOWN="true" disables permission updates Problems? Our Troubleshooting Checklists help you quickly diagnose and solve them: https://docs.photoprism.app/getting-started/troubleshooting/ file umask....: "0002" (u=rwx,g=rwx,o=rx) home directory: /photoprism assets path...: /opt/photoprism/assets storage path..: /photoprism/storage config path...: default cache path....: default backup path...: /photoprism/storage/backups import path...: /photoprism/import originals path: /photoprism/originals switching to uid 99:100 /opt/photoprism/bin/photoprism start I don't see any errors, I just don't know what username to use on the `<ip>/library/login` page.

Hey @binhex (or anyone else), do you have a recommended way to stop the plex service inside the container for maintenance? According to this thread linuxio containers have some shell scripts baked in to handle it. MiB Mem : 32016.9 total, 3851.5 free, 7303.9 used, 20861.4 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 22613.4 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 81 nobody 35 15 64504 44196 9884 S 0.3 0.1 0:03.03 Plex Script Host 64 nobody 20 0 224 4 0 S 0.0 0.0 0:00.00 start.sh 65 nobody 20 0 112784 63856 37464 S 0.0 0.2 0:02.55 Plex Media Server 123 nobody 20 0 40176 11508 10096 S 0.0 0.0 0:00.19 Plex Tuner Server 180 nobody 20 0 109852 89760 10712 S 0.0 0.3 0:06.29 Plex Script Host 182 nobody 20 0 86324 62296 11448 S 0.0 0.2 0:03.14 Plex Script Host 185 nobody 20 0 66720 46852 10096 S 0.0 0.1 0:03.66 Plex Script Host 290 nobody 20 0 4316 3364 2848 S 0.0 0.0 0:00.01 Plex Relay 331 nobody 20 0 63192 43300 9908 S 0.0 0.1 0:01.87 Plex Script Host ... I'm sure I could just pkill -9 all these pids, but there is likely a better way than that right? Edit: For anyone following along `kill <pid of start.sh>` seems to have taken down the other plex services, the script may have an exit hook that takes those things down. I may check later. I'm a little worried supervisord might bring it all back up mid maintenance of database...

@randomninjaatk Is there an AMVD support thread somewhere? I'm having trouble getting videos from AMVD formatted named properly for plex to recognize.

Apologies if this has been talked about/just let me know and I will dig in more. I'm running the ghcr.io/linuxserver/homeassistant container, found via the app store. In addition to that container, I use zwavejs2mqtt. Every time the homeassistant container is updated, unraid brings back the `/path/to/device` template values. Which I do not use. This causes the container not to boot. Does anyone have any advice on this? Is their a null device path I can add for these 3 values or something? Deleting these after each update is rough. Thanks for your time.

Does unRAID have app armor or selinux enabled? This pending vulnerability looks like it can be negated by either. https://nvd.nist.gov/vuln/detail/CVE-2022-0492

In my case the container complains returns the following error after updating these permissions: <Timestamp> INF Starting tunnel tunnelID=<UUID> Tunnel credentials file 'home/nonroot/.cloudflared/<UUID>.json' doesn't exist or is not a file That file seems to be properly shared: ls -li /mnt/user/appdata/cloudflared/ total 12 <size> -rwxrwxrwx 1 nobody users 188 Nov 27 01:09 <UUID>.json* <size> -rwxrwxrwx 1 nobody users 1938 Nov 27 01:08 cert.pem* <size> -rwxrwxrwx 1 nobody users 249 Nov 27 01:13 config.yaml* Anyone have any ideas? Could someone tell me what their permissions look like on those files and what line endings those files have? Also what version of the container is working for you at this point might be helpful. Thanks for your time.

You should be able to open the console from the docker tab: Alternatively, the uri is something like: https://<host>/dockerterminal/<container-name> You can then run `top` to list all processes running, and then you can `pkill -9 <pid>` That should leave you with the container running, but no plex if you shut down all the plex services before they start up again.

@limetech I think add_header Cache-Control: no-cache, no-store Would be a safe change. I opened a pull request for this change to get feedback: https://github.com/novnc/noVNC/pull/1532 If I'm overlooking something I imagine they will call it out there.