Red Hat Bugzilla – Bug 589699
Broker special logging output options in docs don't work
Last modified: 2013-10-23 19:16:18 EDT
The docs in http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/1.2/html/Messaging_Installation_Guide/sect-Messaging_Installation_Guide-Options_for_Running_the_Broker-Logging_Broker_Errors.html describe the following option:
According to these docs, in addition to a file name, the following options are possible:
However, if these values are used in the config file, the broker does not behave as expected. If the entry
(or any of the other special values above) is placed in /etc/qpidd.conf, then the behaviour in Bug #589683 is observed. A file by this name is created in /var/lib/qpidd (in spite of the error message and other issues in Bug #589683) instead of the error going to the console error stream.
The documentation is out of date there. qpidd --help shows:
Logging sink options:
--log-to-stderr yes|no (1) Send logging output to stderr
--log-to-stdout yes|no (0) Send logging output to stdout
--log-to-file FILE Send log output to FILE.
--log-to-syslog yes|no (0) Send logging output to syslog;
customize using --syslog-name and
--syslog-name NAME (lt-qpidd) Name to use in syslog messages
--syslog-facility LOG_XXX (LOG_DAEMON) Facility to use in syslog messages
Using the line
in the config file does not work either. There is no log, nor is the output sent to the console.
It works for me. How are you starting qpidd?
Sorry, should have made that clear. I am starting it as a service using service qpidd start.
This is likely the expected behaviour, however, the docs don't make any distinction.
Right, in daemon mode there is no stderr/stdout. Worth making that point in the docs perhaps.
A service damon process closes it's stderr/stdout since there is nowhere for them to go. That's true of any service daemon not just qpidd. special to
Added under the table:
When running as a service, sending information to stdout or stderr will result in no output. In this case, use <command>syslog</command> or specify a filename instead.