October 2008 - syslog-ng - lists.balabit.hu

[Bug 14] New: Maintain symlinks to current and previous log output files...
by bugzilla＠bugzilla.balabit.com 28 Sep '11

28 Sep '11

https://bugzilla.balabit.com/show_bug.cgi?id=14 Summary: Maintain symlinks to current and previous log output files... Product: syslog-ng Version: 2.0.x Platform: PC URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=218688 OS/Version: Linux Status: NEW Severity: minor Priority: unspecified Component: syslog-ng AssignedTo: bazsi(a)balabit.hu ReportedBy: sasa(a)debian.org Type of the Report: enhancement Estimated Hours: 0.0 >From bugs.debian.org: I'm hoping that upstream might consider adding functionality to syslog-ng to allow it to track current and previous log files and maintain symlinks to them, as a user option. This replicates one of the options that I (and others) find useful in cronolog. This has been previously discussed on the syslog-ng mailing list, though apparently nothing fully came of it. The archive of that discussion is at: https://lists.balabit.hu/pipermail/syslog-ng/2002-June/003452.html Obviously, it's probably somewhat of a low priority, but it would be nice. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 1

syslog-ng client messages delayed
by mark peters 22 Mar '10

22 Mar '10

Hi, We are running into a issue where syslog-ng clients who are configured to forward to a central syslog-ng destination server that are reasonably chatty are getting there messages delayed at the source (ie. 'tcpdump'ing the client shows it is sending messages from N minutes ago, where N is anything from 5 to 60 minutes on average sometimes more). We have also seen a small percentage of loss at the destination. On these 'delayed' clients we also see the resident memory footprint on the growing. Clients are running 1.6.12 (have tried 2.0.8 also - same symptons). The central syslog-ng server is running 2.0.8. relevant config entries are: syslog-ng client: options { sync (1); time_reopen (10); log_fifo_size (2097152); long_hostnames (off); use_dns (no); use_fqdn (no); create_dirs (no); keep_hostname (yes); }; destination d_central { tcp("log2.xyz.com" port(5140)); }; filter f_local5 { facility(local5); }; log { source(s_sys); filter(f_local5); destination(d_central); flags(final); }; syslog-ng central server: options { time_reopen (10); log_fifo_size (2097152); long_hostnames (off); use_dns (yes); dns_cache (yes); dns_cache_expire (28800); use_fqdn (no); create_dirs (yes); dir_perm (0755); perm (0644); keep_hostname (no); use_time_recvd (no); stats_freq(600); flush_timeout(16000); flush_lines(256); time_sleep(80); }; destination d_server { file("/logs/server.$LEVEL.log"); }; filter f_server { facility(local5) and program("server"); }; log { source(s_sys); filter(f_server); destination(d_server); flags(final); }; to give a rough idea of message volume the server is receiving approximately 50 million log lines per day on average any help/information would be appreciated thanks -------------------------------------- Easy + Joy + Powerful = Yahoo! Bookmarks x Toolbar http://pr.mail.yahoo.co.jp/toolbar/

3 4

[Bug 21] New: call shutdown() before closing a socket
by bugzilla＠bugzilla.balabit.com 30 Apr '09

30 Apr '09

https://bugzilla.balabit.com/show_bug.cgi?id=21 Summary: call shutdown() before closing a socket Product: syslog-ng Version: 2.1.x Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: unspecified Component: syslog-ng AssignedTo: bazsi(a)balabit.hu ReportedBy: bazsi(a)balabit.hu Type of the Report: --- Estimated Hours: 0.0 syslog-ng should call shutdown() before closing a socket to ensure the contents of the socket buffer are emptied. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 1

[Bug 23] New: MySQL default configuration causes error on 'pid' column
by bugzilla＠bugzilla.balabit.com 30 Apr '09

30 Apr '09

