Re^3: LOGDOG Issue

So... Did you check that /etc/syslog.conf is correct?

Edit the configuration and replace the

*.info            |${FIFO}
[download]

with

*.info            |/var/log/fifo.logdog
[download]

(be sure that there are TABs, not spaces, separating the sides.) Then send SIGHUP to syslogd...

Comment on Re^3: LOGDOG Issue Select or Download Code

Replies are listed 'Best First'.
Re^4: LOGDOG Issue by vhaphisasset (Initiate) on May 12, 2015 at 16:43 UTC
It has been sometime since I was able to get back into looking at this issue. I took sometime this morning to start trouble shooting again and found out what was causing the problem. This code was written when RHEL used syslogd and in version RHEL 6 they changed it to rsyslogd. So I edited the rsyslog.conf file to reflect the usage of the fifo and everything works as it should with the system alerting on the predefined error phrases. One change is that syslogd accepted the \| symbol but rsyslogd does not. See the code change. This is the old code with using the syslog.conf `.info \|/var/log/fifo.rdp_monitorLogwatch` This is how it needs to be set using rsyslog.conf `.info -/var/log/fifo.rdp_monitorLogwatch` Since I was able to resolve the issue I wanted to let you all know how in case someone wanted to use the code on their server. Thanks again for those that helped out!	[reply] [d/l] [select]
Re^4: LOGDOG FIFOIssue by vhaphisasset (Initiate) on Mar 19, 2015 at 18:15 UTC
I have made the edits as you described and I had already used TAB but still getting the same response. I also restarted the syslogd service (service rsyslog restart) ( `ERROR => Timeout while opening FIFO [/var/log/fifo.logdog]. Possible solution: configure syslogd to log to this FIFO and restart syslogd.` Same error as before. Just cant open the file. Thanks for your input!!	[reply] [d/l]