- syslog-ng - lists.balabit.hu

remote wtmp logging
by paul.reilly＠tcd.ie 23 Jan '03

23 Jan '03

Does syslog-ng support enable remote wtmp logging? If so, with pipe or file or how? Thanks Paul

1 0

syslog-ng 1.9.1 released
by Balazs Scheidler 23 Jan '03

23 Jan '03

Hi, I have released syslog-ng 1.9.1 which is the first member of the 1.9.x branch. In this branch syslog-ng is reimplemented from scratch. Documentation is even more scarce than for syslog-ng 1.5.x so it is recommended to experienced users only. The program itself is in ALPHA state which means that it runs seems to work but almost certainly leaks memory. You can fetch this version by pointing your browser to http://www.balabit.hu/en/downloads/syslog-ng/downloads/ Backward compatibility was kept where possible, but some minor incompatibilies might be possible. Here is the NEWS entry for the never-released 1.9.0 and 1.9.1 which contains a summary of the new features present in this release. Feedback is appreciated. News for the 1.9.1 release Wed, 22 Jan 2003 12:13:44 +0100 This release is still not intended for production use. It has a good number of new features and a couple of them may not be stable enough. New features: * template declarations, the possibility to define a template once and refer to it * flow controlled log paths work, and they are also configurable * supports RFC3339 timestamps with second fractions and time zones, time zone conversion & source time zone specification * MARK messages are generated * keep alive for connections as well as listeners * the ability to follow log files as they are written to * the possibility to mark parts of a message using standard '(' and ')' regexp operators and refer to matches within templates (either filenames or content) This program is still ALPHA. News for the 1.9.0 release Thu, 9 May 2002 20:01:11 +0200 This release is the first release of the new reimplementation of syslog-ng. I moved to using glib instead of libol, as glib is more mature and provides several nice & easy to use features. Here's a bunch of nice things about 1.9.0: * supports flow controlled log paths (still not possible to configure it, but the code exists in the core) * better support for macros (macro support is moved out of affile, thus any other drivers may use it) * more robust detection of closed destination sockets (a closed channel is immediately detected, not at the first write) This avoids losing a log message when the connection is broken. * supports respawning destination programs (should be used with care to avoid DoS situations). This makes it easier to integrate third party extensions to syslog-ng. (SQL backends, on-line log analysis etc) * performance improvements, instead of using linear lookup in linked lists, I use hashtables everywhere. * the ability to define unparsed sources, makes it easier to integrate things like Apache logs * many internal reorganizations to make it easier to implement things like hashed log files, SSL protected TCP sessions and so on. Things still missing: * there are some new features with no configuration interface * internal messages always go to /dev/stderr * Sun's STREAMS is not yet supported 1.9.0 is currently in an ALPHA state, it's been tested only on my development computer, and not real-life traffic. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1

3 3

doesn't write to file after logrotate
by Markus Schabel 23 Jan '03

23 Jan '03

Hello! I've configured some destinations (e.g. /var/log/syslog, /var/log/cron.log, /var/log/dhcp.log) - all the same. Then I've configured logrotate to rotate all these logs and automatically create a new one after rotating. The syslog-ng and logrotate-configurations for these files are exactly the same (just the filters are different), and it works fine for all except /var/log/dhcp.log. After it is rotated, syslog-ng doesn't write to it anymore, for the other log's it does. If I restart syslog-ng, it starts logging to /var/log/dhcp.log again. Always restarting syslog-ng after rotating dhcp.log isn't really a solution, are there any hints what I can do to solve this problem? regards Markus Schabel +--------------------------------------------+ | TGM - Die Schule der Technik, IT-Service | | A-1200 Wien, Wexstrasse 19-23 | | Tel.: +43(1)33126/316 Fax: +43(1)33126/154 | | eMail: markus.schabel(a)tgm.ac.at | | markus.schabel(a)member.fsf.org | | FSF Associate Member #597 | | Linux User #259595 (http://counter.li.org) | +--------------------------------------------+ Computers are like airconditioners: They stop working properly if you open windows.

