I run syslog-ng 1.4.4, and it works fine except for one thing: the Linux klogd seems to have problems with it. When both daemons are running, no kernel messages are logged at all. An strace on klogd shows the following error: connect(1, {sun_family=AF_UNIX, sun_path="/dev/log"}, 10) = -1 EPROTOTYPE (Protocol wrong type for socket) Killing syslog-ng and starting syslogd without touching klogd makes it run fine. What could be the problem? I've read on the list that the starting order of the daemons is important, but I tried all possibilities, always with the same behaviour. My source config: source src { unix-stream( "/dev/log" ); internal(); } ; Stefan
Has anyone attempted sending log messages to a MySQL databse instead of a flat file? Is this possible with syslog-ng or would I need to find some other syslogd replacment? -Eric ######################################################################### Eric Pierce Phone: (813) 974-1798 Academic Computing Fax: (813) 974-1799 University of South Florida
How bout sending the output to a script which in turn sends it into the db? Or send it to a fifo and write a quick perl script to listen to that fifo and insert the logs into MySQL. I'm sure I recall something on this list some time ago regarding MySQL. John Eric Pierce (epierce@ritchie.acomp.usf.edu) wrote:
Has anyone attempted sending log messages to a MySQL databse instead of a flat file? Is this possible with syslog-ng or would I need to find some other syslogd replacment?
-Eric
participants (3)
-
Eric Pierce
-
John
-
Stefan Stammler