Nobody's touched that plugin since InMon donated is - a long time. Certainly not between 2.2.99 and 3.0...
Try turning on --trace-level 4 or higher and see what the log shows. Try turning on the debug in the plugin - be aware that will create a lot of output if there is any data flowing. All the usual ideas - try deleting ntopPrefs.db and recreating it, etc. Otherwise you just going to have to debug it the hard way... -----Burton > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf > Of Greg Paschall > Sent: Monday, April 05, 2004 2:59 PM > To: [EMAIL PROTECTED] > Subject: [Ntop-dev] sFlow won't start automatically > > > I have compiled and installed ntop v.3.0.050 (from CVS 04/05/2004) and > configured it to use sflow (configured sflow, turned the plugin on and > switched the NIC). However, when I restart ntop, the sflow plugin > doesn't start automatically. The configuration is still there (loaded > from the prefs db properly) and it says the plugin is running, but the > only NIC recognized is eth0. To get it to work, I have to turn the > plugin off and then on again (admin:plugins page), and then switch the > NIC to "sFlow-device" again. > > I know this used to work in v.2.2.99. > > Thanks, > > Greg Paschall > > -------- > Greg Paschall -- [EMAIL PROTECTED] > SSL Network & IT Manager > Space Sciences Lab - University of California at Berkeley > Room 230 -- (510) 643-6907 -- Fax: (510) 643-7629 > > _______________________________________________ > Ntop-dev mailing list > [EMAIL PROTECTED] > http://listgateway.unipi.it/mailman/listinfo/ntop-dev _______________________________________________ Ntop-dev mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