1 0

REPLY NEEDEDS_URGENT
by PATRICK KOFI 23 Jan '03

23 Jan '03

ASSISTANCE WE ARE MEMBERS OF A SPECIAL COMMITTEE FOR BUDGET AND PLANNING OF THE NIGERIA NATIONAL PETROLEUM CORPORATION (NNPC)IN WEST AFRICA. THIS COMMITTEE IS PRINCIPALLY CONCERNED WITH CONTRACT AWARDS AND APPROVAL. WITH OUR POSITIONS, WE HAVE SUCCESSFULLY SECURED FOR OURSELVES THE SUM OF THIRTHY ONE MILLION, FIVE HUNDRED THOUSAND UNITED STATES DOLLARS (US$31.5M). THIS AMOUNT WAS CAREFULLY MANIPULATED BY OVER-INVOICING OF AN OLD CONTRACT. BASED ON INFORMATION GATHERED ABOUT YOU, WE BELIEVE YOU WOULD BE IN A POSITION TO HELP US IN TRANSFERING THIS FUND (US$31.5M) INTO A SAFE ACCOUNT. IT HAS BEEN AGREED THAT THE OWNER OF THE ACCOUNT WILL BE COMPENSATED WITH 30% OF THE REMITTED FUNDS, WHILE WE KEEP 60% AS THE INITIATORS AND 10% WILL BE SET ASIDE TO OFFSET EXPENSES AND PAY THE NECESSARY TAXES.WE INTEND TO USE PART OF OUR OWN SHARE TO IMPORT FROM YOUR COUNTRY AGRICULTURAL AND CONSTRUCTION MACHINERY. THIS IS BECAUSE THE PRESENT GOVERNMENT OF MY COUNTRY IS EMPHASISING ON PROVIDING FOOD AND HOUSING FOR ALL ITS CITIZENS BEFORE THE NEXT ELECTION. HENCE, AGRICULTURAL AND CONSTRUCTION EQUIPMENT ARE IN HIGH DEMAND OVER HERE. WE SHALL ALSO NEED YOUR ASSISTANCE IN THIS REGARD ON A COMMISSION TO BE AGREED UPON WHEN WE FINALLY MEET. ALL MODALITIES OF THIS TRANSACTION HAVE BEEN CAREFULLY WORKED OUT AND ONCE STARTED WILL NOT TAKE MORE THAN SEVEN (7) WORKING DAYS, WITH YOUR FULL SUPPORT. THIS TRANSACTION IS 100% RISK FREE. MOREOVER, WE SHALL NEED THE FOLLOWING FROM YOU TO ENABLE US BEGIN THE TRANSACTION FORMALLY. THEY ARE; YOUR FULL NAME AND ADDRESS OR YOUR COMPANY NAME, ADDRESS AND TELEPHONE/FAX NUMBERS, YOUR BANKERS NAME AND ADDRESS, YOUR ACCOUNT NUMBER AND NAME. THIS INFORMATION WILL BE USED ALONGSIDE OTHER VITAL DOCUMENTS OVER HERE IN PREPARING THE NECESSARY APPLICATION FOR PAYMENT TO THE CONCERNED QUARTERS WHERE PAYMENT APPROVALS WOULD BE SECURED IN FAVOUR OF YOUR COMPANY FOR THE PAYMENT OF OUR FUND(US$31.5M) INTO YOUR NOMINATED ACCOUNT FOR US ALL. BY OUR APPLICATION, IT WILL BE ASSUMED THAT THIS SUM IS BEING REQUESTED AS PAYMENT, WHICH IS LONG-OUTSTANDING, FOR A CONTRACT, WE SHALL CLAIM WITH OUR POSITION, YOU OR YOUR COMPANY EXECUTED FOR (NNPC) SOMETIME IN 1997. HENCE, WE SHALL FOLLOW ALL THE LEGAL OFFICIAL PROTOCOLS USUALLY OBSERVED BY FOREIGN CONTRACTORS WHENEVER THEY ARE DEMANDING PAYMENT FOR CONTRACTS EXECUTED FOR THE GOVERNMENT OF MY COUNTRY. FURTHERMORE, IMMEDIATELY THE FINAL APPROVAL IS GRANTED, THE FUND WILL BE TRANSFERRED INTO YOUR ACCOUNT WITHIN 72 HOURS, BY WHICH TIME MY PARTNERS AND I WILL BE IN YOUR COUNTRY FOR THE FINAL DISBURSEMENT IN THE RATIO ALREADY SPELT OUT TO YOU. PLEASE, YOU SHOULD ENDEAVOUR TO GIVE US AN ACCOUNT WHICH YOU HAVE ABSOLUTE CONTROL OVER. THIS IS VERY IMPORTANT BECAUSE WE WOULD NOT WANT A SITUATION WHEN THE MONEY IS IN THE ACCOUNT, YOU NOW TELL US YOU WOULD NEED TO BE AUTHORISED BY ANOTHER PERSON BEFORE WE CAN HAVE OUR OWN SHARE. YOU WILL NOT BE REQUIRED TO TRAVEL OUT OF YOUR COUNTRY, ME AND MY PARTNERS, WE TRAVEL DOWN TO YOUR COUNTRY FOR THE DISBURSEMENT OF THE FUND, AFTER THE FINAL TRANSACTION. WE WILL ALSO DISCUSS ABOUT OIL BUSINEES IN MY COUNTRY WHEN WE COME DOWN OVER THERE. BECAUSE WE WOULD LIKE TO ESTABLISH A JOINT BUSINESS WITH YOU. THAT IS WE WILL USE YOUR NAME TO REGISTER AND INCORPORATE AN OIL COMPANY IN MY COUNTRY. BESIDES, ON THE COMPLETION OF THIS TRANSFER, ALL DOCUMENTS USED FOR THE PURPOSE WILL BE WITHDRAWN FROM THE QUARTERS THEY ARE SUBMITTED BY OUR CONTACTS IN THESE OFFICES AND DESTROYED, THEREAFTER. SO, THERE WILL NOT BE ANY PROBLEM ARISING FROM THIS TRANSACTION NOW OR IN THE FUTURE. IF THIS PROPOSAL SATISFIES YOU, PLEASE REACH US ONLY BY EMAIL FOR MORE INFORMATION. PLEASE, TREAT AS URGENT AND VERY IMPORTANT. YOURS FAITHFULLY, DR.PATRICK KOFI.

