From owner-freebsd-questions@FreeBSD.ORG Wed Sep 30 22:24:38 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 08C01106566B for ; Wed, 30 Sep 2009 22:24:38 +0000 (UTC) (envelope-from austin.friestman@gmail.com) Received: from mail-bw0-f227.google.com (mail-bw0-f227.google.com [209.85.218.227]) by mx1.freebsd.org (Postfix) with ESMTP id 8BC668FC18 for ; Wed, 30 Sep 2009 22:24:37 +0000 (UTC) Received: by bwz27 with SMTP id 27so5014468bwz.43 for ; Wed, 30 Sep 2009 15:24:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=HadV2PgPDQfPfKghX+wkbTgw1dCtYCuIwnj45UGUlN8=; b=Km0T6frmmIrCcyRJLMmYyD4vN6MaKUgZ71ivsFZnvkU+QUG01sAkBKPe5RpwBLemDt DxDJpCN3lUHP7xfJafOE+DsHkM0aPcGTFKKDwvA5Aacr8okYIgYMl1ae25SMGHqZQd90 nqNQU5caltbkwXEMGZr1Yo54aujDaSZ70umHE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=ZHCkhECfDZlzCabb2j/eUBn9lZGimkMI6OT30A8YpGv1TfQDe1Px0RJiozFAyrWoKS WdrS/PL8c5NQsLnlnEKauCl1PKAcpoQsBUUT8WNmUpxT9P/0CJFkv1BYxRviXhrw16y6 wP0kBxbMlHHJUrlUpBFZT18+byx64SqgVqgeg= MIME-Version: 1.0 Received: by 10.204.155.88 with SMTP id r24mr271498bkw.132.1254347773944; Wed, 30 Sep 2009 14:56:13 -0700 (PDT) Date: Wed, 30 Sep 2009 16:56:13 -0500 Message-ID: <96f71bae0909301456w4136b2aao2d3bb5112f42a9ef@mail.gmail.com> From: Austin Friestman To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: syslog-ng.conf.sample from port sysutils/syslog-ng3 errors X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Sep 2009 22:24:38 -0000 The sample config file for syslog-ng3 does not work. When I install sysutils/syslog-ng3 from ports, the sample config file /usr/local/etc/syslog-ng/syslog-ng.conf.sample seems to have a number of things wrong with it. First, the port is looking for it in /usr/local/etc not /usr/local/etc/syslog-ng contrary to what most of the tutorials on it's installation indicate. Once you've moved the file to the right location, this happens [afriestman@monolith /usr/local/etc]$ sudo /usr/local/etc/rc.d/syslog-ng start Starting syslog_ng. Configuration file has no version number, assuming syslog-ng 2.1 format. Please add @version: maj.min to the beginning of the file; WARNING: global: the default value of chain_hostnames is changing to 'no' in version 3.0, please update your configuration accordingly; Your configuration file uses an obsoleted keyword, please update your configuration; keyword='sync', change='flush_lines' WARNING: input: sources do not remove new-line characters from messages by default in version 3.0, please add 'no-multi-line' flag to your configuration if you want to retain this functionality; WARNING: file source: default value of follow_freq in file sources is changing in 3.0 to '1' for all files except /proc/kmsg; WARNING: template: the default value for template-escape is changing to 'no' in version 3.0, please update your configuration file accordingly; Unknown facility; facility='console' Adding @version3.0 to the first line of the file helps quite a bit [afriestman@monolith /usr/local/etc]$ sudo /usr/local/etc/rc.d/syslog-ng start Starting syslog_ng. Your configuration file uses an obsoleted keyword, please update your configuration; keyword='sync', change='flush_lines' Unknown facility; facility='console' Changing options { long_hostnames(off); sync(0); }; to options { long_hostnames(off); flush_lines(0); }; takes care of all but that last line. While searching for answers to this problem, I came across http://dbaspot.com/forums/solaris/240478-syslog-ng-warning-unknown-facility-facility-authpriv.html which suggests mapping of the facilities seems to be done in eventlog (which syslog-ng is based on) Neither of the two files in /usr/local/include/eventlog (evtlog.h and evtmaps.h) mention a thing about a console facility However, there is a LOG_CONSOLE definition in /usr/include/syslog.h, which is included in the above evtlog.h. see next line #define LOG_CONSOLE (14<<3) /* /dev/console output */ I feel like I'm close to getting syslog-ng working, I just need a little help now that I'm getting into parts of the system I'm not familiar with. [afriestman@monolith ~]$ uname -a FreeBSD monolith.vertive.local 7.2-STABLE FreeBSD 7.2-STABLE #0: Mon Sep 21 16:40:02 CDT 2009