https://bugzilla.balabit.com/show_bug.cgi?id=23 Summary: MySQL default configuration causes error on 'pid' column Product: syslog-ng Version: 2.1.x Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: unspecified Component: syslog-ng AssignedTo: bazsi(a)balabit.hu ReportedBy: mark(a)la-croix.net Type of the Report: bug Estimated Hours: 0.0 When configuring a MySQL destination, the default 'pid' column type is INT. However, if a message comes through with no PID, the SQL command tries to insert an empty quoted string, which causes an error in MySQL 5.0. Example error: Error running SQL query; type='mysql', host='!MY_DB_HOST!', port='', user='syslog-ng', database='syslog-ng', error='1366: Incorrect integer value: \'\' for column \'pid\' at row 1', query='INSERT INTO !MY_LOG_CLIENT_HOST!_2008_09_23 (date, facility, level, host, program, pid, message) VALUES (\'2008-09-23 12:24:35\', \'1\', \'5\', \'!MY_LOG_CLIENT!\', \'root\', \'\', \'test\')' The message is coming from a TCP source from which a large percentage of messages have no PID associated. The workaround is to explicitly set the PID column to VARCHAR so it can handle empty strings, but it would be nice to see the empty PID case gracefully handled. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 9

[patch] Add follow_freq_ms option
by Joe Shaw 16 Jan '09

16 Jan '09

Hi, As I mentioned in the last thread, I've found myself wanting to have better than one second resolution for the follow_freq() option. Attached is a patch which adds a follow_freq_ms option, which takes its value in milliseconds rather than full seconds. follow_freq() continues to work as it did previously. Thanks, Joe

3 7

Re: [syslog-ng] syslog-ng takes 100% CPU when network fails
by D S, Manu (STSD) 06 Nov '08

06 Nov '08

