- syslog-ng - lists.balabit.hu

syslog-ng 1.9.6 released
by Balazs Scheidler 16 Oct '05

16 Oct '05

Hi, I've released yet another version in the syslog-ng development series targeted at the stable 2.0, dubbed 1.9.6. It has the following NEWS entry: 1.9.6 Sat, 15 Oct 2005 18:07:07 +0200 * Added new options to control buffer flushing (flush_lines and flush_timeout, see the documentation for more details) * Fixes in local timezone detection, it should properly detect DSTs on Linux, Solaris and probably BSDs. * Fixed facility/priority filtering. * Fixed owner/group/permission setting on target files/directories. * Copied the contrib directory as found in 1.6.x to this tree. * TZ macro is now an alias of TZOFFSET, as I could not find a portable way to determine the string representation of any given timezone offset. * Added some more unit tests. -- Bazsi

2 1

RE: [syslog-ng] syslog-ng 1.9.6 compile error
by Marvin Nipper 16 Oct '05

16 Oct '05

MANY thanks on the time-related fixes. The 1.9.6 compilations seemed to go great in that regard. But then it generated an error much further down in the compilation process. Maybe it's just something stupid that I've done(??). Your input would be appreciated. (The config and a chunk of the compilation output is pasted in below.) THANKS for all of the great work on the new version. Marvin ./configure checking for a BSD-compatible install... ./install-sh -c checking whether build environment is sane... yes checking for gawk... no checking for mawk... no checking for nawk... nawk checking whether make sets $(MAKE)... yes checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for gcc option to accept ANSI C... none needed checking for bison... no checking for byacc... no checking for flex... no checking for lex... lex checking for yywrap in -lfl... no checking for yywrap in -ll... yes checking lex output file root... lex.yy checking whether yytext is a pointer... no checking whether make sets $(MAKE)... (cached) yes checking for ranlib... ranlib checking how to enable static linking for certain libraries... GNU or Solaris checking how to run the C preprocessor... gcc -E checking for egrep... egrep checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... no checking for unistd.h... yes checking dmalloc.h usability... no checking dmalloc.h presence... no checking for dmalloc.h... no checking for strings.h... (cached) yes checking openssl/ssl.h usability... no checking openssl/ssl.h presence... no checking for openssl/ssl.h... no checking getopt.h usability... no checking getopt.h presence... no checking for getopt.h... no checking whether struct tm is in sys/time.h or time.h... time.h checking for struct tm.tm_gmtoff... no checking for door_create in -ldoor... yes checking for socket in -lsocket... yes checking for gethostbyname in -lnsl... yes checking for regexec in -lregex... no checking for strdup... yes checking for strtol... yes checking for inet_aton... no checking for inet_ntoa... yes checking for getopt_long... no checking for pkg-config... /usr/local/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for GLIB_CFLAGS... -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include checking for GLIB_LIBS... -L/usr/local/lib -lglib-2.0 -liconv checking for EVTLOG_CFLAGS... -I/usr/local/include/eventlog checking for EVTLOG_LIBS... -L/usr/local/lib -levtlog checking for static GLib libraries... yes configure: creating ./config.status config.status: creating dist.conf config.status: creating Makefile config.status: creating src/Makefile config.status: creating doc/Makefile config.status: creating doc/docvars.xml config.status: creating contrib/Makefile config.status: creating tests/Makefile config.status: creating tests/unit/Makefile config.status: creating tests/functional/Makefile config.status: creating config.h config.status: executing depfiles commands secdevrsn01 # make make all-recursive Making all in src if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/eventlog -D_GNU_SOURCE -g -O2 -Wall -g -MT misc.o -MD -MP -MF ".deps/misc.Tpo" \ -c -o misc.o `test -f 'misc.c' || echo './'`misc.c; \ then mv -f ".deps/misc.Tpo" ".deps/misc.Po"; \ else rm -f ".deps/misc.Tpo"; exit 1; \ fi ...... numerous successful compiles in here...... rm -f libsyslog-ng.a ar cru libsyslog-ng.a misc.o utils.o messages.o gsockaddr.o syslog-names.o macros.o logmsg.o cfg.o logpipe.o driver.o sgroup.o dgroup.o center.o filter.o logsource.o logreader.o logwriter.o affile.o afunix.o afinet.o afsocket.o afstreams.o afuser.o afprog.o afinter.o cfg-lex.o cfg-grammar.o fdwrite.o fdread.o memtrace.o templates.o children.o ranlib libsyslog-ng.a if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/eventlog -D_GNU_SOURCE -g -O2 -Wall -g -MT main.o -MD -MP -MF ".deps/main.Tpo" \ -c -o main.o `test -f 'main.c' || echo './'`main.c; \ then mv -f ".deps/main.Tpo" ".deps/main.Po"; \ else rm -f ".deps/main.Tpo"; exit 1; \ fi gcc -g -O2 -Wall -g -o syslog-ng main.o libsyslog-ng.a -lnsl -lsocket -ldoor -Wl,-Bstatic -ll -L/usr/local/lib -lglib-2.0 -liconv -L/usr/local/lib -levtlog -Wl,-Bdynamic Undefined first referenced symbol in file LOG_FAC libsyslog-ng.a(filter.o) ld: fatal: Symbol referencing 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 /var/opt/packages/syslog-ng-1.9.6/src *** Error code 1 make: Fatal error: Command failed for target `all-recursive' Current working directory /var/opt/packages/syslog-ng-1.9.6 *** Error code 1 make: Fatal error: Command failed for target `all'

