System log, too many logs from ntop
-
Hello
I have too many logs from ntop on every second.
How can i stop this ?Dec 18 11:20:24 ntop[21542]: **WARNING** RRD: rrd_update(/var/db/ntop/rrd/interfaces/re0/hosts/A4/BA/DB/FE/BC/12/totPeersRcvd.rrd) error: /var/db/ntop/rrd/interfaces/re0/hosts/A4/BA/DB/FE/BC/12/totPeersRcvd.rrd: illegal attempt to update using time 1387358424 when last update time is 1387358424 (minimum one second step) Dec 18 11:20:24 ntop[21542]: **WARNING** RRD: rrd_update(/var/db/ntop/rrd/interfaces/re0/hosts/A4/BA/DB/FE/BC/12/totPeersSent.rrd) error: /var/db/ntop/rrd/interfaces/re0/hosts/A4/BA/DB/FE/BC/12/totPeersSent.rrd: illegal attempt to update using time 1387358424 when last update time is 1387358424 (minimum one second step) Dec 18 11:20:24 ntop[21542]: **WARNING** RRD: rrd_update(/var/db/ntop/rrd/interfaces/re0/hosts/A4/BA/DB/FE/BC/12/bytesBroadcastSent.rrd) error: /var/db/ntop/rrd/interfaces/re0/hosts/A4/BA/DB/FE/BC/12/bytesBroadcastSent.rrd: illegal attempt to update using time 1387358424 when last update time is 1387358424 (minimum one second step)
ntop
ntop v.5.0.1 (64 bit) [amd64-8.3-RELEASE-p3-freebsd8.3]pfSense
2.1-RELEASE (amd64)
built on Wed Sep 11 18:17:37 EDT 2013
FreeBSD 8.3-RELEASE-p11 -
-
-
Sounds like either ntop is running multiple times, or you have a clock issue causing ntop to believe the clock is stepping backward or not ticking properly.
-
[2.1-RELEASE][root@microsoft]/root(4): ps
PID TT STAT TIME COMMAND
58054 v0 Is 0:00.01 login [pam] (login)
58558 v0 I 0:00.00 -sh (sh)
61550 v0 I+ 0:00.00 /bin/sh /etc/rc.initial
99460 v0- IN 0:31.26 /bin/sh /var/db/rrd/updaterrd.sh
58347 v1 Is 0:00.01 login [pam] (login)
58787 v1 I 0:00.00 -sh (sh)
61334 v1 I+ 0:00.00 /bin/sh /etc/rc.initial
8571 0 Is 0:00.00 -sh (sh)
9311 0 S 0:00.00 /bin/sh /etc/rc.initial
35972 0 S 0:00.01 /bin/tcsh
37597 0 R+ 0:00.00 ps[2.1-RELEASE][root@microsoft]/root(6): top
last pid: 77163; load averages: 0.02, 0.01, 0.00 up 2+02:39:36 15:34:32
85 processes: 1 running, 84 sleepingMem: 817M Active, 1829M Inact, 980M Wired, 464K Cache, 814M Buf, 4159M Free
Swap: 16G Total, 16G FreePID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND
57071 root 10 44 0 142M 57844K nanslp 1 3:52 0.00% ntop
39606 root 2 64 20 424M 397M select 1 3:47 0.00% clamd
82125 proxy 1 44 0 116M 99M kqread 1 2:13 0.00% squid
257 root 1 76 20 6908K 1368K kqread 1 1:41 0.00% check_reload_status
74729 root 2 44 0 404M 197M nanslp 1 1:27 0.00% snort
52656 nobody 1 44 0 8112K 3436K select 1 0:40 0.00% darkstat
21524 root 1 44 0 5780K 1440K select 1 0:37 0.00% apinger
99460 root 1 76 20 8296K 1696K wait 1 0:31 0.00% sh
41832 root 1 44 0 26268K 6604K kqread 1 0:09 0.00% lighttpd
43189 root 1 44 0 15264K 7164K select 1 0:08 0.00% ntpd
44271 havp 1 44 0 26344K 6864K nanslp 1 0:06 0.00% havp
63402 root 1 44 0 142M 41772K accept 1 0:05 0.00% php
31010 havp 1 44 0 26344K 8616K accept 0 0:04 0.00% havp
95932 root 1 44 0 11748K 3168K bpf 1 0:03 0.00% tcpdump
32907 havp 1 44 0 28392K 10212K accept 0 0:02 0.00% havp
32286 havp 1 44 0 28392K 10604K accept 0 0:02 0.00% havp
13118 root 1 44 0 6956K 1596K select 1 0:02 0.00% syslogd
32556 havp 1 44 0 28392K 10688K accept 0 0:02 0.00% havp -
Sounds like either ntop is running multiple times, or you have a clock issue causing ntop to believe the clock is stepping backward or not ticking properly.
Time zone set Europe/Athens
from console-terminal is ok.
Must to configure and ntop time ? seperetely ?