Hi Peter, On Mon, Feb 12, 2007 at 03:53:12PM +0100, Peter Haag wrote:
> Can't read from socket means, you do not have an nfsen-comm process. What does > the log file say? You should see the startup of the comm server. As far is I can tell the nfsen-comm process is running: _nfdump 23913 1 0 14:43 ? 00:00:02 /usr/local/bin/nfcapd -w -D -I SURFnet <snip> _nfdump 23919 1 0 14:43 ? 00:00:00 /usr/local/bin/nfcapd -w -D -I Oxygen4 <snip> _nfdump 23965 1 2 14:45 ? 00:03:04 /usr/bin/perl -w /data/nfsen/bin/nfsend _nfdump 23966 23965 0 14:45 ? 00:00:00 /data/nfsen/bin/nfsend-comm The logging seems to look fine. Although this one is probably not good: Feb 12 15:17:27 localhost nfsen[23966]: connection on UNIX socket Feb 12 15:17:37 localhost nfsen[24742]: Failed: Timeout reading from socket! at /data/nfsen/libexec/Nfcomm.pm line 702, <STDIN> line 1. Feb 12 15:17:37 localhost nfsen[23966]: comm child 24742 terminated - no exit value Feb 12 15:17:37 localhost nfsen[23966]: connection on UNIX socket Feb 12 15:17:47 localhost nfsen[24743]: Failed: Timeout reading from socket! at /data/nfsen/libexec/Nfcomm.pm line 702, <STDIN> line 1. Feb 12 15:17:47 localhost nfsen[23966]: comm child 24743 terminated - no exit value Feb 12 15:17:47 localhost nfsen[23966]: connection on UNIX socket Feb 12 15:17:57 localhost nfsen[24744]: Failed: Timeout reading from socket! at /data/nfsen/libexec/Nfcomm.pm line 702, <STDIN> line 1. Feb 12 15:17:57 localhost nfsen[23966]: comm child 24744 terminated - no exit value Feb 12 15:19:12 localhost nfsen[23966]: connection on UNIX socket Feb 12 15:19:22 localhost nfsen[24764]: Failed: Timeout reading from socket! at /data/nfsen/libexec/Nfcomm.pm line 702, <STDIN> line 1. Feb 12 15:19:22 localhost nfsen[23966]: comm child 24764 terminated - no exit value Feb 12 15:19:22 localhost nfsen[23966]: connection on UNIX socket Feb 12 15:19:32 localhost nfsen[24765]: Failed: Timeout reading from socket! at /data/nfsen/libexec/Nfcomm.pm line 702, <STDIN> line 1. > If the comm server is not running - you will not get anything in the > interface. > You should also see the status of nfsen running > ./nfsen status Hmm. two out of three are running :-) Initially it was the SURFnet one which was not running. For the moment it is. liberouter:/data/nfsen# ./bin/nfsen status NfSen status: Collector for 'SURFnet' pid: [23913] is running. Collector for 'Oxygen6' is not running. Collector for 'Oxygen4' pid: [23919] is running. nfsen daemon: pid: [23965] is running. liberouter:/data/nfsen# Cheers, -Wim -/- SURFnet ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Nfsen-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