2 1

RE: [syslog-ng] syslog-ng 1.9.6 compile error
by Marvin Nipper 16 Oct '05

16 Oct '05

Sorry, I should have stated in the previous post that this is all in a Solaris 8 Sparc environment.

1 0

log does not appear on the clients
by Atif Munir 15 Oct '05

15 Oct '05

I have make a syslog-ng server and the clients are pushing their syslog (by default daemon) messages to syslog-ng server. The logs are fine on the server but I am unable to view the logs on the clients dmesg(/var/adm/messages). I m interested to have the logs on both sides...I mean on the syslog-ng server and on the clients it self. The clients have /etc/syslog.conf as under. =====================/etc/syslog.conf===================== *.err;kern.notice;auth.notice @loghost #*.err;kern.notice;auth.notice /dev/sysmsg *.err;kern.debug;daemon.notice;mail.crit @loghost *.err;kern.debug;daemon.notice;mail.crit /var/adm/messages *.alert;kern.err;daemon.err operator *.alert root *.emerg * mail.debug ifdef(`LOGHOST', /var/log/syslog, @loghost) mail.debug ifdef(`LOGHOST', /var/log/syslog, @loghost) ifdef(`LOGHOST', , user.err @loghost user.err /dev/sysmsg user.err @loghost user.err /var/adm/messages user.alert `root, operator' user.emerg * ) ====================================================== Thanks in advance . Atif

2 1

Incompatibility beetween syslogNG 1.6.8(lattest stable) and libol 0.3.8 ?????
by CIKALA Frederic ROSI/DOSI 14 Oct '05

14 Oct '05

Hello Before trying to install the 0.2.24 version of libol, i want to be sure that stable syslog NG version 1.6.8 is not compatible with the 0.3.8 version of libol. According to https://lists.balabit.hu/pipermail/syslog-ng/2001-December/002794.html, a stable version should be used with a 0.2 verison of libol, where as the stderr advises me to use a 0.3 version :-/ :-\ ... checking libol version >= 0.3.16... no configure: error: Required libol version not found, make sure that your libol version is in the 0.3.x branch [root@XXXX-Linux syslog-ng-1.6.8]# .... Thus, i'm totally confused and need Help thanks for those who will answer, there is no others clue on the web ;( *********************************** Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. Le Groupe France Telecom decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. Si vous n'etes pas destinataire de ce message, merci de le detruire immediatement et d'avertir l'expediteur. *********************************** This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration. France Telecom Group shall not be liable for the message if altered, changed or falsified. If you are not receiver of this message, please cancel it immediately and inform the sender. ***********************************

2 1

RE: [syslog-ng] Incompatibility beetween syslogNG 1.6.8(lattest stable)and libol 0.3.8 ?????
by William Bell 14 Oct '05

14 Oct '05

I can save you some trouble, grab one of the latest daily snapshots of the 1.6.8 verison, it configures libol in the process, it has never lead me astray. William -----Original Message----- From: syslog-ng-bounces(a)lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of CIKALA Frederic ROSI/DOSI Sent: Friday, October 14, 2005 7:39 AM To: syslog-ng(a)lists.balabit.hu Subject: [syslog-ng] Incompatibility beetween syslogNG 1.6.8(lattest stable)and libol 0.3.8 ????? Hello Before trying to install the 0.2.24 version of libol, i want to be sure that stable syslog NG version 1.6.8 is not compatible with the 0.3.8 version of libol. According to https://lists.balabit.hu/pipermail/syslog-ng/2001-December/002794.html, a stable version should be used with a 0.2 verison of libol, where as the stderr advises me to use a 0.3 version :-/ :-\ ... checking libol version >= 0.3.16... no configure: error: Required libol version not found, make sure that your libol version is in the 0.3.x branch [root@XXXX-Linux syslog-ng-1.6.8]# .... Thus, i'm totally confused and need Help thanks for those who will answer, there is no others clue on the web ;( *********************************** Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. Le Groupe France Telecom decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. Si vous n'etes pas destinataire de ce message, merci de le detruire immediatement et d'avertir l'expediteur. *********************************** This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration. France Telecom Group shall not be liable for the message if altered, changed or falsified. If you are not receiver of this message, please cancel it immediately and inform the sender. *********************************** _______________________________________________ syslog-ng maillist - syslog-ng(a)lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html

1 0

