-
Problem report
-
Resolution: Fixed
-
Major
-
None
-
Sprint 39, Sprint 40
-
1
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.
Zabbix server versions is 3.2.11
