syslog-ng refuses to open/write destination file
Hello... Any help would be greatly appreciated. I have configured syslog-ng to add a custom application filter and log destination. Let me preface all works when I configure the destination to be in /var/log. However, due to operational needs the file needs to be written off to a directory in /usr/local/ssl/<application location>. Here's the tricky part. The /usr/local/ssl/<application> is actually being exported by a NFS server as a share. I thought perhaps that was the issue as I do see a "cannot open file for writing, permission denied" vomited by syslog-ng and stamped when I kick start the application. I checked the permissions on directory and the log file. They are all good. I am able to touch, create, destroy, move, copy etc data on that directory. It only appears syslog-ng is having the trouble. What makes it more goofy is when I manipulate how I kick start the app (via shell or daemon) sometimes I see the permission error sometimes I do not. Ultimately syslog-ng still just stamps everything to 'messages'. Question, does syslog-ng have a configuration for writing off your destination file to an NFS share? I've never had this problem appear before. Perhaps someone has some experience to lend a hand? Appreciate it in advance! Cheers - Jonathan ----------------------------------------- The information in this message may be proprietary and/or confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify First Data immediately by replying to this message and deleting it from your computer.
What user is the syslog-ng daemon running as, and does that user have permission to write to the NFS directory? ________________________________ From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Peck, Jonathan Sent: 10 November 2008 15:57 To: syslog-ng@lists.balabit.hu Subject: [syslog-ng] syslog-ng refuses to open/write destination file Hello... Any help would be greatly appreciated. I have configured syslog-ng to add a custom application filter and log destination. Let me preface all works when I configure the destination to be in /var/log. However, due to operational needs the file needs to be written off to a directory in /usr/local/ssl/<application location>. Here's the tricky part. The /usr/local/ssl/<application> is actually being exported by a NFS server as a share. I thought perhaps that was the issue as I do see a "cannot open file for writing, permission denied" vomited by syslog-ng and stamped when I kick start the application. I checked the permissions on directory and the log file. They are all good. I am able to touch, create, destroy, move, copy etc data on that directory. It only appears syslog-ng is having the trouble. What makes it more goofy is when I manipulate how I kick start the app (via shell or daemon) sometimes I see the permission error sometimes I do not. Ultimately syslog-ng still just stamps everything to 'messages'. Question, does syslog-ng have a configuration for writing off your destination file to an NFS share? I've never had this problem appear before. Perhaps someone has some experience to lend a hand? Appreciate it in advance! Cheers - Jonathan ________________________________ The information in this message may be proprietary and/or confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify First Data immediately by replying to this message and deleting it from your computer.
Thanks for the quick response.... Syslog-ng is running as root. It does have permission to hit the share, as I can create, modify etc data on that share as root on the local client. I've put syslog-ng into debug mode (syslog-ng -d -v) and it really doesn't yield too much information. I thought perhaps it was the reporting element from the application, so changed it in its .xml config to pipe as the user that runs the application. Still no joy. From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Fegan, Joe Sent: Monday, November 10, 2008 10:02 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] syslog-ng refuses to open/write destination file What user is the syslog-ng daemon running as, and does that user have permission to write to the NFS directory? ________________________________ From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Peck, Jonathan Sent: 10 November 2008 15:57 To: syslog-ng@lists.balabit.hu Subject: [syslog-ng] syslog-ng refuses to open/write destination file Hello... Any help would be greatly appreciated. I have configured syslog-ng to add a custom application filter and log destination. Let me preface all works when I configure the destination to be in /var/log. However, due to operational needs the file needs to be written off to a directory in /usr/local/ssl/<application location>. Here's the tricky part. The /usr/local/ssl/<application> is actually being exported by a NFS server as a share. I thought perhaps that was the issue as I do see a "cannot open file for writing, permission denied" vomited by syslog-ng and stamped when I kick start the application. I checked the permissions on directory and the log file. They are all good. I am able to touch, create, destroy, move, copy etc data on that directory. It only appears syslog-ng is having the trouble. What makes it more goofy is when I manipulate how I kick start the app (via shell or daemon) sometimes I see the permission error sometimes I do not. Ultimately syslog-ng still just stamps everything to 'messages'. Question, does syslog-ng have a configuration for writing off your destination file to an NFS share? I've never had this problem appear before. Perhaps someone has some experience to lend a hand? Appreciate it in advance! Cheers - Jonathan ________________________________ The information in this message may be proprietary and/or confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify First Data immediately by replying to this message and deleting it from your computer. ----------------------------------------- The information in this message may be proprietary and/or confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify First Data immediately by replying to this message and deleting it from your computer.
On Mon, 2008-11-10 at 10:08 -0600, Peck, Jonathan wrote:
Thanks for the quick response….
Syslog-ng is running as root. It does have permission to hit the share, as I can create, modify etc data on that share as root on the local client.
Hmm.. this sounds like a problem with your SELinux/AppArmor policy. Can you check the logfiles for a hint? If it's not SELinux, you could perhaps run syslog-ng under strace and check the return code for the open() call. It most probably is EPERM, in which case it is not syslog-ng to blame, but some kind of local security setup. -- Bazsi
participants (3)
-
Balazs Scheidler
-
Fegan, Joe
-
Peck, Jonathan