Hi Ann, On Tue, Feb 02, 2010 at 11:10:50AM -0800, Wallace, Ann wrote: > Is it possible this is a byte order/endian issue?
yes, that sounds a bit like an endian issue. We used to have an endian problem with double values which was fixed in 4.2.5 and 4.3.1 (and all later versions). Are *all* values sent from Linux to Solaris NaN or just some of them? Especially, can you check if you see a pattern between counter values (CPU usage, network and disk I/O) and gauge values (memory usage, DF graphs)? Did you cross-compile the daemon? I.e. did you compile it on a x86 machine for a SPARC architecture or something similar? In this case the configure script cannot determine the endianness of the target platform automatically. Is the data sent by Solaris machines stored correctly on the Linux server? This is a combination I have several times and know to work. Generally, at least, there's always room for more bugs I'm afraid ;) Regards, -octo -- Florian octo Forster Hacker in training GnuPG: 0x91523C3D http://verplant.org/
signature.asc
Description: Digital signature
_______________________________________________ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
