Date: Wed, 12 Apr 2006 08:49:11 +0200 From: "Valerio daelli" <valerio.daelli@gmail.com> To: freebsd-questions@freebsd.org Subject: Hang in 5.3, related to syslog-ng Message-ID: <27dbfc8c0604112349o5d4ddda6uafd6fd7f60337d6f@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hi all we have a server with 5.3 (latest patches) with twelve jails. One of these jails is a mail server (mail-jail), serving about 300 users, writing a lot of logs to /var/log/maillog. On the same server I installed a jail with syslog-ng (syslog-jail). syslog-ng was configured to listen on the network and write to a named pipe. On the same jail I created a script to read from that named pipe and insert the result to mysql, but I didn't start this script. I was about to start this system of logging, so I modified /etc/syslog.conf in the mail-jail inserting a line like this: mail.* @logger_with_syslog-ng.my.domain then I restarted syslogd on the mail-jail sending a HUP signal. Suddendly the system stopped responding to anything (from ping to console, everything stopped). I rebooted the server turning off the power and deleted that line in syslog.conf. Everything worked. Could it be some issue related to a named pipe? Or pheraps to syslogd? Or syslog-ng? I tried recreating the situation on a test server with 5.4 but everything worked. Sorry if I don't have details but this is a very critical server for us and I can't experiment. Thanks Valerio Daelli
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?27dbfc8c0604112349o5d4ddda6uafd6fd7f60337d6f>