- syslog-ng - lists.balabit.hu

Re: [syslog-ng]Logging Remotely from Solaris to Linux Update
by Ron Braley 04 Jun '02

04 Jun '02

Bradley - Thanks very much for the information! rb Ron Braley Network Team Leader - CCNP Systems Team Leader - MCSE, CNE University of North Dakota (Aerospace College) braley(a)aero.und.edu 701-777-2964 (work) / 2940 (fax) >>> arlt(a)cpsc.ucalgary.ca 06/04/02 08:18AM >>> On Tue, Jun 04, 2002 at 09:22:15AM +0200, Balazs Scheidler wrote: > On Mon, Jun 03, 2002 at 11:36:06AM -0500, Ron Braley wrote: > > Hi Bazsi > > > > Here's an update and continued question: Everything seems to be fine > > when syslogging remotely from the Solaris box to the Linux box except > > that cron priorities of debug - critical don't get sent (just emerg). > > Also, Solaris and Linux boxes alike won't send daemon priorities debug > > or information messages to the log host. > > this might be caused by the different facility codes between linux and > solaris. Syslog-ng uses the codes of the host operating system it was > compiled on. Maybe a feature to map facility codes would be useful. Usually I just a bunch of #defines in syslog-names.c and slap the extra facilities on sl_facilities[]. I only ever bother with this on our loghost, but it is very useful. Linux, Solaris, Irix, and BSD are all a little bit different, and it is handy to be able to handle various faculities correctly. For example I handle the Linux/BSD authpriv, auth, and the BSD only "security" facilities the same, but my loghost runs Solaris and doesn't know about the other two facility by default. Having this built in so I can define it in a configuration file would be sweet! But I am looking more for an index than a map (or maybe that is what you meant by map). What I'd like is something like: (9<<3) -> CRON /* !Sun */ (11<<3) -> FTP /* Linux */ (12<<3) -> NTP /* BSD */ (13<<3) -> AUDIT /* Irix */ (13<<3) -> SECURITY /* BSD */ (15<<3) -> CRON /* Sun */ ---------------------------------------------------------------------------- __o Bradley Arlt Security Team Lead _ \<_ arlt(a)cpsc.ucalgary.ca University Of Calgary (_)/(_) http://pages.cpsc.ucalgary.ca/~arlt/ Computer Science _______________________________________________ syslog-ng maillist - syslog-ng(a)lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng

1 0

Re:[syslog-ng]Logging Remotely from Solaris to Linux Update
by Ron Braley 04 Jun '02

04 Jun '02

Hi Bazsi Here's an update and continued question: Everything seems to be fine when syslogging remotely from the Solaris box to the Linux box except that cron priorities of debug - critical don't get sent (just emerg). Also, Solaris and Linux boxes alike won't send daemon priorities debug or information messages to the log host. New problem: We need to send logs from our Cisco 2511 access router and 6509 switch/router to the Linux log host, but it's not working. I've set logging facility and host from the Cisco devices, but they don't get logged on the log host. Any ideas or advise? As always: Thanks much for all your help!! rb Ron Braley Network Team Leader - CCNP Systems Team Leader - MCSE, CNE University of North Dakota (Aerospace College) braley(a)aero.und.edu 701-777-2964 (work) / 2940 (fax)

4 3

Re: [syslog-ng]Logging Remotely from Solaris to Linux Update
by Ron Braley 04 Jun '02

04 Jun '02

OK Bazsi - thanks again for everything. rb Ron Braley Network Team Leader - CCNP Systems Team Leader - MCSE, CNE University of North Dakota (Aerospace College) braley(a)aero.und.edu 701-777-2964 (work) / 2940 (fax) >>> bazsi(a)balabit.hu 06/04/02 02:22AM >>> On Mon, Jun 03, 2002 at 11:36:06AM -0500, Ron Braley wrote: > Hi Bazsi > > Here's an update and continued question: Everything seems to be fine > when syslogging remotely from the Solaris box to the Linux box except > that cron priorities of debug - critical don't get sent (just emerg). > Also, Solaris and Linux boxes alike won't send daemon priorities debug > or information messages to the log host. this might be caused by the different facility codes between linux and solaris. Syslog-ng uses the codes of the host operating system it was compiled on. Maybe a feature to map facility codes would be useful. > New problem: We need to send logs from our Cisco 2511 access router > and 6509 switch/router to the Linux log host, but it's not working. > I've set logging facility and host from the Cisco devices, but they > don't get logged on the log host. Any ideas or advise? > > As always: Thanks much for all your help!! I'm not experienced in setting up routers to log remotely, though I'm sure many of us on this list do this regularly. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 _______________________________________________ syslog-ng maillist - syslog-ng(a)lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng

