[ZBX-24681] docker "zabbix-proxy-sqlite3" v6.4.16 fails to start Created: 2024 Jun 19 Updated: 2024 Jun 19 Resolved: 2024 Jun 19 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Installation (I), Packages (C) |
| Affects Version/s: | 6.4.16 |
| Fix Version/s: | None |
| Type: | Incident report | Priority: | Trivial |
| Reporter: | Oleksii Zagorskyi | Assignee: | Zabbix Development Team |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Taking 2 version images: docker pull zabbix/zabbix-proxy-sqlite3:alpine-6.4.15 docker pull zabbix/zabbix-proxy-sqlite3:alpine-6.4.16 when run 6.4.15, it creates DB file successfully: ** Updating '/etc/zabbix/zabbix_proxy.conf' parameter "DBName": '/var/lib/zabbix/db_data/zabbix-proxy-sqlite3.sqlite'...updated ... 7:20240619:103626.716 Starting Zabbix Proxy (active) [zabbix-proxy-sqlite3]. Zabbix 6.4.15 (revision 09711f1). ... 7:20240619:103626.716 using configuration file: /etc/zabbix/zabbix_proxy.conf 7:20240619:103626.716 cannot open database file "/var/lib/zabbix/db_data/zabbix-proxy-sqlite3.sqlite": [2] No such file or directory 7:20240619:103626.716 creating database ... 7:20240619:103632.663 current database version (mandatory/optional): 06040000/06040026 but in 6.4.16 the DB file appears to be existing but invalid, so proxy fails to start: ** Updating '/etc/zabbix/zabbix_proxy.conf' parameter "DBName": '/var/lib/zabbix/db_data/zabbix-proxy-sqlite3.sqlite'...updated 7:20240619:103653.562 Starting Zabbix Proxy (active) [zabbix-proxy-sqlite3]. Zabbix 6.4.16 (revision 0bc8c62). ... 7:20240619:103653.562 using configuration file: /etc/zabbix/zabbix_proxy.conf 7:20240619:103653.564 [Z3005] query failed: [0] no such table: users [select userid from users limit 1] 7:20240619:103653.564 cannot use database "/var/lib/zabbix/db_data/zabbix-proxy-sqlite3.sqlite": database is not a Zabbix database I've tried to locate what change could cause that, but could not |
| Comments |
| Comment by Oleksii Zagorskyi [ 2024 Jun 19 ] |
|
This is broken in main stream, not in docker. Reported now in CLOSED. |