Nowjon

Thanks for the info! I think I know the issue, the Palworld docker container (game server) has a memory leak, and it would periodically kill that when the server was running out of memory but I wasn't sure if this freezing issue was related to that. I've moved that container to a different VM with portainer installed so hopefully this won't continue taking down my host. Thanks for the information! :)

Alright, so this happened again today, posting my diagnostics. Unfortunately, I had to reboot the host and these diagnostics are post-reboot, hopefully they still shed some light on the issue? Edit: Forgot to include the time, according to Uptime Kuma (Runs on a different device) I started noticing services go down at 13:44:37 CST (Timezone is set to CST as well) docile-diagnostics-20240126-1951.zip

Will do, I'll update once it happens. Thanks!

Good Afternoon, My server recently stalled, I was able to get into the device via SSH but I could not get to the WebUI nor could I access the shares. I noticed this issue when I was kicked from my server. This has happened a few times, but I've so far been unable to determine why. Possibly because of these? Jan 22 21:28:54 Docile php-fpm[9142]: [WARNING] [pool www] child 21439 exited on signal 9 (SIGKILL) after 560.130631 seconds from start Jan 22 21:29:17 Docile php-fpm[9142]: [WARNING] [pool www] child 26838 exited on signal 9 (SIGKILL) after 12.585703 seconds from start I've attached logs, if anyone can assist, thanks! docile-diagnostics-20240122-2334.zip

Feature Suggestion: Have the ability to automatically add a folder for any containers not already designated to a folder to show in an "Uncategorized" folder. When all containers are removed from this folder by assigning to other containers, hide this folder.

I see! I updated this and it started working as expected. I appreciate your assistance & commitment to ensuring great containers are available for us and supporting issues related to them

Ah sorry! My current IP is 10.10.10.146 and I can get to 10.2.2.10 just fine via traceroute traceroute to 10.2.2.10 (10.2.2.10), 64 hops max, 52 byte packets 1 setup.ubnt.com (10.10.10.1) 3.058 ms * 4.542 ms 2 10.10.10.201 (10.10.10.201) 2.289 ms 2.838 ms 3.330 ms 3 docile (10.2.2.10) 3.737 ms 2.480 ms 2.902 ms Is there anything within the container locking down access to the LAN_NETWORK or something similar? Update: I set my webtop container to the same network as the host (10.2.2.0/24) and verified I was unable to access it there either. Update 2: I set my webtop container to the bestitpros network, and I can access it here via 10.2.2.10:8112 in the container. Now I'm really wondering if there is an allowance or something for the WebUI

I'm attempting to connect to http://10.2.2.10:8112/ Here's my running container: Here's the message I get when attempting to load the site:

I'm having this same issue, were you able to resolve this? If not, I'd appreciate any assistance, I've followed https://github.com/binhex/documentation/blob/master/docker/faq/help.md for the attached log file. supervisord.log

Hello Community, Appreciate any assistance on the below. I'm replacing a data drive on my UNRAID host, due to one having 'Reallocated sector count' of 8. I've got the new drive, pre-cleared it, and I am wondering if I can replace the drive without rebuilding parity. Is there a way I can copy the data from the existing disk 3 to the new drive before replacing it in the array so that I'm not having to re-read from all the disks? I'm thinking I can stop the array, add the new disk to the array, use unBALANCE to copy all the data to the new disk, and then remove the old. Will this work? Appreciate it!

Check came back clear, guess I needed to run one after the correction check to get the number to update. Thanks!

I've started another one, I'll update once it completes. Thanks!

Hey! I'm seeing a ton of errors in UNRIAD, this server did have a unclean shutdown although I've ran a correction check without change. Could someone tell me if these are of concern or how to clear these? Thanks! Update 1: Correction Parity Check Completed last on 2/16 at 07:16:44 AM PST docile-diagnostics-20230217-1051.zip

Not sure if this has been noted here before but wanted to note it for myself and anyone else who comes accross it If you're trying to use MariaDB and it's just looping through the boot Verify you've named your database to photoprism, it doens't have an option for the database name but creating that database instead of what I had before resolved it.

I haven't experienced this issue after reinstalling so I'm assuming that may have resolved it.