I've been working on moving my nfdump/nfsen collectors and reporting
boxes over to freebsd and have run into a snag that I can't seem to
get past.  I'm hoping someone on the list has seen a similar issue and
can point me in the right direction.  The system in question is a
freebsd 6.0-RELEASE box that is running apache 2 and PHP 5.2.6.  All
elements have been installed from ports using portinstall and I have
just upgraded php as well as php5-extensions yesterday.  I have php
compiled with socket support.
I have installed both nfdump and nfsen from ports using the same
mechanisms as the other packages.  I've tried the normal nfsen port
(1.2.4.20060810) as well as nfsen-devel (20070312) and both generate
the same errors.  The errors I'm seeing seem to be pretty common of
those running freebsd (but I've found no solution that works for me,
only problem reports) but I think I need some fresh insight since I
can't seem to make it work.
The error I'm working on now as reported by apache is:

[Fri May 30 14:43:32 2008] [error] [client 10.10.250.33] PHP Notice:
Undefined index:  nfsend in /a/www/htdocs/nfsen/nfsenutil.php on line
96
[Fri May 30 14:43:33 2008] [error] [client 10.10.250.33] PHP Warning:
socket_connect() [<a
href='function.socket-connect'>function.socket-connect</a>]: unable to
connect [61]: Connection refused in /a/www/htdocs/nfsen/nfsenutil.php
on line 25

nfsen is running and nfcapd is collecting flows.  I'm hoping that
someone with a little more fine tuned php/nfsen experience can point
out something I've missed or give me something else to look at, I
believe it's something simple that I'm just overlooking.

Any help appreciated!

nb

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Nfsen-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nfsen-discuss

Reply via email to