- syslog-ng - lists.balabit.hu

syslog-ng 1.3.10
by Balazs Scheidler 18 Dec '99

18 Dec '99

Hi, I've released syslog-ng 1.3.10, fixing pipe handling. I've also updated documentation (internal, unix-dgram & unix-stream drivers are fully documented now). -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt

1 0

Problem with Syslog-ng.
by Ben Kressman 18 Dec '99

18 Dec '99

Currently I am running Syslog-ng on just 2 machines, and they swap log files back and forth for security. Problem is, on one machine syslog-ng just stops running, exits silently.. Anyone else seen this? Syslog-ng v 1.3.8 Libol v 1.3.9 Linux 2.2.13 Slackware 7.0mod -Ben

2 1

1.3.9
by Balazs Scheidler 17 Dec '99

17 Dec '99

I've released 1.3.9 and libol 0.2.10 fixing a pipe() bug. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt

1 0

Filter problem
by John Wingenbach 17 Dec '99

17 Dec '99

I have just installed and configure syslog-ng on a couple of solaris boxes. However, I seem to be getting more then I wanted sent out to the ttys. Here is what I have done: source s_all { sun-streams("/dev/log" door("/etc/.syslog_door")); internal(); udp(); }; filter f_EmergSanUser { level(emerg) and not facility(user); }; destination d_ttys { usertty("*"); }; log { source(s_all); filter(f_EmergSanUser); destination (d_ttys); }; I am trying to mimic the syslog.conf line: *.emerg;user.none * However, what I am getting is notice level messages on the ttys. -- John C. Wingenbach Broadband Technologies Sr. Systems Administrator Work: (919) 405-4627 Fax: (919) 405-4544

1 0

Memory leak in syslog-ng 1.3.7 & FreeBSD?
by George Madden 16 Dec '99

16 Dec '99

I was running syslog-ng 1.2.3 on FreeBSD 3.2 with no problems. I recompiled 1.3.7 and have been running it for the past couple of days. It appears to have a memory leak. I've been using top to output the processes to a file and I keep seeing the mem stats for syslog-ng grow. The system is a fairly busy logger and I did add the use_dns statement and $HOST parameters. Has anyone else seen this? Here are the lines from top. I output 2 lines every 5 minutes. This is about the last 45 minutes or so: 609 root 2 0 1536K 1220K poll 40:04 10.06% 10.06% syslog-ng 609 root 2 0 1536K 1220K poll 40:29 7.86% 7.86% syslog-ng 609 root 2 0 1536K 1220K poll 40:29 7.62% 7.62% syslog-ng 609 root 32 0 1536K 1220K RUN 40:53 9.52% 9.52% syslog-ng 609 root 2 0 1536K 1220K poll 40:54 9.47% 9.47% syslog-ng 609 root 32 0 1544K 1224K RUN 41:13 7.57% 7.57% syslog-ng 609 root 2 0 1544K 1224K poll 41:13 8.45% 8.45% syslog-ng 609 root 32 0 1560K 1240K RUN 41:34 6.20% 6.20% syslog-ng 609 root 2 0 1560K 1240K poll 41:35 8.89% 8.89% syslog-ng 609 root 30 0 1560K 1240K RUN 41:55 6.40% 6.40% syslog-ng 609 root 2 0 1560K 1240K poll 41:56 6.88% 6.88% syslog-ng 609 root 2 0 1560K 1240K poll 42:12 3.86% 3.86% syslog-ng 609 root 2 0 1560K 1240K poll 42:12 3.76% 3.76% syslog-ng 609 root 2 0 1568K 1248K poll 42:32 5.47% 5.47% syslog-ng 609 root 2 0 1568K 1248K poll 42:32 5.22% 5.22% syslog-ng 609 root 2 0 1580K 1260K poll 42:58 8.20% 8.20% syslog-ng 609 root 2 0 1580K 1260K poll 42:58 8.35% 8.35% syslog-ng 609 root 2 0 1580K 1264K poll 43:20 5.96% 5.96% syslog-ng 609 root 2 0 1580K 1264K poll 43:20 5.81% 5.81% syslog-ng

2 2

syslog-ng and FBSD 3-STABLE
by Lowkrantz, Goran 16 Dec '99

16 Dec '99

All fine, except that src/main.c:39 need to be <sys/wait.h>. Cheers, GLZ --- Goran Lowkrantz Email : goran.lowkrantz(a)infologigruppen.se Infologigruppen Alfa AB Telephone: Nat 070-587 8782 Fax: Nat 070-615 8782 Box 202 Int +46 70-587 8782 Int +46 70-615 8782 941 25 Pitea, Sweden

