- syslog-ng - lists.balabit.hu

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

No such DBI driver; type='pgsql'
by ml＠bortal.de 05 Nov '08

05 Nov '08

Hello List, i successfully compiled version 2.9.0+20081022. I used: LDFLAGS=-L/usr/local/lib LIBS=-ldbi ./configure --enable-sql But when i start syslog-ng i get this error: ------------------------------------------------------------------------- syslog-db:~# syslog-ng -F -v -f /etc/syslog-ng.conf -e -v Configuration file has no version number, assuming syslog-ng 2.1 format. Please add @version: maj.min to the beginning of the file; WARNING: global: the default value of chain_hostnames is changing to 'no' in version 3.0, please update your configuration accordingly; Your configuration file uses an obsoleted keyword, please update your configuration; keyword='sync', change='flush_lines' Your configuration file uses an obsoleted keyword, please update your configuration; keyword='stats', change='stats_freq' WARNING: input: sources do not remove new-line characters from messages by default in version 3.0, please add 'no-multi-line' flag to your configuration if you want to retain this functionality; WARNING: file source: default value of follow_freq in file sources is changing in 3.0 to '1' for all files except /proc/kmsg; WARNING: template: the default value for template-escape is changing to 'no' in version 3.0, please update your configuration file accordingly; syslog-ng starting up; version='2.9.0+20081022' Database thread started; No such DBI driver; type='pgsql' My Syslog Config looks like this: ========================== options { chain_hostnames(off); sync(0); stats(43200); }; source src { unix-stream("/dev/log"); internal(); pipe("/proc/kmsg"); }; source src_remote { tcp(ip("foo") port(514) max-connections(20)); }; destination d_sql { # source s_net { udp(encoding("iso-8859-1")); }; # source s_net { udp(flags(validate-utf8)); }; sql(type(pgsql) host("212.87.146.204") username("foo") password("bar") database("syslogng") table("msg_table") columns("msg_rcv_time", "msg_sent_time", "hostname", "msg_facility", "msg_priority", "msg_text") values($R_ISODATE, $S_ISODATE, $HOST, $FACILITY, $PRIORITY, $MSG) ); }; destination messages { file("/var/log/messages"); }; log { source(src_remote); source(src); destination(messages); destination(d_sql); }; Any Idea how to fix this? Cheers, Mario

2 1

Real Time Alerting message from Syslog-ng!
by Wilson Lai 05 Nov '08

05 Nov '08

Hi, I am implementing the real time alert messages in Syslog-ng by using the following script : # TO=wilsonlai(a)abc.com # while read line # do # hostname=`echo $line | awk '{print $4}'`; # echo $line | /bin/mail -s "Syslog Alert Messages from HOST : $hostname" $TO # done My question is while using readline, sometimes the hostname could not be displayed correctly and give the hostname “Report” as the following event message collected : Nov 5 15:57:19 report server (mssqlserver)[error] 106 Scheduled operations cannot be created. SQL Server Agent is not running. How could it be fixed? Thanks. Regards, Wilson Lai System Engineer IT Dept., SJM Office ( : (853)2978585 Mobile ( : (853)66506709 Email ( : wilsonlai(a)macausjm.com

1 0

Re: [syslog-ng] filter on src ip address.
by Esben Laursen 29 Oct '08

29 Oct '08

> -----Oprindelig meddelelse----- > Fra: Leonard Mills [mailto:lenm@ops.corpnet.sel.sony.com] > Sendt: 28. oktober 2008 22:24 > Til: Esben Laursen > Emne: Re: [syslog-ng] filter on src ip address. > > Esben wrote: > >Now the next question is, can I have the syslog-ng accept everyting, but > >"auto" generate a new file for each different source addresses? > > Sure, you can use $HOST as a part of the path. Something like: > > destination cacheflow { file("/c1/logs/$HOST/cacheflow.log" > template("$DATE $HOST $PROGRAM: [$FACILITY.$PRIORITY] $MSG\n")); }; > > (all one line) works just fine. Hmm, looks pretty easy.. So the $HOST is the "remote" source host and not "localhost" right? Where did you find the variable list? It was not in the man 5 syslog-ng.conf file.. Cheers Esben

2 1

Re: [syslog-ng] filter on src ip address.
by Esben Laursen 28 Oct '08

28 Oct '08

