[rsyslog-notify] Forum Thread: Re: omuxsock gives no output (v7.4.4 Debian) - (Mode 'edit_last_post')

[noreply at adiscon.com]

User: Joris 
Forumlink: http://kb.monitorware.com/viewtopic.php?p=24807#p24807

Message: 
----------
[quote="dlang":103lvfzd]did you check the output of lsof to see what socket
rsyslog actually opened?[/quote:103lvfzd]

Rsyslog only opened two domain sockets after creating a file for the
omuxsock example in /etc/rsyslog.d One of them is of course /dev/log but
the other one required a bit more effort to figure out as its name was only
listed as 'socket.' So after trying to find it by inode number, no results,
I can say that I have no idea what it opened there. And if it was for
omuxsock. So if it did open a socket, it did not listen to the
$OMUxSockSocket configuration line.

[quote="dlang":103lvfzd]the other thing is that you can start rsyslog in
debug mode (-dn) and look for an error message

also remember that rsyslog won't open the socket until it receives a log
message that needs to be delivered to that output.[/quote:103lvfzd]

I provided the output of the debug mode in a previous post as a link to
pastebin. As the forum did not allow me to upload a text file. Provided
here again for clarity.
[url:103lvfzd]http://pastebin.com/jF4QFDkG[/url:103lvfzd] This is
after I used logger a few times to create log messages. And omuxsock being
given *.* as a selector.

In my limited knowledge rsyslog I see the messages being processed without
an obvious error message. Nor can I determine if the connection actually
gets made on rsyslog's end.