Ad Widget

Collapse

2.0 zabbix_sender frustration

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Teeleton
    Junior Member
    • Oct 2012
    • 3

    #1

    2.0 zabbix_sender frustration

    Hi everyone,

    Fairly new guy here trying to get my feet wet and understand how all of this hangs together. Managed to set up a host and get the agent running and reporting ok. Now trying to push some custom items into the database and seem to have run into a bit of a brick wall.

    Running v. 2.0.3 of the sender and server, and have tried every combination of things I can think of, and yet the sender keeps coming back with failed when I try to push a new value in.

    Item is configured as "zabbix trapper", host is working OK otherwise. tried using the agent config and putting the server on the command line with -z, and nothing seems to work. Even tried to running the sender on the server itself with -z 127.0.0.1 and it still fails.

    Item config:

    Host: test
    Name: Temp
    Type: Zabbix Trapper
    Key: hwsensors.temp
    Type of Information: Numeric (float)
    Units: C
    Allowed Hosts: (blank)
    Status: Enabled

    Trapper is listening on all interfaces:

    # netstat -ln | grep 10051
    tcp 0 0 0.0.0.0:10051 0.0.0.0:* LISTEN

    and yet...

    # zabbix_sender -z 127.0.0.1 -s test -k hwsensors.temp -o 1.0
    info from server: "Processed 0 Failed 1 Total 1 Seconds spent 0.000040"
    sent: 1; skipped: 0; total: 1

    this doesn't work either, just as a test.

    # zabbix_sender -z 127.0.0.1 -s test -k hwsensors.temp -o 1
    info from server: "Processed 0 Failed 1 Total 1 Seconds spent 0.000044"
    sent: 1; skipped: 0; total: 1

    Any ideas where I might be going wrong? The eventual plan is to use the sender to bulk load a bunch of items, but currently I can't even get it to send even a single one.
    Last edited by Teeleton; 05-11-2012, 00:08.
  • Teeleton
    Junior Member
    • Oct 2012
    • 3

    #2
    I managed to work this one out. Turns out that when I defined the node # in the server.conf to prepare for a distributed setup, I broke it. Commented it out again in the server.conf, and it's working as expected now.

    Comment

    • mdobrinin
      Junior Member
      • Oct 2012
      • 7

      #3
      zabbix_sender has verbosity flag that is very helpful for seeing what went wrong.

      Comment

      • Teeleton
        Junior Member
        • Oct 2012
        • 3

        #4
        For the record, I tried increasing the verbosity, and it was very little help. adding -vvvv to the command line gets the following response.

        zabbix_sender [29050]: DEBUG: answer [{
        "response":"success",
        "info":"Processed 0 Failed 1 Total 1 Seconds spent 0.000037"}]
        info from server: "Processed 0 Failed 1 Total 1 Seconds spent 0.000037"
        sent: 1; skipped: 0; total: 1

        Perhaps I need more than 4 v's?

        Comment

        Working...