1 0

parse error in reading configuration file
by Chethan K.R 04 Jun '02

04 Jun '02

Hi , I could execute a syslog-ng client but when i tried to execute a syslog-ng server it failed. The error message is ################### parse error at 13 Parse error reading configuration file, exiting. ################################### The configuration file in remote server is ############################## source shell { unix-dgram("/dev/log"); internal(); # Listen on public interface, port 514 for incoming connections tcp(ip(192.9.200.22) port(514) max-connections(1)); }; destination localhost { file("/var/log/syslog-ng.all")); }; # Again, we tie both statements together with the log function. log { source(shell); destination(localhost); }; ######################################### can anybody help me? TIA, Cheths _________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com

1 0

Here is a patch to allow template with program in syslog-ng.conf
by PWM＠capmon.dk 03 Jun '02

03 Jun '02

Hi, Here is a patch to syslog-ng 1.5.13 that will allow the template() to be used within a program() - something like this: filter f_cap { program(^Cap); }; destination d_cap { program("perl -I /opt/cap/server/../inc /opt/cap/server/cmSyslog.pl" template(" \"DATE'$ISODATE'PROG'$PROGRAM'HOST'$HOST'TAG'$TAG'MSG'$MSG\n") template_escape(yes)); }; log { source(src); filter(f_cap); destination(d_cap); }; log { source(net); destination(d_cap); }; Enjoy! Please be aware, that I'm not a member of this syslog-ng mailing list, so if you want to send me comments, please use pvm(a)nworks.dk. Sincerely, Peter Morch. (See attached file: syslog-ng.patch)

1 0

lost logs when using syslog-ng on Linux due to /dev/log reopen
by Borsenkow Andrej 03 Jun '02

03 Jun '02

I am using syslog-ng on Mandrake (8.2 and post-8.2), glibc-2.2.5. Unfortunately, it tends to lose logs. As far as I can tell it is related to the fact that syslog-ng recreates /dev/log on HUP. It means that every program that has opened syslog connection won't be able to write to /dev/log anymore. The sad thing is, this is _not_ limited to klogd (that has the same problem) but to every other program (I had very bad case of socks server losing some info used for accounting :( It happens to every program (daemon) that does openlog() only once on startup. Which makes drop in replacement for syslog simply impossible :( -andrej

4 11

configure 1.4.15 fails to detect libol 0.3.3
by Diogo Zulli 01 Jun '02

01 Jun '02

Hi, I am installing syslog-ng for the first here and found a little problem in configure script. I got syslog-ng 1.4.15 and libol 0.3.3 and the syslog-ng configure script fails to detect libol 0.3.3 because it requires at least 0.2.23: configure.in: ... LIBOL_REQ_PATCH=23 ... if test "$LIBOL_MAJOR" != "$LIBOL_REQ_MAJOR" -o \ "$LIBOL_MINOR" -lt "$LIBOL_REQ_MINOR" -o \ >>>HERE>>> "$LIBOL_PATCH" -lt "$LIBOL_REQ_PATCH"; then AC_MSG_RESULT(no) AC_MSG_ERROR(Required libol version not found) fi As you can see 3 is -lt 23. I worked around changing required LIBOL_REQ_PATCH do 2. Thanks for the great software. I hope I debugged it right and didn't missed something and maybe will help you to fix the problem. - Diogo Zulli -- [ http://sphynx.com.br - diogo(a)sphynx.com.br - ICQ# 112204935 ]

1 0

Re: where is ftp location for syslog-ng
by Steve Cobrin 31 May '02

31 May '02

