Hello Zabbix Community,
I'm encountering an issue while deploying an active Zabbix proxy in a Kubernetes environment to monitor equipment for a support company. I'm using the zabbix-proxy-sqlite3: ol-6.2.9 Docker image. The proxy pod fails shortly after receiving the configuration from the Zabbix server.
Here are the relevant logs:
1:20250316:110246.430 Starting Zabbix Proxy (active) [zpx-foo]. Zabbix 6.2.9 (revision 886cdd0).
1:20250316:110246.430 **** Enabled features ****
1:20250316:110246.430 SNMP monitoring: YES
1:20250316:110246.430 IPMI monitoring: YES
1:20250316:110246.430 Web monitoring: YES
1:20250316:110246.430 VMware monitoring: YES
1:20250316:110246.430 ODBC: YES
1:20250316:110246.430 SSH support: YES
1:20250316:110246.430 IPv6 support: YES
1:20250316:110246.430 TLS support: YES
1:20250316:110246.430 **************************
1:20250316:110246.430 using configuration file: /etc/zabbix/zabbix_proxy.conf
1:20250316:110246.431 cannot open database file "/var/lib/zabbix/db_data/zpx-foo.sqlite": [2] No such file or directory
1:20250316:110246.431 creating database ...
1:20250316:110246.886 current database version (mandatory/optional): 06020000/06020016
1:20250316:110246.886 required mandatory version: 06020000
1:20250316:110246.891 proxy #0 started [main process]
222:20250316:110246.892 proxy #1 started [configuration syncer #1]
223:20250316:110246.907 proxy #2 started [trapper #1]
225:20250316:110246.908 proxy #4 started [trapper #3]
226:20250316:110246.909 proxy #5 started [trapper #4]
227:20250316:110246.913 proxy #6 started [trapper #5]
232:20250316:110246.916 proxy #11 started [heartbeat sender #1]
224:20250316:110246.918 proxy #3 started [trapper #2]
228:20250316:110246.918 proxy #7 started [preprocessing manager #1]
248:20250316:110246.919 proxy #27 started [unreachable poller #1]
247:20250316:110246.922 proxy #26 started [poller #5]
251:20250316:110246.923 proxy #30 started [odbc poller #1]
233:20250316:110246.926 proxy #12 started [data sender #1]
234:20250316:110246.927 proxy #13 started [housekeeper #1]
250:20250316:110246.931 proxy #29 started [availability manager #1]
236:20250316:110246.932 proxy #15 started [discoverer #1]
237:20250316:110246.933 proxy #16 started [history syncer #1]
238:20250316:110246.934 proxy #17 started [history syncer #2]
240:20250316:110246.935 proxy #19 started [history syncer #4]
243:20250316:110246.936 proxy #22 started [poller #1]
235:20250316:110246.937 proxy #14 started [http poller #1]
242:20250316:110246.937 proxy #21 started [task manager #1]
239:20250316:110246.937 proxy #18 started [history syncer #3]
241:20250316:110246.938 proxy #20 started [self-monitoring #1]
244:20250316:110246.939 proxy #23 started [poller #2]
245:20250316:110246.945 proxy #24 started [poller #3]
249:20250316:110246.945 proxy #28 started [icmp pinger #1]
246:20250316:110246.945 proxy #25 started [poller #4]
230:20250316:110247.012 proxy #9 started [preprocessing worker #2]
231:20250316:110247.013 proxy #10 started [preprocessing worker #3]
229:20250316:110247.016 proxy #8 started [preprocessing worker #1]
222:20250316:110247.108 received configuration data from server at "externalzabbixserver", datalen 317445
1:20250316:110247.568 One child process died (PID:25,exitcode/signal:0). Exiting ...
1:20250316:110247.980 PROCESS EXIT: 25
1:20250316:110247.995 Zabbix Proxy stopped. Zabbix 6.2.9 (revision 886cdd0).
The error message cannot open database file "/var/lib/zabbix/db_data/zpx-foo.sqlite": [2] No such file or directory followed by the database creation seems normal. However, the proxy pod exits shortly after receiving the configuration data from the server.
We are running this Zabbix proxy in a Kubernetes environment. Has anyone encountered this issue before, or do you have any suggestions for troubleshooting in a Kubernetes context?
Thank you for your assistance.
I'm encountering an issue while deploying an active Zabbix proxy in a Kubernetes environment to monitor equipment for a support company. I'm using the zabbix-proxy-sqlite3: ol-6.2.9 Docker image. The proxy pod fails shortly after receiving the configuration from the Zabbix server.
Here are the relevant logs:
1:20250316:110246.430 Starting Zabbix Proxy (active) [zpx-foo]. Zabbix 6.2.9 (revision 886cdd0).
1:20250316:110246.430 **** Enabled features ****
1:20250316:110246.430 SNMP monitoring: YES
1:20250316:110246.430 IPMI monitoring: YES
1:20250316:110246.430 Web monitoring: YES
1:20250316:110246.430 VMware monitoring: YES
1:20250316:110246.430 ODBC: YES
1:20250316:110246.430 SSH support: YES
1:20250316:110246.430 IPv6 support: YES
1:20250316:110246.430 TLS support: YES
1:20250316:110246.430 **************************
1:20250316:110246.430 using configuration file: /etc/zabbix/zabbix_proxy.conf
1:20250316:110246.431 cannot open database file "/var/lib/zabbix/db_data/zpx-foo.sqlite": [2] No such file or directory
1:20250316:110246.431 creating database ...
1:20250316:110246.886 current database version (mandatory/optional): 06020000/06020016
1:20250316:110246.886 required mandatory version: 06020000
1:20250316:110246.891 proxy #0 started [main process]
222:20250316:110246.892 proxy #1 started [configuration syncer #1]
223:20250316:110246.907 proxy #2 started [trapper #1]
225:20250316:110246.908 proxy #4 started [trapper #3]
226:20250316:110246.909 proxy #5 started [trapper #4]
227:20250316:110246.913 proxy #6 started [trapper #5]
232:20250316:110246.916 proxy #11 started [heartbeat sender #1]
224:20250316:110246.918 proxy #3 started [trapper #2]
228:20250316:110246.918 proxy #7 started [preprocessing manager #1]
248:20250316:110246.919 proxy #27 started [unreachable poller #1]
247:20250316:110246.922 proxy #26 started [poller #5]
251:20250316:110246.923 proxy #30 started [odbc poller #1]
233:20250316:110246.926 proxy #12 started [data sender #1]
234:20250316:110246.927 proxy #13 started [housekeeper #1]
250:20250316:110246.931 proxy #29 started [availability manager #1]
236:20250316:110246.932 proxy #15 started [discoverer #1]
237:20250316:110246.933 proxy #16 started [history syncer #1]
238:20250316:110246.934 proxy #17 started [history syncer #2]
240:20250316:110246.935 proxy #19 started [history syncer #4]
243:20250316:110246.936 proxy #22 started [poller #1]
235:20250316:110246.937 proxy #14 started [http poller #1]
242:20250316:110246.937 proxy #21 started [task manager #1]
239:20250316:110246.937 proxy #18 started [history syncer #3]
241:20250316:110246.938 proxy #20 started [self-monitoring #1]
244:20250316:110246.939 proxy #23 started [poller #2]
245:20250316:110246.945 proxy #24 started [poller #3]
249:20250316:110246.945 proxy #28 started [icmp pinger #1]
246:20250316:110246.945 proxy #25 started [poller #4]
230:20250316:110247.012 proxy #9 started [preprocessing worker #2]
231:20250316:110247.013 proxy #10 started [preprocessing worker #3]
229:20250316:110247.016 proxy #8 started [preprocessing worker #1]
222:20250316:110247.108 received configuration data from server at "externalzabbixserver", datalen 317445
1:20250316:110247.568 One child process died (PID:25,exitcode/signal:0). Exiting ...
1:20250316:110247.980 PROCESS EXIT: 25
1:20250316:110247.995 Zabbix Proxy stopped. Zabbix 6.2.9 (revision 886cdd0).
The error message cannot open database file "/var/lib/zabbix/db_data/zpx-foo.sqlite": [2] No such file or directory followed by the database creation seems normal. However, the proxy pod exits shortly after receiving the configuration data from the server.
We are running this Zabbix proxy in a Kubernetes environment. Has anyone encountered this issue before, or do you have any suggestions for troubleshooting in a Kubernetes context?
Thank you for your assistance.