Michael_P

Try reposting your diagnostic file

Mirror and post your syslog or anything would just be a WAG

You need more RAM, 6GB is too little for whatever you're doing - it's killing off smbd which is causing your file browsing issues. Add RAM or try the swap file plugin

Looks like zoneminder, if it keeps happening you can try to limit its memory usage, add more RAM, or put other services on a diet.

The folks behind Blue Iris have an active, bordering on unreasonable, dislike for anything Reolink, so if you need support you're out of luck there. If you're set on that brand of camera, leave BI off of your list. I have a dozen of them and they work fine, but you're on your own with them.

No idea, I watched my son play it once and couldn't see the point of it

Map any cache directories it's using to a disk, /tmp is a common one. If it's a game server, you'll probably just need to throw more RAM at it, turn off other services while it's running, or use the swap plugin

The game itself is not free, you can get a free trial but you still have to pay for it if you intend to keep playing

Run memtest and/or remove modules until you find the bad stick

Looks like whatever 'TowerServer-Lin' is has run the host OOM twice in your logs, once on the 26th and again yesterday - if it keeps happening you can limit the memory allowed to the container or change its config so that it's not storing data in RAM

When you are able to get in you can run ps -auxf and that will tell you which container is kicking off the ffmpeg processes

No

FCP just sees the "Out of Memory" from your log, it's not the host running OOM it's your nVidia card falling over. Try updating drivers/BIOS see if that fixes it or drop it down to gen 4/3

Looks like it was at boot, and doesn't appear to be anything to worry about - I've seen a few people have MCEs at boot with ryzen cpus, check for an updated bios see if it stops.

Back on the 5th thru around the 8th one of your containers was hitting its memory limit and was being killed, you can toggle advanced view on the docker tab to find whatever container id this matches to figure out which one it is: d922e3e766ff If you've already fixed the issue, you can reboot to clear the log to have FCP stop warning you. Also, NUT appears to be spamming your log, you should fix whatever it's complaining about Oct 22 17:44:46 T upsmon[3194985]: Poll UPS [[email protected]] failed - Data stale Oct 22 17:44:47 T rc.nut: Writing NUT configuration... Oct 22 17:44:48 T usbhid-ups[3194949]: Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!

Tdarr hit its limit and was killed, not tailscale Oct 21 18:54:44 Tower kernel: Memory cgroup out of memory: Killed process 66443 (Tdarr_Server) total-vm:15349868kB, anon-rss:14818028kB, file-rss:35480kB, shmem-rss:0kB, UID:99 pgtables:99960kB oom_score_adj:0

For storage file names, I'd ditch the encode data unless you really need it for something and just keep the imdb if you're worried about Plex or whatever matching

Looks like maybe sonarr was doing work that ran the host OOM, you can reboot to clear the log so it stops warning you and if it happens again, check its config or limit the RAM to the container. You also have problems with really long filenames unable to be copied/moved so you should trim them down to a more reasonable length that the filesystem can manage. Instance: Sep 21 06:00:07 Tower shfs: copy_file: /mnt/cache/media/Movies/The Devil Comes at Night (2023)/The Devil Comes at Night (2023) [imdb-tt23571868][WEBDL-1080p][8bit][h264][EAC3 5.1]-RABiDS.mkv /mnt/disk23/media/Movies/The Devil Comes at Night (2023)/The Devil Comes at Night (2023) [imdb-tt23571868][WEBDL-1080p][8bit][h264][EAC3 5.1]-RABiDS.mkv.partial (5) Input/output error

Looks like it to me. Keep it to a MAX of 4 per connector and stay far far away from the SATA splitters and any other molded style splitter connectors. I added my own additional connectors to the PSU feed lines, they punch down just like ethernet jacks. In my experience, Toshiba drives are very sensitive to power fluctuation.

I don't see anything crazy, qbittorrent is using a lot of CPU but not too out there, try to run it again next time it acts up

And you haven't change the default zfs cache amount? (1/8th system ram) what does ps -auxf look like?

If they were all transcoding to RAM, then that'd do it. You can try caching to disk instead for a while and/or limiting memory to the container. FWIW I have my plex container limited to 4G since if it finds a file it doesn't like during a scan it will spike to infinite RAM usage in a couple of seconds.

The slowdowns are likely because you're very close to running OOM, that's where these are coming from and will make the server unresponsive: Oct 9 20:46:14 unServerD php-fpm[12266]: [WARNING] [pool www] child 3078784 exited on signal 9 (SIGKILL) after 163.772122 seconds from start Oct 9 20:46:28 unServerD php-fpm[12266]: [WARNING] [pool www] child 3080607 exited on signal 9 (SIGKILL) after 76.074364 seconds from start Oct 9 20:46:38 unServerD php-fpm[12266]: [WARNING] [pool www] child 3081694 exited on signal 9 (SIGKILL) after 24.022172 seconds from start Oct 9 20:46:40 unServerD php-fpm[12266]: [WARNING] [pool www] child 3082525 exited on signal 9 (SIGKILL) after 12.009674 seconds from start Oct 9 20:46:50 unServerD php-fpm[12266]: [WARNING] [pool www] child 3082530 exited on signal 9 (SIGKILL) after 12.010067 seconds from start Oct 9 20:46:52 unServerD php-fpm[12266]: [WARNING] [pool www] child 3082531 exited on signal 9 (SIGKILL) after 12.011153 seconds from start Oct 9 20:47:16 unServerD php-fpm[12266]: [WARNING] [pool www] child 3082557 exited on signal 9 (SIGKILL) after 26.023875 seconds from start Oct 9 20:47:18 unServerD php-fpm[12266]: [WARNING] [pool www] child 3082633 exited on signal 9 (SIGKILL) after 26.023854 seconds from start It also looks like plex is choking on one of your files, could be corrupt or just because of the OOM issues Oct 9 21:06:19 unServerD kernel: Plex Transcoder[3143683]: segfault at 18 ip 0000150df840ea23 sp 00007ffc332bb280 error 4 in libavcodec.so.60[4f1a23,150df80a0000+406000] likely on CPU 17 (core 11, socket 1)

You have a lot of ffmpeg transcodes probably from frigate. Change it's cache location so that it's mapped to a disk share instead of RAM

With 96G of RAM you don't need swap, I run an absolute ton of services and a couple of chunky VMs on 32