Ntop with Pfsense 1.2.3
-
Did you uninstall/reinstall the package after the date on my last post?
Also, those promisc. mode messages are typically seen with the rate package, not ntop. Do you have that installed?
The dnsmasq process happens periodically, and that one happened several minutes after your ntop crash, it's not related.
-
sorry, I didn't see your reply before I made my last edit.
Yes, I have rate installed. Should I try uninstalling it? and I installed ntop today for the first time (Feb 2, 2010).
Also, was old accounts wiped or something? I had an account I thought that was under this username from like 2007 or so and I had to recreate this account a while back to post.
-
The presence of the rate package shouldn't help or hurt ntop.
FYI- ntop is still running on my router at work since my post saying it was OK, and it used to only last 10 minutes and behave exactly like yours (core dump and all).
Old accounts shouldn't be wiped, but I can look one up by username or e-mail if you want me to check on one. Send me a PM if you want me to check.
-
Yeah, I tried removing the rate package and it didn't make a bit of difference. I actually deleted the ntop package after I made that post and reinstalled and got the same results. I had to leave work early for a doctor's appointment and had a fellow technician check it out for me. :-[
Anyways, I'm gonna try a few other things throughout the day and see if I can figure out what's going on. I've been pretty loyal to pfSense since I found the project and since I got hired back to this company after one of the owners departed, I've wanted to move from Endian back to pfSense. The only reason we used Endian was for the web interface it has for OpenVPN. Is the client tls/auth package pretty much the same thing?
As a side note, from what I've read, I can't wait to have the openvpn client export package working for 2.0. I woulda really liked to have used pfSense 2.0-BETA instead of 1.2.3-RELEASE but we ran into the issue where putting the IP in staticly made it where the box wouldn't keep the default route (atleast that's what the other tech said he ran into and said after checking google that he found it was a known issue).
If I figure out what my problem is, I'll be sure to report back to the forum as it's been invaluable for me in the past. :)
-
I removed all the network monitoring packages, rebooted the router and reinstalled ntop and now it works. Go figure.
Sorry :-[
-
I found a problem,the logs:
ERROR: sanity check failed < low memory >
what can I do I just knew how to use it
please teach me I am a chinese
-
Well, it looks to me like I've fixed it. Its been running for almost 20 minutes now with no problems. Usually it quits after 3 minutes. Sometimes even 30 secs.
It appears that it was a simple permission and ownership problem.
I just had to do
#chmod -R 755 /var/db/ntop #chown -R nobody:nobody /var/db/ntop
Thanks, this worked for me as well.
ntop was not working for some weeks, and now i can also starts and stops from the gui -
Seems to be working for me too But I had to uninstall darkstat to keep Ntop from crashing.
-
Hi all,
I'm new to pfSense and it's my first post ;)
I installed a pfSense (1.2.3) for my company using a multiwan connection and I have the same problem. Ntop die quickly. I tried to remove "bandwidthd" and reinstall ntop package, but it doesn't work.
I try the chmod/chown method, but it doesn't work neither.
But, perhaps I found something, in the webgui, when you start ntop, you can select the interface to scan. If I select the 3 (2 wan, 1 lan), there's the problem, ntop die. But when I select only the 2 wan, or when I select only the lan, it seems that ntop doesn't crash (usually ntop crash before 10 minutes, with that configuration ntop doesn't crash in one hour).
So, If someone have an idea to solve that in another way …
Cheers.
Gilles.
-
why do you want Ntop running on the WAN???
LAN should have all the info you need -
I committed a fix for the permissions to the ntop package just now, but I didn't do a version bump yet. If it turns out to work for everyone, I may do that just to signal to people there has been a change.
There were commands in there before that should have fixed the permissions, but the command wasn't specified with the full path so it may have been failing. I'd be curious if anyone who is experiencing the crashes would try to reinstall the ntop now (or rather about 5 minutes from the time of this post to be sure the commit is live on the package server).
I have one server I will be trying this one, where ntop would die quite often.
jimp
do you know if your fix is in the a new ntop package yet???
Thanks
-
That post is from almost a year ago, and it was committed at the time I posted the message. If you have problems, please start a new thread instead of hijacking a thread that has been dead for many months.