- syslog-ng - lists.balabit.hu

[Bug 102] New: Add system type "CYGWIN" to system() plugin
by bugzilla＠bugzilla.balabit.com 08 Dec '10

08 Dec '10

https://bugzilla.balabit.com/show_bug.cgi?id=102 Summary: Add system type "CYGWIN" to system() plugin Product: syslog-ng Version: 3.2.x Platform: PC OS/Version: Other Status: NEW Severity: normal Priority: unspecified Component: syslog-ng AssignedTo: bazsi(a)balabit.hu ReportedBy: vinschen(a)redhat.com Type of the Report: enhancement Estimated Hours: 0.0 The scl/system/generate-system-source.sh script driving the system() plugin does not recognize Cygwin. The attached patch adds Cygwin to the script so the system() plugin does the right thing. Corinna -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 2

Re: [syslog-ng] advice/assistance with parsing attempt requested
by syslog-ng2010＠hushmail.com 08 Dec '10

08 Dec '10

thanks for all the help ... in parser.py, i was using sys.stdin.readlines() which, i wound up changing to sys.stdin.xreadlines() to get the desired results. many thanks again! On Wed, 08 Dec 2010 16:50:37 +0100 Lars Kellogg-Stedman <lars(a)oddbit.com> wrote: >> >> the issue has me really stumped. how/why would the output from >perl >> make it to /opt/syslog-ng/logs/logfile in "real-time" yet, the >> output from python only make it to /opt/syslog-ng/logs/logfile >as a >> batch upon stopping the service!?!? >> > >This sort of thing typically happens because the program is using >buffered >IO, and output is only flushed when the buffer is full. If you >were to >leave things running for a while and generate a lot of log >traffic, you >would probably see the output show up periodically in large >chunks. > > This thread on Stackoverflow discusses a variety of solutions to >the >problem: > > http://stackoverflow.com/questions/107705/python-output- >buffering > >The simplest is probably to run Python with the "-u" flag (or >output to >stderr instead of stdout).

1 0

Re: [syslog-ng] advice/assistance with parsing attempt requested
by syslog-ng2010＠hushmail.com 08 Dec '10

08 Dec '10

