On Mon, Mar 10, 2008 at 05:08:06PM -0500, Joe Wells wrote:
> Yup, it's a counter. I'm re-doing it as gauge to see what happens. Looks
> better already, though.
>
> I thought that this would be a counter, and the JFFNMS docs list it as a
> counter.
ICMP messages should be a counter. You don't care
On Wed, Mar 12, 2008 at 02:31:18PM -0400, ... wrote:
> Hi
> Here is some more on that EAGAIN error;
Without knowing what filedescriptor 7 is, it kinda makes it not that
useful.
> Here is the output of that other command I was asked to run;
> [EMAIL PROTECTED]:~# ls -l /proc/3422/fd/7
> lr-x--
Hi
Here is some more on that EAGAIN error;
access("/opt/jffnms/rrd/interface-11379-8.rrd", F_OK) = 0
write(6, "update \'/opt/jffnms/rrd/interfac"..., 57) = 57
fcntl64(7, F_GETFL) = 0x800 (flags O_RDONLY|O_NONBLOCK)
fcntl64(7, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
nanosleep({0, 1000
Hi, i notice same problem on a huge installation (about 1000 host and 15 000
interfaces). Try to figure out what cause the File Decriptor 7 to EAGAIN, if it
is rrdtool, you have to use rrdtool 1.3 beta and tune some things on your disk.
(use a separate block device for your rrd folder, reduce th
