Re: [syslog-ng]1.4.11 fixes SIGHUP problems?
I'm not sure thats a bug, it may be a feature actually. If you look at /var/log/messages, theres an entry saying the new config is bad, and syslog-ng will continue running with the old config. This prevents lost syslog messages. John Delisle Corporate Technology Ceridian Canada Ltd 204-975-5909 jon@dumbo.pobox.com Sent by: To: syslog-ng@lists.balabit.hu syslog-ng-admin@lists. cc: balabit.hu Subject: Re: [syslog-ng]1.4.11 fixes SIGHUP problems? 2001/03/12 11:21 AM Please respond to syslog-ng i noticed one problem. if the configuration file is broken to the point syslog-ng will not start, HUP does not notice this ie. if you forget a semicolon somewhere kill -HUP syslog-ng-pid works w/o erros but kill syslog-ng-pid and syslog-ng dies... y On Fri, Mar 09, 2001 at 10:01:08AM +0100, Balazs Scheidler wrote: | Hi, | | I was wondering whether the 1.4.11 release did really fix the SIGHUP | problems many of you encountered? Some feedback would be useful. | | TIA, | -- | 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 _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng
IMO, it should dump to STDOUT/ERR as well...much like apachectl restart. apache says something like "config is broken, ignoring restart" i've made changes to the config file before(with errors) never thinking there's a problem. logging continued normally, not error messages i could see. not many people will want to have to check a log file after a restart, they may think "telling it to HUP, didn't report any errors, and my other logs are still there..." On Mon, Mar 12, 2001 at 11:33:35AM -0600, John_Delisle@ceridian.ca wrote: | | | I'm not sure thats a bug, it may be a feature actually. If you look at | /var/log/messages, theres an entry saying the new config is bad, and | syslog-ng will continue running with the old config. This prevents lost | syslog messages.
On Mon, Mar 12, 2001 at 12:47:33PM -0500, jon@dumbo.pobox.com wrote:
IMO, it should dump to STDOUT/ERR as well...much like apachectl restart.
apache says something like "config is broken, ignoring restart"
i've made changes to the config file before(with errors) never thinking there's a problem. logging continued normally, not error messages i could see.
I'm afraid I agree totally with this... I've done the same thing.
not many people will want to have to check a log file after a restart, they may think "telling it to HUP, didn't report any errors, and my other logs are still there..."
On Mon, Mar 12, 2001 at 11:33:35AM -0600, John_Delisle@ceridian.ca wrote: | | | I'm not sure thats a bug, it may be a feature actually. If you look at | /var/log/messages, theres an entry saying the new config is bad, and | syslog-ng will continue running with the old config. This prevents lost | syslog messages.
On Mon, Mar 12, 2001 at 12:49:40PM -0500, William Yodlowsky wrote:
On Mon, Mar 12, 2001 at 12:47:33PM -0500, jon@dumbo.pobox.com wrote:
IMO, it should dump to STDOUT/ERR as well...much like apachectl restart.
apache says something like "config is broken, ignoring restart"
i've made changes to the config file before(with errors) never thinking there's a problem. logging continued normally, not error messages i could see.
I'm afraid I agree totally with this... I've done the same thing.
You could tell me a clue _where_ I could write this message? syslog-ng is running in the background with no stderr or stdout. It has nothing to write to except for its logfiles. As I see Apache has a configtest mode which is ran prior to sending a signal to the daemon, and although this can be done with syslog-ng as well, the configuration can be broken even if it's syntactically correct. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
Balazs Scheidler on Mon 12/03 18:57 +0100:
I'm afraid I agree totally with this... I've done the same thing.
You could tell me a clue _where_ I could write this message? syslog-ng is running in the background with no stderr or stdout. It has nothing to write to except for its logfiles.
Can't you just write it to the internal source ?
On Mon, Mar 12, 2001 at 01:03:31PM -0500, Scott McDermott wrote:
Balazs Scheidler on Mon 12/03 18:57 +0100:
I'm afraid I agree totally with this... I've done the same thing.
You could tell me a clue _where_ I could write this message? syslog-ng is running in the background with no stderr or stdout. It has nothing to write to except for its logfiles.
Can't you just write it to the internal source ?
I _write_ it there, that's why it pops up in logs. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
Balazs Scheidler on Mon 12/03 19:07 +0100:
Can't you just write it to the internal source ?
I _write_ it there, that's why it pops up in logs.
Then there's nothing more that can be done :) Person in question will just have to maintain a regex watcher on the logs for failures. Since syslog-ng closes all its terminal-inherited FDs, forks and sets SID, I don't see where else it would go...I mean you could write it to /dev/console but that's icky.
Balazs Scheidler wrote:
You could tell me a clue _where_ I could write this message? syslog-ng is running in the background with no stderr or stdout. It has nothing to write to except for its logfiles.
As I see Apache has a configtest mode which is ran prior to sending a signal to the daemon, and although this can be done with syslog-ng as well, the configuration can be broken even if it's syntactically correct.
Doesn't Squid (or something) come with a testcfg program or similar that checks and verifies its configuration file? Perhaps syslog-ng could benefit from a separate syntax checker / lint program for the configuration file?
participants (6)
-
Balazs Scheidler
-
David Douthitt
-
John_Delisle＠ceridian.ca
-
jon＠dumbo.pobox.com
-
Scott McDermott
-
William Yodlowsky