>> Hi, >> >> I got around the nfstrack issue by commenting out its locally supplied >> LocalErr. It seems to be running, is there a way to accurately check? >> >> However, when I try to graph, I get no graph, and in my syslog I see : >> >> Jun 10 08:29:19 valhalla nfsen[40163]: comm server started: 40536 >> Jun 10 08:29:19 valhalla nfsen[40536]: Cmd Decode: >> PortTracker::get-portgraph >> Jun 10 08:29:22 valhalla nfsen[40163]: connection on UNIX socket >> Jun 10 08:29:22 valhalla nfsen[40163]: comm server started: 40537 >> Jun 10 08:29:22 valhalla nfsen[40537]: Cmd Decode: >> PortTracker::get-portgraph >> Jun 10 08:29:24 valhalla nfsen[40163]: connection on UNIX socket >> Jun 10 08:29:24 valhalla nfsen[40163]: comm server started: 40538 >> Jun 10 08:29:24 valhalla nfsen[40538]: Cmd Decode: >> PortTracker::get-portgraph >> Jun 10 08:29:35 valhalla nfsen[40163]: comm child[40532] terminated >> Exit: >> 0, Signal: 13, Core: 0 >> Jun 10 08:29:41 valhalla nfsen[40163]: comm child[40535] terminated >> Exit: >> 0, Signal: 13, Core: 0 >> Jun 10 08:29:55 valhalla nfsen[40163]: comm child[40537] terminated >> Exit: >> 0, Signal: 13, Core: 0 >> Jun 10 08:29:56 valhalla nfsen[40163]: comm child[40536] terminated >> Exit: >> 0, Signal: 13, Core: 0 >> Jun 10 08:29:56 valhalla nfsen[40163]: comm child[40534] terminated >> Exit: >> 0, Signal: 13, Core: 0 >> Jun 10 08:29:58 valhalla nfsen[40163]: comm child[40538] terminated >> Exit: >> 0, Signal: 13, Core: 0 >> >> Any way to track whats happening? >> >> Thanks, Tuc >> > I printed out the RRDARGS incase thats my issue, and I see : > > > Jun 10 09:02:28 valhalla nfsen[41421]: - > DEF:Port37506=/usr/local/logs/flows/ports-db/tcp-bytes-36.rrd:p642:AVERAGE > DEF:Port23=/usr/local/logs/flows/ports-db/tcp-bytes-0.rrd:p23:AVERAGE > DEF:Port445=/usr/local/logs/flows/ports-db/tcp-bytes-0.rrd:p445:AVERAGE > DEF:Port65533=/usr/local/logs/flows/ports-db/tcp-bytes-63.rrd:p1021:AVERAGE > DEF:Port65532=/usr/local/logs/flows/ports-db/tcp-bytes-63.rrd:p1020:AVERAGE > DEF:Port65531=/usr/local/logs/flows/ports-db/tcp-bytes-63.rrd:p1019:AVERAGE > DEF:Port65530=/usr/local/logs/flows/ports-db/tcp-bytes-63.rrd:p1018:AVERAGE > DEF:Port65529=/usr/local/logs/flows/ports-db/tcp-bytes-63.rrd:p1017:AVERAGE > DEF:Port65528=/usr/local/logs/flows/ports-db/tcp-bytes-63.rrd:p1016:AVERAGE > DEF:Port65527=/usr/local/logs/flows/ports-db/tcp-bytes-63.rrd:p1015:AVERAGE > --start 1276087500 --end 1276173900 -w 288 -h 150 --no-legend COMMENT:Top > 10 Ports\n LINE1:Port37506#ff0000:Port 37506 LINE1:Port23#ff8000:Port 23 > LINE1:Port445#ffff00:Port 445 LINE1:Port65533#80ff00:Port 65533 > LINE1:Port65532#00ff00:Port > > > Actually, I'm finding that anything using rrdgraph.cgi is an issue. Is there anything I need to be aware of with this?
Tuc ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Nfsen-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
