INCLUDE not working for me :(
I have implemented the following version: syslog-ng -V syslog-ng 3.0.1 Revision: ssh+git://bazsi@git.balabit//var/scm/git/syslog-ng/syslog-ng-ose--mainline-- 3.0#master#93a342dae3a2b0cb15811d0c34ea7f58b3fba14e Compile-Date: Mar 13 2009 16:29:42 Enable-Threads: off Enable-Debug: on Enable-GProf: off Enable-Memtrace: off Enable-Sun-STREAMS: off Enable-Sun-Door: off Enable-IPv6: on Enable-Spoof-Source: on Enable-TCP-Wrapper: on Enable-SSL: on Enable-SQL: off Enable-Linux-Caps: off Enable-Pcre: off When I try to implement file inclusion, I get an error at the point where I include the file. I essentially cut the section out of the main syslog-ng.conf file, place it into a new file and replace the area cut in the main syslog-ng.conf file with: include "/etc/syslog-ng/syslog-ng-local.conf"; When I do this I get the following error on service start: service syslog-ng start Starting syslog-ng: syntax error in /etc/syslog-ng/syslog-ng.conf at line 114. [FAILED] Charles Jennings | Network Security Engineer "There is one safeguard known generally to the wise, which is an advantage and security to all, but especially to democracies as against despots. What is it? Distrust." Demosthenes (c 384-322 B.C.), Greek orator. Second Philippic, sct. 24 (344 B.C.)
On Fri, 2009-03-27 at 14:41 -0500, Charles Jennings wrote:
I have implemented the following version:
syslog-ng -V syslog-ng 3.0.1 Revision: ssh +git://bazsi@git.balabit//var/scm/git/syslog-ng/syslog-ng-ose--mainline--3.0#master#93a342dae3a2b0cb15811d0c34ea7f58b3fba14e Compile-Date: Mar 13 2009 16:29:42 Enable-Threads: off Enable-Debug: on Enable-GProf: off Enable-Memtrace: off Enable-Sun-STREAMS: off Enable-Sun-Door: off Enable-IPv6: on Enable-Spoof-Source: on Enable-TCP-Wrapper: on Enable-SSL: on Enable-SQL: off Enable-Linux-Caps: off Enable-Pcre: off
When I try to implement file inclusion, I get an error at the point where I include the file. I essentially cut the section out of the main syslog-ng.conf file, place it into a new file and replace the area cut in the main syslog-ng.conf file with:
include "/etc/syslog-ng/syslog-ng-local.conf";
When I do this I get the following error on service start:
service syslog-ng start Starting syslog-ng: syntax error in /etc/syslog-ng/syslog-ng.conf at line 114.
The 3.0.1 relase came out _before_ the include feature was added. Please use a nightly snapshot for the most recent version, or alternatively I've created a developer's snapshot when I released the new experimental binary packages. That has a version number 3.0.1+binpkg4, this is much newer than 3.0.1, although still somewhat older than a nightly snapshot would be and already contains the include feature. The only thing holding back a real 3.0.2 release, is that I have not really received feedback on the binary packages so far. And without some field testing I'd reluctant to call it a release. So if you have 30 minutes, please download the installer for one platform and tell me if it works for you. This means an immense contribution towards a 3.0.2 release. You can download the binary packages from: https://www.balabit.com/network-security/syslog-ng/opensource-logging-system... Thanks in advance. -- Bazsi
Didn't work for me :( # rpm -i syslog-ng-3.0.1+binpkg4-1.rhel5.i386.rpm warning: syslog-ng-3.0.1+binpkg4-1.rhel5.i386.rpm: Header V3 DSA signature: NOKEY, key ID 2aa28252 /var/tmp/rpm-tmp.51449: line 2: /etc/init.d/syslog: Permission denied Stopping syslog-ng: [ OK ] Starting syslog-ng: OK [root@syslog-svr RPMs]# syslog-ng -V syslog-ng 3.0.1 Revision: ssh+git://bazsi@git.balabit//var/scm/git/syslog-ng/syslog-ng-ose--mainline-- 3.0#master#93a342dae3a2b0cb15811d0c34ea7f58b3fba14e Compile-Date: Mar 13 2009 16:29:42 Enable-Threads: off Enable-Debug: on Enable-GProf: off Enable-Memtrace: off Enable-Sun-STREAMS: off Enable-Sun-Door: off Enable-IPv6: on Enable-Spoof-Source: on Enable-TCP-Wrapper: on Enable-SSL: on Enable-SQL: off Enable-Linux-Caps: off Enable-Pcre: off -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Balazs Scheidler Sent: Friday, March 27, 2009 2:50 PM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] INCLUDE not working for me :( On Fri, 2009-03-27 at 14:41 -0500, Charles Jennings wrote:
I have implemented the following version:
syslog-ng -V syslog-ng 3.0.1 Revision: ssh +git://bazsi@git.balabit//var/scm/git/syslog-ng/syslog-ng-ose--mainlin +e--3.0#master#93a342dae3a2b0cb15811d0c34ea7f58b3fba14e Compile-Date: Mar 13 2009 16:29:42 Enable-Threads: off Enable-Debug: on Enable-GProf: off Enable-Memtrace: off Enable-Sun-STREAMS: off Enable-Sun-Door: off Enable-IPv6: on Enable-Spoof-Source: on Enable-TCP-Wrapper: on Enable-SSL: on Enable-SQL: off Enable-Linux-Caps: off Enable-Pcre: off
When I try to implement file inclusion, I get an error at the point where I include the file. I essentially cut the section out of the main syslog-ng.conf file, place it into a new file and replace the area cut in the main syslog-ng.conf file with:
include "/etc/syslog-ng/syslog-ng-local.conf";
When I do this I get the following error on service start:
service syslog-ng start Starting syslog-ng: syntax error in /etc/syslog-ng/syslog-ng.conf at line 114.
The 3.0.1 relase came out _before_ the include feature was added. Please use a nightly snapshot for the most recent version, or alternatively I've created a developer's snapshot when I released the new experimental binary packages. That has a version number 3.0.1+binpkg4, this is much newer than 3.0.1, although still somewhat older than a nightly snapshot would be and already contains the include feature. The only thing holding back a real 3.0.2 release, is that I have not really received feedback on the binary packages so far. And without some field testing I'd reluctant to call it a release. So if you have 30 minutes, please download the installer for one platform and tell me if it works for you. This means an immense contribution towards a 3.0.2 release. You can download the binary packages from: https://www.balabit.com/network-security/syslog-ng/opensource-logging-system /upgrades Thanks in advance. -- Bazsi ____________________________________________________________________________ __ 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
On Mon, 2009-03-30 at 16:19 -0500, Charles Jennings wrote:
Didn't work for me :(
# rpm -i syslog-ng-3.0.1+binpkg4-1.rhel5.i386.rpm warning: syslog-ng-3.0.1+binpkg4-1.rhel5.i386.rpm: Header V3 DSA signature: NOKEY, key ID 2aa28252 /var/tmp/rpm-tmp.51449: line 2: /etc/init.d/syslog: Permission denied Stopping syslog-ng: [ OK ] Starting syslog-ng: OK [root@syslog-svr RPMs]# syslog-ng -V
Thanks. As it seems you don't have "x" right on /etc/init.d/syslog, is that right? Can you give me the output of $ ls -l /etc/init.d/syslog Thanks. -- Bazsi
Looks like I was mistaken. The install did work - but I just didn't realize it. (I had already chmod -x /etc/init.d/syslog when I installed compiled version) However, A couple of points to the installer: 1) Positive feedback needed. 2) Notify users that their existing configuration is migrated. (this one took a while to figure out) (Mine moved from /etc/syslog-ng/syslog-ng.conf to /opt/syslog-ng/etc/syslog-ng.conf) 3) Notify users that the init script is being modified. 4) Change init script to act like other RHEL5 scripts: Old: [OK] in green at certain column position Now: OK - no bracket, no green, located right after text. 5) Change path statement to reflect new executable location (mine was still looking at old executable) -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Balazs Scheidler Sent: Tuesday, March 31, 2009 5:19 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] INCLUDE not working for me :( On Mon, 2009-03-30 at 16:19 -0500, Charles Jennings wrote:
Didn't work for me :(
# rpm -i syslog-ng-3.0.1+binpkg4-1.rhel5.i386.rpm warning: syslog-ng-3.0.1+binpkg4-1.rhel5.i386.rpm: Header V3 DSA signature: NOKEY, key ID 2aa28252 /var/tmp/rpm-tmp.51449: line 2: /etc/init.d/syslog: Permission denied Stopping syslog-ng: [ OK ] Starting syslog-ng: OK [root@syslog-svr RPMs]# syslog-ng -V
Thanks. As it seems you don't have "x" right on /etc/init.d/syslog, is that right? Can you give me the output of $ ls -l /etc/init.d/syslog Thanks. -- Bazsi ____________________________________________________________________________ __ 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
Hi, Thanks for the feedback, it's really appreciated. On Tue, 2009-03-31 at 09:38 -0500, Charles Jennings wrote:
Looks like I was mistaken. The install did work - but I just didn't realize it. (I had already chmod -x /etc/init.d/syslog when I installed compiled version)
However, A couple of points to the installer:
1) Positive feedback needed.
There are multiple installers for syslog-ng right now, and the ".run" based installers (that can run on RHEL/SUSE/Debian) has positive feedback. My understanding of RPM based systems is that rpms are not usually interactive. On Debian, there's debconf and the installer uses that to ask for some installation options, but rpm has no similar feature. We could perhaps write messages to the console, but I don't see how we could make the RPM interactive without affecting the non-interactive installations.
2) Notify users that their existing configuration is migrated. (this one took a while to figure out) (Mine moved from /etc/syslog-ng/syslog-ng.conf to /opt/syslog-ng/etc/syslog-ng.conf) 3) Notify users that the init script is being modified.
Again, I think this can be solved by writing important notifications to the standard output.
4) Change init script to act like other RHEL5 scripts: Old: [OK] in green at certain column position Now: OK - no bracket, no green, located right after text.
We're using LSB based initscripts so that we can integrate with the systems better, however a lot of distributions have bugs in their LSB installations (such as RHEL5 and anything before that) so we're falling back to our own LSB implementation. But that is meant to be run on all systems, thus it is not completely the same as RHEL5. Anyway, I'll see if we can reuse at least parts of the local LSB implementation, such as printing the success/failure of the daemon startup.
5) Change path statement to reflect new executable location (mine was still looking at old executable)
This is difficult again. What path to modify, the system wide default, or the root's local settings. Is he using bash/ksh/zsh/tcsh. Each has a different startup script. That's why this is not implemented. The .run based installers displays a notification dialog that you need to change your PATH environment variable in order to use the new binaries from the shell prompt. But again, since the RPM is completely silent, this is not printed. Do you think it'd be enough to print this information? I'd be reluctant to break the user's profile script. Also, does the "include" file feature work for you after installation?
-- Bazsi
Thanks for your response. I am a medium-core (not hard-core) linux users so I don't know all the in's and out's. A stdout message just pointing to a README would suffice for me - stating to review for important changes... As to the include - yes - it is working just fine. Thanks. Regards, Charles Jennings -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Balazs Scheidler Sent: Wednesday, April 01, 2009 2:12 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] INCLUDE not working for me :( Hi, Thanks for the feedback, it's really appreciated. On Tue, 2009-03-31 at 09:38 -0500, Charles Jennings wrote:
Looks like I was mistaken. The install did work - but I just didn't realize it. (I had already chmod -x /etc/init.d/syslog when I installed compiled version)
However, A couple of points to the installer:
1) Positive feedback needed.
There are multiple installers for syslog-ng right now, and the ".run" based installers (that can run on RHEL/SUSE/Debian) has positive feedback. My understanding of RPM based systems is that rpms are not usually interactive. On Debian, there's debconf and the installer uses that to ask for some installation options, but rpm has no similar feature. We could perhaps write messages to the console, but I don't see how we could make the RPM interactive without affecting the non-interactive installations.
2) Notify users that their existing configuration is migrated. (this one took a while to figure out) (Mine moved from /etc/syslog-ng/syslog-ng.conf to /opt/syslog-ng/etc/syslog-ng.conf) 3) Notify users that the init script is being modified.
Again, I think this can be solved by writing important notifications to the standard output.
4) Change init script to act like other RHEL5 scripts: Old: [OK] in green at certain column position Now: OK - no bracket, no green, located right after text.
We're using LSB based initscripts so that we can integrate with the systems better, however a lot of distributions have bugs in their LSB installations (such as RHEL5 and anything before that) so we're falling back to our own LSB implementation. But that is meant to be run on all systems, thus it is not completely the same as RHEL5. Anyway, I'll see if we can reuse at least parts of the local LSB implementation, such as printing the success/failure of the daemon startup.
5) Change path statement to reflect new executable location (mine was still looking at old executable)
This is difficult again. What path to modify, the system wide default, or the root's local settings. Is he using bash/ksh/zsh/tcsh. Each has a different startup script. That's why this is not implemented. The .run based installers displays a notification dialog that you need to change your PATH environment variable in order to use the new binaries from the shell prompt. But again, since the RPM is completely silent, this is not printed. Do you think it'd be enough to print this information? I'd be reluctant to break the user's profile script. Also, does the "include" file feature work for you after installation?
-- Bazsi ____________________________________________________________________________ __ 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
participants (2)
-
Balazs Scheidler
-
Charles Jennings