MANY thanks for all of the great answers guys! as the pattern permutations would be less than desirable to maintain, i've gone ahead and given the program destination another attempt. this time leveraging python as opposed to perl (even though i too believe perl ought be able to handle the volume (roughly 300k per 5 minutes). i didn't write the original non- functional script and happen to favor python. by setting two destinations (one writing the raw stream to file and the other sending to a program which does parsing) i can see that this external parsing does indeed keep a one to one ratio! now, i'm now faced with a new challenge which for the life of me can't begin to get my head around ... original script had: destination d_parser { program("/opt/bin/perl /opt/syslog-ng/config/parser.pl >> /opt/syslog-ng/logs/logfile"); }; and, for what it was able to output (albeit anemic), worked fine. however ... current script has: destination d_parser { program("/opt/bin/python /opt/syslog-ng/config/parser.py >> /opt/syslog-ng/logs/logfile"); }; when i run "/opt/bin/python /opt/syslog-ng/config/parser.py" from the cmd line, and pipe input into it (i'm reading stdin); it runs as expected and the desired output is sent to screen/stdout when i start the syslog-ng service (which uses the conf file which in turn calls the python program in destination d_parser), unlike the perl script which does the same thing (print to screen/stdout) and does in fact add entries to /opt/syslog-ng/logs/logfile; no output is ever sent to the /opt/syslog-ng/logs/logfile ... UNTIL, i stop the syslog service and then, all the expected output comes flushing into /opt/syslog-ng/logs/logfile the issue has me really stumped. how/why would the output from perl make it to /opt/syslog-ng/logs/logfile in "real-time" yet, the output from python only make it to /opt/syslog-ng/logs/logfile as a batch upon stopping the service!?!? to clarify, i'm only sending to file currently to test, eventually this will be handed off to another syslog server via: destination d_logdevice { tcp("10.0.0.1" port(11235)); }; i hope this is something simple because as soon as i can get the output from the python like the perl, this project is almost done! lastly, this all being done with syslog-ng ose 3.1.1 thanks in advance! On Mon, 06 Dec 2010 21:01:37 +0100 Bill Anderson <Bill.Anderson(a)bodybuilding.com> wrote: >On Dec 6, 2010, at 12:37 PM, Martin Holste wrote: > >>> Agreed, Perl is plenty quick, hence my wondering about the >actual volume. If it is too much for Perl I'd go w/C++. >> >> From what I can tell, PCRE in Perl (or Python or whatever) is >really >> close to C/C++ speeds because they're essentially using the same >> library and therefore mostly the same syscalls. I'd be really >> interested if anyone has benchmarks. I'd expect something like >10% >> better performance in C, but not much more, assuming that the >vast >> majority of CPU time is spent on PCRE. > >Yeah I was thinking the overhead might be in what is done, as >opposed to just the RE portion. Of course, the OP script might be >implemented rather differently. ;) > > >> >>> Personally, I'd make the last step routing back into syslog-ng >with a source on a custom port and letting syslog handle the >writing to disk. That way you can still use macros such as >timestamps, etc.. Then again, that may be because I do that all >the time. ;) A log statement that takes everything from the custom >source and logs to a file should work beautifully; no need for >filters though you could still do additional processing if needed. >That said I'd also consider running a daemon that accepted all the >input, formatted it, and then sent it to syslog-ng, pointing the >clients at the custom daemon if that was possible. >>> >>> One advantage to the daemon route is that it wouldn't *have* to >reside on the same system. >> >> Yep, you could definitely let Syslog-NG handle the last mile as >well. >> I was trying to keep the scope as narrow as possible in my >example. >> >> I wonder if you could build an NFA state machine by >conditionally >> looping output from a pattern-db parsed message into a source in >> Syslog-NG with a different pattern-db, depending on the previous >> output. Something like a token parser pdb that does an ESTRING >up >> until " " and another one that only expects the key/val pair to >be >> sent to it as the message. So it comes in as k1=v1 k2=v2 and >the >> first kv gets gobbled up and then sent to another pdb source >with a >> pdb which only matches if the message starts with certain terms. > Then >> the rest of the original message is looped back to itself using >> @ANYSTRING@ to capture the remainder, that is, minus the kv >which was >> sent to the kv pdb. It would keep recursively looping like that >until >> there's no message left. If that all worked, your pattern db >would be >> extremely simple as it would just be a pattern per key you were >> looking for, and order would no longer be an issue. > >Maybe I'm nuts, but that sounds awesome to me. :D > >> Of course there's >> still the problem of demuxing the whole thing back into a >coherent >> message, but I think that could be done a number of ways by >passing >> the MSGID token with each part and using the new conditionals >present >> in OSE 3.2. > >Well, there is message correlation in 3.2.1 right? muahahaha > >> If OSE 3.3 can really do close to 1 million msgs/sec, >> then the overhead of resubmitting the same log many times may be >> bearable, especially with the threading. > >True the rate might be the downside to that mechanism. However, >the terseness of the messages might make up for some of it. > > >___________________________________________________________________ >___________ >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

3 2

[Bug 100] New: Hostnames that start with 4+ digits mess up the time system
by bugzilla＠bugzilla.balabit.com 08 Dec '10

08 Dec '10

https://bugzilla.balabit.com/show_bug.cgi?id=100 Summary: Hostnames that start with 4+ digits mess up the time system Product: syslog-ng Version: 2.0.x Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: unspecified Component: syslog-ng AssignedTo: bazsi(a)balabit.hu ReportedBy: D.Ojalvo(a)f5.com Type of the Report: --- Estimated Hours: 0.0 Created an attachment (id=26) --> (https://bugzilla.balabit.com/attachment.cgi?id=26) My patch proposal If syslog is handling a message with an rfc 3164-type timestamp then a hostname that begins with 4 digits, the time parser will mess up because it thinks that it is dealing with a linksys-style timestamp that includes the year, when the rfc3164 timestamp does not. I wrote a patch that adds a strict rfc3164 parsing option to the syslog startup. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 2

Re: [syslog-ng] [Bug 100] New: Hostnames that start with 4+ digits mess up the time system
by Patrick H. 08 Dec '10

08 Dec '10

