[Solved] openpty failed: 'out of pty devices'

[DigitalCorpus]

Should I worry about this error? Every time I emerge something I have this come up. I'm running a q6700 on a 965P-DS3 and am using the official sources and amd64 minimal CD.

[NathanZachary]

Can you please post a little bit of of the text surrounding the error message so that we can more readily find the cause of the problem? Thanks.

[DigitalCorpus]

Here is a sample as I emerge ntp:

Code: Select all

 * ntp-4.2.4p4.tar.gz RMD160 SHA1 SHA256 size ;-) ...                                                                    [ ok ]
 * checking ebuild checksums ;-) ...                                                                                     [ ok ]
 * checking auxfile checksums ;-) ...                                                                                    [ ok ]
 * checking miscfile checksums ;-) ...                                                                                   [ ok ]
openpty failed: 'out of pty devices'
 * Adjusting permissions for FEATURES=userpriv: '/ccache'
 * Adding group 'ntp' to your system ...
 *  - Groupid: 123
 * Adding user 'ntp' to your system ...
 *  - Userid: 123
 *  - Shell: /sbin/nologin
 *  - Home: /dev/null
 *  - Groups: ntp
>>> Unpacking source...

Before that all it is doing is downloading the source with wget which works just fine.

[NathanZachary]

Ah, I think I remember seeing this as a bug report, but it was a while back:

http://bugs.gentoo.org/show_bug.cgi?id=186876

Are you using the newest version of Portage?

[DigitalCorpus]

2.2 rc8 is my current portage version. I can install everything just fine afaik. I had this error when working with an unofficial CD for Reiser4 support.

[DigitalCorpus]

If it is of any consequence I'm also getting a warning each time I use emerge:

Code: Select all

livecd / # emerge -p portage
WARNING: repository at /usr/local/portage is missing a repo_name entry

[NathanZachary]

Ah, that is still in ~ARCH, so I would recommend trying to downgrade back to 2.1.4.4. That will most likely get rid of the problem.

[DigitalCorpus]

Wanted to use gcc 4.3.x for the core2 march flag. Should I avoid ~ARCH it until it is labeled as stable then? I didn't have a problem in the past with betas

[NathanZachary]

No, it's fine to use ~ARCH if you would like but be aware that some things may not function properly (or have annoyances such as this one). If it isn't causing breakage I wouldn't worry about it. However, if you do want to ONLY downgrade Portage to 2.1.4.4 you can just edit /etc/portage/package.keywords to have this line in it:

Code: Select all

<=sys-apps/portage-2.1.4.4 amd64

[DigitalCorpus]

sorry, but shouldn't x86 be amd64?

[NathanZachary]

You are certainly correct! I was doing too many things at one time; I apologise for the error.

[DigitalCorpus]

Don't worry about it. I have to get accustomed to the fine-toothed control that portage gives with versioning and usage of each package available.

[NathanZachary]

Well I don't think that the error will cause any big problems. However, if you're worried about it then try downgrading to Portage 2.1.4.4 and it will most likely go away.

[DigitalCorpus]

I'll do that as soon as gcc is done compiling here. Thanks again for the help.

[NathanZachary]

No problem at all. Let us know how the downgrade works out for you.

[DigitalCorpus]

unless I remove ~amd64 in my make.conf file, portage still insists on updating itself to 2.2_rc8. I'm verifying this by running emerge -p portage before I update world.

/etc/portage/package.keywords

Code: Select all

<=sys-apps/portage-2.1.4.4 amd64
<=sys-devel/gcc-4.3.1_rc1 ~amd64

[NathanZachary]

You could always remove the ~amd64 from your make.conf, then emerge -av portage (to get 2.1.4.4), and then add sys-apps/portage to /etc/portage/package.mask. I don't THINK that should cause any problems (but I'm not certain). As I said earlier though, you don't have to downgrade as it doesn't seem like the notification is causing any breakages.

[cyrillic]

Code: Select all

openpty failed: 'out of pty devices' 

I think this is a warning rather than an error. I see it too, when I am emerging inside a chroot.

I have not tried this, but you could probably get rid of the warnings by using "mount --rbind" for /dev instead of "mount --bind".

[DigitalCorpus]

Thanks for the tip about adding the read only flag. Solves the extraneous output.

[NathanZachary]

If you are satisfied with this solution, please add [SOLVED] to the title of the original thread. Thanks.

[Hu]

Thanks for the tip about adding the read only flag. Solves the extraneous output.

Minor correction: --rbind is a recursive bind, not a read-only bind. See man mount for full details.

[Dinini]

I realize the original problem is solved but this advice seems wrong.

However, if you do want to ONLY downgrade Portage to 2.1.4.4 you can just edit /etc/portage/package.keywords to have this line in it:

Code: Select all

<=sys-apps/portage-2.1.4.4 amd64

if ~amd64 is the default, I believe you need

Code: Select all

>=sys-apps/portage-2.1.4.4 -~amd64 

to only upgrade from 2.1.4.4 when the package is stable. Note the minus/hyphen for removing the ~amd64 keyword for the package and ">" for matching greater packages (such as 2.2_rc8). /etc/portage/package.keywords changes a bit in portage 2.2 so double check your syntax "man portage" when upgrading and downgrading.