2 1

syslog-ng 1.3.8
by Balazs Scheidler 16 Dec '99

16 Dec '99

Hi, I've released syslog-ng 1.3.8 and libol 0.2.9 with a couple of bugfixes. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt

2 2

syslog-ng: destination connection broken, reopening in 60 seconds
by Brian Johnson 15 Dec '99

15 Dec '99

I set-up syslog-ng last week, it's bee working great, but started giving this message every minute src@in syslog-ng: destination connection broken, reopening in 60 seconds I am running syslog-ng with the following command: supervise /var/supervise/syslog-ng /usr/sbin/syslog-ng -d 2>&1 |logger -t syslog-ng & I did it this way because I wanted to use the supervise utility to make sure it stays running, and to do that I needed to keep syslog-ng from becoming a daemon otherwise supervise will think it crashed and run it again and so I'm using the logger command to pass any error messages back into my logs.. in my syslog-nf.conf file all of my destinations are either files or virtual terminals (eg: /dev/tty1) and so I don't see how the connection to any of those could be broken? it seems to be logging ok otherwise.. any thoughts?? btw - I'm running on Redhat 6.0 ..and my thanks to the authors of the program - this is very helpfull

1 0

syslog-ng 1.3.7/Solaris 2.7
by ger 15 Dec '99

15 Dec '99

Hi, don't know if I'm doing something stupid here, or if I'm missing something, but here goes.. I have been running 1.3.6 successfully on Solaris 2.7 as a central logging solution, but I upgraded to 1.3.7 to check the new DNS functionality, and ran into some name resolution problems. I added the use_dns(yes) and use_fqdn(no) options to the options section of the configuration file, but my logfiles were still being created with <facility>.log.<ip_address> rather than <facility>.log.<hostname>, as had previously been the case with 1.3.6. I also tried removing the long_hostnames option in case it was conflicting with the new DNS code, but to no avail. I used the same version of libol for both, as no changes seem to have been made to the libs (0.2.8., Dec 3). Am I missing something, or has anyone else noticed this behaviour? Maybe something to do with the Solaris 7 resolver? Thanks, Ger. -- Ger Mulcahy, Technical Consultant, Harvard Business School

2 1

Logging console?
by Erich Reitz 09 Dec '99

09 Dec '99

Hi, I would like to know if it is possible/wise to log messages sent to the console? Unattended machines without monitors usually report messages during bootup that I never see since they are exclusively directed to the console. During normal operations I believe there are messages that can be sent exclusively to the console (ie: perl -w warning messages when the perl script process is run/forked from a background process without a controlling terminal) and these messages are never seen/logged. I am wondering if I can set the console up as a source for syslog-ng on these machines without monitors?

2 1

RE: [syslog-ng] SIGHUP kills syslog-ng on FreeBSD 3-STABLE
by Lowkrantz, Goran 09 Dec '99

09 Dec '99

Yes, this worked. Cheers, GLZ -----Original Message----- From: Balazs Scheidler [mailto:bazsi@balabit.hu] Sent: Thursday, December 09, 1999 7:01 PM To: syslog-ng(a)venus.terrasoft.hu Subject: Re: [syslog-ng] SIGHUP kills syslog-ng on FreeBSD 3-STABLE On Wed, Dec 08, 1999 at 03:38:42AM +0100, Lowkrantz, Goran wrote: > Hi, > > No, it didn't help. Now it just dies silently, not even a work on the > console. > > The only thing I can see is that if I start the old syslogd immediately > after syslog-ng died on HUP, I get the following on the console: > syslogd: cannot create /var/run/log: Address already in use I have yet another patch which should really fix your problems under BSD. Touch afinet.c.x and afunix.c.x before rebuilding, if you don't have scsh installed. diff -urN syslog-ng-1.3.6/src/afinet.c syslog-ng.bsd/src/afinet.c --- syslog-ng-1.3.6/src/afinet.c Tue Nov 23 20:45:45 1999 +++ syslog-ng.bsd/src/afinet.c Thu Dec 9 16:31:34 1999 @@ -269,11 +269,15 @@ case AFSOCKET_DGRAM: { struct afsocket_source_connection *conn; struct io_fd *client = make_io_fd(cfg->backend, fd); + int res; self->super.num_connections = 1; conn = make_afinet_source_connection(client, NULL, &self->super, self->super.super.super.next); - LOG_HANDLER_INIT(conn, cfg, NULL); - + res = LOG_HANDLER_INIT(conn, cfg, NULL); + if ((res & ST_FAIL) == 0) { + conn->queue_node = + object_queue_add_tail(self->super.connections, &conn->super.super.super); + } break; } default: diff -urN syslog-ng-1.3.6/src/afunix.c syslog-ng.bsd/src/afunix.c --- syslog-ng-1.3.6/src/afunix.c Tue Nov 23 20:32:37 1999 +++ syslog-ng.bsd/src/afunix.c Thu Dec 9 16:33:15 1999 @@ -241,11 +241,16 @@ case AFSOCKET_DGRAM: { struct afsocket_source_connection *conn; struct io_fd *client = make_io_fd(cfg->backend, fd); - + int res; + self->super.num_connections = 1; conn = make_afunix_source_connection(client, NULL, &self->super, self->super.super.super.next); - LOG_HANDLER_INIT(conn, cfg, NULL); - + res = LOG_HANDLER_INIT(conn, cfg, NULL); + + if ((res & ST_FAIL) == 0) { + conn->queue_node = + object_queue_add_tail(self->super.connections, &conn->super.super.super); + } break; } default: -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt _______________________________________________ syslog-ng maillist - syslog-ng(a)lists.balabit.hu http://lists.balabit.hu/mailman/listinfo/syslog-ng