Newbi with syslogNG & libol : Libol not recognize :(
by CIKALA Frederic ROSI/DOSI 14 Oct '05

14 Oct '05

Hello' I've found the server to install syslog-ng and i downloaded the stable version with the 0.3.8 version of the libol librairie. I found a document on the web which explain HowTo install it ... therefore i tried, but i got some problem during installation. First i've installed the libol libs (0.3.8) with the ./configure, make, make install - and it seems to be all right. Then, i tried the same sequence with syslogNG and i' got an error concerning libol, as following : [root@XXX-Linux syslog-ng-1.6.8]# ./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes ... ... checking libol version >= 0.3.16... no configure: error: Required libol version not found, make sure that your libol version is in the 0.3.x branch [root@XXX-Linux syslog-ng-1.6.8]# Where as libol seems to be great installed : [root@XXX-Linux download]# libol-config --version 0.3.8 I saw a paper about this problem ( https://lists.balabit.hu/pipermail/syslog-ng/2004-April/006023.html ) but the answer is not goood for me cause' it tells that it is a version problem (like 0.3.9 is too old, and older than the 0.3.13 ... i cannot understand this :-/) so i'm quite Lost ... can anyone help please ? *********************************** Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. Le Groupe France Telecom decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. Si vous n'etes pas destinataire de ce message, merci de le detruire immediatement et d'avertir l'expediteur. *********************************** This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration. France Telecom Group shall not be liable for the message if altered, changed or falsified. If you are not receiver of this message, please cancel it immediately and inform the sender. ***********************************

1 0

RE: [syslog-ng] v1.6.8: usertty fails for usernames > 7 characters
by Patterson, Jay 14 Oct '05

14 Oct '05

I commented out some expressions on lines 103 and 108 of src/afuser.c src/afuser.c:103 ( /*self->username->length == strlen(ut->ut_user) &&*/ src/afuser.c:108 ( /*self->username->length == strlen(ut->ut_name) &&*/ These expressions appear to be optimizations that avoid doing a subsequent memcpy when the two strings obviously won't match, so I think commenting them out is harmless. From what I can tell, the strlen function will return a length much greater than the actual length for user names that go over 7 (or 31 for ut_user) characters, as there is no null-terminator in that case. I guess it eventually finds a zero somewhere beyond that point in memory. Experimentation with getutent more or less convinced me of that, as 8 character user names were returned with a bit of additional text, the null-string interpretation of ut_id. I had to touch afuser.c to set its modification date back to Jan 31 2003 after editing. Something in the build process breaks if the modification date on the file is too recent. This fixed the problem I was having with 8-character arguments to usertty Jay Patterson OpenView Consultant E-Mail: Jay.Patterson(a)T-Mobile.com Phone: 862-812-3436 -----Original Message----- From: syslog-ng-bounces(a)lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] Sent: Thursday, October 13, 2005 2:12 PM To: syslog-ng(a)lists.balabit.hu Subject: [syslog-ng] v1.6.8: usertty fails for usernames > 7 characters syslog-ng-1.6.8 compiled with GCC 3.4.2 on Solaris 2.8 syslog-ng won't write to userttys for login names that are greater than 7 characters Equivalent functionality on syslogd works Never used getutent until today, but ... After using getutent a little, I've come to the conclusion that the utmp fields are not null-terminated. Coincidently, ut_name has a size of 8 ut_user has a size of 32 The code near source file "afuser.c", line 98, seems to treat the ut_name and ut_user fields as if they were null-terminated. Jay Patterson OpenView Consultant E-Mail: Jay.Patterson(a)T-Mobile.com Phone: 862-812-3436

1 0

v1.6.8: usertty fails for usernames > 7 characters
by Patterson, Jay 13 Oct '05

13 Oct '05

syslog-ng-1.6.8 compiled with GCC 3.4.2 on Solaris 2.8 syslog-ng won't write to userttys for login names that are greater than 7 characters Equivalent functionality on syslogd works Never used getutent until today, but ... After using getutent a little, I've come to the conclusion that the utmp fields are not null-terminated. Coincidently, ut_name has a size of 8 ut_user has a size of 32 The code near source file "afuser.c", line 98, seems to treat the ut_name and ut_user fields as if they were null-terminated. Jay Patterson OpenView Consultant E-Mail: Jay.Patterson(a)T-Mobile.com Phone: 862-812-3436

1 0

bugreport for 1.9.5 on solaris
by Nate Campi 13 Oct '05

13 Oct '05

I built 1.9.5 and eventlog-0.2.3+20050116+1856 on Solaris 8. It wouldn't start with command line arguments like "--pidfile=/foo/syslog-ng.pid", I had to change it to "-p /foo/syslog-ng.pid". The usage message it spits out claims that the --long syntax is supported. The other thing is that "bad_hostname()" isn't implemented in 1.9.5, but I'm sure you already knew that. The 2.0 reference guide lists this as a supported option though. Just FYI. -- Nate NT is the only OS that has caused me to beat a piece of hardware to death with my bare hands.

8 16