syslog debug destination error on start up

[GoogleCodeExporter]

What steps will reproduce the problem?
Restarting syslog-ng

What is the expected output? What do you see instead?
Syslog will start, but it gives the following error:
Starting syslog-ng
Connection failed; fd='13', server='AF_UNIX(/data/elsa/tmp/debug)', 
local='AF_UNIX(anonymous)', error='No such file or directory (2)'
Initiating connection failed, reconnecting; time_reopen='60'

What version of the product are you using? On what operating system?
This started with r909

Please provide any additional information below.
The unix socket is not being created.  I think a source is needed to create it. 
 From the syslog admin guide:
"The unix-stream() and unix-dgram() drivers open an AF_UNIX socket and start 
listening on it for messages."

The destination documentation doesn't mention opening a socket.
I tested this theory by commenting out the s_ops source and enabling the 
d_unclassified destination, and this caused an identical error, but complaining 
about the missing ops socket. 

Original issue reported on code.google.com by kebut...@gmail.com on 13 Jun 2013 at 11:24

[GoogleCodeExporter]

This is a harmless warning, but I'm not sure how to get rid of it.  The socket 
connection is there to connect to the /data/elsa/tmp/debug socket which is 
created when /usr/local/elsa/contrib/livetail.pl script runs.  The livetail.pl 
is for dumping all logs that go to elsa.pl to standard out for debugging 
purposes.  The reason for using the socket is that it guarantees that any thing 
that happens in livetail.pl won't affect other processing.

Original comment by mchol...@gmail.com on 14 Jun 2013 at 4:07