Ahh, didnt know that was overridden. Thanks :-) -Patrick Sent: Tue Dec 07 2010 17:17:42 GMT-0700 (Mountain Standard Time) From: Daniel Ojalvo <D.Ojalvo(a)F5.com> To: Patrick H. <syslogng(a)feystorm.net>, Syslog-ng users' and developers' mailing list <syslog-ng(a)lists.balabit.hu> Subject: Re: [syslog-ng] [Bug 100] New: Hostnames that start with 4+ digits mess up the time system > > Yes, but that is superseded by rfc 1123. > http://tools.ietf.org/html/rfc1123#page-13 > > > > It's definitely an edge case though. I googled around for a while and > I found no other mentions of a bug like this. > > > > Daniel > > > > *From:* feystorm(a)q.com [mailto:feystorm@q.com] *On Behalf Of *Patrick H. > *Sent:* Tuesday, December 07, 2010 4:07 PM > *To:* Syslog-ng users' and developers' mailing list; Daniel Ojalvo > *Subject:* Re: [syslog-ng] [Bug 100] New: Hostnames that start with 4+ > digits mess up the time system > > > > Well to be fair, hostnames that start with a number are a violation of > RFC 952. > http://www.ietf.org/rfc/rfc952.txt > "The first character must be an alpha character" > > -Patrick > > > Sent: Tue Dec 07 2010 16:49:03 GMT-0700 (Mountain Standard Time) > From: bugzilla(a)bugzilla.balabit.com <mailto:bugzilla@bugzilla.balabit.com> > To: syslog-ng(a)lists.balabit.hu <mailto:syslog-ng@lists.balabit.hu> > Subject: [syslog-ng] [Bug 100] New: Hostnames that start with 4+ > digits mess up the time system > > https://bugzilla.balabit.com/show_bug.cgi?id=100 > > Summary: Hostnames that start with 4+ digits mess up the time > system > Product: syslog-ng > Version: 2.0.x > Platform: PC > OS/Version: Linux > Status: NEW > Severity: normal > Priority: unspecified > Component: syslog-ng > AssignedTo: bazsi(a)balabit.hu <mailto:bazsi@balabit.hu> > ReportedBy: D.Ojalvo(a)f5.com <mailto:D.Ojalvo@f5.com> > Type of the Report: --- > Estimated Hours: 0.0 > > > Created an attachment (id=26) > --> (https://bugzilla.balabit.com/attachment.cgi?id=26) > My patch proposal > > If syslog is handling a message with an rfc 3164-type timestamp then a hostname that begins with 4 digits, > the time parser will mess up because it thinks that it is dealing with a linksys-style timestamp that includes the year, > when the rfc3164 timestamp does not. I wrote a patch that adds a strict rfc3164 parsing option to the syslog startup. > > >

1 0

Support of welf format
by Yann I. 07 Dec '10

07 Dec '10

Hello, I would like to know whether syslog-ng can receive and manage logs which have the welf format ? Regards, Yann I.

3 2

Software for Analysing and Reporting Syslog Logs
by Heinze, René 07 Dec '10

07 Dec '10

Hello, I'm looking for a software to analyse and creating reports from syslog logs. It there anything you can recommend? Thanks, Best, René Heinze

3 2

Syslog-ng and Mysql Not working
by Girish-Agarwal (Contractor) 06 Dec '10

06 Dec '10

Hi, We are trying to setup syslog-ng to directly log messages to mysql but I get the following Error in the client messages file:- Dec 1 14:45:27 testbox syslog-ng[15637]: Error running SQL query; type='mysql', host='10.10.10.10', port='4406', user='syslog', database='testdb', error='1142: create command denied to user: \'syslog(a)10.20.30.40\' for table \'logs\'', query='CREATE TABLE logs (host text, facility text, priority text, tag text, datetime text, program text, server text, msg text)' Dec 1 14:45:27 testbox syslog-ng[15637]: Error checking table, disconnecting from database, trying again shortly; time_reopen='60' I am really confused as to why it is trying to create Table into the database. I already have the table created and I have verified successful connection from this box to the database server. It needs to insert the entries into the database and should not try to CREATE TABLE. I am using syslog-ng 3.0.6 version . Regards, Girish

3 10

