[ZBX-12446] process_dhis_data(): "" is not a valid hostname Created: 2017 Jul 31  Updated: 2017 Aug 21  Resolved: 2017 Aug 03

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: None
Affects Version/s: 2.2.19, 3.0.10, 3.2.7, 3.4.0beta1
Fix Version/s: 2.2.20rc1, 3.0.11rc1, 3.2.8rc1, 3.4.0beta1

Type: Problem report Priority: Trivial
Reporter: Eduardo Wutzl da Silva Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

CentOS Linux release 7.3.1611 (Core)
zabbix_server (Zabbix) 3.2.7
Revision 70298 18 July 2017, compilation time: Jul 18 2017 16:10:01


Attachments: File 3.2.7.diff    
Issue Links:
Duplicate
is duplicated by ZBX-12484 Network discovery, not adding devices... Closed

 Description   

After migrating from version 3.2.6 to 3.2.7, this type of information appeared without my log file.

Following information.
6856:20170731:100232.777 process_dhis_data(): "" is not a valid hostname
6856:20170731:100232.777 process_dhis_data(): "" is not a valid hostname
6856:20170731:100232.777 process_dhis_data(): "" is not a valid hostname
6856:20170731:100232.777 process_dhis_data(): "" is not a valid hostname
6850:20170731:100233.749 process_dhis_data(): "" is not a valid hostname
6850:20170731:100233.749 process_dhis_data(): "" is not a valid hostname
6850:20170731:100233.749 process_dhis_data(): "" is not a valid hostname
6853:20170731:100243.068 process_dhis_data(): "" is not a valid hostname
6853:20170731:100243.068 process_dhis_data(): "" is not a valid hostname
6853:20170731:100243.068 process_dhis_data(): "" is not a valid hostname
6853:20170731:100243.068 process_dhis_data(): "" is not a valid hostname
6853:20170731:100243.068 process_dhis_data(): "" is not a valid hostname
6853:20170731:100243.069 process_dhis_data(): "" is not a valid hostname
6851:20170731:100244.314 process_dhis_data(): "" is not a valid hostname
6851:20170731:100244.315 process_dhis_data(): "" is not a valid hostname
6853:20170731:100253.110 process_dhis_data(): "" is not a valid hostname
6853:20170731:100253.110 process_dhis_data(): "" is not a valid hostname
6853:20170731:100253.110 process_dhis_data(): "" is not a valid hostname
6853:20170731:100253.110 process_dhis_data(): "" is not a valid hostname
6853:20170731:100253.110 process_dhis_data(): "" is not a valid hostname
6853:20170731:100253.110 process_dhis_data(): "" is not a valid hostname
6853:20170731:100253.110 process_dhis_data(): "" is not a valid hostname
6850:20170731:100253.923 process_dhis_data(): "" is not a valid hostname



 Comments   
Comment by Vladislavs Sokurenko [ 2017 Jul 31 ]

This is because discovered IP address is missing DNS entry, current workaround is to add DNS entry, but it will be fixed and empty DNS will be allowed again.

Comment by Eduardo Wutzl da Silva [ 2017 Jul 31 ]

Many ips from my network, do not have DNS entry. What should I do? Just wait?
vso I can give a patch if that's an option for you

Comment by Eduardo Wutzl da Silva [ 2017 Jul 31 ]

I will! Waiting for the next instructions!
vso please apply 3.2.7.diff patch.

Comment by Andris Mednis [ 2017 Aug 01 ]

Successfully tested.

Comment by Vladislavs Sokurenko [ 2017 Aug 01 ]

Fixed in:
pre-2.2.20rc1 r70804
pre-3.0.11rc1 r70807
pre-3.2.8rc1 r70811
pre-3.4.0beta1 r70812

Comment by Viktors Dauksts [ 2017 Aug 08 ]

When do you plan to release 3.0.11 version?

Comment by Eduardo Wutzl da Silva [ 2017 Aug 08 ]

I'm having trouble applying the patch ...
What is the procedure for applying it?

I am installing packages in CentOS environments

But it has a development environment where it compiles zabbix binaries around here.

Comment by Marc [ 2017 Aug 08 ]

[email protected], see Getting help.

Generated at Fri Apr 26 17:55:24 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.