Ad Widget

Collapse

Status not reset in database for item

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • dreas
    Member
    • Aug 2007
    • 89

    #1

    Status not reset in database for item

    I had a few unsupported items which became supported. They also show correctly in the Zabbix frontend. They show incorrectly however in the MySQL database?

    Code:
    zabbix:~# mysql -uzabbix -p -e "use zabbix; select * from items where status=3;" 
    +--------+------+----------------+-----------------------------------------+-----------+--------+-------------+------------+-------+---------+--------+------------+-----------+------------+-----------+--------+------------+---------------+-------+------------+-------+--------------+---------------------+----------------------+-----------------------+-----------------------+---------+--------------------------------+-------------+------------+------------+------------+------------+--------+
    | itemid | type | snmp_community | snmp_oid                                | snmp_port | hostid | description | key_       | delay | history | trends | nextcheck  | lastvalue | lastclock  | prevvalue | status | value_type | trapper_hosts | units | multiplier | delta | prevorgvalue | snmpv3_securityname | snmpv3_securitylevel | snmpv3_authpassphrase | snmpv3_privpassphrase | formula | error                          | lastlogsize | logtimefmt | templateid | valuemapid | delay_flex | params |
    +--------+------+----------------+-----------------------------------------+-----------+--------+-------------+------------+-------+---------+--------+------------+-----------+------------+-----------+--------+------------+---------------+-------+------------+-------+--------------+---------------------+----------------------+-----------------------+-----------------------+---------+--------------------------------+-------------+------------+------------+------------+------------+--------+
    |  21495 |    0 | public         | interfaces.ifTable.ifEntry.ifInOctets.1 |       161 |  10048 | Email test  | email.test |   600 |      90 |    365 | 1207566909 | NULL      | 1207566309 | NULL      |      3 |          3 |               |       |          0 |     0 | NULL         |                     |                    0 |                       |                       | 1       | Not supported by ZABBIX agent  |           0 |            |      21392 |          0 |            |        | 
    |  21546 |    0 | public         | interfaces.ifTable.ifEntry.ifInOctets.1 |       161 |  10049 | Email test  | email.test |   600 |      90 |    365 | 1207566906 | NULL      | 1207566306 | NULL      |      3 |          3 |               |       |          0 |     0 | NULL         |                     |                    0 |                       |                       | 1       | Not supported by ZABBIX agent  |           0 |            |      21392 |          0 |            |        | 
    +--------+------+----------------+-----------------------------------------+-----------+--------+-------------+------------+-------+---------+--------+------------+-----------+------------+-----------+--------+------------+---------------+-------+------------+-------+--------------+---------------------+----------------------+-----------------------+-----------------------+---------+--------------------------------+-------------+------------+------------+------------+------------+--------+
    zabbix:~#
    Is this a bug? I am actively monitoring for status 3 items to make sure all my items are functioning properly. I manually checked the item IDs in the frontend and they are active and supported.
  • swaterhouse
    Senior Member
    • Apr 2006
    • 268

    #2
    Yes it is a bug. It has been talked about before and I am pretty sure its been logged but haven't personally verified it was logged.

    Comment

    • dreas
      Member
      • Aug 2007
      • 89

      #3
      Thanks for the quick response. Can I just remove those entries or should I simply reset the status to 2 using MySQL?

      Comment

      • dreas
        Member
        • Aug 2007
        • 89

        #4


        I just use the MySQL command from there to reset the status.

        Comment

        • dreas
          Member
          • Aug 2007
          • 89

          #5
          Actually this post is invalid. We moved our Zabbix server some weeks ago but the unsupported item was monitoring the old server that did not get any updates anymore

          Comment

          Working...