Ad Widget

Collapse

zabbix_sender weird source IP selection

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ShyLionTmn
    Junior Member
    • Dec 2014
    • 5

    #1

    zabbix_sender weird source IP selection

    Hello.

    Code:
    # zabbix_sender -V
    Zabbix Sender v2.2.7 (revision 50148) (24 October 2014)
    Compilation time: Nov  2 2014 08:54:43
    Code:
    ]# /bin/zabbix_sender -vv -T -I 127.0.0.1 -z 127.0.0.1 -i /tmp/olt_data.olt-02-27.10.0.7.27
    zabbix_sender [17849]: DEBUG: answer [{
            "response":"success",
            "info":"processed: 0; failed: 250; total: 250; seconds spent: 0.008477"}]
    info from server: "processed: 0; failed: 250; total: 250; seconds spent: 0.008477"
    zabbix_sender [17850]: DEBUG: answer [{
            "response":"success",
            "info":"processed: 0; failed: 214; total: 214; seconds spent: 0.007216"}]
    info from server: "processed: 0; failed: 214; total: 214; seconds spent: 0.007216"
    sent: 464; skipped: 0; total: 464
    Code:
    # tail zabbix_server.log
      3448:20150127:092954.719 cannot process trapper item "onuMAC[EPON0/3:18]": connection from "10.1.1.18" rejected, allowed hosts: "127.0.0.1"
      3448:20150127:092954.719 cannot process trapper item "onuStatus[EPON0/3:18]": connection from "10.1.1.18" rejected, allowed hosts: "127.0.0.1"
      3448:20150127:092954.719 cannot process trapper item "onuifAdminStatus[EPON0/3:19]": connection from "10.1.1.18" rejected, allowed hosts: "127.0.0.1"
      3448:20150127:092954.719 cannot process trapper item "onuifOperStatus[EPON0/3:19]": connection from "10.1.1.18" rejected, allowed hosts: "127.0.0.1"
      3448:20150127:092954.719 cannot process trapper item "onuifInOctets[EPON0/3:19]": connection from "10.1.1.18" rejected, allowed hosts: "127.0.0.1"
      3448:20150127:092954.719 cannot process trapper item "onuifOutOctets[EPON0/3:19]": connection from "10.1.1.18" rejected, allowed hosts: "127.0.0.1"
      3448:20150127:092954.719 cannot process trapper item "onuoltRxPower[EPON0/3:19]": connection from "10.1.1.18" rejected, allowed hosts: "127.0.0.1"
      3448:20150127:092954.719 cannot process trapper item "onuonuRxPower[EPON0/3:19]": connection from "10.1.1.18" rejected, allowed hosts: "127.0.0.1"
      3448:20150127:092954.719 cannot process trapper item "onuMAC[EPON0/3:19]": connection from "10.1.1.18" rejected, allowed hosts: "127.0.0.1"
      3448:20150127:092954.719 cannot process trapper item "onuStatus[EPON0/3:19]": connection from "10.1.1.18" rejected, allowed hosts: "127.0.0.1"
    WTF? Why 10.1.1.18 is chosen for source IP?
    Is there a way to specify wildcard for item allowed IPs?

    Code:
    ]# uname -a
    Linux net-mon-01.local 3.10.0-123.8.1.el7.x86_64 #1 SMP Mon Sep 22 19:06:58 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
    Code:
    # cat /etc/centos-release
    CentOS Linux release 7.0.1406 (Core)
  • Abhiram_Cloud4c
    Junior Member
    • Nov 2016
    • 10

    #2
    facing same issue with zabbix trapper and sender

    We are facing the same error when trying to send data from zabbix sender. Could you please share the solution if this issue was resolved for you?

    Comment

    • ShyLion
      Junior Member
      • Jul 2009
      • 4

      #3
      I've stoped using zabbix long ago and created my own custom software.
      Decided it's better for me to make own software than struggle with zabbix.

      Comment

      • allexpetrov
        Senior Member
        Zabbix Certified Trainer
        Zabbix Certified SpecialistZabbix Certified Professional
        • May 2017
        • 361

        #4
        Originally posted by Abhiram_Cloud4c
        We are facing the same error when trying to send data from zabbix sender. Could you please share the solution if this issue was resolved for you?
        Code:
         connection from "10.1.1.18" rejected, allowed hosts: "127.0.0.1"
        Abhiram_Cloud4c,
        this means that, in this case, zabbix are trying to connect using 10.1.1.18 interface, not the 127.0.0.1 which is defined in your config file. It is normal, just add another IP to white list and voilĂ 

        Comment

        Working...