Xavier Fustero wrote:
> I have running syslog-ng on this server. I am wondering if there is a
> compatibily problem with the perl package Sys::Syslog and syslog-ng.
Not sure if this solves anything, but I always have an issue on Solaris
with
Sys::Syslog::setlogsock('unix');
I usually change this to
Sys::Syslog::setlogsock('inet');
I even considered asking Peter to make this some kind of configuration
option.
This is definitely not the solution to your issue that you can't see
any data. I also don't see any data. But at least I see something in
syslog. ;-)
Aug 8 18:52:05 nfsen[26751]: connection on UNIX socket
Aug 8 18:52:05 nfsen[26751]: comm server started: 8124
Aug 8 18:52:05 nfsen[8124]: Cmd Decode: get-globals
Aug 8 18:52:05 nfsen[8124]: Cmd Decode: get-du
Aug 8 18:52:05 nfsen[8124]: comm child[8125] terminated with no exit value
Aug 8 18:52:05 nfsen[8124]: Cmd Decode: get-profile
Aug 8 18:52:05 nfsen[8124]: Cmd Decode: quit
Aug 8 18:52:05 nfsen[26751]: comm child[8124] terminated with no exit value
Aug 8 18:52:05 nfsen[26751]: connection on UNIX socket
Aug 8 18:52:05 nfsen[8126]: Cmd Decode: get-picture
Aug 8 18:52:05 nfsen[26751]: comm server started: 8126
Cheers,
-Wim
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Nfdump-discuss mailing list
Nfdump-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfdump-discuss
