Ad Widget

Collapse

Cannot evaluate function error

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • royc
    Junior Member
    • Mar 2015
    • 10

    #1

    Cannot evaluate function error

    Hello

    I'm getting 'Cannot evaluate function' error on this trigger expression:

    ({TRIGGER.VALUE}=0&{host1:logrt[/usr/local/schedulers/activeeon/proactivescheduler/logs/Scheduler.log,ERROR,,20].count(1d)}>0)|({TRIGGER.VALUE}=1&{host1:logrt[/usr/local/schedulers/activeeon/proactivescheduler/logs/Scheduler.log,ERROR,,20].nodata(1d)}=0)

    host1 is a valid host name.

    Any ideas?
  • pablos
    Junior Member
    • Mar 2015
    • 22

    #2
    Hi,

    When I hit these types of issues, I open my favorite editor and copy and paste the entire expression to it. Next, I paste back one expression at a time and test it. For example "{TRIGGER.VALUE}=0" Next,

    Code:
    ({TRIGGER.VALUE}=0&{host1:logrt[/usr/local/schedulers/activeeon/proactivescheduler/logs/Scheduler.log,ERROR,,20].count(1d)}>0)
    As I'm a newbie too, I thought Zabbix 2.x is using boolean names such as and, or, not rather than the old &, |

    Please try:

    Code:
    ({TRIGGER.VALUE}=0 and {host1:logrt[/usr/local/schedulers/activeeon/proactivescheduler/logs/Scheduler.log,ERROR,,20].count(1d)}>0)
    FWIW, I once tried uppercase AND and Zabbix barked at me. So, I now use lowercase.

    HTH.

    Cheers,
    -pablo

    Comment

    • royc
      Junior Member
      • Mar 2015
      • 10

      #3
      Thanks Pablo, it was actually a curroped file that couldn't be opened!

      Comment

      • pablos
        Junior Member
        • Mar 2015
        • 22

        #4
        Good find! Was the error message in the Zabbix Agent's log?

        Cheers,
        -pablo

        Comment

        • royc
          Junior Member
          • Mar 2015
          • 10

          #5
          Thanks

          No it wasn't I just attempted to open it and got a prompt it's a binary when the extension is .log so clearly a problem with the file. Deleting the file and allowing the server regenerating a new one resolved it.

          Comment

          • pablos
            Junior Member
            • Mar 2015
            • 22

            #6
            Excellent troubleshooting!

            You're using the same strategy I use: break the problem down and start at the beginning. If step 1 works, go to the next. Usually works well. ha!

            Comment

            • royc
              Junior Member
              • Mar 2015
              • 10

              #7
              ha he, the good thing about being a newbie at something is that you do just that

              Comment

              • pablos
                Junior Member
                • Mar 2015
                • 22

                #8
                It never fails either newbie or oldbie ...

                Comment

                • royc
                  Junior Member
                  • Mar 2015
                  • 10

                  #9
                  Very True

                  Comment

                  Working...