sqlite3 image for proxy broken

[Zabac7887]

Greetings

I have been struggling quite a lot trying get a a k8s proxy working recently. From what I have figured out the ONLY working image for sqlite3 is on the 7.2 trunk branch https://hub.docker.com/r/zabbix/zabbix-proxy-sqlite3 which is incompatible with any supported Zabbix server version. I attempted to update a test Zabbix server version to 7.2 but the repo link is broken for upgrade packages.

The 7.2 trunk tag does work, I can get the proxy recognized on the server but of course errors unsupported.

From the hair pulling issues I have come across this bug which is closed and fixed : https://support.zabbix.com/browse/ZBX-24682 I am unable to find a link right now but I believe that there was also a issue on this submitted around the 1st of June where it was also marked fixed.

cannot open database file "/var/lib/zabbix/db_data/zabbix-proxy.sqlite": [2] No such file or directory
creating database ...
Got signal [signal:15(SIGTERM),sender_pid:0,sender_uid:0,reaso n:0]. Exiting ...

Can someone please sanity check me on this I feel like I am missing something because the only fix to a completely broken issue like this is only applied to the latest unsupported branch for a upcoming release? I have tried every latest tag on 6x and 7x including different images than alpine, no dice.

Thank you in advance for your time.

[Markku]

The issue you linked says 6.4.17 has fixed that. Are you saying that 6.4.17 has not fixed that?

I don't know about your "PID 0 sent me a SIGTERM" error though.

Markku

[Zabac7887]

Heres another post from last month where you also responded: https://www.zabbix.com/forum/zabbix-...bix-on-aws-eks

However, it says that it's fixed in current master branch. So, do you still have to problem if you checkout the latest master?

In that post you recommended using the master (which is the alpha 7.2) a version which is incapatable with Zabbix as there is no Zabbix server 7.2

The issue you linked says 6.4.17 has fixed that. Are you saying that 6.4.17 has not fixed that?

The issue states both 6, 7, and 7.2 trunk have it fixed. Which is the two supported versions and a dev version (master)

• 6.4.17rc1 4b8f14c22a2
• 7.0.1rc1 ccce4dabb05
• 7.2.0alpha1 (master) a72b3ce849e, b005e6fcaaa

The 7.2 works, I verified it however it is incompatible with Zabbix server and the repos for Zabbix server are broken for that build.

6.4.17 does not work.: https://hub.docker.com/layers/zabbix...9a4c1e3420e94a c71daf47514aab?context=explore

7.0.1 Does not exist: https://hub.docker.com/r/zabbix/zabb...ng=&name=7.0.1

Regardless tagging the latest build does not work. IE "alpine-7.0-latest" should be pulling 7.0.1 same with 6.4. I have tried all the images. The ONLY working images is the trunks ( Zabbix proxy 7.2 ) which is unsupported.

[Markku]

Heres another post from last month where you also responded: https://www.zabbix.com/forum/zabbix-...bix-on-aws-eks
In that post you recommended using the master (which is the alpha 7.2) a version which is incapatable with Zabbix as there is no Zabbix server 7.2

Note that in that post the author specifically used the master branch (7.2.0alpha) so that's why it was reasonable to reply with hints about the latest development in it.

7.0.1 Does not exist: https://hub.docker.com/r/zabbix/zabb...ng=&name=7.0.1

7.0.1 has not been released yet, but since they are already in rc2 (and 7.0.0 has some major-ish bugs) my guess is that 7.0.1 will be out within a few days.

6.4.17 does not work.: https://hub.docker.com/layers/zabbix...9a4c1e3420e94a c71daf47514aab?context=explore

I don't do docker but the normal version works here:

6209:20240719:112426.882 Starting Zabbix Proxy (passive) [Proxy3]. Zabbix 6.4.17 (revision c12261f00b4).
6209:20240719:112426.882 **** Enabled features ****
6209:20240719:112426.882 SNMP monitoring: YES
6209:20240719:112426.883 IPMI monitoring: YES
6209:20240719:112426.883 Web monitoring: YES
6209:20240719:112426.883 VMware monitoring: YES
6209:20240719:112426.883 ODBC: YES
6209:20240719:112426.883 SSH support: YES
6209:20240719:112426.884 IPv6 support: YES
6209:20240719:112426.884 TLS support: YES
6209:20240719:112426.884 **************************
6209:20240719:112426.884 using configuration file: /etc/zabbix/zabbix_proxy.conf
6209:20240719:112426.885 cannot open database file "/var/lib/zabbix/zabbix_proxy": [2] No such file or directory
6209:20240719:112426.885 creating database ...
6209:20240719:112429.281 current database version (mandatory/optional): 06040000/06040027
6209:20240719:112429.281 required mandatory version: 06040000
6209:20240719:112429.286 proxy #0 started [main process]

Markku

[Zabac7887]

I don't do docker but the normal version works here:

Markku

Right but that has no relevance. The issue is that somewhere in the pipline changes are not being pushed to all release channels, this is a emergency change type of situation not a ... wait and see what happens on a slow release cycle. It looks like tagging latest also does not pull the latest image.

Also 6.4 while still supported is out dated and will throw warnings. Even if the image did work it would be silly to deploy a proxy environment with it. https://www.zabbix.com/documentation.../compatibility

Zabbix server is LTS 7.0 limiting the functionality of the outdated proxy....

[Markku]

Now that you said the server version that you are using, would it be possible for you to use 7.0.1rc2 compiled from sources? Or is it not possible to do without the official image when docker is used?

Markku

[Zabac7887]

Now that you said the server version that you are using, would it be possible for you to use 7.0.1rc2 compiled from sources? Or is it not possible to do without the official image when docker is used?

Markku

Respectfully, you have no idea what your talking about. Please move on.

If anyone else is listening, impressively 7x latest and others are still broken. The only working image I believe is 6.4.17 and each supported versions trunk. 6.4 is outdated in the matrix.

Revisiting this issue and from a fresh pull


using configuration file: /etc/zabbix/zabbix_proxy.conf
cannot open database file "/var/lib/zabbix/db_data/zabbix-proxy.sqlite": [2] No such file or directory
creating database ...
Got signal [signal:15(SIGTERM),sender_pid:0,sender_uid:0,reaso n:0]. Exiting ...

## Zabbix proxy Docker image name
repository: zabbix/zabbix-proxy-sqlite3
## Tag of Docker image of Zabbix proxy
tag: alpine-7.0-latest
pullPolicy: Always


There is currently no possible way to deploy a new ks/docker environment to be monitored for the last 3 months or so.

[Markku]

Linking back your issue for those that "have idea": https://support.zabbix.com/browse/ZBX-25109

Markku

[Zabac7887]

This issue is now resolved for the 7.X branch with this update: https://hub.docker.com/layers/zabbix...ontext=explore