On 5/29/08 4:38 PM, "Kevin Freels" <[EMAIL PROTECTED]> wrote:
> Greetings! > > We have ntop v.3.3.5 running on a server. This server has had ntop > running on it for quite a while (an earlier version, not sure which, 2.x > most likely) when all of a sudden it started dying on us with no reason. > I thought that it might be because I had set up a cron job to run tshark > (wireshark) on the same interfaces to do 5-minute captures on the > quarter-hours, but even disabling the cron had no effect. I also > upgraded the ntop to the version it's at now, but it still dies for no > apparent reason. > > I set it up to do a level 5 debug trace, but could not see anything that > was immediatly apparent from the stdout. Running in daemon mode had no > effect, it dies after anywhere from 30 seconds to 20 minutes after being > started. > > The only questionable error on stdout is: > > **ERROR** Sanity check failed (2) [Low memory?] > > but memory at the time that message was spit out was still about 300Mb > with nothing from swap even touched. When it dies, it frees up about > 30Mb of memory. > Out of curiosity, have you done a memory test on that box? http://www.memtest.org/ Snag and burn an iso and boot with it and see what happens....don't know why, but that's my hunch ;) James _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
