Ad Widget

Collapse

Trigger: trouble with tcp,port

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • mtuckerb
    Junior Member
    • May 2005
    • 6

    #1

    Trigger: trouble with tcp,port

    I have tried creating a trigger for an existing host, using a simple tcp,port item.
    syntax =
    {host:tcp,53.last(0)} = 0

    I get:
    [ERROR:Invalid trigger expression]

    Thoughts?
  • johnl
    Junior Member
    • Jan 2005
    • 27

    #2
    try item

    check_port[server_name,port_number]

    then trigger

    ({server:check_port[port_number].last(0)}=0)&({server:check_port[port_number].delta(150)}=0)

    delta part adds a delay of 150 seconds before trigger activates to allow for network glitches etc

    regards
    john

    Comment

    • mtuckerb
      Junior Member
      • May 2005
      • 6

      #3
      Thanks, but that doesn't seem to work either. I used
      {publish:check_port[vader,53].last(0)} = 0

      I have a host named vader and a host named publish. do I need to use IPs instead?

      Comment

      • johnl
        Junior Member
        • Jan 2005
        • 27

        #4
        your entry should be
        {publish:check_port[53].last(0)} = 0 if you want to monitor port 53 on publish and
        {vader:check_port[53].last(0)} = 0 if you want to monitor port 53 on vader

        regards
        john

        Comment

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

          #5
          Originally posted by mtuckerb
          I have tried creating a trigger for an existing host, using a simple tcp,port item.
          syntax =
          {host:tcp,53.last(0)} = 0

          I get:
          [ERROR:Invalid trigger expression]

          Thoughts?
          Remove spaces to make it work:

          {host:tcp,53.last(0)}=0
          Alexei Vladishev
          Creator of Zabbix, Product manager
          New York | Tokyo | Riga
          My Twitter

          Comment

          • mtuckerb
            Junior Member
            • May 2005
            • 6

            #6
            Originally posted by Alexei
            Remove spaces to make it work:

            {host:tcp,53.last(0)}=0
            Yup, tried that too. I get
            [ERROR:Invalid trigger expression. No such host (vader) or monitored parameter (tcp,53)]

            Comment

            • mtuckerb
              Junior Member
              • May 2005
              • 6

              #7
              Originally posted by johnl
              your entry should be
              {publish:check_port[53].last(0)} = 0 if you want to monitor port 53 on publish and
              {vader:check_port[53].last(0)} = 0 if you want to monitor port 53 on vader

              regards
              john
              Thanks John,
              I've tried {vader:check_port[53].last(0)} = 0 if you want to monitor port 53 on vader as well,
              I get:
              [ERROR:Invalid trigger expression. No such host (vader) or monitored parameter (check_port[53])]

              Comment

              • mtuckerb
                Junior Member
                • May 2005
                • 6

                #8
                Oh Crap.
                I figured it out. I was missing the check_port Item. I could have sworn that I set it up, but this is my second installation of zabbix this week, so maybe I did it on the other box. Thanks for all of your suggestions, and sorry for the d'oh.
                -=Tucker

                Comment

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

                  #9
                  Originally posted by mtuckerb
                  Yup, tried that too. I get
                  [ERROR:Invalid trigger expression. No such host (vader) or monitored parameter (tcp,53)]
                  Obviously, you either have no host 'vader' or item 'tcp,53' is missing!
                  Alexei Vladishev
                  Creator of Zabbix, Product manager
                  New York | Tokyo | Riga
                  My Twitter

                  Comment

                  Working...