Ad Widget

Collapse

ZabbixW32 windows agent dying in beta5

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • steveh
    Junior Member
    • Jan 2006
    • 9

    #1

    ZabbixW32 windows agent dying in beta5

    I'm seeing the agent dying daily on a number of machines (all in fact!)

    The OS's are: Windows XP SP1, Windows XP Sp2, Windows Server 2003 SP1

    Anything I can do to gather somethign more useful than "It's crashed"?

    I've verified that the config files are ok, which they are and the server happily collects data from them for some hours. We then end up with the ZabbixW32 error and whether we want to report this to MS, I can save away a log and see whether this contains anything useful, or are you already aware of the issue?

    Steve
  • steveh
    Junior Member
    • Jan 2006
    • 9

    #2
    This is from the event log:

    Faulting application ZabbixW32.exe, version 0.0.0.0, faulting module ZabbixW32.exe, version 0.0.0.0, fault address 0x0000b92d.

    Also, post this after the service has restarted we see a large numbner of "error reciving data from" and our zabbix server IP address.

    The description for Event ID ( 32 ) in Source ( Zabbix Win32 Agent ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Error while receiving data from [193.195.25.40:10051] [No error].

    Comment

    • Alexei
      Founder, CEO
      Zabbix Certified Trainer
      Zabbix Certified SpecialistZabbix Certified Professional
      • Sep 2004
      • 5654

      #3
      Hmm... The 1.1beta5 agent is exactly the same as 1.1beta4 which proved to be very stable. Anyone else experiencing this?
      Alexei Vladishev
      Creator of Zabbix, Product manager
      New York | Tokyo | Riga
      My Twitter

      Comment

      • steveh
        Junior Member
        • Jan 2006
        • 9

        #4
        I should probably point out that it's dying on about 12 machines (haven't rolled it out any further yet), and that the only thing I've done that might be different from other people, is extended the win32 template to include drive letters upto h for capacity and free space?

        Comment

        • bbrendon
          Senior Member
          • Sep 2005
          • 870

          #5
          Most of our systems are on the b2 agent. We have a few on b5 agents, but none of them have died yet.
          Unofficial Zabbix Expert
          Blog, Corporate Site

          Comment

          • SparHawk
            Junior Member
            • Oct 2004
            • 19

            #6
            ZABBIXw32 agent 1.1beta3 to 1.1beta5 not Starting

            Windows 2003 Server with SP1 and most of the latest patches installed.

            ZABBIXw32 agent installs, but as soon as you start it, it stays in starting mode indefinite in the services mmc .

            Previous agents working fine.

            SparHawk

            Comment

            • steveh
              Junior Member
              • Jan 2006
              • 9

              #7
              Just to clarify the agents are starting here, but on the bulk of the machines they fall over after a few hours usage (12-24 hours typically).

              Comment

              • steveh
                Junior Member
                • Jan 2006
                • 9

                #8
                I've grabbed a copy of the memory dump etc from the latest crash, is this of any use to you Alexei?

                Seems to always be crashing in the same place, and this is regardless of the version of operating system or service pack level.

                Comment

                • edeus
                  Senior Member
                  • Aug 2005
                  • 120

                  #9
                  I am having the same problems:

                  Windows 2003 SP1, Windows 2000 Server.

                  It seems to die on me silently (although it is running as service). No common cause in the event logs (some have a alert, some have nothing).

                  I was able to make it "better" by removing all perfcounters and revert to using the built in parameters.

                  Is there a stable version to revert to?

                  Comment

                  Working...