- syslog-ng - lists.balabit.hu

Cutting Off.
by Jim Gifford 03 Sep '02

03 Sep '02

Version 1.5.20. The cut-off problem is back. Here is a sample. Here is a few samples. Sep 3 12:59:46 server SRC=63.171.79.154 DST=64.30.195.78 LEN=576 TOS=0x00 PREC=0x00 TTL=114 ID=44751 PROTO=TCP SPT=80 DPT=4959 SEQ=168963 ACK=2319997928 WINDOW=17373 RES=0x00 ACK URGP=0 ip_conntrack_tcp: INVALID: Out of window data; SEQ is over the upper bound (over the window of the receiver) It should be. Sep 3 12:59:46 server IPT: Reject_TCP_Packet: IN=eth0 OUT= MAC=00:50:ba:5c:16:53:00:10:67:00:51:f7:08:00 SRC=63.171.79.154 DST=64.30.195.78 LEN=576 TOS=0x00 PREC=0x00 TTL=114 ID=44750 PROTO=TCP SPT=80 DPT=4959 WINDOW=17373 RES=0x00 ACK URGP=0 ip_conntrack_tcp: INVALID: Out of window data; SEQ is over the upper bound (over the window of the receiver)

1 0

replacing plpgsql timestamp fn calls in 7.2
by colm ennis 02 Sep '02

02 Sep '02

hi, a plpgsql trigger i used in 7.1 made the following use of the timestamp function: insert into syslog_table values (timestamp(new.sdate, new.stime), hostid, ciscomsgid, new.smsg); ive had to upgrade to 7.2 and i read in the release notes that this function is gone in 7.2: The timestamp() function is no longer available. Use timestamp 'string' instead, or CAST. how do i get this insert to work? i have no idea of the syntax required. thanks for your help, colm ennis

1 0

Central Logging
by Lightfoot.Michael 02 Sep '02

02 Sep '02

I am setting up central logging for all my DMZ systems which are all Sun boxes running Solaris 2.6 or Solaris 8. What I want to achieve is to logg stuff locally as standard syslog did previously and in addition forward all syslog data to a central host to be stored identically in a subdirectory /var/log/$HOST/ - so I'll have files such as /var/log/foo/messages, /var/log/foo/syslog, /var/log/foo/authlog, etc. Has anyone done this in a way that doesn't demand a humungous config file on the central host with near identical settings for each remote host? Michael Lightfoot Unix Consultant ISG Host Systems Comcare +61 2 62750680 NOTICE: This e-mail message and attachments may contain confidential information. If you are not the intended recipient you should not use or disclose any information in the message or attachments. If received in error, please notify the sender by return email immediately. Comcare does not waive any confidentiality or privilege. Comcare's Canberra and Melbourne offices have moved to new premises. We hope this notice makes it easier for you to update your records. New street addresses: Canberra office Level 1 14 Moore street CANBERRA CITY ACT 2601 Melbourne Office Level 2 121 William Street MELBOURNE VIC 3001 Claims Fax Number 03 9620 4721 Please call Comcare on 1300 366 979 if you have any queries.

1 0

Incomplete library checking when building 1.4.15 on Sol7/SPARC
by Adam Steffes 30 Aug '02

30 Aug '02

While trying to build syslog-ng v1.4.15 on a rather plain Solaris 7/SPARC machine, I found that the configure script doesn't look everywhere it should to find yywrap. My system had it in /usr/lib/libl.a while the configure script seemed to look only in /usr/lib/libfl.a. I basically hardcoded the configure script to look at libl.a in a hurried attempt to get it to compile. Is this something anyone has looked at before? I admit I am not a developer by any means, and certainly do not want to insult anyone. It seems a small bit of code could be added to the 'case' statement in the configure script to perform a more extensive search for yywrap. Here is how I found the location of yywrap on my machine: $ for lib in /usr/lib/*.a ; do echo $lib ; nm $lib | grep yywrap ; done <other libs snipped> /usr/lib/libintl.a /usr/lib/libkrb.a /usr/lib/libl.a /usr/lib/libl.a[yywrap.o]: [5] | 0| 8|FUNC |GLOB |0 |2 |yywrap [1] | 0| 0|FILE |LOCL |0 |ABS |yywrap.c /usr/lib/libldfeature.a /usr/lib/libm.a /usr/lib/libmail.a /usr/lib/libmalloc.a <the rest snipped> I hope this helps. -Adam

