[ZBX-23232] 6.4.5 proxies are running disabled web scenarios httptest Created: 2023 Aug 10 Updated: 2024 May 06 Resolved: 2024 Feb 01 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Proxy (P) |
Affects Version/s: | 6.4.5 |
Fix Version/s: | 6.4.12rc1, 7.0.0beta2, 7.0 (plan) |
Type: | Problem report | Priority: | Trivial |
Reporter: | bunkzilla | Assignee: | Andrejs Sitals (Inactive) |
Resolution: | Fixed | Votes: | 1 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
zabbix 6.4.5 postgresql server with zabbix proxies sqlite3 |
Issue Links: |
|
||||||||||||
Team: | |||||||||||||
Sprint: | S2401-2 | ||||||||||||
Story Points: | 1.5 |
Description |
Steps to reproduce: Result: ``` zabbix=# select hostid,name,status from httptest where hostid=61787 order by hostid; Expected: The proxy should be getting the correct status on the httptest items. In 6.0.4, the proxies only received hte httptest records it was to run. |
Comments |
Comment by bunkzilla [ 2023 Sep 21 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Is there any status on this ticket? Its now been over 1 month. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Comment by Bartosz Mickiewicz (Inactive) [ 2023 Nov 02 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Thanks for reaching Zabbix, can you check now if the proxy's DB has that webscenario entry? | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Comment by bunkzilla [ 2023 Nov 02 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
I understand what you are saying but this is on a proxy that has been running. In order to test, I stopped the proxy, removed the database, started the proxy process, and let the proxy contact the server and download the config.
From the proxy host: ==================================================================================================== All activities performed on this system will be monitored. 11/02 15:31[login_user@monproxy-dev641b:b ~]$ suod -s -bash: suod: command not found 11/02 15:31[login_user@monproxy-dev641b:b ~]$ sudo -s 11/02 15:31[root@monproxy-dev641b:b login_user]# sqlite3 /ebs/var/lib/sqlite/zabbix.db SQLite version 3.7.17 2013-05-20 00:56:22 Enter ".help" for instructions Enter SQL statements terminated with a ";" sqlite> select hostid,name,status from httptest where status = 0 ...> ; 37583|Check API Responsiveness|0 37584|Check API Responsiveness|0 74544|Monolith Health Check|0 59151|Check API Responsiveness|0 59146|Check API Responsiveness|0 59134|Check API Responsiveness|0 59201|Check API Responsiveness|0 37594|Check API Responsiveness|0 37595|Check API Responsiveness|0 59141|Check API Responsiveness|0 37582|Check API Responsiveness|0 74784|Monolith Health Check|0 59050|Check API Responsiveness|0 76886|{HOSTNAME} Status|0 74474|Monolith Health Check|0 37585|Check API Responsiveness|0 76885|{HOSTNAME} Status|0 76887|{HOSTNAME} Status|0 59149|Check API Responsiveness|0 78252|Check API Responsiveness|0 78256|Monolith Health Check|0 78260|Monolith Health Check|0 78366|Monolith Health Check|0 78369|Monolith Health Check|0 79687|Monolith Health Check|0 79688|Monolith Health Check|0 69779|Check API Responsiveness|0 69777|Check API Responsiveness|0 75350|Check API Responsiveness|0 69780|Check API Responsiveness|0 69778|Check API Responsiveness|0 75349|Check API Responsiveness|0 80617|Check API Responsiveness|0 80603|Check API Responsiveness|0 80600|Check API Responsiveness|0 80601|Check API Responsiveness|0 80604|Check API Responsiveness|0 80597|Monolith Health Check|0 83398|Monolith Health Check|0 83423|{HOSTNAME} Status|0 83422|{HOSTNAME} Status|0 83443|{HOSTNAME} Status|0 61669|Monolith Health Check|0 85041|Monolith Health Check|0 85042|Monolith Health Check|0 85043|Monolith Health Check|0 80409|Check API Responsiveness|0 80408|Check API Responsiveness|0 80406|Check API Responsiveness|0 83403|Monolith Health Check|0 81404|Monolith Health Check|0 61673|Monolith Health Check|0 87127|Monolith Health Check|0 80420|Check API Responsiveness|0 88527|{HOSTNAME} Status|0 88528|{HOSTNAME} Status|0 88529|{HOSTNAME} Status|0 88632|Monolith Health Check|0 90343|Monolith Health Check|0 74482|Monolith Health Check|0 77578|Monolith Health Check|0 91223|Monolith Health Check|0 sqlite> quit ...> Error: incomplete SQL: quit 11/02 15:33[root@monproxy-dev641b:b login_user]# systemctl stop zabbix-proxy.service 11/02 15:33[root@monproxy-dev641b:b login_user]# set -o vi 11/02 15:33[root@monproxy-dev641b:b login_user]# 11/02 15:33[root@monproxy-dev641b:b login_user]# rm -fr /ebs/var/lib/sqlite/zabbix.db 11/02 15:34[root@monproxy-dev641b:b login_user]# ls -al /ebs/var/lib/sqlite/zabbix.db ls: cannot access /ebs/var/lib/sqlite/zabbix.db: No such file or directory 11/02 15:34[root@monproxy-dev641b:b login_user]# systemctl start zabbix-proxy.service 11/02 15:34[root@monproxy-dev641b:b login_user]# ls -al /ebs/var/lib/sqlite/zabbix.db -rw-r--r--. 1 zabbix zabbix 800768 Nov 2 15:34 /ebs/var/lib/sqlite/zabbix.db 11/02 15:34[root@monproxy-dev641b:b login_user]# ls -al /ebs/var/lib/sqlite/zabbix.db -rw-r--r--. 1 zabbix zabbix 2018304 Nov 2 15:34 /ebs/var/lib/sqlite/zabbix.db 11/02 15:34[root@monproxy-dev641b:b login_user]# tail -f /var/log/zabbix/zabbix_proxy.log 31905:20231102:153422.977 proxy #68 started [icmp pinger #14] 31879:20231102:153422.978 proxy #45 started [unreachable poller #1] 31906:20231102:153422.982 proxy #69 started [icmp pinger #15] 31907:20231102:153422.982 proxy #70 started [icmp pinger #16] 31908:20231102:153422.983 proxy #71 started [icmp pinger #17] 31885:20231102:153422.984 proxy #51 started [unreachable poller #7] 31886:20231102:153422.990 proxy #52 started [unreachable poller #8] 31909:20231102:153422.997 proxy #72 started [icmp pinger #18] 31910:20231102:153423.000 proxy #73 started [icmp pinger #19] 31825:20231102:153424.970 received configuration data from server at "monapp20b.aue1t.internal", datalen 6349106 31833:20231102:153431.162 slow query: 5.155432 sec, "select nextid from ids where table_name='proxy_history' and field_name='history_lastid'" ^C 11/02 15:34[root@monproxy-dev641b:b login_user]# sqlite3 /ebs/var/lib/sqlite/zabbix.db SQLite version 3.7.17 2013-05-20 00:56:22 Enter ".help" for instructions Enter SQL statements terminated with a ";" sqlite> select hostid,name,status from httptest where status = 0 ...> ; 80420|Check API Responsiveness|0 81404|Monolith Health Check|0 37583|Check API Responsiveness|0 87127|Monolith Health Check|0 37584|Check API Responsiveness|0 80617|Check API Responsiveness|0 83423|{HOSTNAME} Status|0 74544|Monolith Health Check|0 78252|Check API Responsiveness|0 59151|Check API Responsiveness|0 59146|Check API Responsiveness|0 80603|Check API Responsiveness|0 59134|Check API Responsiveness|0 69779|Check API Responsiveness|0 59201|Check API Responsiveness|0 78256|Monolith Health Check|0 85043|Monolith Health Check|0 61669|Monolith Health Check|0 37594|Check API Responsiveness|0 88529|{HOSTNAME} Status|0 69777|Check API Responsiveness|0 37595|Check API Responsiveness|0 75350|Check API Responsiveness|0 59141|Check API Responsiveness|0 37582|Check API Responsiveness|0 80600|Check API Responsiveness|0 75349|Check API Responsiveness|0 88632|Monolith Health Check|0 74784|Monolith Health Check|0 59050|Check API Responsiveness|0 83403|Monolith Health Check|0 78366|Monolith Health Check|0 80409|Check API Responsiveness|0 69780|Check API Responsiveness|0 77578|Monolith Health Check|0 83398|Monolith Health Check|0 78260|Monolith Health Check|0 80597|Monolith Health Check|0 80406|Check API Responsiveness|0 76886|{HOSTNAME} Status|0 74474|Monolith Health Check|0 80601|Check API Responsiveness|0 80408|Check API Responsiveness|0 79687|Monolith Health Check|0 88528|{HOSTNAME} Status|0 85042|Monolith Health Check|0 37585|Check API Responsiveness|0 85041|Monolith Health Check|0 88527|{HOSTNAME} Status|0 74482|Monolith Health Check|0 76885|{HOSTNAME} Status|0 76887|{HOSTNAME} Status|0 80604|Check API Responsiveness|0 61673|Monolith Health Check|0 69778|Check API Responsiveness|0 78369|Monolith Health Check|0 79688|Monolith Health Check|0 91223|Monolith Health Check|0 83422|{HOSTNAME} Status|0 59149|Check API Responsiveness|0 90343|Monolith Health Check|0 83443|{HOSTNAME} Status|0 sqlite> select hostid,name,status from httptest where hostid = 37583 ; 37583|Check API Responsiveness|0 sqlite> select hostid,name,status from httptest where hostid = 37584 ; 37584|Check API Responsiveness|0 sqlite> 11/02 15:36[root@monproxy-dev641b:b login_user]# sqlite3 /ebs/var/lib/sqlite/zabbix.db SQLite version 3.7.17 2013-05-20 00:56:22 Enter ".help" for instructions Enter SQL statements terminated with a ";" sqlite> select hostid,httptestid,name,status from httptest where hostid = 37584 ; 37584|13644|Check API Responsiveness|0 sqlite> select hostid,httptestid,name,status from httptest where hostid = 37583 ; 37583|13643|Check API Responsiveness|0 sqlite>
from the database server where it shows the zabbix=# zabbix=# select hostid,httptestid,name,status from httptest where hostid=37584 order by hostid; hostid | httptestid | name | status --------+------------+--------------------------+-------- 37584 | 13644 | Check API Responsiveness | 1 (1 row)zabbix=# select hostid,httptestid,name,status from httptest where hostid=37583 order by hostid; hostid | httptestid | name | status --------+------------+--------------------------+-------- 37583 | 13643 | Check API Responsiveness | 1 (1 row)zabbix=# | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Comment by Thiago Melo [ 2024 Jan 23 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Hello, Im experiencing the same issue with Zabbix Server and Zabbix Proxy 6.4.6 and MySQL 8.0 We already dropped zabbix proxy database but it come back as enabled. The only workaround that solved was go directly to zabbix proxy database and update scenario to status=1
It looks like Zabbix Proxy didnt get status from Zabbix Server, and as Default Status is 0, looks like zabbix proxy add scenario to DB and DB fill value as 0.
desc httptest;
-----------------
-----------------
Best Regards
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Comment by Andrejs Sitals (Inactive) [ 2024 Jan 31 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Available in versions:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Comment by Andrejs Sitals (Inactive) [ 2024 Mar 07 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Unfortunately this fix broke compatibility between older proxies and newer servers (and the other way around - between newer proxies and older servers), resulting in When web scenarios are used, 6.4.12 proxies work only with 6.4.12 server.
|