Re: trouble forwarding fsl to syslog
On Wed, Apr 02, 2003, Martin Andrews wrote:
Dear Martin,
Finally working with fsl again. fsl-l2tool helped some, but a logger
type tool that actually read the fsl config would be great. [...]
I put this good idea on the wishlist.
Still
struggled with the fsl.postfix configuration. Syntax or other errors in
the fsl.postfix file caused postfix to dump core. Ug. Finally found that
this works: [...]
Skipping the target=remote would cause a core dump. Shouldn't that be
the default (only allowed) value? More importantly, moving the
target=remote attribute also causes bus errors - any idea why: [...]
The two examples you posted were identical (i assume by accident) and
they do not work. Here is a working configuration:
##
## fsl.postfix -- OSSP fsl configuration for Postfix
##
ident (postfix/.+)/.+ q{
prefix(
prefix=%b %d %H:%M:%S %N %L $1[%P]:
)
- {
debug: syslog(
facility=mail,
ident=postfix,
remotehost=127.0.0.1,
remoteport=514,
target=remote
)
}
};
As i explained in a previous posting, order of the parameters within the
syslog channel is important. This is a known issue (we) the OSSP l2 team
has to fix eventually. There is no default for the target option, it
must be set either local or remote.
--
[EMAIL PROTECTED]
Development Team, Operations Northern Europe, Cable Wireless
__
The OpenPKG Projectwww.openpkg.org
User Communication List [EMAIL PROTECTED]
Re: trouble forwarding fsl to syslog
On Thu, Apr 03, 2003, [EMAIL PROTECTED] wrote: On Wed, 2 Apr 2003, Martin Andrews wrote: struggled with the fsl.postfix configuration. Syntax or other errors in the fsl.postfix file caused postfix to dump core. Ug. [...] The fact that changes in the fsl or errors in configuring lead to core dumps lets me doubt if fsl is a good approach to the problem. In general I had several reports of people having problems with fsl which have been hard to track down. E.g. a program crashes because the log file is not writable etc. Besides my statements below regarding kolab disable fsl i want you to know that i was not able to crash postfix with syntatically or logically wrong fsl configs. I used postfix-2.0.2-1.2.1 with fsl-1.0.8-1.2.2 for testing. If you use these or later versions and find a configuration which crashes please tell me about it. Make sure you rebuild applications like postfix after an fsl upgrade - it's statically linked and won't change until after rebuild and reinstall the application. Additionally because of the static nature of OpenPKG it is not so easy to track down. It is as easy to find out if a program uses fsl and which version, even in a static configuration - see http://www.ossp.org/pkg/lib/fsl/faq.html#static-fsl In the kolab project we therefor decided to disable fsl everywhere. We are aware of this and i have an item on by TODO list to - check that really all packages using syslog(3) become fsl enabled - every use of fsl becomes an option which defaults to yes So in the near future you could easily inhibit fsl without having to hack every spec file. This decision was primarily driven by kolab. However, we still believe in fsl, even the current incarnation, and continue to support it. We are currently designing a major improvment of the underlying OSSP l2 library. This library is much more sophisticated than syslog(3) and the tradeoff is that the more complex code could more easily fail. This won't change because it can't. But we're working on a asynchronous channel which dedicates most of the logging to a different process, so crashes won't touch the main program anymore. If this work has been completed, fsl will inherit those improvments. It is our hope that kolab will finally come back on the fsl track in the future. We need the feedback of the community to improve the code. In general people are not used to crashes due to a non working logging setup. Taditionally if logging was not possible for whatever reason programs did continue to work. Agree, and that's what (we) the OSSP l2 team are working on. Thanks to this thread i improved and created - http://www.ossp.org/pkg/lib/fsl/faq.html#syslog-fsl - http://www.ossp.org/pkg/lib/fsl/faq.html#static-fsl Thank you for your feedback. -- [EMAIL PROTECTED] Development Team, Operations Northern Europe, Cable Wireless __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
Re: trouble forwarding fsl to syslog
Am Donnerstag, 3. April 2003 10:45 schrieb Thomas Lotterer: Hi Thomas, wrong fsl configs. I used postfix-2.0.2-1.2.1 with fsl-1.0.8-1.2.2 for testing. If you use these or later versions and find a configuration which crashes please tell me about it. We will retry our tests. which version, even in a static configuration - see http://www.ossp.org/pkg/lib/fsl/faq.html#static-fsl Thanks for the hint. So in the near future you could easily inhibit fsl without having to hack every spec file. This decision was primarily driven by kolab. This is very good news. has been completed, fsl will inherit those improvments. It is our hope that kolab will finally come back on the fsl track in the future. We need the feedback of the community to improve the code. If it serves our purposes I happily will go back to fsl. (We adopted fsl maybe a little too early and got burned..) Regards, -- martin Dipl.-Phys. Martin Konold e r f r a k o n Erlewein, Frank, Konold Partner - Beratende Ingenieure und Physiker Nobelstrasse 15, 70569 Stuttgart, Germany fon: 0711 67400963, fax: 0711 67400959 email: [EMAIL PROTECTED] __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
Re: trouble forwarding fsl to syslog
Martin,
here are examples that i have tested to work successfully.
Verify syslog.conf was prepared. The syslog.conf(5) wants to see tabs
not spaces, i marked the output manually to make that clear.
$ grep mail.info /etc/syslog.conf
mail.info\t\t\t/var/log/maillog
Check if syslog is usable using standard tool.
$ logger -p mail.info from logger
Check if l2 can use syslog locally.
$ echo from l2, loc | fsl-l2tool 'syslog(facility=mail, ident=info,
target=local)'
Check if l2 can use syslog remotly. Make sure syslogd accepts network
connections, see it's -s option for syslogd(8) on FreeBSD, -r option for
syslogd(8) on Linux or -t for syslogd(1M) on Solaris. Also note that the
l2spec requires a certain order of the remotehost, remoteport an target
keywords, see http://cvs.ossp.org/chngview?cn=3313.
$ echo from l2, net | fsl-l2tool 'syslog(facility=mail, ident=info,
remotehost=127.0.0.1, remoteport=514, target=remote)'
Now create a fsl config entry. This one is for openssh.
##
## fsl.openssh -- OSSP fsl configuration for openssh
##
ident (ssh(d|-.+)?|scp|sftp(-server)?)/.+ q{
prefix(
prefix=%b %d %H:%M:%S %N %L $1[%P]:
)
- {
debug: file(
path=/usr/opkg/var/openssh/sshd.log,
append=1, perm=0644
);
debug: syslog(
facility=mail, ident=info,
remotehost=127.0.0.1, remoteport=514, target=remote
)
}
};
#Note: do not put HASH comments inside a l2spec
--
[EMAIL PROTECTED]
Development Team, Operations Northern Europe, Cable Wireless
__
The OpenPKG Projectwww.openpkg.org
User Communication List [EMAIL PROTECTED]
Re: trouble forwarding fsl to syslog
On Wed, Mar 19, 2003, Thomas Lotterer wrote: I also want to point out that the OSSP l2 library comes with a nifty command line l2tool which allows a user to quickly try a l2spec. This is half the way towards fsl. Unfortunately the l2tool is not installed along OpenPKG fsl so you either have to hack the fsl.spec (item for my personal TODO list) [...] OK, fsl now installes the tool. To avoid naming conflicts with the l2 package the binary is installed as fsl-l2tool. ftp://ftp.openpkg.org/current/SRC/fsl-1.0.8-20030320.src.rpm ftp://ftp.openpkg.org/release/1.2/UPD/fsl-1.0.8-1.2.2.src.rpm ftp://ftp.openpkg.org/release/1.1/UPD/fsl-1.0.8-1.1.2.src.rpm Quick and dirty example: $ echo foo | /cw/bin/fsl-l2tool \ 'debug: prefix ( prefix=[%b %d %H:%M:%S] %L [%P] ) - fd(fd=1)' [Mar 10 17:06:01] info [12726]foo -- [EMAIL PROTECTED] Development Team, Operations Northern Europe, Cable Wireless __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
