Hello, On 03/04/2011 07:43 AM, Hidayath Basha wrote:
Hi Peter,
Thanks, disabling apparmor really worked. Thank you very much Disabling apparmor is just a workaround. The solution is to add the files to AppArmor. If you read from the file, then a line like this to /etc/apparmor.d/sbin.syslog-ng: /some/file.log r, If it's a destination outside of /var/log, then a line like this: /some/file.dest rw, This way your applications are still protected by AppArmor, but syslog-ng can reach files outside of /var/log Bye, CzP
Thanks and regards, *Hidayath* **
-----Original Message----- *From:* syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu]*On Behalf Of *Peter Czanik *Sent:* Thursday, March 03, 2011 7:06 PM *To:* Syslog-ng users' and developers' mailing list *Subject:* Re: [syslog-ng] Permission Denied (13)
Hello,
On 03/03/2011 02:28 PM, Hidayath Basha wrote:
When I start the service at client, I'm getting the following error Starting syslog servicesError opening file for reading; filename='/some/file.log', error='Permission denied (13)' Error initializing source driver; source='s_mysrc' startproc: exit status of parent of /sbin/syslog-ng: 2
The file /some/file.log has -rw-rw-rw- permissions
You should try to disable AppArmor (rcapparmor stop), and if it helps, then add the file to /etc/apparmor.d/sbin.syslog-ng Bye,
-- Peter Czanik (CzP) <czanik@balabit.hu> BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.campin.net/syslog-ng/faq.html
-- Peter Czanik (CzP) <czanik@balabit.hu> BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/