net.if.in and net.if.out not working right

[marius]

I have net.if.in[eth0], net.if.in[eth1], net.if.out[eth0], and net.if.out[eth1] all configured identically with "float" type, Bps unit, 8 mutiplier, speed per second, etc.

For some bizarre reason, only net.if.in[eth0] is collecting data. The other three are always showing 0 Bps.

So I looked at the agent logs and found that the other three are always sending the same number: 4294967295.

Any idea what's going on? I'm using Beta9.

thanks.

[marius]

bug?

it appears that this might be a bug. I think zabbix is hitting the int/float limit. Will this be fixed in beta10? I can attempt to fix interfaces.* files myself or write a custom script, but if it will be fixed in beta10 i'd rather wait.

[Alexei]

What correct big number do you expect from net.if.in[eth1]?

[just2blue4u]

see my thread ... i got a similar problem. This could really be int limit!

[marius]

What correct big number do you expect from net.if.in[eth1]?

eth1:17773837926 22979267 0 0 0 0 0 4036 4808081744 19905268 0 0 0 0 0 0

[marius]

FYI. This issue still not fixed in beta10.

[madm1ke]

I have that on x86_64 with 32bit-agent.
It has been fixed by simple recompiling agent in 64bit.

[marius]

I have that on x86_64 with 32bit-agent.
It has been fixed by simple recompiling agent in 64bit.

Ah... duh. I think that's it - i'll give it a shot. thanks!

[edit] that was it. thanks for the help madm1ke! [/edit]