Ad Widget

Collapse

[Zabbix 1.8.1] - Windows zabbix_agentd dies

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • sarts
    Junior Member
    • Mar 2010
    • 3

    #1

    [Zabbix 1.8.1] - Windows zabbix_agentd dies

    I am currently doing a PoC with zabbix, but I have come across one problem.
    I have one server where the zabbix agent (v 1.8.1) keeps crashing.

    It is the binary version I downloaded from this website.

    Is this a known issue? How can it be solved?
  • Peteris
    Member
    • Feb 2010
    • 89

    #2
    I had this issue with Zabbix 1.8 on some Windows 2003/2008/2008 R2 Servers, have no idea why. We had servers with configuration 1:1, and one server works, other doesn't. Probably the problem is same in 1.8.1.

    Workaround to this problem is simple - use older 1.6.8 agents...

    Comment

    • sarts
      Junior Member
      • Mar 2010
      • 3

      #3
      Originally posted by Peteris
      I had this issue with Zabbix 1.8 on some Windows 2003/2008/2008 R2 Servers, have no idea why. We had servers with configuration 1:1, and one server works, other doesn't. Probably the problem is same in 1.8.1.

      Workaround to this problem is simple - use older 1.6.8 agents...
      Lets see if I understand correctly: zabbix-server 1.8.1 works with 1.6.8 agents?

      Comment

      • sarts
        Junior Member
        • Mar 2010
        • 3

        #4
        Older agents from Zabbix 1.0, Zabbix 1.1.x, Zabbix 1.4.x and Zabbix 1.6.x can be used with Zabbix 1.8. It does not require any configuration changes on agent side.
        Answers my question
        (solves a problem too, it means I can just use the zabbix-agents from redhat-repos)

        Comment

        • tchjts1
          Senior Member
          • May 2008
          • 1605

          #5
          As long as you understand you will lose some of the new functionality that goes with the 1.8.x agent.

          Of course if it isn't working... then you have no functionality to lose.

          On the other hand... if you are experiencing true issues that are reproduceable, you should report it on the bug tracker.

          Comment

          Working...