-
Incident report
-
Resolution: False Positive
-
Trivial
-
None
-
7.2.1
-
None
Steps to reproduce:
- Use latest docker container for Zabbix Proxy MySQL with alpine linux "zabbix/zabbix-proxy-mysql:alpine-7.2-latest"
- Start Proxy server, logs will show "cannot open file "zbx-psk.key": [2] No such file or directory"
- Roll Back to image: zabbix/zabbix-proxy-mysql:7.2.0-alpine
- Zabbix proxy is able to load psk encryption key "zbx-psk.key" without any configuration changes to docker compose.
Result:
Unable to load "[2] No such file or directory"
Expected:
Zabbix Proxy to load encryption key file
This was not present in Zabbix Proxy MySQL 7.2.1 docker image published 2024-12-22, but is affecting docker image downloaded using the latest tag on 30.12.2024 ([Image Layer Details - zabbix/zabbix-proxy-mysql:7.2-alpine-latest | Docker Hub|https://hub.docker.com/layers/zabbix/zabbix-proxy-mysql/7.2-alpine-latest/images/sha256-3d9e58dede31aa6d29afcc422562b7ce6b107e91ee5037b4cfba5e15af9b5c6a]).
Some Logs to back things up:
** Preparing Zabbix proxy ** Preparing database ** Using MYSQL_USER variable from ENV ** Using MYSQL_PASSWORD variable from ENV ******************** * DB_SERVER_HOST: zbx-proxy-mysql * DB_SERVER_PORT: 3306 * DB_SERVER_DBNAME: zabbix_proxy ******************** ** Database 'zabbix_proxy' already exists. Please be careful with database COLLATE! ** Table 'zabbix_proxy.dbversion' already exists. Starting Zabbix Proxy (active) [zbx-proxy1.null-byte.local]. Zabbix 7.2.1 (revision 67f3c83). Press Ctrl+C to exit. 1:20241230:110917.541 Starting Zabbix Proxy (active) [zbx-proxy1.null-byte.local]. Zabbix 7.2.1 (revision 67f3c83). 1:20241230:110917.541 **** Enabled features **** 1:20241230:110917.541 SNMP monitoring: YES 1:20241230:110917.541 IPMI monitoring: YES 1:20241230:110917.542 Web monitoring: YES 1:20241230:110917.542 VMware monitoring: YES 1:20241230:110917.542 ODBC: YES 1:20241230:110917.542 SSH support: YES 1:20241230:110917.542 IPv6 support: YES 1:20241230:110917.542 TLS support: YES 1:20241230:110917.542 ************************** 1:20241230:110917.542 using configuration file: /etc/zabbix/zabbix_proxy.conf 1:20241230:110917.550 Zabbix supports only "utf8_bin,utf8mb3_bin,utf8mb4_bin" collation(s). Database "zabbix_proxy" has default collation "utf8mb4_uca1400_ai_ci" 1:20241230:110917.561 character set name or collation name that is not supported by Zabbix found in 579 column(s) of database "zabbix_proxy" 1:20241230:110917.561 only character set(s) "utf8,utf8mb3,utf8mb4" and corresponding collation(s) "utf8_bin,utf8mb3_bin,utf8mb4_bin" should be used in database 1:20241230:110917.564 current database version (mandatory/optional): 07020000/07020000 1:20241230:110917.564 required mandatory version: 07020000 1:20241230:110917.567 proxy #0 started [main process] 23:20241230:110917.568 proxy #1 started [configuration syncer #1] 23:20241230:110917.576 cannot open file "zbx-psk.key": [2] No such file or directory 1:20241230:110918.570 One child process died (PID:23,exitcode/signal:1). Exiting ... 1:20241230:110918.573 Zabbix Proxy stopped. Zabbix 7.2.1 (revision 67f3c83).