security wrote: > I'm trying to bring up a ntop 3.3 instance to be only a netflow receiver > from a cisco 6500. interfaces are set to none (which seems to annoy the > web interface). I start the server and the initialization seems to take > forever (at this point it's over an hour and it's still not done). It's > running on a dual 3ghz, 8 GB memory box that's idle. To the best of my > knowledge, I haven't enabled any debug other than setting the trace > level to 4 to help debug this. I downloaded from sourceforge a few days > ago, > > Seems unlikely this is the way it should be running. Any ideas on what > I might check? > More data. If I start ntop NOT using the conf file, not as a daemon, but just pass what I want on the command line, it works fine.
/usr/local/bin/ntop -P /usr/local/share/ntop -u ntop -i none -w 80 (only the NetFlow and RRD plugins are enabled) If I tell it from the command line, to go to daemon mode OR use syslog, it goes to crawl mode and is unusable. This is the latest svn, 3.3.4 Any ideas why becoming daemon would have that effect? I'm also seeing, "Fri Nov 9 13:11:24 2007 **WARNING** INITWEB: Reporting device (2) invalid (> max, 2), defaulting to 0" thanks jim _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
