network-interfaces traffic - problem

[yso]

Hi there

I've searched allready the forum, but I didn't found a solution.

We monitor many linux-servers. They all will have a long uptime.

Now the problem is, that the networkinterface isn't monitored.

Error we get on the item (net.if.in[eth0,bytes] / net.if.out[eth0,bytes]) is:
Type of received value [2537397249427] is not suitable for value type [Numeric (float)]

We have others systems, witch running fine, but the don't have so much traffic.

I found 2 Bugs about this problems, but they should be fixed in 1.8.3

Server is running: 1.8.6 (mysql)
Agent is running 1.8.5

Anybody has the same Problem? Is there any workaround?

thanks for any hint

andy

[richlv]

what's the item configuration - specifically, "multiplier" and "store as" ?

[yso]

I've added a screenshot.



The same Item is working on another linux-server.

I think the problem is related to the high value, the agent gives to the server.

[richlv]

hmm, indeed the only problems i can recall regarding this should be fixed in your version. no further ideas at this point.

just a small note, update interval of 5 seconds is terribly small, i'd seriously suggest increasing it (although that wouldn't solve your problem)

[yso]

Thanks for reply.

There are several BUG's-Reports.. but they looks all fixed.


Does nobody have Interfaces with more than 2 TB Traffic since reoot?

The only idea I have to reset the counter wth a cron job, but to reset I need to unload the kernel-driver, witch end in a short connectio brake.

Any suggestion how to proceed? Open new BUG? Reopen existing BUG?

Some Links (Zabbix-BUG-Reports):
ZBX-1741
ZBX-2272
ZBX-1126

[richlv]

you could try testing with a controlled dataset and figure out what exactly triggers the problem

[yso]

In my point of view, the high value is the problem.

But I don't know how to change the Database to Support the higher value, or howto do more debugging.

Zabbix-Agent:

ifconfig
eth0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX
inet addr:192.168.XX.XX Bcast:192.168.XX.XX Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:xx:xx/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5575302648 errors:0 dropped:0 overruns:0 frame:0
TX packets:5570671806 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2629197322144 (2.3 TiB) TX bytes:2565441169083 (2.3 TiB)

Zabbix-Server:

non-working:

xxxx:/var/log# zabbix_get -s192.168.XX.XX -knet.if.out[eth0,bytes]
2565445062711

working:

xxxx:/var/log# zabbix_get -s192.168.YY.YY -knet.if.out[eth0,bytes]
8443584

[richlv]

