[ZBX-14593] vmware monitoring produces STDERR garbage to server log when pointed to a usual web server Created: 2018 Jul 10 Updated: 2018 Aug 23 Resolved: 2018 Aug 10 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Proxy (P), Server (S) |
Affects Version/s: | None |
Fix Version/s: | 3.0.21rc1, 3.4.13rc1, 4.0.0beta1, 4.0 (plan) |
Type: | Problem report | Priority: | Major |
Reporter: | Oleksii Zagorskyi | Assignee: | Michael Veksler |
Resolution: | Fixed | Votes: | 0 |
Labels: | logging, stderr, vmware | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Issue Links: |
|
||||
Team: | Team A | ||||
Sprint: | Sprint 39, Sprint 40 | ||||
Story Points: | 1 |
Description |
I've configured a host in zabbix and mistakenly pointed to a usual web server and my zabbix_server.log started to collect lots of such strange blocks, I guess its a STDERR of libxml2: noname.xml:1: parser error : Space required after the Public Identifier <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> ^ noname.xml:1: parser error : SystemLiteral " or ' expected <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> ^ noname.xml:1: parser error : SYSTEM or PUBLIC, the URI is missing <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> ^ When I enabled trace level of debug, I was able to isolate it: 7764:20180710:114121.031 In vmware_service_update_perf() 'zabbix'@'https://192.168.200.235/sdk' 7764:20180710:114121.031 In vmware_service_authenticate() 'zabbix'@'https://192.168.200.235/sdk' 7764:20180710:114121.045 vmware_service_authenticate() SOAP response: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL /sdk was not found on this server.</p> </body></html> noname.xml:1: parser error : Space required after the Public Identifier <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> ^ noname.xml:1: parser error : SystemLiteral " or ' expected <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> ^ noname.xml:1: parser error : SYSTEM or PUBLIC, the URI is missing <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> ^ 7764:20180710:114121.045 End of vmware_service_authenticate():SUCCEED 7764:20180710:114121.056 In vmware_service_parse_perf_data() noname.xml:1: parser error : Space required after the Public Identifier <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> ^ noname.xml:1: parser error : SystemLiteral " or ' expected <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> ^ noname.xml:1: parser error : SYSTEM or PUBLIC, the URI is missing <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> ^ 7764:20180710:114121.056 End of vmware_service_parse_perf_data() 7764:20180710:114121.056 In vmware_service_copy_perf_data() 7764:20180710:114121.056 End of vmware_service_copy_perf_data() 7764:20180710:114121.056 End of vmware_service_update_perf(): processed 201 bytes of data Would be good that zabbix server will not fill my log file with the STDERR garbage, at least in this particular case. It's unclear for not experienced users. vmware monitoring for real vmware hosts work fine. |
Comments |
Comment by Oleksii Zagorskyi [ 2018 Jul 27 ] |
One-line warning in the log would be much more user friendly. For example that it's not an XML or so. |
Comment by Michael Veksler [ 2018 Aug 02 ] |
Available for testing in svn://svn.zabbix.com/branches/dev/ZBX-14593-30 in r83399, r83403. |
Comment by Michael Veksler [ 2018 Aug 09 ] |
Available in:
|