search

imTHAI / adguardhome-unbound-redis

5 stars 0 forks source link

Log: "# WARNING Memory overcommit must be enabled!" #2

Open Bristopher opened 4 weeks ago

Bristopher commented 4 weeks ago

Just installed and noticed in the ReadMe "AdGuard DNS filter , HaGeZi's Threat Intelligence Feeds Blocklist, and HaGeZi's Multi Pro DNS Blocklist" are supposed to be enabled but only AdGuard DNS filter is listed/enabled. If I try to add them the blocklists just loads forever and I get this error in logs.

7:C 21 Oct 2024 18:54:02.116 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.

Edit: If I wait a long time they finally load but either way they aren't enabled by default and overcommit_memory isn't enabled by default if it should be. Also permissions set it so no user groups can access the config folder so it doesn't work over smb and changing any permissions get reset every time the container is ran. feel free to close if this is known or doesn't matter.

~~Edit2: Fix for smb perms until the dockerfile is edited, add this to the Unraid Container settings Post Arguments: chmod -R g+rwX /config~~ This work but can get docker to start after it, and when I do I can't get the perms to be correct oh well

Trustwbc commented 4 weeks ago

try to delete the Docker / Image and Reinstall again with a new IP. i had the same Problem when i try to install this Docker to an IP that was first reserved by an other Instance of AGH (that i deleted bevore).

Bristopher commented 4 weeks ago

try to delete the Docker / Image and Reinstall again with a new IP. i had the same Problem when i try to install this Docker to an IP that was first reserved by an other Instance of AGH (that i deleted bevore).

Thanks, It seems to have worked for the block list but I still get the "# WARNING Memory overcommit must be enabled!" and still don't have access to the files over smb (unless I add the Post Arg from Edit2).

I believe the dockerfile needs a user set, or PUID PGUID environmental variables so they can be set in the Unraid docker template.

imTHAI commented 4 weeks ago

Hello, This message comes from Redis as you might expect. I think it's a parameter that can be set only at the host level (so the unraid server itself). vm.overcommit_memory = 1 in the /etc/sysctl.conf or the command sysctl vm.overcommit_memory=1

If you install the official Redis docker, from the CA, you'll get the same error message. So in my opinion, if it was fixable, they would have done it for their own docker. Or maybe it's possible to set it from the container, if it runs in privileged mode ? I'll try to do some tests when I have some time.

Bristopher commented 4 weeks ago

Hello, This message comes from Redis as you might expect. I think it's a parameter that can be set only at the host level (so the unraid server itself). vm.overcommit_memory = 1 in the /etc/sysctl.conf or the command sysctl vm.overcommit_memory=1

If you install the official Redis docker, from the CA, you'll get the same error message. So in my opinion, if it was fixable, they would have done it for their own docker. Or maybe it's possible to set it from the container, if it runs in privileged mode ? I'll try to do some tests when I have some time.

Ah ok gotcha nvm then, only thing of concern is perms then