Ad Widget

Collapse

HELP!!! Issues on 2 of 18 proxy servers following large number of new hosts

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • tmroberts
    Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Jan 2017
    • 73

    #1

    HELP!!! Issues on 2 of 18 proxy servers following large number of new hosts

    Last Friday a fairly large number of new Windows hosts had their agents updated, including new config files to point to our new Zabbix environment (currently v3.4.8). Once I was able to get all of the hosts placed into their correct host groups I made a sweep through all of the hosts and found that a fair number of them were not getting active checks done via the proxy server. In troubleshooting this issue I found that two of the proxy servers were getting a frequent error in their logs:

    received configuration data from server at "<zabbix server ip>", datalen 127304
    21953:20180515:231518.915 [Z3005] query failed: [1366] Incorrect string value: '\xE9' for column 'name' at row 16 [insert into hosts (hostid,host,status,ipmi_authtype,ipmi_privilege,i pmi_username,ipmi_password,name,tls_connect,tls_ac cept,tls_issuer,tls_subject,tls_psk_identity,tls_p sk,description) values (<......LOTS OF ROWS TO INSERT>);]
    21953:20180515:231518.918 failed to update local proxy configuration copy: database error
    22025:20180515:231545.857 cannot send list of active checks to "<host ip>": host [<host name>] not found

    ALL of the proxy servers have identical config files with the exception of a couple different parameters to accommodate more traffic and ALL of the hosts have identical agent config files. Most windows hosts are having no issues communicating with Zabbix. Even windows hosts on the same proxy are having no issues. And there are only two proxy servers that are having these issues. I have dropped and recreated the proxy database several times ensuring they are using UTF8. Can someone PLEASE help!
  • tmroberts
    Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Jan 2017
    • 73

    #2
    Figured it out.... Found a couple of hosts managed by those proxies that had invalid characters in their host names. Fixed the host name(s) and all is well.

    Comment

    Working...