Follow up to my question regarding broken ftp link on syslog-ng web page -- Steve ---------- Forwarded Message ---------- Subject: Re: inaccessible syslog-ng directories Date: Fri, 31 May 2002 18:17:15 +0200 (CEST) From: Attila Nagy <bra(a)fsn.hu> To: Steve Cobrin <cobrin(a)highbury.net> Hello, > Hi I'm trying to download syslog-ng and libol, but have been unable to > access the following directories for several months That's because Balabit has always forgotten to start rsyncd on their webserver, so I asked them to decide, wether they want me to mirror the stuff, or not. I got no answer, so I first restricted the directory and now deleted all the stuff. Please use http://www.balabit.hu/ instead. Thanks, --------[ Free Software ISOs - ftp://ftp.fsn.hu/pub/CDROM-Images/ ]------- Attila Nagy e-mail: Attila.Nagy(a)fsn.hu Free Software Network (FSN.HU) phone @work: +361 210 1415 (194) cell.: +3630 306 6758 ------------------------------------------------------- On Tuesday 07 May 2002 23:29, Steve Cobrin wrote: > Hi there, I'm interested in experimenting with syslog-ng. > > I usually much prefer to download software using ftp rather than http. Is > there a main ftp site or mirror site.? > > The syslog-ng web page refers to ftp://ftp.fsn.hu/pub/syslog-ng but I have > been unable to connect to the site since January, with the site complaining > that the directory doesn't have read permission. > > Can anybody help? > > -- Steve

1 0

Re: Fwd: [syslog-ng]Logging Remotely from Solaris to Linux
by Ron Braley 31 May '02

31 May '02

Bazsi I've tested every facility and priority, and present the final results of testing facilities and priorities from the Solaris box to the Linux log host: - The only cron facility from the Solaris box recorded at the Linux log host was cron.emerg. No other cron priorities would show up at the log host, but they did log locally OK. - Two daemon facility priorities would not get recorded at the loghost from the Solaris server: daemon.info and daemon. debug. All other daemon priorities worked fine. All other facilities and priorities worked fine from the Solaris box to the Linux log host (except kern, which you addressed earlier). All facility and priorities work fine from the Linux servers to the log host. Thoughts? rb Ron Braley Network Team Leader - CCNP Systems Team Leader - MCSE, CNE University of North Dakota (Aerospace College) braley(a)aero.und.edu 701-777-2964 (work) / 2940 (fax) >>> bazsi(a)balabit.hu 05/31/02 02:45AM >>> On Thu, May 30, 2002 at 09:58:23PM -0500, Ron Braley wrote: > Hi Bazsi. > > Here's where things are with the syslog-ng and Solaris vs Linux: > > Using facility filters (i.e. f_cron) on the Linux box will result in > not logging any messages from the Solaris box. Other Linux boxes work > fine with the facility filters, though. Here's the list of facilities that Solaris uses, and the same on Linux: Solaris: #define LOG_KERN (0<<3) /* kernel messages */ #define LOG_USER (1<<3) /* random user-level messages */ #define LOG_MAIL (2<<3) /* mail system */ #define LOG_DAEMON (3<<3) /* system daemons */ #define LOG_AUTH (4<<3) /* security/authorization messages */ #define LOG_SYSLOG (5<<3) /* messages generated internally by syslogd */ #define LOG_LPR (6<<3) /* line printer subsystem */ #define LOG_NEWS (7<<3) /* netnews subsystem */ #define LOG_UUCP (8<<3) /* uucp subsystem */ #define LOG_CRON (15<<3) /* cron/at subsystem */ /* other codes through 15 reserved for system use */ #define LOG_LOCAL0 (16<<3) /* reserved for local use */ #define LOG_LOCAL1 (17<<3) /* reserved for local use */ #define LOG_LOCAL2 (18<<3) /* reserved for local use */ #define LOG_LOCAL3 (19<<3) /* reserved for local use */ #define LOG_LOCAL4 (20<<3) /* reserved for local use */ #define LOG_LOCAL5 (21<<3) /* reserved for local use */ #define LOG_LOCAL6 (22<<3) /* reserved for local use */ #define LOG_LOCAL7 (23<<3) /* reserved for local use */ Linux: #define LOG_KERN (0<<3) /* kernel messages */ #define LOG_USER (1<<3) /* random user-level messages */ #define LOG_MAIL (2<<3) /* mail system */ #define LOG_DAEMON (3<<3) /* system daemons */ #define LOG_AUTH (4<<3) /* security/authorization messages */ #define LOG_SYSLOG (5<<3) /* messages generated internally by syslogd */ #define LOG_LPR (6<<3) /* line printer subsystem */ #define LOG_NEWS (7<<3) /* network news subsystem */ #define LOG_UUCP (8<<3) /* UUCP subsystem */ #define LOG_CRON (9<<3) /* clock daemon */ #define LOG_AUTHPRIV (10<<3) /* security/authorization messages (private) */ #define LOG_FTP (11<<3) /* ftp daemon */ /* other codes through 15 reserved for system use */ #define LOG_LOCAL0 (16<<3) /* reserved for local use */ #define LOG_LOCAL1 (17<<3) /* reserved for local use */ #define LOG_LOCAL2 (18<<3) /* reserved for local use */ #define LOG_LOCAL3 (19<<3) /* reserved for local use */ #define LOG_LOCAL4 (20<<3) /* reserved for local use */ #define LOG_LOCAL5 (21<<3) /* reserved for local use */ #define LOG_LOCAL6 (22<<3) /* reserved for local use */ #define LOG_LOCAL7 (23<<3) /* reserved for local use */ You can define facilities by their number, so if you want to select CRON messages from a Solaris box, you can use the filter: filter f_cron { facility(15); }; > On a non-Solaris related issue, if I try to test the kern facility by > doing a command like "logger -p kern.crit TEST" nothing happens locally > or on the loghost. Is there a reason why that should act differently > than other facilities? kernel messages are read from a special file (/proc/kmsg on linux), I suppose logger refuses to send a message with facility=kern from userspace. Try using truss on logger to see whether logger sends the message at all. (it does work on Linux however as strace shows) -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 _______________________________________________ syslog-ng maillist - syslog-ng(a)lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng

1 0

Re: Fwd: [syslog-ng]Logging Remotely from Solaris to Linux
by Ron Braley 31 May '02

31 May '02

Bazsi I'll give these a try this morning. As always, thanks for the quick, expert response. :) Have a great weekend! rb Ron Braley Network Team Leader - CCNP Systems Team Leader - MCSE, CNE University of North Dakota (Aerospace College) braley(a)aero.und.edu 701-777-2964 (work) / 2940 (fax) >>> bazsi(a)balabit.hu 05/31/02 02:45AM >>> On Thu, May 30, 2002 at 09:58:23PM -0500, Ron Braley wrote: > Hi Bazsi. > > Here's where things are with the syslog-ng and Solaris vs Linux: > > Using facility filters (i.e. f_cron) on the Linux box will result in > not logging any messages from the Solaris box. Other Linux boxes work > fine with the facility filters, though. Here's the list of facilities that Solaris uses, and the same on Linux: Solaris: #define LOG_KERN (0<<3) /* kernel messages */ #define LOG_USER (1<<3) /* random user-level messages */ #define LOG_MAIL (2<<3) /* mail system */ #define LOG_DAEMON (3<<3) /* system daemons */ #define LOG_AUTH (4<<3) /* security/authorization messages */ #define LOG_SYSLOG (5<<3) /* messages generated internally by syslogd */ #define LOG_LPR (6<<3) /* line printer subsystem */ #define LOG_NEWS (7<<3) /* netnews subsystem */ #define LOG_UUCP (8<<3) /* uucp subsystem */ #define LOG_CRON (15<<3) /* cron/at subsystem */ /* other codes through 15 reserved for system use */ #define LOG_LOCAL0 (16<<3) /* reserved for local use */ #define LOG_LOCAL1 (17<<3) /* reserved for local use */ #define LOG_LOCAL2 (18<<3) /* reserved for local use */ #define LOG_LOCAL3 (19<<3) /* reserved for local use */ #define LOG_LOCAL4 (20<<3) /* reserved for local use */ #define LOG_LOCAL5 (21<<3) /* reserved for local use */ #define LOG_LOCAL6 (22<<3) /* reserved for local use */ #define LOG_LOCAL7 (23<<3) /* reserved for local use */ Linux: #define LOG_KERN (0<<3) /* kernel messages */ #define LOG_USER (1<<3) /* random user-level messages */ #define LOG_MAIL (2<<3) /* mail system */ #define LOG_DAEMON (3<<3) /* system daemons */ #define LOG_AUTH (4<<3) /* security/authorization messages */ #define LOG_SYSLOG (5<<3) /* messages generated internally by syslogd */ #define LOG_LPR (6<<3) /* line printer subsystem */ #define LOG_NEWS (7<<3) /* network news subsystem */ #define LOG_UUCP (8<<3) /* UUCP subsystem */ #define LOG_CRON (9<<3) /* clock daemon */ #define LOG_AUTHPRIV (10<<3) /* security/authorization messages (private) */ #define LOG_FTP (11<<3) /* ftp daemon */ /* other codes through 15 reserved for system use */ #define LOG_LOCAL0 (16<<3) /* reserved for local use */ #define LOG_LOCAL1 (17<<3) /* reserved for local use */ #define LOG_LOCAL2 (18<<3) /* reserved for local use */ #define LOG_LOCAL3 (19<<3) /* reserved for local use */ #define LOG_LOCAL4 (20<<3) /* reserved for local use */ #define LOG_LOCAL5 (21<<3) /* reserved for local use */ #define LOG_LOCAL6 (22<<3) /* reserved for local use */ #define LOG_LOCAL7 (23<<3) /* reserved for local use */ You can define facilities by their number, so if you want to select CRON messages from a Solaris box, you can use the filter: filter f_cron { facility(15); }; > On a non-Solaris related issue, if I try to test the kern facility by > doing a command like "logger -p kern.crit TEST" nothing happens locally > or on the loghost. Is there a reason why that should act differently > than other facilities? kernel messages are read from a special file (/proc/kmsg on linux), I suppose logger refuses to send a message with facility=kern from userspace. Try using truss on logger to see whether logger sends the message at all. (it does work on Linux however as strace shows) -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 _______________________________________________ syslog-ng maillist - syslog-ng(a)lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng

1 0

Re: Fwd: [syslog-ng]Logging Remotely from Solaris to Linux
by Ron Braley 31 May '02

31 May '02

Hi Bazsi. Here's where things are with the syslog-ng and Solaris vs Linux: Using facility filters (i.e. f_cron) on the Linux box will result in not logging any messages from the Solaris box. Other Linux boxes work fine with the facility filters, though. The following is a syslog-ng.conf excerpt that lets all facilities (except mail and LPR) from the Solaris box log to /var/log/messages: destination d_messages { file("/var/log/messages"); }; log { source(s_all); filter(f_sirius); filter(f_warn); destination(d_messages); }; Again, if I add "filter(f_cron)" then nothing from the Solaris box works. The entry "filter(f_sirius)" a host filter, and that works fine. On a non-Solaris related issue, if I try to test the kern facility by doing a command like "logger -p kern.crit TEST" nothing happens locally or on the loghost. Is there a reason why that should act differently than other facilities? Thanks much for your help in these two matters. rb Ron Braley Network Team Leader - CCNP Systems Team Leader - MCSE, CNE University of North Dakota (Aerospace College) braley(a)aero.und.edu 701-777-2964 (work) / 2940 (fax)

2 1

syslog-ng-1.4.15 patch for libol-0.3.3
by Carlos Velasco 30 May '02

30 May '02

Hello, I tried to run "configure" with libol-0.3.3 and found out that configure was not capable to find or use my libol-0.3.3 although I tried to specify "--with-libol=" parameter. Looking into the code I see that libol version needed is at least: 0.2.23 As my libol is 0.3.3, configure script does a comparation between 23 and 3, seeing that 3 is minor (23 > 3), it abort compilation. I have issued the next patch: --- configure Fri Apr 26 11:45:46 2002 +++ configure.new2 Thu May 30 20:21:12 2002 @@ -2623,7 +2623,7 @@ LIBOL_MAJOR=`echo $LIBOL_VERSION | sed -e 's/$[0-9]*$\.[0-9]*\.[0-9]*/\1/'` LIBOL_MINOR=`echo $LIBOL_VERSION | sed -e 's/[0-9]*\.$[0-9]*$\.[0-9]*/\1/'` -LIBOL_PATCH=`echo $LIBOL_VERSION | sed -e 's/[0-9]*\.[0-9]*\.$[0-9]*$/\1/'` +LIBOL_PATCH=`echo $LIBOL_VERSION | sed -e 's/[0-9]*\.[0-9]*\.$[0-9]*$/\1/' | sed -e 's/^$[0-9]$$/\10/'` if test "$LIBOL_MAJOR" != "$LIBOL_REQ_MAJOR" -o \ "$LIBOL_MINOR" -lt "$LIBOL_REQ_MINOR" -o \ "$LIBOL_PATCH" -lt "$LIBOL_REQ_PATCH"; then Regards, Carlos Velasco