well... the only idea i have right now is that you somehow are running an older version of server (or maybe there's a regression...). i'd suggest doublechecking that you don't have two zabbix server binaries in the system and that the one starting up is indeed 1.8.6 or .7

[yso]

sorry... no luck!

xxxx:/var/log# ps aux | grep zabbix
zabbix 964 0.0 0.0 49952 560 ? SN Aug31 0:00 /usr/sbin/zabbix_agentd
zabbix 970 0.1 0.0 49952 772 ? SN Aug31 3:02 /usr/sbin/zabbix_agentd
zabbix 971 0.0 0.0 52056 1132 ? SN Aug31 1:07 /usr/sbin/zabbix_agentd
zabbix 972 0.0 0.0 49984 756 ? SN Aug31 1:04 /usr/sbin/zabbix_agentd
zabbix 973 0.0 0.0 52056 1132 ? SN Aug31 1:05 /usr/sbin/zabbix_agentd
zabbix 974 0.0 0.0 52056 1132 ? SN Aug31 1:11 /usr/sbin/zabbix_agentd
zabbix 975 0.0 0.0 49984 760 ? SN Aug31 1:06 /usr/sbin/zabbix_agentd
zabbix 976 0.0 0.0 49952 564 ? SN Aug31 0:06 /usr/sbin/zabbix_agentd
zabbix 1675 0.0 0.1 122028 2492 ? SN Aug31 0:01 /usr/sbin/zabbix_server
zabbix 1676 0.0 0.4 122100 8780 ? SN Aug31 1:35 /usr/sbin/zabbix_server
zabbix 1677 0.0 0.9 122472 18764 ? SN Aug31 2:50 /usr/sbin/zabbix_server
zabbix 1678 0.0 0.9 122472 18824 ? SN Aug31 2:35 /usr/sbin/zabbix_server
zabbix 1679 0.1 0.9 122472 18804 ? SN Aug31 3:03 /usr/sbin/zabbix_server
zabbix 1680 0.0 0.9 122472 18784 ? SN Aug31 2:14 /usr/sbin/zabbix_server
zabbix 1681 0.1 0.9 122472 18904 ? SN Aug31 3:04 /usr/sbin/zabbix_server
zabbix 1682 0.0 0.0 122108 1964 ? SN Aug31 0:01 /usr/sbin/zabbix_server
zabbix 1683 0.0 0.0 122108 1964 ? SN Aug31 0:01 /usr/sbin/zabbix_server
zabbix 1684 0.0 0.0 122108 1964 ? SN Aug31 0:01 /usr/sbin/zabbix_server
zabbix 1685 0.0 0.0 122108 1964 ? SN Aug31 0:01 /usr/sbin/zabbix_server
zabbix 1686 0.0 0.0 122108 1964 ? SN Aug31 0:01 /usr/sbin/zabbix_server
zabbix 1689 0.1 0.7 122592 15592 ? SN Aug31 3:00 /usr/sbin/zabbix_server
zabbix 1690 0.0 0.0 122028 1932 ? SN Aug31 0:01 /usr/sbin/zabbix_server
zabbix 1691 0.1 0.0 122092 1872 ? SN Aug31 3:31 /usr/sbin/zabbix_server
zabbix 1692 0.1 0.2 122100 5320 ? SN Aug31 3:50 /usr/sbin/zabbix_server
zabbix 1693 0.0 0.9 125872 19976 ? SN Aug31 1:14 /usr/sbin/zabbix_server
zabbix 1695 0.0 0.5 124316 11368 ? SN Aug31 0:55 /usr/sbin/zabbix_server
zabbix 1696 0.0 0.1 122028 2764 ? SN Aug31 0:00 /usr/sbin/zabbix_server
zabbix 1697 0.2 0.7 122304 14784 ? SN Aug31 6:46 /usr/sbin/zabbix_server
zabbix 1698 0.0 0.0 122100 2000 ? SN Aug31 0:09 /usr/sbin/zabbix_server
zabbix 1704 0.0 0.8 125524 17652 ? SN Aug31 1:36 /usr/sbin/zabbix_server
zabbix 1705 0.0 0.8 125216 17316 ? SN Aug31 0:58 /usr/sbin/zabbix_server
zabbix 1706 0.0 0.8 125492 17568 ? SN Aug31 1:23 /usr/sbin/zabbix_server
zabbix 30937 0.0 0.0 3952 564 ? SN 13:42 0:00 sh -c /usr/bin/fping -q -C3 2>&1 </tmp/zabbix_server_1689.pinger;/usr/bin/fping6 -q -C3 2>&1 </tmp/zabbix_server_1689.pinger
zabbix 30938 0.0 0.0 5964 688 ? SN 13:42 0:00 /usr/bin/fping -q -C3
root 30940 0.0 0.0 7548 832 pts/1 S+ 13:42 0:00 grep zabbix
xxxx:/var/log#


xxxx:/var/log# /usr/sbin/zabbix_server -V
Zabbix Server v1.8.6 (revision 20932) (4 August 2011)
Compilation time: Aug 31 2011 11:47:40

[yso]

just a small note, update interval of 5 seconds is terribly small, i'd seriously suggest increasing it (although that wouldn't solve your problem)

Thanks for this Tip, will change it to 60 Sec.

[yso]

Solved..

Problem was.. that we still ran the old version. I've replaced, the Binaries and tried to restart the server.

But the server did not restart.. so the old 1.8.2-Binary was still in memory and running. After a small change in the Configfile, the 1.8.2-Binary is up and running.

And my Problems are fixed... thank you very very much.. richlv

[richlv]

do i get a cookie for a correct guess ? :>

i also hope "1.8.2-Binary is up and running" part is not correct

[yso]

You are welcome for cookie and coffee in our Office in Zurich.

Sorry.. I will make to much multitasking at the moment.