1 0

RE: [syslog-ng]does syslog-ng conflict with syslogd? how avoid
by Hamilton, Andrew 22 Jan '03

22 Jan '03

Yes it will do that transparently. There is a lot of help here: http://www.campin.net/syslog-ng/faq.html Regards, Drew -----Original Message----- From: seberino(a)spawar.navy.mil [mailto:seberino@spawar.navy.mil] Sent: Wednesday, January 22, 2003 3:10 PM To: syslog-ng(a)lists.balabit.hu Subject: [syslog-ng]does syslog-ng conflict with syslogd? how avoid I just installed syslog-ng. If I kill syslogd and start the syslog-ng daemon will it capture messages from apps trying to talk to syslogd transparently??? So to avoid conflicts and compatibility problems I just have to kill syslogd and swap in the new daemon??? That would be great if so.... then if I could get syslog-ng.conf done right I'm in business!! Chris -- _______________________________________ Dr. Christian Seberino SPAWAR Systems Center San Diego Code 2363 49590 Lassing Road, Room A339 San Diego, CA 92152-6147 U.S.A. Phone: (619) 553-7940 Fax: (619) 553-1269 Email: seberino(a)spawar.navy.mil _______________________________________ _______________________________________________ syslog-ng maillist - syslog-ng(a)lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html

1 0

does syslog-ng conflict with syslogd? how avoid
by seberino＠spawar.navy.mil 22 Jan '03

22 Jan '03

