From: Unix Admin <unix@cobalt-financial.com>
To: selinux@tycho.nsa.gov
Subject: Kernel woes
Date: Mon, 17 Oct 2005 10:16:41 +0000 [thread overview]
Message-ID: <43537A09.5080005@cobalt-financial.com> (raw)
Greetings all. After a recent reboot to one of my servers, the kernel
began showing the following errors:
[root@odin logs]# uname -a
Linux odin 2.6.9-11.ELsmp #1 SMP Wed Jun 8 17:54:20 CDT 2005 i686 i686
i386 GNU/Linux
Oct 17 09:01:05 odin kernel: post_create: setxattr failed, rc=28
(dev=sda1 ino=8339458)
Oct 17 09:05:33 odin kernel: post_create: setxattr failed, rc=28
(dev=sda1 ino=8339457)
Oct 17 09:05:33 odin kernel: post_create: setxattr failed, rc=28
(dev=sda1 ino=8339458)
Oct 17 09:06:57 odin kernel: post_create: setxattr failed, rc=28
(dev=sda1 ino=8339457)
Oct 17 09:06:57 odin kernel: post_create: setxattr failed, rc=28
(dev=sda1 ino=8339458)
Oct 17 09:01:05 odin kernel: audit(1129554065.524:0): avc: denied {
write } for pid=527 comm=httpd name=log dev=tmpfs ino=271982
scontext=root:system_r:httpd_t tcontext=root:object_r:device_t
tclass=sock_file
Oct 17 09:05:33 odin kernel: audit(1129554333.429:0): avc: denied {
write } for pid=522 comm=httpd name=log dev=tmpfs ino=271982
scontext=root:system_r:httpd_t tcontext=root:object_r:device_t
tclass=sock_file
Oct 17 09:06:21 odin kernel: audit(1129554381.723:0): avc: denied {
write } for pid=524 comm=httpd name=log dev=tmpfs ino=271982
scontext=root:system_r:httpd_t tcontext=root:object_r:device_t
tclass=sock_file
Oct 17 09:06:57 odin kernel: audit(1129554417.668:0): avc: denied {
write } for pid=527 comm=httpd name=log dev=tmpfs ino=271982
scontext=root:system_r:httpd_t tcontext=root:object_r:device_t
tclass=sock_file
Oct 17 09:17:10 odin kernel: audit(1129555030.530:0): avc: denied {
write } for pid=522 comm=httpd name=log dev=tmpfs ino=271982
scontext=root:system_r:httpd_t tcontext=root:object_r:device_t
tclass=sock_file
Oct 17 09:17:32 odin kernel: audit(1129555052.254:0): avc: denied {
write } for pid=525 comm=httpd name=log dev=tmpfs ino=271982
scontext=root:system_r:httpd_t tcontext=root:object_r:device_t
tclass=sock_file
No changes were made to anything but we had to recently reboot due to an
IP collision. Any ideas on why this is happening, any pointers on where
to check for perhaps permission errors?
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next reply other threads:[~2005-10-17 14:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 10:16 Unix Admin [this message]
2005-10-17 14:33 ` Kernel woes Daniel J Walsh
2005-10-17 11:37 ` Kernel woes (summary) Unix Admin
2005-10-17 14:45 ` Kernel woes Stephen Smalley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43537A09.5080005@cobalt-financial.com \
--to=unix@cobalt-financial.com \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.