1 0

Re: Syslog-ng-1.5.17+"--enable-tcpwrapper"
by Balazs Scheidler 30 May '02

30 May '02

On Thu, May 30, 2002 at 06:28:05PM +0300, Sergey Holod wrote: > ? ?????? ?? ?? 30 ??? 2002 15:38 ?? ????????: > > On Thu, May 30, 2002 at 12:02:43PM +0300, Sergey Holod wrote: > > > ? ?????? ?? ?? 30 ??? 2002 11:55 ?? ????????: > > > > On Thu, May 30, 2002 at 10:21:55AM +0300, Sergey Holod wrote: > > > > can you send me your configure output and config.log? > $./configure --enable-tcp-wrapper ok, when I fixed the detection of libwrap, I made a mistake, so -lwrap wasn't added to LIBS. Try this patch (and regenerate your configure script using autoconf ) diff -u -r1.49 configure.in --- configure.in 29 May 2002 10:24:42 -0000 1.49 +++ configure.in 30 May 2002 15:43:42 -0000 @@ -190,7 +190,7 @@ if test "x$enable_tcp_wrapper" = "xyes"; then AC_CHECK_HEADERS(tcpd.h) dnl AC_CHECK_LIB(wrap, hosts_access) - if test $blb_cv_c_lwrap = "xyes"; then + if test "x$blb_cv_c_lwrap" = "xyes"; then LIBS="$LIBS -lwrap" fi fi -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1

1 0

Re: [syslog-ng]syslog-ng 1.5.18 released
by Michael Earls 30 May '02

30 May '02

On this new ver does it fix the broken pipe on debian? michael >>> bazsi(a)balabit.hu 05/30/02 02:32 AM >>> Hi, I've released syslog-ng 1.5.18 with the folowing NEWS entry: News for the 1.5.18 release Wed, 29 May 2002 12:23:45 +0200 Changes: * fixed a crash bug when an UDP destination was unreachable In addition to this you can now specify log_prefix() for pipe sources. It can be downloaded from the usual places: http://www.balabit.hu/en/downloads/syslog-ng/ -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 _______________________________________________ syslog-ng maillist - syslog-ng(a)lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng

2 1

1.5.18/bison-1.32/stdio.h problem
by Borsenkow Andrej 30 May '02

30 May '02

Obviously new bison includes stdio.h only when debugging is enabled. Without it fails miserably in yyerror: /* Enable debugging if requested. */ #if YYDEBUG # ifndef YYFPRINTF # ifdef __cplusplus # include <cstdio> /* INFRINGES ON USER NAME SPACE */ # else # include <stdio.h> /* INFRINGES ON USER NAME SPACE */ # endif # define YYFPRINTF YYSTD (fprintf) # endif (this is not the original cfg-grammar.c but regenerated locally). The following patch is bandaid but I am not sure how to do it portably enough (meaning - accounting for earlier bison versions). One possibility is of course move yyerror out of cfg-grammar.y to avoid confusion. -andrej --- syslog-ng-1.5.18/src/cfg-grammar.y.orig Thu May 30 11:39:06 2002 +++ syslog-ng-1.5.18/src/cfg-grammar.y Thu May 30 11:39:52 2002 @@ -698,6 +698,8 @@ extern int linenum; +#include <stdio.h> + void yyerror(char *msg) { fprintf(stderr, "%s at %d\n", msg, linenum);

2 1

syslog-ng 1.5.18 released
by Balazs Scheidler 30 May '02

30 May '02

Hi, I've released syslog-ng 1.5.18 with the folowing NEWS entry: News for the 1.5.18 release Wed, 29 May 2002 12:23:45 +0200 Changes: * fixed a crash bug when an UDP destination was unreachable In addition to this you can now specify log_prefix() for pipe sources. It can be downloaded from the usual places: http://www.balabit.hu/en/downloads/syslog-ng/ -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1

2 1

Re: Fwd: [syslog-ng]Logging Remotely from Solaris to Linux
by Ron Braley 29 May '02

29 May '02