I just installed syslog-ng. If I kill syslogd and start the syslog-ng daemon will it capture messages from apps trying to talk to syslogd transparently??? So to avoid conflicts and compatibility problems I just have to kill syslogd and swap in the new daemon??? That would be great if so.... then if I could get syslog-ng.conf done right I'm in business!! Chris -- _______________________________________ Dr. Christian Seberino SPAWAR Systems Center San Diego Code 2363 49590 Lassing Road, Room A339 San Diego, CA 92152-6147 U.S.A. Phone: (619) 553-7940 Fax: (619) 553-1269 Email: seberino(a)spawar.navy.mil _______________________________________

1 0

Where docs for syslog-ng.conf installation and remote logging??
by seberino＠spawar.navy.mil 22 Jan '03

22 Jan '03

I looked thru README and INSTALL files and table of contents for syslog-ng big doc. I cannot find anything on installing the /etc/syslog-ng.conf. I assume one must make their own and just put the file there themselves??? Can I just use my old syslog.conf as is??? Where are docs for setting up secure (ssh) remote logging??? Chris -- _______________________________________ Dr. Christian Seberino SPAWAR Systems Center San Diego Code 2363 49590 Lassing Road, Room A339 San Diego, CA 92152-6147 U.S.A. Phone: (619) 553-7940 Fax: (619) 553-1269 Email: seberino(a)spawar.navy.mil _______________________________________

1 0

1.5.24 hangs, Red Hat Linux 7.1 2.96-98
by Greg Hartung 22 Jan '03

22 Jan '03

