- syslog-ng - lists.balabit.hu

autoconf confusion attempting to install v1.6.6
by Joe 29 Mar '05

29 Mar '05

on FreeBSD 4.11 Stable #1 I'm obtaining the following error which seems pretty obvious: aclocal.m4:39: error: Autoconf version 2.54 or higher is required aclocal.m4:39: the top level autoheader: autom4te failed with exit status: 1 However, output from suggests I'm using the latest autoconf (I also installed the latest) The one hack I did do was to delete the system installed autoconf and symlink autoconf to the autoconf259 executable #`which autoconf` -V autoconf (GNU Autoconf) 2.59 Written by David J. MacKenzie and Akim Demaille. Not sure where to go with this. -- Joe -- Joe S. ------------ praxis makes perfect. - anon

2 1

Syslog-ng on Sol10 Compile problems...
by Smith, James 29 Mar '05

29 Mar '05

ok, I admit, I'm not great at compiling. Has anyone had any issues with getting syslog-ng to compile on Solaris10? I'm getting the following, but am not sure how to go about solving the issue. I'm compiling on an E3500 with gcc3.4.2, libol-0.3.15, and syslog-ng-1.6.6 gcc -g -O2 -Wall -I/usr/local/include/libol -D_GNU_SOURCE -o syslog-ng main.o sources.o center.o filters.o destinations.o log.o cfgfile.o cfg-grammar.o cfg-lex.o affile.o afsocket.o afunix.o afinet.o afinter.o afuser.o afstreams.o afprogram.o afremctrl.o nscache.o utils.o syslog-names.o macros.o -lpthread -lnsl -lsocket -ldoor -lresolv /usr/local/lib/libol.a -lsocket -lnsl -lxnet -Wl,-Bstatic -ll -Wl,-Bdynamic ld: fatal: library -ll: not found ld: fatal: File processing errors. No output written to syslog-ng collect2: ld returned 1 exit status *** Error code 1 make: Fatal error: Command failed for target `syslog-ng' Current working directory /tmp/syslog-ng-1.6.6/src *** Error code 1 The following command caused the error: set fnord $MAKEFLAGS; amf=$2; \ dot_seen=no; \ target=`echo all-recursive | sed s/-recursive//`; \ list='. tests'; for subdir in $list; do \ echo "Making $target in $subdir"; \ if test "$subdir" = "."; then \ dot_seen=yes; \ local_target="$target-am"; \ else \ local_target="$target"; \ fi; \ (cd $subdir && make $local_target) \ || case "$amf" in *=*) exit 1;; *k*) fail=yes;; *) exit 1;; esac; \ done; \ if test "$dot_seen" = "no"; then \ make "$target-am" || exit 1; \ fi; test -z "$fail" make: Fatal error: Command failed for target `all-recursive' Current working directory /tmp/syslog-ng-1.6.6/src *** Error code 1 make: Fatal error: Command failed for target `all' Current working directory /tmp/syslog-ng-1.6.6/src *** Error code 1 The following command caused the error: set fnord $MAKEFLAGS; amf=$2; \ dot_seen=no; \ target=`echo all-recursive | sed s/-recursive//`; \ list='src doc contrib'; for subdir in $list; do \ echo "Making $target in $subdir"; \ if test "$subdir" = "."; then \ dot_seen=yes; \ local_target="$target-am"; \ else \ local_target="$target"; \ fi; \ (cd $subdir && make $local_target) \ || case "$amf" in *=*) exit 1;; *k*) fail=yes;; *) exit 1;; esac; \ done; \ if test "$dot_seen" = "no"; then \ make "$target-am" || exit 1; \ fi; test -z "$fail" make: Fatal error: Command failed for target `all-recursive'

2 1

OpenBSD on SPARC64 - Syslog-ng hostname issues
by list.mail＠comcast.net 29 Mar '05

29 Mar '05

I was wondering if someone knows if the Syslog-ng issue with reading remote host hostname/IP addresses on SPARC64 has been resolved? https://lists.balabit.hu/pipermail/syslog-ng/2004-July/006320.html https://lists.balabit.hu/pipermail/syslog-ng/2004-August/006395.html Or Am I missing something in my config? - I tried every option with the hostname as suggested in http://www.campin.net/syslog-ng/faq.html#hostname Config is simple until I figure out this remote hostname/IP issue. - Please check comments in config.. And the Sample log file below... Any help would be great appricated. Thanks, Eric #---------------------------------------------------------------------- # General options #---------------------------------------------------------------------- options { chain_hostnames(no); create_dirs (no); dir_perm(0755); keep_hostname(yes); log_fifo_size(1024); long_hostnames(off); perm(0644); sync(1); time_reopen (10); use_dns(yes); use_fqdn(no); }; #---------------------------------------------------------------------- # Log sources #---------------------------------------------------------------------- source network { udp(); internal(); }; # source local { unix-stream("/dev/log"); internal(); }; #---------------------------------------------------------------------- # Log Destinations #---------------------------------------------------------------------- destination net { file("/var/syslog-ng/hosts/imd.log" ); }; #---------------------------------------------------------------------- # host-based filters - This is the only way I can get logs - filter for localhost # I can not get logs filtering for remote host - IP or hostname. #---------------------------------------------------------------------- filter net { host("obsd"); }; #---------------------------------------------------------------------- # put it all together #---------------------------------------------------------------------- log { source(network); filter(net); destination(net); }; Sample Log Message -from tail of log file - Mar 24 08:46:47 obsd Mar 24 2005 08:46:47 hcpix Localhost ----------^ Remotehost -------------------------------------------^