Host name handling : FULLHOST_FROM explanation
by Christophe Brocas 06 Dec '10

06 Dec '10

Hello I am working on the right and consistent way to store log messages in destination files. I try to obtain a single file per host, based on HOST value in log messages.. Currently, I have inconsistent values in HOST part of log messages, so destination files are also inconsistents. To answer to this problem, I am going to use at first the SOURCEIP macro in my destination file paths. But I want to improve this situation. So I would like to be sure of the understanding I have of the FULLHOST_FROM macro. If use_dns() is set to yes, does the expansion of FULLHOST_FROM macro follow this stream ? 1. Syslog-NG takes the IP address of the host sending the message 2. Syslog-NG tries to get the reverse value (as dig -x) from the IP address 3. Syslog-NG expands the macro with the FQDN obtained in point 2 (What if DNS reverse fails ? The macro returns only the IP address ?) Bye Christophe -- Christophe Brocas keyid : 3072R/0x0661CBBA ***************************************************** "Le contenu de ce courriel et ses eventuelles pièces jointes sont confidentiels. Ils s'adressent exclusivement à la personne destinataire. Si cet envoi ne vous est pas destiné, ou si vous l'avez reçu par erreur, et afin de ne pas violer le secret des correspondances, vous ne devez pas le transmettre à d'autres personnes ni le reproduire. Merci de le renvoyer à l'émetteur et de le détruire. Attention : L'Organisme de l'émetteur du message ne pourra être tenu responsable de l'altération du présent courriel. Il appartient au destinataire de vérifier que les messages et pièces jointes reçus ne contiennent pas de virus. Les opinions contenues dans ce courriel et ses éventuelles pièces jointes sont celles de l'émetteur. Elles ne reflètent pas la position de l'Organisme sauf s'il en est disposé autrement dans le présent courriel." ******************************************************

2 3

[Bug 97] New: syslog-ng crashes after SIGHUP
by bugzilla＠bugzilla.balabit.com 04 Dec '10

04 Dec '10

https://bugzilla.balabit.com/show_bug.cgi?id=97 Summary: syslog-ng crashes after SIGHUP Product: syslog-ng Version: 3.0.x Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: unspecified Component: syslog-ng AssignedTo: bazsi(a)balabit.hu ReportedBy: zhengxiang.pan(a)alcatel-lucent.com Type of the Report: bug Estimated Hours: 0.0 Syslog-ng 3.0.6 crashes with following trace: Program terminated with signal 11, Segmentation fault. [New process 6311] #0 0x08063558 in log_source_group_queue (s=0x8ca6e00, msg=0x8caecc0, path_options=0xbfffaf18) at sgroup.c:98 98 (*self->processed_messages)++; (gdb) bt #0 0x08063558 in log_source_group_queue (s=0x8ca6e00, msg=0x8caecc0, path_options=0xbfffaf18) at sgroup.c:98 #1 0x08070580 in log_source_queue (s=0x8cadc78, msg=0x8caecc0, path_options=0xbfffaf74) at logpipe.h:121 #2 0x08063e80 in log_reader_fd_dispatch (source=0x8cadd10, callback=0, user_data=0x0) at logpipe.h:121 #3 0x08080081 in g_main_context_dispatch () #4 0x08083103 in g_main_context_iterate () #5 0x0808327f in g_main_context_iteration () #6 0x0804b52f in main_loop_run (cfg=0xbfffb0e8) at main.c:163 #7 0x0804bbcd in main (argc=147613904, argv=0xbfffb110) at main.c:443 The problem happens from version 3.0.6 ( I did not test other version lower than that) until the lastest 3.1.3. I guess what happens is that when SIGHUP is recevied, some connections are persisted, while the persistent connections points to the already-freed pipe (via pipe_next), if there are messages coming before the freed-pipes are replaced, the messages are forwarded to the freed-pipe handler. For version 3.1.3, in logpipe.c, log_pipe_forward_msg() may add check the pipe_next flags, however this may be not enough. log_pipe_forward_msg(LogPipe *self, LogMessage *msg, const LogPathOptions *path_options) { if (self->pipe_next && self->flags&PIF_INITIALIZED) { log_pipe_queue(self->pipe_next, msg, path_options); -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 5