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-facility
  --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

log-to-stderr=yes

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:

<note>
	<title>Note</title>
	<para>
		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.
	</para>
</note>

LKB