-
Incident report
-
Resolution: Won't fix
-
Minor
-
None
-
2.4.4
-
None
-
CentOS 6.6
HP Blade
When using HostnameItem=system.hostname the system automatically looks up the hostname from the local machine. I noticed on a windows 2003 r2 server that it converts the hostname to capital letters.
The same thing also goes for Windows Server 2008 R2.
if you lookup hostname via the hostname command it displays "server01", however the zabbix agent converts it to capitals which gives an error in the zabbix agent log:
5332:20150831:112006.790 Starting Zabbix Agent [SERVER01]. Zabbix 2.4.4 (revision 52334). 5332:20150831:112006.790 using configuration file: c:\zabbix\conf\zabbix_agentd.conf 5332:20150831:112006.805 agent #0 started [main process] 7620:20150831:112006.805 agent #1 started [collector] 6792:20150831:112006.805 agent #2 started [listener #1] 6180:20150831:112006.821 agent #3 started [listener #2] 7428:20150831:112006.821 agent #4 started [listener #3] 6520:20150831:112006.821 agent #5 started [active checks #1] 6520:20150831:112006.837 no active checks on server [zabbix.dewulf.be:10051]: host [SERVER01] not found
When I manually fill out the hostname field in the zabbix_agentd.conf the error disappears:
7408:20150831:112202.681 Zabbix Agent stopped. Zabbix 2.4.4 (revision 52334). 584:20150831:112202.931 Starting Zabbix Agent [server01]. Zabbix 2.4.4 (revision 52334). 584:20150831:112202.947 using configuration file: c:\zabbix\conf\zabbix_agentd.conf 584:20150831:112202.947 agent #0 started [main process] 7588:20150831:112202.962 agent #1 started [collector] 5764:20150831:112202.962 agent #2 started [listener #1] 6600:20150831:112202.962 agent #3 started [listener #2] 8176:20150831:112202.962 agent #4 started [listener #3] 4760:20150831:112202.962 agent #5 started [active checks #1]