I upgraded from 1.4.14 to 1.5.24 because I needed support for named pipes. Now the daemon hangs every few hours or so (with or without the use of pipes). All the output files (about 90 devices) have the same last timestamp. It happens a dozen or more times a day with no obvious pattern in the timing. Does seem to be proportional to volume (doesn't hang overnight). The output actually stops mid-message. Many of the files are 2GB or more. kill -HUP or syslog-ng restart seems to clear the problem up (continues writing to the same large files). syslog-ng conf file is about 10k with about 20 filter/log/destination combo's. Any ideas? If you want to see the config, let me know, I just didn't want to clutter the list... Thanks, Greg

3 2

Embarrassing newbie question
by rich coco 22 Jan '03

22 Jan '03

I have installed syslog-ng on two RedHat PCs (7.0 and 8.0). I first stopped syslogd/klogd. ran "syslog-ng -s" to verify that the syntax of my cfg file was ok and then ran syslog-ng. I even ran syslog-ng in debug mode, in the foreground. it spews a bunch of output to stdout as it parses the cfg file (i believe), but then gets silent afterwards...even as I run logger(1). Nothing ever appears in any log file! same result on both systems, so i have to assume it is something silly I am not doing right. Here is my painfully simple cfg file: source src { pipe("/proc/kmsg"); unix-stream("/dev/log"); internal(); }; destination messages { file("/var/log/messages"); }; # Log anything of level debug or higher. filter f_messages { level(debug); }; log { source(src); filter(f_messages); destination(messages); }; i tried testing this by running logger(1), which I understand writes output to /dev/log. Nothing ever appears in /var/log/messages. In fact, no files in /var/log *ever* get written. Well, actually, i am leaving something out...and it is very strange but probably a key clue: when i shutdown syslog-ng and restart syslogd/klogd, I *do* get output in /var/log/messages. A bunch of lines announcing the startup of syslogd/klogd and, at *after* those entries, a single line announcing the shutdown of syslog-ng (the *only* output I *ever* get from syslog-ng): Jan 21 21:08:48 ape syslog: syslogd startup succeeded Jan 21 21:08:48 ape kernel: klogd 1.3-3, log source = /proc/kmsg started. Jan 21 21:08:48 ape kernel: Inspecting /boot/System.map-2.2.19-7.0.1 Jan 21 21:08:48 ape syslog: klogd startup succeeded Jan 21 21:08:48 ape kernel: Loaded 7296 symbols from /boot/System.map-2.2.19-7.0.1. Jan 21 21:08:48 ape kernel: Symbols match kernel version 2.2.19. Jan 21 21:08:48 ape kernel: Loaded 409 symbols from 12 modules. Jan 21 21:08:26 ape syslog-ng: syslog-ng shutdown succeeded Notice that the timestamp of the last line is 22 seconds EARLIER THAN the timestamp of the preceeding line! No doubt 22 seconds passed between the time I stopped syslog-ng and restarted syslogd/klogd. But how/why did the syslog-ng appear *after* the syslogd/klogd startup announcements? Some strange buffering of syslog-ng output? Why isn't syslog-ng monitoring /dev/log as I asked it to? Did I ask it incorrectly? Is it writing output to somewhere I cannot see? HELP! this is making me nuts!!!

2 1

Suggestions/enhancements miscellany
by Ted_Rule＠flextech.co.uk 22 Jan '03

22 Jan '03

Whilst at least some of the following has been mentioned before, I'd like to make a another little plea for some extra features and tidyups to syslog-ng and its associated documentation. a) SIGHUP/keep-listening feature request The current version supports the keepalive stream socket feature for both TCP and Unix-Stream which means that existing connections are kept open across a SIGHUP/reconfig. This is all well and good, and provides sufficient functionality to avoid losing a Stream Source Socket message. However, for UDP sockets, I believe the socket is closed/re-opened on SIGHUP, which thereby has the potential for loss of messages across a SIGHUP. Unix syslog client boxes in general could in theory all be reconfigured to use syslog-ng and hence use TCP, and hence avoid message drops on a central syslog server, but most embedded devices such as Cisco routers, HP printers, etc etc, can only use UDP. Hence the request to provide the "enhanced Frasier" option, as in "I'm still listening" for both types of datagram socket. I would suggest calling this option "keep-listening()". I'm well aware this may be tricky to code, but given the large population of UDP only devices, I would have thought many people would like to see it implemented. I did have a brief attempt to try and follow enough of the code layout to work out how and where it might be glued into place - but this bear of little brain got somewhat too confused to take it further. b) SIGUSR1/logrotate feature. To avoid losing UDP messages, one extra trick might be to include another signal - say SIGUSR1 - which is used merely to close all open destinations. This would be used for log rotation - I'm assuming there would never be a requirement to add open() code to this as well, as any required destination should be simply opened on demand. At present, SIGHUP is used to ensure destination closure for log rotation purposes, but this has the side-effect of closing sources, and hence potentially losing UDP messages. Adding SIGUSR1 would avoid any loss of messages during the overnight rotation, although there is obviously still the potential for message loss during any other required SIGHUP/reconfiguration without the keep-listening() feature. c) --checkconf option Once a new syslog-ng.conf has been built, it may be dangerous to SIGHUP it into life; a simple spelling error or a missed semi-colon could in theory lead to death of the running daemon, I believe. In mimicry of bind9's named-checkconf utility, can we have an extra command-line option to syslog-ng which merely checks for all potential syntactical errors in syslog-ng.conf returning non-zero error code and messaging stderr with any syntax errors thus found. I suggest "--checkconf" for the command line option name. Using this, a general init script wrapper might contain: syslog-ng.conf --checkconf && kill -HUP `cat /var/run/syslog-ng.pid` to avoid sending a signal if the configuration check fails. This option is also probably dependent on making the SIGUSR1 option available, elsewise a broken configuration file may lead to loss of log rotation. d) Default options settings documentation. This page in the current copy of the documentation: http://www.balabit.hu/static/syslog-ng/reference/x564.html would benefit greatly from a rewrite showing the default setting as an extra column for each option. Some options have their defaults listed here, but most do not. e) Working examples of regex usage. There are very few of the example configurations I have seen which show specific examples of the regex matching capabilities of the filter() functions. If anyone has some samples perhaps some more examples could be added to either the FAQ or the Documentation or both, please? Ted ************************************************************************************************ 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. ************************************************************************************************

2 1