5252525111

It's a large container. it is normal. code project will report it is communicating on port 32168, but if you changed the port in the docker edit tab that is the port your unraid machine will be communicating to point to that container. For the mesh you'll likely need to change from bridge to a different network. the issue is that the container is on it's own network I havn't tried but host may work. What i did tog et it to work for me was switch to custom network BR0 and gave it a static ip, and had my router assign it the same ip then the mesh worked.

For those running CP.AI using the gpu docker container. It seems like CP hasn't been building it for about 5 months. What you can do is change it to a cuda container and have the latest version. Simply update `codeproject/ai-server:gpu` to one of the following depending on your GPUs capabilities. - `codeproject/ai-server:cuda11_7` - `codeproject/ai-server:cuda12_2`

You need to create a new variable in your configuration, click `add another path, port, variable, label or device` and choose `variable` set key to `NODE_ENV` and value to `production` and it should work after that.

Change setting under 'Settings > Global Shares Settings' look for Tunable (support Hard Links): and set it to No.

So far it's holding up well. I'm having new issues with NFS but don't think that's related to this at all. Long story short, no more panics. That was one of the main fixes for me. I used a range outside my DHCP and reserve that for containers on unraid. If I recall correctly since I currently don't have access to my system, 100-223 is my LAN range, 50-99 I used for static and 224-255 (192.168.99.224/27) I reserve for containers on unraid.

Sadly I use NFS everyday. Will see if I can find an alternative for my other devices. I'll look into what limetech suggested and set "Settings/NFS/Tunable (fuse remember)" to 0.

adding latest log. tatooine-diagnostics-20211006-2222.zip

noticed this. Not sure what would cause this to happen. d????????? ? ? ? ? ? user/ drwxrwxrwx 1 nobody users 71 Oct 6 16:15 user0/

I've attached my logs in hopes someone can help. 30 days is the most I've ever managed to get unraid to not crash. But the past couple days I've gone back to daily crashes. This time it seems to crash my shares and containers but the gui is still responsive. After a reboot everything is fine again. No hardware changes or new software I can think of. From my limited understanding, the logs are saying the docker network crashed? Any advise is much appreciated. EDIT: Updated title from "6.9.2 I've been running stable for 30days and now daily crashes." to "6.9.2 30 days stable, suddenly unraid unmounts /mnt/user" tatooine-diagnostics-20211005-1600.zip

I believe you need to add the following to your nginx config # Make a regex exception for `/.well-known` so that clients can still # access it despite the existence of the regex rule # `location ~ /(\.|autotest|...)` which would otherwise handle requests # for `/.well-known`. location ^~ /.well-known { # The following 6 rules are borrowed from `.htaccess` location = /.well-known/carddav { return 301 /remote.php/dav/; } location = /.well-known/caldav { return 301 /remote.php/dav/; } # Anything else is dynamically handled by Nextcloud location ^~ /.well-known { return 301 /index.php$uri; } try_files $uri $uri/ =404; } See documentation https://docs.nextcloud.com/server/21/admin_manual/installation/nginx.html and also https://docs.nextcloud.com/server/21/admin_manual/issues/general_troubleshooting.html#service-discovery

started happening to me today as well. Have to turn it off for the time being.

Every time I search this issue, I come right back to this post. I MAY have found the solution and hope it may help someone else. I'll preface this first. I've been having this issue for months. On average I would crash 3-4 days, and once I made it to 5 only to be let down again. At time of writing this it marks my 10th day stable, which is no major milestone but looks promising. I made a few changes at once and I'm not sure which one fixed it so I'll write them all down. I noticed we had the same switch, the Mikrotik CRS312-4C+8XG-RM. My first change was here, under the link tab I disabled (unchecked) all "Flow Control Tx/Rx" from unraid ports. I don't know why this was enabled by default but unless you need it, disable it. In unraid I made changes to my network settings. The `nf_nat_setup_info` issue when doing research is network related. after digging in non unraid specific issues it seems to be a wide range of things. Settings> Network Settings My main network in unraid was let mostly unchanged. I assigned a static IP in unraid, matching the static mapping on my router. If you have VLans on your main network it seems that unraid broadcasts the vlans with the same mac and can cause confusion for your router. I set all vlans on this network to not get auto assigned IP. Note, if you are using bridge network on this vlan you'll have to have an ip. I followed a guide to set this up. https://staging.forums.unraid.net/topic/62107-network-isolation-in-unraid-64/?ct=1612387651 Settings > Docker This is the one I truly believe may have fixed the issue. One of the issues I've read is that the docker service assigns an ip address to containers that are in use by something else on your network.... or something along those lines. So you should be setting a range that your router doesn't use and have your docker service run in that range. To do this set enable docker to no and apply change. Once your containers are turned off make sure you're in advanced view. You'll see check boxes for custom network. for each of those enabled you'll want to set a DHCP range. So lets say on your router you isolate 192.168.1.128 to 192.168.1.159 which is br0 you can write the CIDR as 192.168.1.128/27 (you can do CIDR transitions at this site https://www.ipaddressguide.com/cidr). Hopefully those make sense. Figured I'd share, in hopes this is the solution and possibly help someone else out there. If I crash again I'll update this to let other know. If something above is not clear let me know I'll try to clarify. This is mostly new to me.

Will we be getting the emergency release update soon? https://mariadb.org/mariadb-10-5-8-10-4-17-10-3-27-and-10-2-36-now-available/ Also thanks for all the hard work supporting this!

For anyone else getting this, seems to be mariadb. https://jira.mariadb.org/browse/MDEV-24121 Looks like they resolved the issue but the version with the solution has not been pushed to docker hub yet.

Been getting this error for the past couple days, not sure if it was from the snipe-it or mariabd update. D'oh! Looks like we can't connect to your database. Please update your database settings in your .env file. Your database says: SQLSTATE[HY000]: General error: 1835 Malformed communication packet (SQL: select 2 + 2) Any suggestions?

^^ glad I'm not the only one 😅

Humm... but the latest patch says to move to v4 and they've changed the projects default branch. I hope they merge down to master/main.

there was an update to the docker sample you linked. maybe you docker make file needs the same updates. https://github.com/open-eats/OpenEats/pull/85/commits/ccfb9c30b058664b8033d3049a2ecb2e26edd9f6

Not sure if people are still interested. But you can do the snippet below to restart all running docker containers. ```` docker restart $(docker ps -q) ````