Ad Widget

Collapse

Windows agent don't show up

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Moulins
    Junior Member
    • Jun 2009
    • 4

    #1

    Windows agent don't show up

    I have a newly installed Zabbix server, built from source last week (v 1.6.4).
    I have a Linux test agent on a distinct computer, working fine.
    I have a Windows test agent, working fine... until this morning.

    The Zabbix web interface show the Windows agent hasn't connected since hours (into "monitoring / Latest data"). But everything is correct for the Linux agent.

    I can start and stop the Windows agent. The local log file show the expected corresponding lines. Those lines indicate communication with Zabbix server. On the Zabbix server, netstat show the corresponding sockets (in time TIME_WAIT state because the communication is brief). But the Zabbix server seems blind: no fresh datas into "monitoring / Latest data".

    Where can I look for more informations about this problem ?
  • pesadilla
    Member
    • Nov 2006
    • 69

    #2
    did you change hostname?

    Comment

    • Moulins
      Junior Member
      • Jun 2009
      • 4

      #3
      Originally posted by pesadilla
      did you change hostname?
      Nope.

      If I change the hostname into the Windows agent config file, I have the expected error into the log:
      Code:
      3436:20090615:165851 No active checks on server: host [dummy_name] not found
      Code:
      grep dummy_name /var/log/zabbix_server.log
      --> 5287:20090615:165847 Send list of active checks to [90.20.xxx.xxx] failed: host [dummy_name] not found
      Which are the expected results. This also demonstrate the communication is good.


      But
      Code:
      grep win_test /var/log/zabbix_server.log
      returns only lines from hours ago, before this problem show up.


      Maybe this is important, on the server, the last lines I have for the Windows machine are:
      Code:
      4978:20090615:121627 Expression [{12338}=1] for item [22264][win_test:agent.ping] cannot be evaluated: unable to get function value: lastvalue IS NULL for function [12338][win_test:agent.ping.nodata(100000)]
      4978:20090615:121657 Expression [{12338}=1] for item [22264][win_test:agent.ping] cannot be evaluated: unable to get function value: lastvalue IS NULL for function [12338][win_test:agent.ping.nodata(100000)]
      4978:20090615:121727 Expression [{12338}=1] for item [22264][win_test:agent.ping] cannot be evaluated: unable to get function value: lastvalue IS NULL for function [12338][win_test:agent.ping.nodata(100000)]
      I had those errors because I tested some triggers.
      But the web interface display 08:26:02 as the lastest data ! And you seem on those previous lines 12:16:27 to 12:17:27 (same day) into the log on the server, which is 4 hours later that the latest datas. I don't understand.

      Comment

      • Moulins
        Junior Member
        • Jun 2009
        • 4

        #4
        Bug found ?

        Originally posted by pesadilla
        did you change hostname?
        longer answer: yes

        The hostname of the Windows computer is win_test.
        Into the agent's configuration file, I wrote "hostname=win_test", and everything was ok.
        Later I commented out the hostname line to verify if the behaviour is the same as on Linux. Into the log file everything seems fine... but in fact the problem started here.

        If if write "hostname=win_test" then the agent transmit "win_test". But if I comment out this line, the agent transmit "WIN_TEST" (capitals). On the server side, no warning, no error. The whole log file in debug mode show nothing. But the datas aren't writen anymore into the database. The other checks seems ok (connection, triggers, and maybe more).

        If I write "hostname=WIN_TEST" I obtain the same problem.

        --> I think hostnames should be internaly capitalized (or the opposite) on the server side.

        Comment

        Working...