3 2

syslog-ng keeps dying on sol 2.6/2.7
by Jacob Zehnder 09 Dec '99

09 Dec '99

on my earlier post i forgot to include which version i was running of syslog-ng. 1.2.2 on all machines * * * * * * * * * * * * * * * * * * Jacob Zehnder * * * * * * * * * Grill Master * * * * * * * * "The dude abides." * * * * 'The Big Lebowski' * * * * * * * * * * * * * *

1 0

syslog-ng 1.3.7 released
by Balazs Scheidler 09 Dec '99

09 Dec '99

Hi, I've released syslog-ng 1.3.7, which fixes the remaining SIGHUP bugs, and adds two global configuration options: * use_dns() yes/no enables or disables DNS lookups * use_fqdn() yes/no enables or disables FQDN usage Note that these are not too well tested (tm). Since there's a major bug in syslog-ng 1.2.x, which is fixed by 1.3.x, and is cannot be easily backported, I am thinking about releasing 1.4.0 before adding further features. (the bug is that all AF_UNIX and AF_INET connections are dropped when syslog-ng is reinitialized) So please _test_ this release as much as you can, and I'll release 1.4.0 before christmas. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt

1 0

RE: [syslog-ng] SIGHUP kills syslog-ng on FreeBSD 3-STABLE
by Lowkrantz, Goran 09 Dec '99

09 Dec '99

