June 2002 - syslog-ng - lists.balabit.hu

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