Ad Widget

Collapse

Raspberry PI 2 not returning net.if.out via zabbix_proxy

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • MichaelM
    Member
    • Sep 2008
    • 38

    #1

    Raspberry PI 2 not returning net.if.out via zabbix_proxy

    Hi,

    finally I had the time to setup a Raspberry PI 2 with Ubuntu 16.04 and zabbix_agentd and zabbix_proxy 3.2.1. This setup should report back to my zabbix_server 3.2.1 at the office.

    My host is linked with the default "OS Linux" template which includes net.if.in and net.if.out for the discovered interfaces. But if this host is setup as "behind proxy" no values are returned for this items. Most of the other items having proper values.

    A snmp_get for net.if.out is returning the correct value and if I query the zabbix_agent on the proxy machine directly (not monitored by proxy) the values are returned as well.

    Is this a bug or a regular behavior? Should the agent on the proxy machine defined as monitored by proxy?

    Thanks for bringing some light into this.

    --Michael
  • MichaelM
    Member
    • Sep 2008
    • 38

    #2
    Hi all,

    never mind, I don't what went wrong. I cleared the history for all items of that host, but it back to "monitored by proxy" and everything seems well.

    It's really to nice to give this raspi a new job

    --Michael

    Comment

    • Colttt
      Senior Member
      Zabbix Certified Specialist
      • Mar 2009
      • 878

      #3
      do you configure the host that is been monitored by a proxy? do you use active or passive proxy?
      Debian-User

      Sorry for my bad english

      Comment

      • MichaelM
        Member
        • Sep 2008
        • 38

        #4
        Hi Colttt,

        yes, my host "sensor-1" which runs an agent and a proxy is now set as "monitored by proxy", which is the machine itself. I don't know if this is wise idea or better should be avoided.

        ProxyMode=0, aka active mode.

        ServerActive points to server and proxy, the log complains about that my host is not defined on the server, I guess because of the proxy setting. Maybe I should change this to the proxy ip only.

        --Michael

        Comment

        Working...