From: Petre Rodan <kaiowas@gentoo.org>
To: SELinux <selinux@tycho.nsa.gov>
Subject: Re: run_init: Fork:: No such file or directory
Date: Sat, 22 Oct 2005 17:46:09 +0300 [thread overview]
Message-ID: <20051022144609.GA9002@peter.sunspire.org> (raw)
In-Reply-To: <1129986782.31615.37.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 2593 bytes --]
On Sat, Oct 22, 2005 at 02:13:01PM +0100, Antoine Martin wrote:
> Next time, I'll wait before posting...
> I can't explain why that fixed it, but I rebooted, relabeled and now
> everything works ok. I've had issues with ttys/ptys before, I guess this
> is what has happened here.
> Not understanding the problem or the fix makes me nervous though.
it is a quite common problem that is happening since around ~ 2.6.9. sometimes even ssh logins are impossible because of this bug ("can't open pty" error IIRC).
for me the only way to unlock the situation is to close all open ssh terminals left open toward that server.
once that done, everything (including run_init behavior) returns to normal.
bye,
peter
> Thanks
> Antoine
>
>
>
> On Sat, 2005-10-22 at 13:59 +0100, Antoine Martin wrote:
> > Hi,
> >
> > I've been running a system with SELinux enforcing mode for some time
> > (Gentoo x86), but since yesterday I can't seem to use run_init to start
> > daemons, it fails with:
> > Fork:: No such file or directory
> >
> > When I straced it, I found that it is failing to open /dev/ptmx|pty?? :
> > open("/dev/ptmx", O_RDWR) = -1 EIO (Input/output error)
> > open("/dev/ptyp0", O_RDWR) = -1 ENXIO (No such device or
> > address)
> > open("/dev/ptyp1", O_RDWR) = -1 ENXIO (No such device or
> > address)
> > (...)
> > open("/dev/ptyef", O_RDWR) = -1 ENXIO (No such device or
> > address)
> > dup(2) = 3
> > fcntl64(3, F_GETFL) = 0x2 (flags O_RDWR)
> > brk(0) = 0x804b000
> > brk(0x806c000) = 0x806c000
> > fstat64(3, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 1), ...}) = 0
> > mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
> > 0) = 0xb7f17000
> > _llseek(3, 0, 0xbfc256e4, SEEK_CUR) = -1 ESPIPE (Illegal seek)
> > write(3, "Fork:: No such file or directory"..., 33Fork:: No such file or
> > directory
> > ) = 33
> > close(3) = 0
> > munmap(0xb7f17000, 4096) = 0
> > exit_group(71) = ?
> >
> > Obviously, the devices are there and I'm not using devfs (kernel
> > 2.6.13.4) /dev is static on ext3 /.
> > I am really stumped. I've tried rebuilding it, rebuilding the libraries
> > it depends on, switched to non-enforcing mode, etc.. No luck
> > Any ideas would be much appreciated.
--
petre rodan
<kaiowas@gentoo.org>
Developer,
Hardened Gentoo Linux
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2005-10-22 14:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-22 12:59 run_init: Fork:: No such file or directory Antoine Martin
2005-10-22 13:13 ` Antoine Martin
2005-10-22 14:46 ` Petre Rodan [this message]
2005-10-22 14:55 ` Chris PeBenito
2005-10-22 15:47 ` Antoine Martin
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=20051022144609.GA9002@peter.sunspire.org \
--to=kaiowas@gentoo.org \
--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.