Ad Widget

Collapse

Item never gets any value, shows "Not supported" status

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • emx
    Junior Member
    • Aug 2006
    • 19

    #1

    Item never gets any value, shows "Not supported" status

    I am trying to define a new item to monitor the status of the DNS service running on our DNS servers.

    I am creating a new item in the template Unix_t as follows:

    Description: DNS service is running
    Type: Zabbix agent
    Key: net.tcp.service[domain]
    Type of information: Numeric (float)

    And default values for the rest.

    Basically, this item looks exactly like some already existing (and working!) in the Unit_t template, such as "Email (SMTP) server is running" (the only difference being 'domain' instead of 'smtp').

    My /etc/services of course contains the 'domain' service.

    This new item in Unix_t shows as being in 'active' state, so things look ok.

    When I look at a host using the Unix_t profile, I can see that the item has been added, however it shows "Not supported" status. I can change the status but eventually it comes back to "Not supported" state.

    No data is ever received (in monitoring).

    Anyone care to help me out? I find it strange that the SMTP item works well and the DNS one does not (since the only difference between the two is the service name).

    Thanks!
  • emx
    Junior Member
    • Aug 2006
    • 19

    #2
    New item "not supported" follow-up

    Still no answer, so I continue investigating. This error disturbs me because it isn't logical.

    I'm thinking, maybe Zabbix doesn't take the service name from /etc/services? This could explain why 'domain' is not recognized.

    To verify this, I modified the IMAP service number in /etc/services and changed it to 53 (the 'domain' port). I restarted client and server. Zabbix shows IMAP as being down, even though its "new" associated port in /etc/services (53) is bound to a service (the DNS) that is up.

    Hmmm... this could confirm the fact the Zabbix doesn't use /etc/services for service name lookup. Maybe it's in a DB table? I'll have to dig.

    Meanwhile, is there ANYONE here that created a new tcp or udp service to be monitored? How did it go for you?

    Comment

    • emx
      Junior Member
      • Aug 2006
      • 19

      #3
      Workaround found!

      I changed the string to net.tcp.dns instead of net.tcp.service[domain].

      Does what I need perfectly.

      Comment

      Working...