zabbix-proxy.JPG
zabbix-server.JPG
[ZBX-14762] failed to update local proxy configuration copy: unexpected field "hosts.available" Created: 2018 Aug 23 Updated: 2018 Oct 26 Resolved: 2018 Aug 27 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Proxy (P), Server (S) |
| Affects Version/s: | 3.4.12 |
| Fix Version/s: | None |
| Type: | Incident report | Priority: | Blocker |
| Reporter: | Stevel | Assignee: | Unassigned |
| Resolution: | Won't fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
zabbix-proxy.JPG
zabbix-server.JPG
|
| Description |
|
Steps to reproduce:
Result: And then hosts are not found and no active check are listed |
| Comments |
| Comment by Edgar Akhmetshin [ 2018 Aug 23 ] |
|
Hello, Stevel Is this a new installation or was it updated? What kind of database is used for the Zabbix Proxy? Regards, |
| Comment by Stevel [ 2018 Aug 23 ] |
|
Hi Edgar, It is a new proxy, the db is mysql |
| Comment by Edgar Akhmetshin [ 2018 Aug 23 ] |
|
Please, show output from the following commands: zabbix_proxy -V zabbix_server -V Also provide log file from the Zabbix Proxy containing starting lines of the Zabbix Proxy process. Regards, |
| Comment by Stevel [ 2018 Aug 23 ] |
863:20180823:141315.319 Starting Zabbix Proxy (active) [Zabbix_proxy_******]. Zabbix 3.4.12 (revision 83229). 863:20180823:141315.320 **** Enabled features **** 863:20180823:141315.320 SNMP monitoring: YES 863:20180823:141315.320 IPMI monitoring: YES 863:20180823:141315.320 Web monitoring: YES 863:20180823:141315.320 VMware monitoring: YES 863:20180823:141315.320 ODBC: YES 863:20180823:141315.320 SSH2 support: YES 863:20180823:141315.320 IPv6 support: YES 863:20180823:141315.320 TLS support: YES 863:20180823:141315.320 ************************** 863:20180823:141315.320 using configuration file: /etc/zabbix/zabbix_proxy.conf 863:20180823:141315.406 [Z3001] connection to database 'zabbix_proxy' failed: [2002] Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) 863:20180823:141315.406 database is down: reconnecting in 10 seconds 863:20180823:141325.451 database connection re-established 863:20180823:141325.634 current database version (mandatory/optional): 03040000/03040007 863:20180823:141325.634 required mandatory version: 03040000 863:20180823:141325.861 proxy #0 started [main process] 1214:20180823:141325.870 proxy #3 started [data sender #1|#1] 1215:20180823:141325.872 proxy #4 started [housekeeper #1|#1] 1212:20180823:141325.872 proxy #1 started [configuration syncer #1|#1] 1216:20180823:141325.878 proxy #5 started [http poller #1|#1] 1213:20180823:141325.879 proxy #2 started [heartbeat sender #1|#1] 1217:20180823:141325.881 proxy #6 started [discoverer #1|#1] 1218:20180823:141325.886 proxy #7 started [history syncer #1|#1] 1219:20180823:141325.887 proxy #8 started [history syncer #2|#2] 1220:20180823:141325.888 proxy #9 started [history syncer #3|#3] 1221:20180823:141325.889 proxy #10 started [history syncer #4|#4] 1222:20180823:141325.889 proxy #11 started [java poller #1|#1] 1223:20180823:141325.894 proxy #12 started [java poller #2|#2] 1224:20180823:141325.896 proxy #13 started [java poller #3|#3] 1225:20180823:141325.902 proxy #14 started [java poller #4|#4] 1226:20180823:141325.911 proxy #15 started [java poller #5|#5] 1227:20180823:141325.915 proxy #16 started [snmp trapper #1|#1] 1228:20180823:141325.924 proxy #17 started [self-monitoring #1|#1] 1240:20180823:141325.940 proxy #19 started [poller #1|#1] 1241:20180823:141325.948 proxy #20 started [poller #2|#2] 1227:20180823:141325.950 cannot stat SNMP trapper file "/var/log/snmptrap/snmptrap.log": [2] No such file or directory 1242:20180823:141325.959 proxy #21 started [poller #3|#3] 1243:20180823:141325.966 proxy #22 started [poller #4|#4] 1244:20180823:141325.974 proxy #23 started [poller #5|#5] 1245:20180823:141325.982 proxy #24 started [unreachable poller #1|#1] 1246:20180823:141325.998 proxy #25 started [trapper #1|#1] 1247:20180823:141326.010 proxy #26 started [trapper #2|#2] 1212:20180823:141326.018 received configuration data from server at "**.***.***", datalen 9369 1248:20180823:141326.019 proxy #27 started [trapper #3|#3] 1239:20180823:141326.020 proxy #18 started [task manager #1|#1] 1249:20180823:141326.020 proxy #28 started [trapper #4|#4] 1212:20180823:141326.021 failed to update local proxy configuration copy: unexpected field "hosts.available" 1250:20180823:141326.026 proxy #29 started [trapper #5|#5] 1255:20180823:141326.107 proxy #30 started [icmp pinger #1|#1] 1250:20180823:141407.433 cannot send list of active checks to "192.168.1.12": host [EVSRV03] not found 1250:20180823:141415.517 cannot send list of active checks to "127.0.0.1": host [Zabbix_proxy_******] not found 1227:20180823:141425.278 cannot stat SNMP trapper file "/var/log/snmptrap/snmptrap.log": [2] No such file or directory |
| Comment by Edgar Akhmetshin [ 2018 Aug 23 ] |
|
Please, recreate Proxy database accordingly to this manual. Regards, |
| Comment by Stevel [ 2018 Aug 24 ] |
|
Hello Edgar,
Problem is that on the appliance the doxs are not there in the mean time i totaly broke the virtual machine so i have setup a new one starting from zabbix_appliance_3.4.11_x86_64 and updating to 3.4.12 and i have the same issue. Is there any way you can send me a script to verify the sql schema? |
| Comment by Edgar Akhmetshin [ 2018 Aug 24 ] |
|
Hello, Stevel After the upgrade you must to recreate database of the Proxy server. Also Zabbix Appliance 3.4.12 is available. This issue tracker is for bug reports only. Please check https://www.zabbix.org/wiki/Getting_help for community or commercial support options. No indication of a bug. Closing as Won't fix. |
| Comment by Stevel [ 2018 Aug 24 ] |
|
Hi edgar, I tried with the appliance 3.4.12 and i have the same error |
| Comment by Edgar Akhmetshin [ 2018 Aug 24 ] |
|
Stevel, please, provide the following information: Regards, |
| Comment by Stevel [ 2018 Aug 24 ] |
|
Hi Edgar,
The problem is solved, loks like the problem was on the server side not the proxy side, I reran the upgrade and restarted the service but still the same problem, for some reason it was solved by restarting the whole server. You can close the ticket, thanks for the help. |
| Comment by Rickk Barbosa [ 2018 Oct 26 ] |
|
Hi guys,
In my case, the root cause was Zabbix Proxy database. If you are using zabbix-proxy with SQLite3, it can't upgrade DB and fails. Try stop the zabbix-proxy service, move /var/lib/zabbix/zabbix_proxy.db (or whatever you're placed Sqlite DB) to another place and restart the service.
|