pfSense » pfSense Packages

It looks like the includes on that package are rather messed up. It's trying to install a bunch of unneeded X libraries and who knows what else.

And yet, the problem is it doesn't include all the packages it really needs.

In a default install the following packages are missing:

• GeoIP (uses /usr/lib/libGeoIP.so.5)

• rrdtool (uses /usr/lib/librrd_th.so) rrdtool also pulls in a HUGE load of packages itself, including python26 (could a custom lib-only package be provided? be enough?), xproto, freetype, cairo (linked in ntop as well), pango (linked in ntop), fonts, etc.

So yes all the packages it pulls, it actually uses (wow), but it missed these two and the basketload of dependencies they pull.

Extra update. it seems rrdtool 1.4.3 pulled in this build is too new for this ntop, since it provides librrd_th.so.5 and ntop is linked against librrd_th.so.4.

The crude hack of symlinking .so.5 to .so.4 works... but, it's a crude hack.

I hate being an utter n00b, but how does one attempt to install the various missing packages? I would love to get ntop running, but I am a little clueless as to how. Do I add the ports collection as some people have suggested?

See additional related errors in #1285 and #1330

Hello,
on my secondary machine (CARP as backup) the service starts, but after 1 minute the service stops and I see on the log:

kernel: pid 27907 (ntop), uid 0: exited on signal 11 (core dumped)

On the Master machine it's working great... The machine has been just updated and all the packages reinstalled... I don't know if I can send you some more log to see...

Thanks,
Michele

One of the many joys of ntop... you might try to remove the package and reinstall it, to make sure it's got all of the proper dependencies.

I did, no way, still stops after few time...
maybe updating ntop to the latest version could help, but anyway it's another bug than this and in my case has no real impact since it's only on the secondary machine...

We're using the latest version of ntop from the FreeBSD ports tree.

The only other thing I can think of that might help in your case might be to remove all other packages, then do a firmware update, and reinstall ntop. That should make sure that libraries are known-good versions from the base system and ntop. Failing that, a wipe+reload+restore the config, then reinstall the package might help.

Sadly ntop has so many dependencies that debugging it can be quite a pain. I've installed it on several more systems/VMs since yesterday and still haven't had any issues. It's been running for over 24hrs on one of my VMs, which is more than it did most of the time on 1.2.3 for me...