Ad Widget

Collapse

Can't figure out "Not all Templates are linked to host"

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • arli
    Member
    • Jan 2008
    • 71

    #1

    Can't figure out "Not all Templates are linked to host"

    I have a lot of templates. Some of them are created from scratch and some are created using full cloning feature.
    Today I discovered, that I cannot save many of them.
    When going into Configuration > Templates > choose one > Triggers > edit the trigger and hit Save button, it gives me this error:
    Not all Templates are linked to host [ ant01.mydomain.com ]
    I suspected that there was some mixup with this host and deleted it and retried again, but then there was error about ant02... so I guess, it is complaining about that host just because it is alfabetically the first one.
    I haven't changed my templates recently so it has to be control mechanism created in some new Zabbix version, that is kicking in now.

    I looked up from the triggers.inc.php file and there is this function
    Code:
    // Deny adding dependency between templates ifthey are not high level templates
    	function validate_trigger_dependency($expression, $deps)
    I have a template that includes checks that host is up and zabbix agent is running. And inside this template, agent trigger A is depending on the host trigger B.
    All the other triggers on the other templates are depending on either trigger A (agent related checks: cpu, disk etc.) or trigger B (agentless checks: ports, web).

    So what does this "high level template" mean? I thought all templates were on the same level.
    It seems to me that dependencies between templates are forbidden now. Go figure it out.
  • arli
    Member
    • Jan 2008
    • 71

    #2
    Hi Zabbix developers, can you please explain this or confirm a bug so I could fill a report in tracker.
    At the moment I'm very confused about this kind of behaviour and I hope I don't have to redesign my templates system

    Comment

    • DSon
      Member
      • Sep 2009
      • 44

      #3
      I've got exactly the same problem..

      Appears to have started happening since upgrading from Zabbix 1.8.1 to 1.8.3, after which I imported some Templates.

      Now when trying to ammend any Trigger containing dependencies, I get "Not all Templates are linked to host <NNNN>..".

      I've tried looking for circular references but not found any. All these templates were working with dependencies before the upgrade.

      Is the latest stable version of Zabbix broke?

      Please help,
      Danny.

      Comment

      • DSon
        Member
        • Sep 2009
        • 44

        #4
        Here is what is wrong...

        I'm not a programmer.. but it seems the code Zabbix is now using for checking trigger dependencies within linked templates is definitely broke.

        Here's a simplified example of what is happening:

        - Template (1) is linked to both HOST (A) and HOST (B)
        - Template (2) is only linked to HOST (A)
        - I attempt to update a Trigger in Template (2) which contains a dependency to a Trigger in Template (1)
        - ERROR: "Not all Templates are linked to host [ HOST (B) ]"
        - I then link Template (2) to HOST (B) as well as HOST (A)
        - I attempt to update the Trigger in Template (2)
        - WORKS!

        How does one go about reporting bugs?

        Danny.

        Comment

        • Andreas Bollhalder
          Senior Member
          Zabbix Certified Specialist
          • Apr 2007
          • 144

          #5
          Same with 2.0.4

          Has this only be resolved in 1.8.4 and later ?

          I get the message in 2.0.4 if I make a dependency of a trigger to a trigger of another template.

          Any news ?

          Thanks in advance.

          Andreas
          Zabbix statistics
          Total hosts: 380 - Total items: 12190 - Total triggers: 4530 - Required server performance: 224.2

          Comment

          • jairoalves
            Junior Member
            • Jan 2015
            • 15

            #6
            Can anyone confirm this problem still exists? I'm on 2.0.3.

            Comment

            Working...