Hi, I have tried syslog-ng versions 1.5.18 and 1.5.21 with the same problem. My system is:
uname -a Linux atlas 2.4.19 #1 Tue Aug 6 01:59:40 CEST 2002 i586 unknown
syslog-ng.conf: source src { internal(); }; destination syslog { file("/var/log/syslog.log"); }; log { source(src); destination(syslog); }; I can't see any internal messages in /var/log/syslog.log file tcp, udp and unix-streams works fine, only problem is with internal. Any help would be apreciated. Regards, Carlos Velasco
It works if I send a HUP signal to daemon AFTER launching: kill -HUP 22765 Oct 2 12:01:49 src@atlas syslog-ng[22765]: new configuration initialized Oct 2 12:02:18 src@atlas syslog-ng[22765]: syslog-ng version 1.5.18 going down bug? Regards, Carlos Velasco *********** REPLY SEPARATOR *********** On 02/10/2002 at 11:54 Carlos Velasco wrote:
Hi,
I have tried syslog-ng versions 1.5.18 and 1.5.21 with the same problem.
My system is:
uname -a Linux atlas 2.4.19 #1 Tue Aug 6 01:59:40 CEST 2002 i586 unknown
syslog-ng.conf: source src { internal(); }; destination syslog { file("/var/log/syslog.log"); }; log { source(src); destination(syslog); };
I can't see any internal messages in /var/log/syslog.log file tcp, udp and unix-streams works fine, only problem is with internal.
Any help would be apreciated.
Regards, Carlos Velasco
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
On Wed, Oct 02, 2002 at 12:04:35PM +0200, Carlos Velasco wrote:
It works if I send a HUP signal to daemon AFTER launching:
kill -HUP 22765
Oct 2 12:01:49 src@atlas syslog-ng[22765]: new configuration initialized Oct 2 12:02:18 src@atlas syslog-ng[22765]: syslog-ng version 1.5.18 going down
internal() messages are generated by syslog-ng itself. If you want kernel logs, you need to do it differently. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
Hi Bazsi,
internal() messages are generated by syslog-ng itself. If you want kernel logs, you need to do it differently.
Yes, no INTERNAL messages are logged until I do a kill -HUP to syslog.ng process, after that then I can see them:
kill -HUP 22765
Oct 2 12:01:49 src@atlas syslog-ng[22765]: new configuration initialized
kill 22765
Oct 2 12:02:18 src@atlas syslog-ng[22765]: syslog-ng version 1.5.18 going down
I can grant you a root account in this machine if you want to pursue this issue. Regards, Carlos Velasco *********** REPLY SEPARATOR *********** On 02/10/2002 at 12:26 Balazs Scheidler wrote:
On Wed, Oct 02, 2002 at 12:04:35PM +0200, Carlos Velasco wrote:
It works if I send a HUP signal to daemon AFTER launching:
kill -HUP 22765
Oct 2 12:01:49 src@atlas syslog-ng[22765]: new configuration initialized Oct 2 12:02:18 src@atlas syslog-ng[22765]: syslog-ng version 1.5.18 going down
internal() messages are generated by syslog-ng itself. If you want kernel logs, you need to do it differently.
-- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
On Wed, Oct 02, 2002 at 12:37:28PM +0200, Carlos Velasco wrote:
Hi Bazsi,
internal() messages are generated by syslog-ng itself. If you want kernel logs, you need to do it differently.
Yes, no INTERNAL messages are logged until I do a kill -HUP to syslog.ng process, after that then I can see them:
IIRC the startup messages are missing since 1.5.something (they go to /dev/null to avoid sending messages to an uninitialized configuration.) I might look into this, once I have some time. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
Hi Bazsi,
IIRC the startup messages are missing since 1.5.something (they go to /dev/null to avoid sending messages to an uninitialized configuration.)
Well, actually not only the startup message, if I don't do the kill -HUP I don't see any messages from internal.
I might look into this, once I have some time.
Good, I will try to do it too. Regards, Carlos Velasco
Hi Bazsi, I think this is the right patch for this problem: root@atlas:/home/ftp/compile > diff -u syslog-ng-1.5.21/src/main.c main.c --- syslog-ng-1.5.21/src/main.c Wed Sep 4 16:52:25 2002 +++ main.c Fri Oct 4 11:48:20 2002 @@ -494,6 +494,7 @@ } if (!debug_flag) { + set_internal_cfg(backend->configuration); set_error_internal(); } else { Regards, Carlos Velasco *********** REPLY SEPARATOR *********** On 02/10/2002 at 12:51 Carlos Velasco wrote:
Hi Bazsi,
IIRC the startup messages are missing since 1.5.something (they go to /dev/null to avoid sending messages to an uninitialized configuration.)
Well, actually not only the startup message, if I don't do the kill -HUP I don't see any messages from internal.
I might look into this, once I have some time.
Good, I will try to do it too.
Regards, Carlos Velasco
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
On Fri, Oct 04, 2002 at 11:55:33AM +0200, Carlos Velasco wrote:
Hi Bazsi,
I think this is the right patch for this problem:
root@atlas:/home/ftp/compile > diff -u syslog-ng-1.5.21/src/main.c main.c --- syslog-ng-1.5.21/src/main.c Wed Sep 4 16:52:25 2002 +++ main.c Fri Oct 4 11:48:20 2002 @@ -494,6 +494,7 @@ }
if (!debug_flag) { + set_internal_cfg(backend->configuration); set_error_internal(); } else {
Thanks. as this seems to be right, I added it to my CVS tree. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
participants (2)
-
Balazs Scheidler
-
Carlos Velasco