Hi Leo, Thanks for your quick reply.. Im looking at it, but it does not seem to make much sense to me.. Am I correct to assume that destination is a sort of container for what goes where? I extracted this from my Debian syslog-ng install source s_all { # message generated by Syslog-NG internal(); # standard Linux log source (this is the default place for the syslog() # function to send logs to) unix-stream("/dev/log"); # messages from the kernel file("/proc/kmsg" log_prefix("kernel: ")); # use the following line if you want to receive remote UDP logging messages # (this is equivalent to the "-r" syslogd flag) # udp(); }; ###### # destinations # some standard log files destination df_auth { file("/var/log/auth.log"); }; # auth,authpriv.* /var/log/auth.log log { source(s_all); filter(f_auth); destination(df_auth); }; So, I could do something like: Source MyAppliance { udp(<src IP>) }; Destination MyAppliance_log { file("/var/log/MyAppliance"); }; Log { Source(MyAppliance); Destination(MyAppliance_log); }; Does that make sense? Now the next question is, can I have the syslog-ng accept everyting, but "auto" generate a new file for each different source addresses? Cheers Esben > -----Oprindelig meddelelse----- > Fra: Leonard Mills [mailto:lenm@ops.corpnet.sel.sony.com] > Sendt: 28. oktober 2008 21:53 > Til: Esben Laursen > Emne: Re: [syslog-ng] filter on src ip address. > > You should probably start with: > > man syslog-ng.conf > > Pay particular attention to the section "DESTINATIONS" > What you want to do is _very_ easy with NG. > > Len > > On Tue, 28 Oct 2008, Esben Laursen wrote: > > > Hi Guys, > > > > I've been looking at syslog-ng's website, but cannot seem to find the > correct info. > > > > I need to have a syslog server that gather logs from different > appliances devices. Currently I just a regular syslogd, the problem is > that I need to have every appliance in a different file, and that does > syslogd not support. > > > > I've looked at the webpage for it appear that syslog-ng support this, I > look at the feature list, it says something like this: > > > > Filtering for sending IP address, check for syslog-ng. > > > > However I have no idea how to configure it or if I misunderstood the > meaning of the feature list. > > > > Could someone please point me in the correct direction? > > > > Cheers > > > > Esben > > > > > __________________________________________________________________________ > ____ > > Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng > > Documentation: > http://www.balabit.com/support/documentation/?product=syslog-ng > > FAQ: http://www.campin.net/syslog-ng/faq.html > > > > > > >

1 0

Kevin Gorski/IS/NEU is out of the office.
by K.Gorski＠neu.edu 28 Oct '08

28 Oct '08

I will be out of the office starting 10/28/2008 and will not return until 10/30/2008. I will respond to your message when I return Thursday morning.

1 0

filter on src ip address.
by Esben Laursen 28 Oct '08

28 Oct '08

Hi Guys, I've been looking at syslog-ng's website, but cannot seem to find the correct info. I need to have a syslog server that gather logs from different appliances devices. Currently I just a regular syslogd, the problem is that I need to have every appliance in a different file, and that does syslogd not support. I've looked at the webpage for it appear that syslog-ng support this, I look at the feature list, it says something like this: Filtering for sending IP address, check for syslog-ng. However I have no idea how to configure it or if I misunderstood the meaning of the feature list. Could someone please point me in the correct direction? Cheers Esben

1 0

Re: [syslog-ng] Reload does not free up RAM
by Evan Rempel 27 Oct '08

27 Oct '08

Evan Rempel wrote: > Balazs Scheidler wrote: >> On Mon, 2008-10-06 at 11:38 -0700, Evan Rempel wrote: >>> Balazs Scheidler wrote: >>>> On Sun, 2008-10-05 at 13:49 -0700, Evan Rempel wrote: >>>>> Balazs Scheidler wrote: >>>>>>>>>>> We have cases where a syslog-ng buffers quite a bit of data (2GB or so) before >>>>>>>>>>> it is able to flush the data to the destination. Currently, the only way to "free up" that RAM >>>>>>>>>>> is to restart syslog-ng, which means that some log messages are lost during the restart >>>>>>>>>>> window. >>>>>> Both PE and OSE frees up disk/memory when possible. If they don't, then >>>>>> that's probably a leak. >>> No, it isn't a memory leak as the process can be months old and only grows when >>> it buffers messages. >>> >>>>>> So if your syslog-ng process is 2GB in size, and you didn't specify an >>>>>> overly large log_fifo_size(), it's probably because of a leak. >>> >> >>>>> I have a large log_fifo_size() but the process starts small, grows when it needs >>>>> to buffer, and does NOT get small again when the destination is available. >>>> Hmm... that might be related to the malloc implementation. Which >>>> platform are you using? >>>> >>>>>>> 2. The buffer space should be thrown away only after the message >>>>>>> has been delivered to the destination. >>>>>> I see, this is what should happen now. >>> >> >>>>> This does not appear to be happening. >>>>> I am using OSE 2.0.8 Have there been memory fixes/changes since then? >>>> Not that I know of. >>>> >>>>> Is there a way to get buffer count statistics out? How many messages are >>>>> in each fifo buffer? >>>> In the experimental 3.0 branch, yes there is. In current 2.0, I'm afraid >>>> there's none. >>>> >>>> Is there a limit on the growth of syslog-ng? I mean if it gets large >>>> once and then empties its buffers, it stays large, but does it start >>>> growing again, or it stays steadily at the size it was before? >>> I have not specifically tested this scenario, but we do track processes >>> and memory usage, and it appears that once the space is allocated, it does >>> not grow unless a larger set of messages gets buffered. >>> >>> >>>> Again, the platform matters a lot, how the local malloc implementation >>>> takes care about fragmentation, whether it shrinks the process once >>>> memory is freed. >>> This is running on Redhat AS 3 (2.4 kernel) and Redhat AS 4 (2.6 kernel) >>> >>> On the Redhat 4 system the glibc packages installed are >>> >>> glibc-common-2.3.4-2.36 >>> glibc-devel-2.3.4-2.36 >>> glibc-headers-2.3.4-2.36 >>> glib2-2.4.7-1 >>> glibc-kernheaders-2.4-9.1.100.EL >>> >> hmm.. this version should be all right, at least in my experience glibc >> tries to release memory back to the system once the application freed it >> using free(). >> >> Maybe it is some kind of memory fragmentation issue. How easy is this to >> reproduce? Does it require months of running, or you have a simple >> recipe to create it? > > We are encountering this fairly easily in production, so I should be able to > verify a recipe. It will take me a couple of days to "get to it", but will report back. I thought that this deserved some attention... make a destination destination erempel { pipe("/var/log/syslog.pipes/erempel" log_fifo_size(1000000) perm(0666) ); }; and set up some logging to it. I directed only *.debug stuff to mine. filter f_debug { priority(debug); }; log { source(local); filter(f_debug); destination(erempel); flags(final); }; Start a "tail -f /var/log/syslog.pipes/erempel" and then generate some logs ls -1 /usr/bin | logger -p user.debug and I see the stuff pop out from the "tail -f" Cancel the tail process and product a whole bunch more logs. ls -1 /usr/bin | logger -p user.debug repeatedly while watching the size of the syslog process. Tue Oct 7 08:56:09 PDT 2008 root 23265 1.7 0.1 4004 1396 ? Ss 08:53 0:02 /usr/local/sbin/syslog-ng Tue Oct 7 08:56:14 PDT 2008 root 23265 1.7 0.1 4004 1412 ? Ss 08:53 0:02 /usr/local/sbin/syslog-ng Tue Oct 7 08:56:19 PDT 2008 root 23265 1.7 0.1 4004 1412 ? Ss 08:53 0:02 /usr/local/sbin/syslog-ng Tue Oct 7 08:56:24 PDT 2008 root 23265 2.5 1.2 15524 12840 ? Ss 08:53 0:04 /usr/local/sbin/syslog-ng Tue Oct 7 08:56:29 PDT 2008 root 23265 3.6 3.1 35384 32668 ? Ss 08:53 0:06 /usr/local/sbin/syslog-ng Tue Oct 7 08:56:34 PDT 2008 root 23265 4.7 5.1 55904 53264 ? Ss 08:53 0:08 /usr/local/sbin/syslog-ng Tue Oct 7 08:56:40 PDT 2008 root 23265 5.7 7.0 75724 73100 ? Ss 08:53 0:10 /usr/local/sbin/syslog-ng Tue Oct 7 08:56:45 PDT 2008 root 23265 5.6 7.1 76504 73864 ? Ss 08:53 0:10 /usr/local/sbin/syslog-ng Tue Oct 7 08:56:50 PDT 2008 root 23265 6.8 7.1 76504 73864 ? Ss 08:53 0:13 /usr/local/sbin/syslog-ng Tue Oct 7 08:56:55 PDT 2008 root 23265 6.6 7.1 76504 73864 ? Ss 08:53 0:13 /usr/local/sbin/syslog-ng The intent is to start the "rail -f" again to read all of the records and see if the memory gets smaller, but when I start the tail -f again, I get NOTHING. Syslog-ng seems to have closed the pipe destination and is NOT reopening it. Fortunately, the author produced a HUP signal that will cause all outputs to be closed and opened again. So, I do a HUP, and only the LAST 10 records are displayed. Where did all of the other records go? If I do ls -1 /usr/bin | logger -p user.debug I see the full list from the "tail -f" Back to memory. The memory never gets smaller. Now I am beginning to thing that the records got orphaned inside of syslog-ng such that they never made it to the destination, and as such are never candidates for memory reclaiming. I think I have stumbled on a bug for record loss, and I would like to state again that ALL destinations should follow the time_reopen() setting. -- Evan Rempel

3 2

syslog-ng takes 100% CPU when network fails
by D S, Manu (STSD) 26 Oct '08

26 Oct '08

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. Thanks, Manu

2 1

syslog-ng and multiple interfaces
by brandon askme 24 Oct '08

24 Oct '08

Hello- I have successfully moved all of our servers over to syslog-ng. All but a few are reporting to the remote "logging" server I have setup. What I have found is that the clients that are not reporting have multiple interfaces, IE eth0, eth0:1, eth1 etc.. Thus the current firewall rules are not setup to allow all the ips. So my question is, can I configure syslog-ng to only use a certain ip/interface when sending the logs to the remote logging server? The clients and the remote logging server are running Linux. Thanks -Brandon

3 2