Bazsi I'll try this right away!! I really appreciate you and all you do for the people asking syslog questions regularly. rb Ron Braley Network Team Leader - CCNP Systems Team Leader - MCSE, CNE University of North Dakota (Aerospace College) braley(a)aero.und.edu 701-777-2964 (work) / 2940 (fax) >>> bazsi(a)balabit.hu 05/29/02 06:47AM >>> On Tue, May 28, 2002 at 11:44:22AM -0500, Ron Braley wrote: > Hi bazsi > > Yes, I'm running syslog-ng on both platforms. > > I've attached the configuration files from the Linux box used to record > logs, and from the Solaris box sending logs. I hope this helps. > > Please keep in mind that I've only configured cron to send to the > source s_tcp destination for testing. I've used the logger command > "logger -p cron.crit TEST FROM JUB" to test things. Also, I'm new to > syslogging (as I'm sure you can tell). > > Thanks again, and have a great day! Are you sure that the facility code for cron matches on Solaris and Linux? Try to create a bare bone configuration like: (solaris) source s_all { internal(); sun-streams("/dev/log" door("/etc/.syslog_door"); }; destination d_tcp { tcp("1.2.3.4"); }; log { source(s_all); destination(d_tcp); }; (linux) source s_all { internal(); unix-stream("/dev/log"); tcp(); }; destination d_messages { file("/var/log/messages"); }; log { source(s_all); destination(d_messages); }; And as soon as it works, try playing with filters and the rest. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 _______________________________________________ syslog-ng maillist - syslog-ng(a)lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng

1 0

Re: Fwd: [syslog-ng]Logging Remotely from Solaris to Linux
by Balazs Scheidler 29 May '02

29 May '02

On Tue, May 28, 2002 at 11:44:22AM -0500, Ron Braley wrote: > Hi bazsi > > Yes, I'm running syslog-ng on both platforms. > > I've attached the configuration files from the Linux box used to record > logs, and from the Solaris box sending logs. I hope this helps. > > Please keep in mind that I've only configured cron to send to the > source s_tcp destination for testing. I've used the logger command > "logger -p cron.crit TEST FROM JUB" to test things. Also, I'm new to > syslogging (as I'm sure you can tell). > > Thanks again, and have a great day! Are you sure that the facility code for cron matches on Solaris and Linux? Try to create a bare bone configuration like: (solaris) source s_all { internal(); sun-streams("/dev/log" door("/etc/.syslog_door"); }; destination d_tcp { tcp("1.2.3.4"); }; log { source(s_all); destination(d_tcp); }; (linux) source s_all { internal(); unix-stream("/dev/log"); tcp(); }; destination d_messages { file("/var/log/messages"); }; log { source(s_all); destination(d_messages); }; And as soon as it works, try playing with filters and the rest. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1

1 0

stresstest
by Sangbutsarakum, Patai 29 May '02

29 May '02

I'm going to implement central log server in my datacenter to accept many tons of log from many servers and equipments. I'm newbies in syslog-ng, I've run stresstest.sh on my solaris 2.6 [ 2SPARCs, 1 GB RAM] [I've use version 1.4.15] after run just a moment. It show "Segmentation Fault". What does it means for syslog-ng [can't tolerate] or my machine is suck? Should I concern about this? what should i do ? Please suggest Patrick

2 1

"fifo" and "file" source difference?
by Borsenkow Andrej 28 May '02

28 May '02

I needed a source that takes input from a FIFO so I made an obvious "fifo" source. Then I realized I needed log_prefix (that is not supported by fifo) so I changed it to "file". So far I cannot see any real difference. When should "fifo" and when "file" be used? Or are they exactly the same, just under different name? TIA -andrej

2 1

Logging Remotely from Solaris to Linux
by Ron Braley 28 May '02

28 May '02

Greetings! I'm having trouble getting my Solaris servers to log remotely to a Linux 7.1 server. The other Linux boxes log remotely to it OK, and the Solaris boxes will log to a Solaris server configured to listen (source s_tcp { tcp(); };). However, the Linux boxes won't log to a Solaris server, nor will the Solaris boxes log to a Linux server. What am I missing? Is there a format problem or something I need to overcome? Thanks in advance for helping me save the rest of my hair!! rb

1 0

RE: [syslog-ng]syslog-ng survey
by Ohrberg, Mick 27 May '02

27 May '02

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bazsi, Do you have any preliminary results for the survey? I'm very curious to see how popular syslog-ng really is! /Mick | -----Original Message----- | From: Balazs Scheidler [mailto:bazsi@balabit.hu] | Sent: Wednesday, May 15, 2002 5:58 AM | To: syslog-ng(a)lists.balabit.hu | Subject: [syslog-ng]syslog-ng survey | | | Hi, | | Please find the time to fill out the survey below to help us | to further | improve syslog-ng. You can either fill it out in this mail message | by entering the appropriate marks in the brackets, or on-line by | pointing your | browser to this url: | | http://www.balabit.hu/en/downloads/syslog-ng/survey/ | | Thanks in advance, [snip] | -- | Bazsi | PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD | 804E C82C 8EB1 | | _______________________________________________ | syslog-ng maillist - syslog-ng(a)lists.balabit.hu | https://lists.balabit.hu/mailman/listinfo/syslog-ng | -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com> iQA/AwUBPO5bUueVnE5KiyKKEQKHMQCeLlhisonB112W6+3nrUoKn1+sOBwAoLNB RbMXeluositTHLBtN9x1+kIQ =x5iJ -----END PGP SIGNATURE-----

2 1

Re: [syslog-ng]Problem with HP-UX 11.0
by dcntrnoc＠cmp.com 23 May '02

23 May '02

Thanks for the info - I did try a number of different source statements, none of which gave me anything useful. I'll deal with syslogd on the HP boxes until we're able to upgrade. Thanks, Sharon. Balazs Scheidler <bazsi(a)balabit.hu> To: syslog-ng(a)lists.balabit.hu Sent by: cc: syslog-ng-admin@lists bcc: .balabit.hu Subject: Re: [syslog-ng]Problem with HP-UX 11.0 05/17/2002 03:51 AM Please respond to syslog-ng On Thu, May 16, 2002 at 12:53:33PM -0600, Brad Arlt wrote: > On Thu, May 16, 2002 at 02:16:58PM -0400, dcntrnoc(a)cmp.com wrote: > > Hi all, > > > > I have been running syslog-ng on a handful of Solaris boxes for some time > > now with no problems, and am attempting to get it running on HP-UX. > > I have compiled (with gcc) and installed syslog-ng 1.5.16 and libol 0.3.2 on > > a system running HP-UX 11.00. I am using the following source statement > > in my config file: > > > > source s_sys { pipe("/dev/log"); internal(); }; > > Err... Ah, are you sure that opening a pipe from /dev/log will yeild > what you want? /dev/log is usually a Unix domain socket, which might > put more in the stream asside from ASCII. I'd turn off any syslog > daemons you have and just cat /dev/log | od Sorry, but HP-UX's /dev/log is really a pipe and not a socket. The problem seems to be that programs sending messages to /dev/log write a whole 2048 bytes block regardless the real length of the message. As syslog-ng reads _lines_ from a pipe, the rest of the 2048 bytes block is also read, which is what you see there. Currently my development branch of syslog-ng 2.0 supports this, but 1.5.x doesn't. A temporary solution would be to use both original syslogd from HP-UX and have it send messages to localhost where a syslog-ng is listening. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 _______________________________________________ syslog-ng maillist - syslog-ng(a)lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng

2 1

Christopher Leonardos/Triumph is out of the office.
by Christopher_Leonardos＠interliant.com 23 May '02

23 May '02

I will be out of the office starting 05/22/2002 and will not return until 05/28/2002. If you need immediate assistance please send email too either scott_tobias(a)interliant.com or mitchell_hryckowian(a)interliant.com Thank You

1 0

Newbie Question - Error Upon Installation - Help!
by Ron Braley 20 May '02

20 May '02

Greetings! Upon installing syslog-ng-1.4.10-1.0.24, and trying to run syslog-ng, I received an error: Cannot open configuration file /etc/syslog-ng/syslog-ng.conf for reading Parse error reading configuration file, exiting. So, I specified the configuration file and now am getting the following error: # syslog-ng -f /etc/syslog-ng.conf io.c: bind_unix_socket(): /var/chroot/named/dev/log not a socket Error initializing configuration, exiting. I'd greatly appreciate any help given by anyone. Take care. rb Ron Braley Network Team Leader - CCNP Systems Team Leader - MCSE, CNE University of North Dakota (Aerospace College) braley(a)aero.und.edu 701-777-2964 (work) / 2940 (fax)

1 0