Ad Widget

Collapse

zabbix 3.4.0 - unsupported value (0)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • mvrk
    Member
    • Oct 2008
    • 71

    #1

    zabbix 3.4.0 - unsupported value (0)

    Hi,

    I have script that is currently returning 0 for a certain item, and it was working with zabbix agent 3.0.9, but now with 3.4.0 i get unsupported:

    zabbix_agentd -t "syslog.errors[scsi 2]"
    syslog.errors[scsi 2] zabbix_agentd [87101]: Warning: 0
    [m|ZBX_NOTSUPPORTED] [0]

    The item configured on zabbix is Numeric (unsigned)

    Any ideas?
  • vso
    Zabbix developer
    • Aug 2016
    • 190

    #2
    Originally posted by mvrk
    Hi,

    I have script that is currently returning 0 for a certain item, and it was working with zabbix agent 3.0.9, but now with 3.4.0 i get unsupported:

    zabbix_agentd -t "syslog.errors[scsi 2]"
    syslog.errors[scsi 2] zabbix_agentd [87101]: Warning: 0
    [m|ZBX_NOTSUPPORTED] [0]

    The item configured on zabbix is Numeric (unsigned)

    Any ideas?
    Could try increasing log level and looking into Zabbix log on agent, what does it say?
    Last edited by vso; 22-08-2017, 19:01.

    Comment

    • mvrk
      Member
      • Oct 2008
      • 71

      #3
      I configured log level 5, but nothing much appears:

      on server:

      89436:20170822:190137.023 Item [DB1:syslog.errors[e1000 eth1]] error: 0

      89449:20170822:190137.023 End of preprocessor_get_queued_item()
      89436:20170822:190137.023 End of get_value():NOTSUPPORTED

      on agent:

      103656:20170822:185526.964 Requested [syslog.errors[e1000 eth1]]
      103656:20170822:185526.964 In zbx_popen() command:'/var/lib/zabbix/syslog.sh e1000 eth1 '
      103656:20170822:185526.964 End of zbx_popen():6
      104497:20170822:185526.964 zbx_popen(): executing script
      103656:20170822:185526.969 In zbx_waitpid()
      103656:20170822:185526.969 zbx_waitpid() exited, status:1
      103656:20170822:185526.969 End of zbx_waitpid():104497
      103656:20170822:185526.969 0

      103656:20170822:185526.969 Sending back [ZBX_NOTSUPPORTED: 0

      Comment

      • vso
        Zabbix developer
        • Aug 2016
        • 190

        #4
        Originally posted by mvrk
        I configured log level 5, but nothing much appears:

        on server:

        89436:20170822:190137.023 Item [DB1:syslog.errors[e1000 eth1]] error: 0

        89449:20170822:190137.023 End of preprocessor_get_queued_item()
        89436:20170822:190137.023 End of get_value():NOTSUPPORTED

        on agent:

        103656:20170822:185526.964 Requested [syslog.errors[e1000 eth1]]
        103656:20170822:185526.964 In zbx_popen() command:'/var/lib/zabbix/syslog.sh e1000 eth1 '
        103656:20170822:185526.964 End of zbx_popen():6
        104497:20170822:185526.964 zbx_popen(): executing script
        103656:20170822:185526.969 In zbx_waitpid()
        103656:20170822:185526.969 zbx_waitpid() exited, status:1
        103656:20170822:185526.969 End of zbx_waitpid():104497
        103656:20170822:185526.969 0

        103656:20170822:185526.969 Sending back [ZBX_NOTSUPPORTED: 0
        What if you replace you script contents to printf 0
        Does it work then ?
        Last edited by vso; 22-08-2017, 22:05.

        Comment

        • mvrk
          Member
          • Oct 2008
          • 71

          #5
          Its a bash script.

          returns values using echo

          ex: echo "0"

          Comment

          • vso
            Zabbix developer
            • Aug 2016
            • 190

            #6
            Originally posted by mvrk
            Its a bash script.

            returns values using echo

            ex: echo "0"
            what if you replace to printf "0" ?

            Comment

            • mvrk
              Member
              • Oct 2008
              • 71

              #7
              Originally posted by vso
              what if you replace to printf "0" ?
              Already did, same error.

              Comment

              • sles
                Member
                • Oct 2005
                • 80

                #8
                We have the same problem here

                I created issue https://support.zabbix.com/browse/ZBX-12594

                Comment

                • sles
                  Member
                  • Oct 2005
                  • 80

                  #9
                  OK, they say this is not bug, this is feature,
                  now they check if errorlevel is not 0 and if not- then script failed.
                  this means grep or find are usually failed and almost all scripts have to be rewritten by at least edding exit 0 ..

                  this is crazy...

                  Comment

                  Working...