[rsyslog] Output to named pipes not working on v4.5.5?
Rainer Gerhards
rgerhards at hq.adiscon.com
Wed Nov 4 07:22:01 CET 2009
Hi,
that actually could be a regression caused by the rewrite of omfile. I'll
look at it as soon as I have time, but it probably is a good idea to file a
bug tracker with bugzilla. I first need to finish what I am currently
implementing (custom parser interface) and then I need to look into which
bugs are open and have priority.
Rainer
> -----Original Message-----
> From: rsyslog-bounces at lists.adiscon.com [mailto:rsyslog-
> bounces at lists.adiscon.com] On Behalf Of Luis Fernando Muñoz Mejías
> Sent: Tuesday, November 03, 2009 7:05 PM
> To: rsyslog at lists.adiscon.com
> Subject: [rsyslog] Output to named pipes not working on v4.5.5?
>
> Hello, world
>
> I must be doing something really dumb. I need to send some output to a
> named pipe that I have already created, but rsyslog is refusing to
> open it.
>
> My configuration states:
>
> *.* |/var/log/external/all/unknown;RSYSLOG_FileFormat
>
> And, of course, the named pipe exists:
>
> # ls -Z /var/log/external/all/unknown
>
> prw-r----- root logreaders user_u:object_r:var_log_t
> /var/log/external/all/unknown
>
> But when I start the syslog daemon it complains with this message:
>
> rsyslogd-2039: Could no open output file
> '|/var/log/external/all/unknown' [try http://www.rsyslog.com/e/2039 ]
>
> It may be a SELinux problem, but the logs show nothing about any
> denied requests. And the context for the named pipe is the exact same
> I have for the log files, which lie in the same directory as well.
>
> Am I the only one experiencing such problems?
>
> Thanks.
> --
> Luis Fernando Muñoz Mejías
> Luis.Fernando.Munoz.Mejias at cern.ch
>
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog
> http://www.rsyslog.com
More information about the rsyslog
mailing list