1 0

Priming the database.
by Scott A. McIntyre 30 Aug '02

30 Aug '02

Hi, I'm pondering moving towards mysql logging for syslog-ng, but was wondering if anyone has already got a tool/script laying around to take current logs and import into the database accurately and correctly. Thanks for any pointers, Scott

1 0

syslog over TCP
by BONIKOWSKE, SCOTT 28 Aug '02

28 Aug '02

--- Received from WPS.SBONIKOW (608) 226-2630 08-28-02 1021a Hello, I am new to syslog-ng, and I had a couple questions that I have not seen answered before in the archives (from what I saw), and I was wondering if anyone out there could help. I hope this is the right area for these questions. First, Does TCP increase the load on the CPU alot over UDP? the situation is, we are looking at using syslog-ng on a midsized company (overall about 6,000+ people). we would like to monitor all syslog activity from NT,2000, XP, HPUX, AIX, Cisco routers/switches/PIXs, linux. The windows machiens are mostly file/application servers, the linux boxes are file/web/application servers, the HPUX and AIX boxes are application servers also. There is a lot of logging that will need to be watched because of security reasons (including file access, logins, etc.), so we are expecting a lot of traffic. The end goal will be to have all of the logs filtered by machine (in some cases even more granular than that like cisco errors going into the main log, and a seperate error log for that machine, and an error log for all networking devices), and maybe even searchable if I have enough time. I am only going into high detail above becase I would like to know opinions about using TCP vs UDP for load on the CPU, and to see if anyone else has maybe done something like this themselves for a company close to the same size. Any help and comments would be welcome. Thanks Scott Bonikowske Open Systems Analyst WPS ---- 08-28-02 1021a ---- Sent to ------------------------------------ -> syslog-ng(a)lists.balabit.hu

1 0

syslog-ng documentation and some minor niggles
by Ted_Rule＠flextech.co.uk 28 Aug '02

28 Aug '02

