io.c: do_read: read( ) failed (errno 1), Operation not permitted
I installed syslog-ng version 1.6.9 on Fedora Core 4 in a chroot jail and when starting it, I receive the following message "io.c: do_read: read( ) failed (errno 1), Operation not permitted". I believe this message is the result of syslog-ng not being able to read from /proc/kmsg. However, I'm a newbie to Linux and Sylog-ng! Any suggestions would be greatly appreciated!
Rick.Daoust@borealc.on.ca wrote:
I installed syslog-ng version 1.6.9 on Fedora Core 4 in a chroot jail and when starting it, I receive the following message "io.c: do_read: read( ) failed (errno 1), Operation not permitted". I believe this message is the result of syslog-ng not being able to read from /proc/kmsg. However, I'm a newbie to Linux and Sylog-ng! Any suggestions would be greatly appreciated!
Remove the /proc/kmsg from your configuration, it's unneeded when a syslog daemon running outside of the chroot already reads the kernel messages. If this doesn't help, show your syslog-ng.conf file. -- Sandor Geller wildy@balabit.hu
I only have one sylog deamon -- syslog-ng and it is running in the chroot jail. Gellér Sándor <wildy@balabit.hu> Sent by: syslog-ng-bounces@lists.balabit.hu 01/02/2006 01:59 AM Please respond to Syslog-ng users' and developers' mailing list To: Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu> cc: Subject: Re: [syslog-ng] io.c: do_read: read( ) failed (errno 1), Operation not permitted Rick.Daoust@borealc.on.ca wrote:
I installed syslog-ng version 1.6.9 on Fedora Core 4 in a chroot
jail and when starting it, I receive the following message "io.c: do_read: read( ) failed (errno 1), Operation not permitted". I believe this message is the result of syslog-ng not being able to read from /proc/kmsg. However, I'm a newbie to Linux and Sylog-ng! Any suggestions would be greatly appreciated!
Remove the /proc/kmsg from your configuration, it's unneeded when a syslog daemon running outside of the chroot already reads the kernel messages. If this doesn't help, show your syslog-ng.conf file. -- Sandor Geller wildy@balabit.hu _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
Rick.Daoust@borealc.on.ca wrote:
I only have one sylog deamon -- syslog-ng and it is running in the chroot jail.
This is a very uncommon setup (for my best knowledge FC4 ships with the traditional syslogd and klogd, where the latter reads /proc/kmsg). Please doublecheck whether some processes are reading /proc/kmsg or not (use fuser or lsof), /proc is mounted in the chroot or not. -- Sandor Geller wildy@balabit.hu
On Wed, 2006-02-01 at 16:01 +0100, Sandor Geller wrote:
Rick.Daoust@borealc.on.ca wrote:
I only have one sylog deamon -- syslog-ng and it is running in the chroot jail.
This is a very uncommon setup (for my best knowledge FC4 ships with the traditional syslogd and klogd, where the latter reads /proc/kmsg). Please doublecheck whether some processes are reading /proc/kmsg or not (use fuser or lsof), /proc is mounted in the chroot or not.
and whether SELinux is enabled and permits syslog-ng to open /proc/kmsg. -- Bazsi
participants (4)
-
Balazs Scheidler
-
Gellér Sándor
-
Rick.Daoust＠borealc.on.ca
-
Sandor Geller