[zabbix-community/zabbix] wrong value of "StartJavaPollers" in config file

[alex-vyverman]

Describe the bug
When zabbixJavaGateway is set to enabled: false, the env var - name: ZBX_STARTJAVAPOLLERS has no value, and creates an error wrong value of "StartJavaPollers" in config file

Version of Helm and Kubernetes:
helm v3.16.3
k3s v1.30.6+k3s1

Anything else we need to know:
zabbixImageTag: ubuntu-7.2-latest was set in zabbix-values.yaml

Adding for example

- name: ZBX_STARTJAVAPOLLERS 
  value: "0"

in the deployment works around the issue

[fibbs]

There was a recent change in the docker images of Zabbix as of 7.2: the config files of Zabbix now support using environment variables inside them, natively and the guys maintaining the container images have changed the structure of the config file and the docker-entrypoint.sh accordingly and just recently: now the docker-entrypoint.sh does not try to set all the config variables in the file (/etc/zabbix/zabbix_server.conf) by the according env variables, and the config file of zabbix server is split into several configuration files.

Nevertheless, I can not reproduce the error you reported. As in such case it would indeed be a bug in the zabbix docker image, documenting that it is not necessary to supply ZBX_STARTJAVAPOLLERS to be set to "0" when no java pollers should be started, I have chosen simple docker commands to verify:

docker run -d --name postgres -e POSTGRES_PASSWORD=zabbix123 -e POSTGRES_DB=zabbix -e POSTGRES_USER=zabbix postgres:16
docker run -ti --rm --name zabbix -e DB_SERVER_HOST=postgres -e DB_SERVER_DBNAME=zabbix -e POSTGRES_USER=zabbix -e POSTGRES_PASSWORD=zabbix123 --link postgres:postgres zabbix/zabbix-server-pgsql:ubuntu-7.2-latest

...and Zabbix Server starts just nicely, without supplying the above mentioned variable set to "0".

May it be there have been a temporary broken image provided by Zabbix? Can you confirm that it's not (anymore?) a problem?

[fibbs]

OK, I have to apologize! Actually, there is a bug in the Helm Chart causing to render the deployment manifest this way:

...
      - env:
      ...
        - name: ZBX_JAVAGATEWAYPORT
          value: "10052"
        - name: ZBX_STARTJAVAPOLLERS
        - name: ZBX_WEBDRIVERURL
          value: http://zabbix-chrome:4444

which causes the error reported by you. I am working on a bigger Pull Request right now and I will fix this issue there.