Many thanks to Stephen Frost and Balazs for the useful information and suggestions regarding PIX syslogging. Having had a slightly deeper read of the latest src tree, I'd like to just make a few suggestions and comments. Several of the options available have Default Settings in their relevant subsection of the HTML tree within: /usr/src/syslog-ng/syslog-ng-1.5.19/doc/sgml/syslog-ng.html However, several options don't have defaults listed therein. Perhaps the next round of documentation updates could double check that all defaults are fully listed in the html pages. The Main HTML Doc Pages at http://www.balabit.hu/static/syslog-ng/reference/book1.html contain no reference to recent dns_cache options - even though this option appears to have been available for about 18 months. As I think several others have mentioned on the list, it would seem reasonable for a more up to date copy of the html pages to be glued up onto the website. The syslog-ng man pages explicitly state that destinations are closed and re-opened on SIGHUP, as per dear-old syslogd's behaviour. There have been references on the mailing list and the FAQs to the corresponding close / re-open of sources, but no explicit statement in the docs. Could I request that an explicit statement of source file descriptor open/close behaviour on SIGHUP be added to the docs/FAQ, please. Others on the list have noted that closing /dev/log on HUP causes certain programs grief - notably sendmail which requires a further HUP to itself to properly heal the broken syslog file descriptor. If syslog-ng does indeed close descriptors on HUP, can we please have an option to explicitly keep certain descriptors open on HUP. ( The docs suggest this may already be possible for TCP sockets, and Unix SOCK_STREAM sockets, but not Unix SOCK_DGRAM sockets ). See ensuing paragraphs for why I'd like the option to be available on Unix SOCK_DGRAM. In all the syslog-ng docs, Linux platforms are documented as having a default log listener socket of /dev/log SOCK_STREAM. However, the most recent RedHat sysklogd RPMs open /dev/log in SOCK_DGRAM mode. I believe this was done as part of a security patch to avoid a potential DoS attack against the stream socket. To the best of my recollection, this behaviour changed about a year ago. This seems to bring RedHat - at least - in line with other BSD variants. glibc openlog() call on RedHat opens SOCK_DGRAM first, falling back to SOCK_STREAM if that fails. Hence RedHat's glibc still supports either socket type, and hence syslog-ng's documented Linux defaults still work. Likewise, Perl's Syslog.pm module calls SOCK_DGRAM first falling back to SOCK_STREAM. Sometime during the change from kernel 2.0 to 2.2 I believe, the Unix DGRAM socket type behaviour was adjusted to blocking ( this assumption purely based on the perceived behaviour of sysklogd ). Thus it should be impossible to drop a message across a Unix DGRAM socket , as compared with the ease of such a message being dropped across an UDP DGRAM socket when the system is really busy. Hence the change from SOCK_STREAM to SOCK_DGRAM within sysklogd should not make the system more prone to dropping locally logged messages, as might have been the case with earlier kernels? Given all of the above, is it reasonable to change the preferred documented socket type from STREAM to DGRAM on /dev/log for syslog-ng on Linux? "logger-ng" - I believe others may also have asked for this - does such a thing exist? to allow one to create test messages and the like over TCP etc etc etc. Sys::Syslog-NG.pm ?? does such a thing exist to support Perl Syslogging over TCP and suchlike? Ted Rule, Flextech Television *************************************************************************************************** This E-mail message, including any attachments, is intended only for the person or entity to which it is addressed, and may contain confidential information. If you are not the intended recipient, any review, retransmission, disclosure, copying, modification or other use of this E-mail message or attachments is strictly forbidden. If you have received this E-mail message in error, please contact the author and delete the message and any attachments from your computer. You are also advised that the views and opinions expressed in this E-mail message and any attachments are the author's own, and may not reflect the views and opinions of FLEXTECH Television Limited. ***************************************************************************************************

1 0

Please help fast...
by Keven Belanger 28 Aug '02

28 Aug '02

What is incorrect in this line ??? log { source(s_udp); destination(d_std); flags(fallback); }; Thanx... Kéven Belanger Analyste en solutions de sécurité Logicon Inc. - Division Sécurité 819.825.8049 x7717 800.567.6399 x7717

2 1

2 more question...please help
by Keven Belanger 27 Aug '02

27 Aug '02

Okay! We have 2 problems; 1- The hostname of the syslog receiver is SECU-Rcv1 and SECU-Rcv2 So with a destinations like destination: d_std { file("/export/disk1/log/$HOST/$YEAR/$MONTH/messages.log"); }; We receive the log in /export/disk1/log/SECU-Rcv2 on the local host why not the ip like other host ?? 2- We have 2 syslog collector and a big config file with each host (customer) defined line by line and a rule with unknown, the problem is that each host log correctly to the respective directory but they also log to my unknown directory, I want to be able to say, if no filter match, log to unknown... Thanx a lot! Kéven Belanger Analyste en solutions de sécurité Logicon Inc. - Division Sécurité 819.825.8049 x7717 800.567.6399 x7717

1 0

some questions
by Joerg Sommer 27 Aug '02

27 Aug '02

Hi, * What's the difference between long_hostnames() and use_fqdn()? * How get I names instead of ips in the logs? With use_dns()? How dangerouse is use of use_dns()? * Can I write a hostname instead of a ip in tcp()? * I miss the default values of the options in the docu. What's default for use_dns(), stats(),...? * When will encryption and authentication come? Joerg.

3 4