fping: Cannot allocate memory

[heath]

Hi, I'm a beginner to Zabbix
I deployed Zabbix with docker-compose and see these msgs from server log
What cause and how to solve this?

[vladimir_lv]

Looks like you have to increase the server memory.

[tim.mooney]

Hi, I'm a beginner to Zabbix
I deployed Zabbix with docker-compose and see these msgs from server log
What cause and how to solve this?

I'm not using the docker images for my site's Zabbix install so it's not clear to me: is fping inside one of the docker containers, or is it installed on your OS?

I ask because some distros don't install fping setuid root or with the necessary capabilities(5) to allow it to work correctly unless it's run by the root user. Since the Zabbix install runs as a non-privileged user, fping may not have the necessary access it needs.

If fping is part of your distro and not part of the Docker container, you probably need to look into what the best way is to give it the capabilities it needs for your distro.

[heath]

Looks like you have to increase the server memory.

Assigned 8GB memory to server container. And I run

docker stat

, memory is enough

[heath]

I'm not using the docker images for my site's Zabbix install so it's not clear to me: is fping inside one of the docker containers, or is it installed on your OS?

I ask because some distros don't install fping setuid root or with the necessary capabilities(5) to allow it to work correctly unless it's run by the root user. Since the Zabbix install runs as a non-privileged user, fping may not have the necessary access it needs.

If fping is part of your distro and not part of the Docker container, you probably need to look into what the best way is to give it the capabilities it needs for your distro.

Thx for your reply, fping is inside server container

[juniorogs]

health, did you manage to solve this problem? recently i've got upgraded from 5.0 to 6.0 using zabbix-docker image and im having the same scenario as you described.

[zkry.akgul]

Hi, did you guys find any solution about this issue? Im using zabbix 6.2 inside the docker container and im facing the exact same issue in my setup.

[juniorogs]

Hi, did you guys find any solution about this issue? Im using zabbix 6.2 inside the docker container and im facing the exact same issue in my setup.

Hi,

While I was doing the tests, I ran zabbix docker in another instance (with a newer S.O Version) and it didn't show these errors.. I believe it may be something related to some configuration or limitation of the operating system that runs docker, or either the docker version installed, but I still don't have any conclusions about it.

A workaround suggestion is to try to run it in another instance with another version of the linux distribution, a newer or a different one.

[FabrizioA]

You can resolve this problem by run container in privileged mode.
You can edit your compose's yaml file as something like this:

web:
image: an_image-image:1.0
container_name: my-container
privileged: true
entrypoint: ["/usr/sbin/init"]
ports:
- "8280:8280"