Hi, No, it didn't help. Now it just dies silently, not even a work on the console. The only thing I can see is that if I start the old syslogd immediately after syslog-ng died on HUP, I get the following on the console: syslogd: cannot create /var/run/log: Address already in use Cheers, GLZ -----Original Message----- From: Balazs Scheidler [mailto:bazsi@balabit.hu] Sent: Tuesday, December 07, 1999 10:52 PM To: syslog-ng(a)venus.terrasoft.hu Subject: Re: [syslog-ng] SIGHUP kills syslog-ng on FreeBSD 3-STABLE On Tue, Dec 07, 1999 at 09:37:44PM +0100, Lowkrantz, Goran wrote: > Hi, > > Here it is. This patch should solve the problem with SIGHUP, because it drops messages while the configuration is initialized. The real problem is not solved though, the error message says that for some reason syslog-ng cannot bind to 0.0.0.0:514. I'll check that out too later. diff -u -r1.18 sources.c --- sources.c 1999/11/22 18:26:16 1.18 +++ sources.c 1999/12/07 13:19:22 @@ -182,7 +182,10 @@ CAST(log_source_group, self, c); struct ol_string *name = get_source_hostname(logmsg->saddr); - assert(self->super.next); + if (!self->super.next) { + log_info_free(logmsg); + return; + } logmsg->source = c; if (self->long_hostnames) { if (logmsg->flags & LF_LOCAL) { -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt _______________________________________________ syslog-ng maillist - syslog-ng(a)lists.balabit.hu http://lists.balabit.hu/mailman/listinfo/syslog-ng

2 2

Config file size and performance
by ger 09 Dec '99

09 Dec '99

Hi, I'm configuring syslog-ng for use on a central log server, processing logs from 60 busy syslog clients, and I've realised that without hostname macro expansion in the config file I'm going to end up with a file >600 lines long. Is this likely to cause performance problems with syslog-ng when it's trying to compare each syslog packet against this kind of filter/action list, and has anyone else used it in a similar environment? Thanks, Ger. -- Ger Mulcahy, Technical Consultant, Harvard Business School

3 3

Host Seperation
by Nigel Bovey 09 Dec '99

09 Dec '99

Hi, We run a rather large network, and are looking at running a secured machine for syslog, running syslog-ng hopefully. Obviously, we want to seperate out the log files for each host. Due to the number of hosts, this looks most easily done with the latest beta having the $HOST variable. So its syslog-ng 1.3.6 on debian running 2.2.12 . I made a rough fast configuration (see below). The idea is that the files end up in /syslog/hostname/file. Now, I've turned long_hostnames(on) which I guessed (docs are rather vague on most things) would make it use long host names for comparisons. To test, I didn't create the /syslog/name directories, and ran syslog-ng -d -v and it came up with "unable to open /syslog/max1/debug". Obviously this is incorrect as I wanted it to have a long host name. I thought the obvious method here, is to just remove hostnames all together, and use ip addresses (we use ip's for all radius related stuff, to stop dns dependency). So I remove resolv.conf and restart it with syslog-ng -d -v, this time it comes up with "unable to open /syslog/1.1.1.1/debug" which is fine. So I create the directory 1.1.1.1 and restart the daemon, now it comes up with "unable to write to /syslog/1.1.1.1/debug, its a directory". I switch the names back on and try, and it writes the file fine under /syslog/max1/debug. Turn names off again, and once again it will not write the file. Any ideas ? or is this a bug that may be fixed soon =) The program looks great from where I am standing, if I could sort out this problem. My other annoyance, is that it does partial name matches, unless there is some way to turn this off that I havn't come across. Even with ip addresses, using host(1.1.1.1) matches 1.1.1.1 and 1.1.1.10,100,101 etc etc. Any help greatly appreciated. --- Nigel Bovey IHUG Network Operations Team -------------------------------------------------------------------------- options { long_hostnames(on); sync(0); }; source src { unix-stream("/dev/log"); internal(); udp(ip(0.0.0.0) port(514)); }; # filters filter f_auth { facility(auth, authpriv); }; filter f_cron { facility(cron); }; filter f_daemon { facility(daemon); }; filter f_kern { facility(kern); }; filter f_lpr { facility(lpr); }; filter f_mail { facility(mail); }; filter f_user { facility(user); }; filter f_uucp { facility(cron); }; filter f_news { facility(news); }; filter f_debug { not facility(auth, authpriv, news, mail); }; filter f_messages { level(info..warn); }; filter f_emergency { level(emerg); }; # destinations destination auth { file("/syslog/$HOST/auth"); }; destination cron { file("/syslog/$HOST/cron"); }; destination daemon { file("/syslog/$HOST/daemon"); }; destination kern { file("/syslog/$HOST/kern"); }; destination lpr { file("/syslog/$HOST/lpr"); }; destination mail { file("/syslog/$HOST/mail"); }; destination user { file("/syslog/$HOST/user"); }; destination uucp { file("/syslog/$HOST/uucp"); }; destination news { file("/syslog/$HOST/news"); }; destination debug { file("/syslog/$HOST/debug"); }; destination emergency { file("/syslog/$HOST/emergency"); }; destination messages { file("/syslog/$HOST/messages"); }; # log statements log { source(src); filter(f_auth); destination(auth); }; log { source(src); filter(f_cron); destination(cron); }; log { source(src); filter(f_daemon); destination(daemon); }; log { source(src); filter(f_kern); destination(kern); }; log { source(src); filter(f_lpr); destination(lpr); }; log { source(src); filter(f_mail); destination(mail); }; log { source(src); filter(f_user); destination(user); }; log { source(src); filter(f_uucp); destination(uucp); }; log { source(src); filter(f_news); destination(news); }; log { source(src); filter(f_debug); destination(debug); }; log { source(src); filter(f_messages); destination(messages); }; log { source(src); filter(f_emergency); destination(emergency); };

3 6

RE: [syslog-ng] SIGHUP kills syslog-ng on FreeBSD 3-STABLE
by Lowkrantz, Goran 07 Dec '99

07 Dec '99

Hi, Here it is. Cheers, GLZ -----Original Message----- From: Balazs Scheidler [mailto:bazsi@balabit.hu] Sent: Tuesday, December 07, 1999 2:21 PM To: syslog-ng(a)venus.terrasoft.hu Subject: Re: [syslog-ng] SIGHUP kills syslog-ng on FreeBSD 3-STABLE Hi, Could you please send me your configuration file? -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt _______________________________________________ syslog-ng maillist - syslog-ng(a)lists.balabit.hu http://lists.balabit.hu/mailman/listinfo/syslog-ng

2 1

source syntax
by Chris Scheller 07 Dec '99

07 Dec '99

I just upgraded to 1.3.6 and i am getting a syntax error on my source line. this is what i have in my conf source s_all { unix-stream("/dev/log" max-connections(10)); udp(); tcp(); }; did something change and i missed it? or did i fubar this source line? Chris Scheller Network One Internet, inc. http://www.networkone.net/ System/Network Administration 1.888.GOT-NET1

3 3

SIGHUP kills syslog-ng on FreeBSD 3-STABLE
by Lowkrantz, Goran 07 Dec '99

07 Dec '99

Hi again, I rebuilt it with debug and here is the full backtrace. > gdb -c syslog-ng.core src/syslog-ng GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... Core was generated by `syslog-ng'. Program terminated with signal 6, Abort trap. Reading symbols from /usr/lib/libc.so.3...done. Reading symbols from /usr/libexec/ld-elf.so.1...done. #0 0x280a546c in kill () from /usr/lib/libc.so.3 (gdb) bt #0 0x280a546c in kill () from /usr/lib/libc.so.3 #1 0x280d9818 in abort () from /usr/lib/libc.so.3 #2 0x280b53ba in __assert () from /usr/lib/libc.so.3 #3 0x804a284 in do_add_source_name (c=0x8069448, logmsg=0x806d30c) at sources.c:185 #4 0x8051c48 in write_internal_message (level=3, length=71, data=0xbfbfd498 "io.c: bind_inet_socket() bind failed 0.0.0.0:514 Address already in use\n\\b\005\b\204Ú¿¿L\001") at afinter.c:55 #5 0x8055229 in msg_vformat () #6 0x805525e in werror () #7 0x80549cd in bind_inet_socket () #8 0x8054eb4 in io_open_socket () #9 0x80514f9 in do_init_afinet_source (c=0x805e908, cfg=0x805e608, persistent=0x805c668) at afinet.c:246 #10 0x804a3e8 in do_init_group (c=0x8069448, cfg=0x805e608, persistent=0x805c668) at sources.c:222 #11 0x804bd88 in do_init_config (self=0x805e608, p=0x805c668) at cfgfile.c:149 #12 0x8049716 in do_reread_config (c=0x805a014) at main.c:71 #13 0x8053fd9 in io_iter () #14 0x80498b1 in main_loop (backend=0x805d008) at main.c:139 #15 0x8049d13 in main (argc=1, argv=0xbfbfdabc) at main.c:292 #16 0x8049555 in _start () Cheers, GLZ --- Goran Lowkrantz Email : goran.lowkrantz(a)infologigruppen.se Infologigruppen Alfa AB Telephone: Nat 070-587 8782 Fax: Nat 070-615 8782 Box 202 Int +46 70-587 8782 Int +46 70-615 8782 941 25 Pitea, Sweden

2 2

SIGHUP kills syslog-ng on FreeBSD 3-STABLE
by Lowkrantz, Goran 06 Dec '99

06 Dec '99

Hi, After upgrading to 1.3.6 I get the following problem: Dec 6 00:26:50 src@tandgrisner syslog-ng[56400]: syslog-ng version 1.3.6 starting Dec 6 00:26:56 src@tandgrisner syslog-ng[56400]: SIGHUP received, restarting syslog-ng pid 56400 (syslog-ng), uid 0: exited on signal 6 (core dumped) Here is the bt: # gdb -c syslog-ng.core work.d/syslog-ng-1.3.6/src/syslog-ng GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... (no debugging symbols found)... Core was generated by `syslog-ng'. Program terminated with signal 6, Abort trap. Reading symbols from /usr/lib/libc.so.3...(no debugging symbols found)...done. Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)... done. #0 0x280a246c in kill () from /usr/lib/libc.so.3 (gdb) bt #0 0x280a246c in kill () from /usr/lib/libc.so.3 #1 0x280d6818 in abort () from /usr/lib/libc.so.3 #2 0x280b23ba in __assert () from /usr/lib/libc.so.3 #3 0x8049d77 in do_add_source_name () #4 0x804ec2e in write_internal_message () #5 0x8051b91 in msg_vformat () #6 0x8051bc6 in werror () #7 0x8051335 in bind_inet_socket () #8 0x805181c in io_open_socket () #9 0x804e79b in do_init_afinet_source () #10 0x8049e38 in do_init_group () #11 0x804af08 in do_init_config () #12 0x8049563 in do_reread_config () #13 0x8050941 in io_iter () #14 0x804967a in main_loop () #15 0x8049a06 in main () #16 0x8049445 in _start () Any ides? Cheers, GLZ --- Goran Lowkrantz Email : goran.lowkrantz(a)infologigruppen.se Infologigruppen Alfa AB Telephone: Nat 070-587 8782 Fax: Nat 070-615 8782 Box 202 Int +46 70-587 8782 Int +46 70-615 8782 941 25 Pitea, Sweden

1 0

syslog-ng 1.2.3 & syslog-ng 1.3.6
by Balazs Scheidler 03 Dec '99

03 Dec '99

Hi, I've released syslog-ng 1.2.3 and syslog-ng 1.3.6 fixing two small bugs. 1) If a SIGHUP signal was sent to syslog-ng while restart was in progress, syslog-ng terminated with a segmentation fault. 2) An assertion may have failed in some cases, where it shouldn't. 3) If poll() was interrupted, callouts were not called. Oops, these were three bugs. You know there are three kind of people, one who can calculate, and one who can't. :) You'll find these at the usual place: http://www.balabit.hu/products/syslog-ng -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt

1 0

syslog-ng 1.2.2 & syslog-ng 1.3.5
by Balazs Scheidler 24 Nov '99

24 Nov '99

Hi, I have released syslog-ng 1.2.2 and syslog-ng 1.3.5. Changes in syslog-ng 1.2.2: * a small log parsing bug caused problems in Solaris STREAMS support Changes in syslog-ng 1.3.5: * A bug in UDP support caused segmentation fault immediately at startup I've removed the debian packaging files from the source distribution, because syslog-ng is now part of debian, and those files are maintained by a debian maintainer. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt

1 0

RE: [syslog-ng] syslog-ng 1.3.3 on FreeBSD 3-STABLE
by Lowkrantz, Goran 23 Nov '99

23 Nov '99

Hi, Works just fine. Cheers, GLZ -----Original Message----- From: Balazs Scheidler [mailto:bazsi@balabit.hu] Sent: Tuesday, November 23, 1999 8:36 PM To: syslog-ng(a)lists.balabit.hu Subject: Re: [syslog-ng] syslog-ng 1.3.3 on FreeBSD 3-STABLE On Tue, Nov 23, 1999 at 08:25:26PM +0100, Lowkrantz, Goran wrote: > Hi, > > This is what I get when I run gdb on the core. It seems like the child dies, > the parent get a SIGCHLD but will continue to wait. > > GNU gdb 4.18 > Copyright 1998 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-unknown-freebsd"... > Core was generated by `syslog-ng'. > Program terminated with signal 11, Segmentation fault. > Reading symbols from /usr/lib/libc.so.3...done. > Reading symbols from /usr/libexec/ld-elf.so.1...done. > #0 0x8050f50 in do_init_afinet_source_connection (c=0x8069188, > cfg=0x805f008, > persistent=0x0) at afinet.c:69 > 69 notice("AF_INET client connected from %S, port %i\n", > (gdb) bt oopss.. this is the problem. try to apply the following patch: --- afinet.c 1999/11/23 19:32:37 1.2 +++ afinet.c 1999/11/23 19:33:09 @@ -64,10 +64,12 @@ struct persistent_config *persistent) { CAST(afsocket_source_connection, self, c); - CAST(inet_address_info, inet, self->client_addr); - - notice("AF_INET client connected from %S, port %i\n", - inet->ip, inet->port); + if (self->client_addr) { + CAST(inet_address_info, inet, self->client_addr); + + notice("AF_INET client connected from %S, port %i\n", + inet->ip, inet->port); + } io_read(self->client, make_log_reader(1, c), make_afsocket_source_close_callback(self)); @@ -90,10 +92,13 @@ do_close_afinet_connection(struct afsocket_source_connection *c, int close_reason) { - CAST(inet_address_info, inet, c->client_addr); assert(c->owner); - notice("AF_INET client dropped connection from %S, port %i\n", - inet->ip, inet->port); + if (c->client_addr) { + CAST(inet_address_info, inet, c->client_addr); + + notice("AF_INET client dropped connection from %S, port %i\n", + inet->ip, inet->port); + } object_queue_remove(c->queue_node); c->owner->num_connections--; return ST_OK | ST_GOON; if you have no scsh installed touch afinet.c.x before trying to remake. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt _______________________________________________ syslog-ng maillist - syslog-ng(a)lists.balabit.hu http://lists.balabit.hu/mailman/listinfo/syslog-ng

1 0

RE: [syslog-ng] syslog-ng 1.3.3 on FreeBSD 3-STABLE
by Lowkrantz, Goran 23 Nov '99

23 Nov '99

Hi, This is what I get when I run gdb on the core. It seems like the child dies, the parent get a SIGCHLD but will continue to wait. GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... Core was generated by `syslog-ng'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libc.so.3...done. Reading symbols from /usr/libexec/ld-elf.so.1...done. #0 0x8050f50 in do_init_afinet_source_connection (c=0x8069188, cfg=0x805f008, persistent=0x0) at afinet.c:69 69 notice("AF_INET client connected from %S, port %i\n", (gdb) bt #0 0x8050f50 in do_init_afinet_source_connection (c=0x8069188, cfg=0x805f008, persistent=0x0) at afinet.c:69 #1 0x805156e in do_init_afinet_source (c=0x805f108, cfg=0x805f008, persistent=0x0) at afinet.c:270 #2 0x804a390 in do_init_group (c=0x805d2c8, cfg=0x805f008, persistent=0x0) at sources.c:222 #3 0x804bd30 in do_init_config (self=0x805f008, p=0x0) at cfgfile.c:149 #4 0x8049c28 in main (argc=1, argv=0xbfbfdabc) at main.c:268 #5 0x8049555 in _start () I will check further. Cheers, GLZ -----Original Message----- From: Balazs Scheidler [mailto:bazsi@balabit.hu] Sent: Tuesday, November 23, 1999 8:06 PM To: syslog-ng(a)venus.terrasoft.hu Subject: Re: [syslog-ng] syslog-ng 1.3.3 on FreeBSD 3-STABLE On Tue, Nov 23, 1999 at 07:56:38PM +0100, Lowkrantz, Goran wrote: > > There seems to be somthing wrong with the forking in the new version. It > never goes deamon. > > Here are the truss lists from 1.3.1 and 1.3.4 resp. I'm currently downloading FreeBSD, so I can test this. Under Linux it works o.k. > Any ideas or pointers where to look? syslog-ng goes to background the following way: parent: read configuration if config syntactically correct then fork(); wait for SIGTERM signal child: initialize configuration (open sockets etc.) if successful; close fds 0, 1, 2, become a session leader, send SIGTERM signal to parent You can find all of this in main.c -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt _______________________________________________ syslog-ng maillist - syslog-ng(a)lists.balabit.hu http://lists.balabit.hu/mailman/listinfo/syslog-ng

2 1

syslog-ng 1.3.3 on FreeBSD 3-STABLE
by Lowkrantz, Goran 23 Nov '99

23 Nov '99

There seems to be somthing wrong with the forking in the new version. It never goes deamon. Here are the truss lists from 1.3.1 and 1.3.4 resp. 1.3.1 ======================================= # truss /usr/local/sbin/syslog-ng syscall __sysctl(0xbfbfd9c8,0x2,0x2806518c,0xbfbfd9d0,0x0,0x0) returns 0 (0x0) syscall mmap(0x0,32768,0x3,0x1002,-1,0x0) returns 671506432 (0x28066000) syscall geteuid() returns 0 (0x0) syscall getuid() returns 0 (0x0) syscall getegid() returns 0 (0x0) syscall getgid() returns 0 (0x0) syscall open("/var/run/ld-elf.so.hints",0,05001446514) returns 3 (0x3) syscall read(0x3,0xbfbfd97c,0x80) returns 128 (0x80) syscall lseek(3,0x80,0) returns 128 (0x80) syscall read(0x3,0x2806a000,0x67) returns 103 (0x67) syscall close(3) returns 0 (0x0) syscall access("/usr/lib/libc.so.3",0) returns 0 (0x0) syscall open("/usr/lib/libc.so.3",0,05001446514) returns 3 (0x3) syscall read(0x3,0xbfbfc9f8,0x1000) returns 4096 (0x1000) syscall mmap(0x0,528384,0x5,0x2,3,0x0) returns 671539200 (0x2806e000) syscall mmap(0x280db000,20480,0x3,0x12,3,0x6c000) returns 671985664 (0x280db000) syscall mmap(0x280e0000,61440,0x3,0x1012,-1,0x0) returns 672006144 (0x280e0000) syscall close(3) returns 0 (0x0) syscall readlink("/etc/malloc.conf",0xbfbfd96c,63) errno 2 'No such file or directory' syscall mmap(0x0,4096,0x3,0x1002,-1,0x0) returns 672067584 (0x280ef000) syscall break(0x8059000) returns 0 (0x0) syscall break(0x805a000) returns 0 (0x0) syscall break(0x805b000) returns 0 (0x0) syscall open("/etc/syslog-ng/syslog-ng.conf",0,0666) returns 3 (0x3) syscall break(0x8060000) returns 0 (0x0) syscall ioctl(3,TIOCGETA,0xbfbfd484) errno 25 'Inappropriate ioctl for device' syscall fstat(3,0xbfbfd400) returns 0 (0x0) syscall break(0x8062000) returns 0 (0x0) syscall read(0x3,0x8060000,0x2000) returns 2523 (0x9db) syscall read(0x3,0x8060000,0x2000) returns 0 (0x0) syscall break(0x8063000) returns 0 (0x0) syscall break(0x8064000) returns 0 (0x0) syscall break(0x8065000) returns 0 (0x0) syscall break(0x8066000) returns 0 (0x0) syscall ioctl(3,TIOCGETA,0xbfbfd478) errno 25 'Inappropriate ioctl for device' syscall close(3) returns 0 (0x0) syscall fork() returns 498 (0x1f2) syscall sigaction(0xf,0xbfbfd9e8,0xbfbfd9dc) returns 0 (0x0) syscall sigprocmask(0x1,0x0) returns 0 (0x0) SIGNAL 15 SIGNAL 15 syscall sigaction(0xf,0xbfbfd948,0xbfbfd93c) returns 0 (0x0) syscall sigreturn(0xbfbfd980) returns 0 (0x0) ======================================= 1.3.4 ======================================= # truss src/syslog-ng syscall __sysctl(0xbfbfd9d4,0x2,0x2806618c,0xbfbfd9dc,0x0,0x0) returns 0 (0x0) syscall mmap(0x0,32768,0x3,0x1002,-1,0x0) returns 671510528 (0x28067000) syscall geteuid() returns 0 (0x0) syscall getuid() returns 0 (0x0) syscall getegid() returns 0 (0x0) syscall getgid() returns 0 (0x0) syscall open("/var/run/ld-elf.so.hints",0,05001456514) returns 3 (0x3) syscall read(0x3,0xbfbfd988,0x80) returns 128 (0x80) syscall lseek(3,0x80,0) returns 128 (0x80) syscall read(0x3,0x2806b000,0x67) returns 103 (0x67) syscall close(3) returns 0 (0x0) syscall access("/usr/lib/libc.so.3",0) returns 0 (0x0) syscall open("/usr/lib/libc.so.3",0,05001456514) returns 3 (0x3) syscall read(0x3,0xbfbfca04,0x1000) returns 4096 (0x1000) syscall mmap(0x0,528384,0x5,0x2,3,0x0) returns 671543296 (0x2806f000) syscall mmap(0x280dc000,20480,0x3,0x12,3,0x6c000) returns 671989760 (0x280dc000) syscall mmap(0x280e1000,61440,0x3,0x1012,-1,0x0) returns 672010240 (0x280e1000) syscall close(3) returns 0 (0x0) syscall readlink("/etc/malloc.conf",0xbfbfd974,63) errno 2 'No such file or directory' syscall mmap(0x0,4096,0x3,0x1002,-1,0x0) returns 672071680 (0x280f0000) syscall break(0x805a000) returns 0 (0x0) syscall break(0x805b000) returns 0 (0x0) syscall break(0x805c000) returns 0 (0x0) syscall break(0x805d000) returns 0 (0x0) syscall open("/etc/syslog-ng/syslog-ng.conf",0,0666) returns 3 (0x3) syscall break(0x8062000) returns 0 (0x0) syscall ioctl(3,TIOCGETA,0xbfbfd490) errno 25 'Inappropriate ioctl for device' syscall fstat(3,0xbfbfd40c) returns 0 (0x0) syscall break(0x8064000) returns 0 (0x0) syscall read(0x3,0x8062000,0x2000) returns 2523 (0x9db) syscall read(0x3,0x8062000,0x2000) returns 0 (0x0) syscall break(0x8065000) returns 0 (0x0) syscall break(0x8066000) returns 0 (0x0) syscall break(0x8067000) returns 0 (0x0) syscall break(0x8068000) returns 0 (0x0) syscall ioctl(3,TIOCGETA,0xbfbfd484) errno 25 'Inappropriate ioctl for device' syscall close(3) returns 0 (0x0) syscall fork() returns 808 (0x328) syscall sigaction(0xf,0xbfbfd9f4,0xbfbfd9e8) returns 0 (0x0) syscall sigprocmask(0x1,0x0) returns 0 (0x0) SIGNAL 20 ======================================= Any ideas or pointers where to look? Cheers, GLZ --- Goran Lowkrantz Email : goran.lowkrantz(a)infologigruppen.se Infologigruppen Alfa AB Telephone: Nat 070-587 8782 Fax: Nat 070-615 8782 Box 202 Int +46 70-587 8782 Int +46 70-615 8782 941 25 Pitea, Sweden

2 1