2 1

syslog-ng dies randomly on solaris
by Ian Veach 29 Mar '05

29 Mar '05

Greetings - We're just chomping at the bit to switch to syslog-ng from the standard syslog. Although it sounds like plenty of solaris people are having success, our testing is not going well. Our configs are all great, but syslog-ng just simply stops running at random times (sometimes an hour, the last one 35 days) on my test machine (low volume except for occasional load testing). Can anyone give me (a neophyte in this arena) any ideas on how to fix this? Ideally, I would like to solve the problem (or figure out what it is), but am open to things like a cron to verify syslog-ng is running...Could try to debug, but not great with truss, and for some reason syslog-ng cores don't show much useful info (to me, a noob). Syslog-ng 1.6.5 and libol version required at the time standard compile for solaris (details available) Solaris 9, recently patched thanks very much! ivo

3 4

snapshots now working
by Balazs Scheidler 29 Mar '05

29 Mar '05

hi, As of today I've disabled snapshot generation because of some internal changes of our web service. It will be restored soon. (you can remind me if it does not work in about a week) -- Bazsi

3 3

Log line lost during TCP connection?
by Jay Guerette 27 Mar '05

27 Mar '05

I have a postfix server logging via syslog-ng. The log data is written to a local file and also sent via TCP to a central syslog-ng loghost. On the source server (syslog-ng 1.6.6 on Linux) I see: 05:32:21 internal/smtpd[15534]: 9AE172D29A5: client=x.x.net[10.x.x.x] 05:32:21 internal/qmgr[9993]: 9AE172D29A5: from=<x(a)x.com>, size=1557811, nrcpt=1 (queue active) On the central loghost (syslog-ng 1.6.5 on Linux) I see: 05:32:21 syslog-ng[28919]: AF_INET client connected from 10.x.x.x, port 33645 and 05:32:21 internal/qmgr[9993]: 9AE172D29A5: from=<x(a)x.com>, size=1557811, nrcpt=1 (queue active) The 1st line from the source server is missing on the central loghost. Is this a bug?

2 3

destination Program - missing syslog sutdown message
by Brian Kee 19 Mar '05

19 Mar '05

I have a relatively simple perl program that is called from syslog-ng using destination <name> { program("/path/to/program"); }; syntax in syslog-ng.conf. I have noticed an interesting thing regarding the syslog-ng stop/start messages. When starting the syslog-ng daemon (via init script), I get an appropriate log messages sent to my program: Mar 19 01:54:52 loki2 syslog-ng[21700]: syslog-ng version 1.6.5 starting However, when stopping the daemon, I get no stop messages sent to the program, though I do see them sent to other configured destinations. (example stop message: Mar 19 01:48:41 loki2 syslog-ng[21187]: syslog-ng version 1.6.5 going down) Any ideas, or experience with a similar behavior? Any way to force the stop message to be sent to my program? IOW is this behavior configurable? Thank You, Brian A. Kee __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/

1 0

problem in logging apache-log
by niraj 18 Mar '05

18 Mar '05

Hi I want to log access log of apache with the help of syslog-ng.But it is not working.I have added the code below. TIA Niraj source apachesrc{ file("/var/log/httpd/access_log"); }; destination destfile{ file("apache-ng.log"); }; log { source(apachesrc); destination(destfile); };

2 1

logging problem
by niraj 18 Mar '05

18 Mar '05

Hi I want to log access log of apache with the help of syslog-ng.But it is not working.I have added the code below. TIA Niraj source apachesrc{ file("/var/log/httpd/access_log"); }; destination destfile{ file("apache-ng.log"); }; log { source(apachesrc); destination(destfile); };

2 1

sudden hourly restarts
by sscalsk 16 Mar '05

16 Mar '05

I have been running syslog-ng v1.6.5 for about 6 months with no problems. Its the main syslog process and logs the days traffic to a single messages file, it does a little filtered for selected hosts and forwards them on (w/spoofing) to another device. Just this week, for some unknown reason I've yet to find, syslog-ng reinitializes a new configuration on the hour (just as if it received a HUP) and overwrites the previous hours file. Now I rotate the logs at midnight via cron, there i move the file and kill HUP the syslog-ng process which works fine. remove_if_older is not set in my config so its taking the default. Anyone else ever have unexplained hourly restarts on the syslog-ng process? -= stan ________________________________________________________________ Sent via the WebMail system at mail.ameritel.net --- [This E-mail scanned for viruses by mail.ameritel.net]

2 1