Ad Widget

Collapse

zabbix on low powered board

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • wpervaiz
    Member
    • May 2009
    • 30

    #1

    zabbix on low powered board

    so i installed zabbix on a low powered board. This will be running a zabbix proxy.

    Installation and configuration went fine. Proxy reports back to server perfectly.

    The only trouble I'm having now is that some pings are being reported falsely. Certain devices return 0 when ping'ed, but I know those devices are up. The devices come back up in 10 minutes, and then go back down. This keeps happening all day.

    I was assuming the board didnt have enough juice, but using the "top" command (its ubuntu) zabbix proxy is using no more than 5% of cpu and 1 % of memory. ntop reports network usage as normal as well. its flash memory so I'm certain its not read/write speeds that are causing the problem.

    Its "wrong" ping responses more than "missing" ping responses. i.e. devices are reported as down.

    From the config file, I changed forked instances to minimums (i.e. 1) but still no luck. Increased timeout to 15 seconds. still no go.

    Any ideas? has anyone experienced this before ?

    thanks guys !
  • wpervaiz
    Member
    • May 2009
    • 30

    #2
    bump, anyone ??

    Comment

    • wpervaiz
      Member
      • May 2009
      • 30

      #3
      ok, so i figured out its fping with the -s option thats causing the problem.

      how do i disable the -s option or add that to my fping file ??

      thanks !

      Comment

      • wpervaiz
        Member
        • May 2009
        • 30

        #4
        this is what i get when i do something like:

        fping -s www.google.com

        www.google.com is alive

        1 targets
        1 alive
        0 unreachable
        0 unknown addresses

        0 timeouts (waiting for response)
        1 ICMP Echos sent
        1 ICMP Echo Replies received
        0 other ICMP received

        *** buffer overflow detected ***: fping terminated
        ======= Backtrace: =========
        /lib/libc.so.6(__fortify_fail+0x44)[0x40104a2c]
        /lib/libc.so.6(__vsprintf_chk+0x88)[0x40101c7c]
        ======= Memory map: ========
        00008000-0000f000 r-xp 00000000 fd:01 21177 /usr/bin/fping
        00016000-00017000 r-xp 00006000 fd:01 21177 /usr/bin/fping
        00017000-00018000 rwxp 00007000 fd:01 21177 /usr/bin/fping
        00018000-0003a000 rwxp 00000000 00:00 0 [heap]
        40000000-4001d000 r-xp 00000000 fd:01 1140 /lib/ld-2.9.so
        4001d000-4001f000 rwxp 00000000 00:00 0
        40023000-40024000 rwxp 00000000 00:00 0
        40024000-40025000 r-xp 0001c000 fd:01 1140 /lib/ld-2.9.so
        40025000-40026000 rwxp 0001d000 fd:01 1140 /lib/ld-2.9.so
        40026000-40147000 r-xp 00000000 fd:01 1322 /lib/libc-2.9.so
        40147000-4014f000 ---p 00121000 fd:01 1322 /lib/libc-2.9.so
        4014f000-40151000 r-xp 00121000 fd:01 1322 /lib/libc-2.9.so
        40151000-40152000 rwxp 00123000 fd:01 1322 /lib/libc-2.9.so
        40152000-40155000 rwxp 00000000 00:00 0
        40155000-4015e000 r-xp 00000000 fd:01 1310 /lib/libnss_files-2.9.so
        4015e000-40166000 ---p 00009000 fd:01 1310 /lib/libnss_files-2.9.so
        40166000-40167000 r-xp 00009000 fd:01 1310 /lib/libnss_files-2.9.so
        40167000-40168000 rwxp 0000a000 fd:01 1310 /lib/libnss_files-2.9.so
        befad000-befc2000 rw-p 00000000 00:00 0 [stack]
        Aborted

        Comment

        Working...