This patch fixes the issue. Thanks! - Manu > > Hi, > > > > We are running syslog-ng 2.0.9 on a HP-UX 11.31 server. We > have configured this system as a client to forward logs to a remote > server. When there is a network failure ( simulated by ifconfig down ) > syslog-ng starts to consume CPU and even after the network comes back, > it does not forward any log messages and continues to hog CPU. > > > > We did system call tracing using tusc and found that "poll()" > gets "POLLERR" event from TCP socket descriptor, but syslog-ng does not > call any socket calls for the TCP, only calls "gettimeofday()". > > > > In the logs given, TCP connection to server is disconnected > at 13:10:30. From that time, poll() receives POLLERR on the TCP socket > (fd=6) and starts loop on gettimeofday(). Attached are the sar, > netstat and tusc logs. > > First of all, Thanks for the detailed error report. > > As I see the problem seems to be caused by the fact that HP-UX returns > POLLERR only without the other bits (e.g. POLLHUP) syslog-ng would > handle this gracefully if either the other bits would be set, or > there'd > be some pending messages to send, in which case a normal write() error > would occur. > > This patch should fix the problem, although I only compile-tested it. > I'd appreciate if you could test this patch in your environment. > > diff --git a/src/logwriter.c b/src/logwriter.c > index bb82b43..7a5fcf7 100644 > --- a/src/logwriter.c > +++ b/src/logwriter.c > @@ -139,6 +139,13 @@ log_writer_fd_dispatch(GSource *source, > log_writer_broken(self->writer, NC_CLOSE); > return FALSE; > } > + else if (self->pollfd.revents & (G_IO_ERR)) > + { > + msg_error("POLLERR occurred while idle", > + evt_tag_int("fd", self->fd->fd), > + NULL); > + log_writer_broken(self->writer, NC_WRITE_ERROR); > + } > else if (self->writer->queue->length || self->writer->partial) > { > if (!log_writer_flush_log(self->writer, self->fd)) > > > > > > -- > Bazsi >

2 1

Problems compiling on RHEL 5 (flex error)
by Douglas E. Warner 06 Nov '08

06 Nov '08

I'm getting the following error trying to build packages for RHEL5: flex `test -f cfg-lex.l || echo './'`cfg-lex.l "cfg-lex.l", line 1: unrecognized '%' directive "cfg-lex.l", line 3: bad character: # "cfg-lex.l", line 3: unknown error processing section 1 "cfg-lex.l", line 3: bad character: " "cfg-lex.l", line 3: bad character: . "cfg-lex.l", line 3: bad character: " "cfg-lex.l", line 5: bad character: } make[2]: *** [cfg-lex.c] Error 1 make[2]: Any ideas on what I can do here? -Doug

2 4

[PATCH] anonymizing filter
by Micah Anderson 06 Nov '08

06 Nov '08

Hello, A couple years ago this patch was submitted to the list for consideration for inclusion into syslog-ng. I am writing this email again to request that it be considered again. The patch provides a simple replace which enables you to strip out IP addresses from your logs before they are written to disk. The patch has been included in the Debian stable distribution, and currently is included in both Debian Sid and Lenny (unstable and testing). It has had a very wide testing base and is non-intrusive, it has existed since 2004 and has been adapted to work with the newer syslog-ng. The goal of this patch is to give an organization the means to implement site logging policies, by allowing for easy control over exactly what data is retained in the logfiles. When I first requested consideration for inclusion the reactions were some suggestions for improvement (which were done), some side discussions about the various states of data retention laws, and a general agreement that this patch is non-intrusive and had a valid use case (at least in the U.S., but also likely in other countries as well[0]). The side-discussions about data-retention laws were mostly around specific geographic localities that were considering laws that would make stripping of addresses illegal, or had already mandated such things. Although these were interesting discussions, as EU data retention laws would prohibit many people from making such configuration changes to their syslog-ng.conf, they were tangential to the point because this patch does not cause those to break such laws. On the other side of the pond, in the U.S., the EFF[1] has made it very clear that this mechanism of anonymizing logs is perfectly (a) legal in the U.S., and (b) advisable. There are many instances where it is preferable to keep less information on users than is collected by default on many systems. In the United States it is not currently required to retain data on users of a server, but you may be required to provide all data on a user which you have retained. OSPs can protect themselves from legal hassles and added work by choosing what data they wish to retain. The current climate in the U.S. makes this problem so much more important now than it was many years ago. Having the ability to implement a site-policy that enables an organization to decide if the trade-off between privacy and analysis is worthwhile. This patch allows organizations to have that choice if they feel that it is more important to avoid retaining sensitive data rather than having a full history of everything logged. Please accept this patch[2], Micah [0] EPIC International Data Retention Page http://www.epic.org/privacy/intl/data_retention.html [1] The EFF is the major civil liberties internet watchdog in the US, their "Best Practices for Online Service Providers" can be found here: http://www.eff.org/osp, they explicitly link to our patch as a recommendation [2] The latest patch can be found at https://code.autistici.org/trac/privacy/browser/trunk/syslog-ng

6 11

Re: [syslog-ng] Encoding provlem when writing to postgres
by ml＠bortal.de 05 Nov '08

05 Nov '08

Hi, where can i get syslog-ng 3.0? I cant find it on http://www.balabit.com/downloads/files/syslog-ng/sources/ Thanks, Mario Am 15.10.2008 um Uhr haben Sie geschrieben: > On Wed, 2008-10-15 at 09:53 +0200, ml(a)bortal.de wrote: > > Hello List, > > > > How can i fix this? I am running postgresql-8.1 with Debian 4.0. > > Probably the syslog client sends non-utf8 characters in its message. > syslog-ng 2.0 and 2.1 do not really care about the message contents. > > 3.0 has support for various encodings and utf8 validation like this: > > This assumes that the input is latin1: > > source s_net { udp(encoding("iso-8859-1")); }; > > And this one enforces valid utf8 messages > > source s_net { udp(flags(validate-utf8)); }; > > I was planning to add another flag, but this is not yet implemented: > > source s_net { udp(flags(force-utf8)); }; > > Which would enforce valid utf8 sequences by changing the input. > > As an alternative don't use utf8 as the character encoding of your > database, use latin1, that'll permit any kind of data in the database. >

3 7

syslog-ng .2.1.1 AIX module libglib-2.0.a(libglib-2.0.so.0) could not be loaded
by CentralRegion IPAdmin 05 Nov '08

05 Nov '08

Hi I have configured and compiled syslog-ng 2.1.1 on AIX 5.2 using the DEFAULT configure options. I can start the binary on the device where I have compiled it, but when I transfer it to another AIX device I'm getting an error saying "Could not load program ./syslog-ng.2.1.1: Dependent module libglib-2.0.a(libglib-2.0.so.0) could not be loaded. Could not load module libglib-2.0.a(libglib-2.0.so.0). System error: No such file or directory" I have tried the same with version 2.0.9 - This works fine. Do you have an idea what I have to change for 2.1.1? Thank You! Werner Keuler

4 6