View previous topic :: View next topic |
Author |
Message |
DigitalCorpus Apprentice
Joined: 30 Jul 2007 Posts: 283
|
Posted: Fri Aug 15, 2008 9:43 pm Post subject: [Solved] openpty failed: 'out of pty devices' |
|
|
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.
Last edited by DigitalCorpus on Sun Aug 17, 2008 6:11 pm; edited 1 time in total |
|
Back to top |
|
|
NathanZachary Moderator
Joined: 30 Jan 2007 Posts: 2605
|
Posted: Fri Aug 15, 2008 9:44 pm Post subject: |
|
|
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. _________________ “Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio--- |
|
Back to top |
|
|
DigitalCorpus Apprentice
Joined: 30 Jul 2007 Posts: 283
|
Posted: Fri Aug 15, 2008 9:58 pm Post subject: |
|
|
Here is a sample as I emerge ntp:
Code: | * 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. |
|
Back to top |
|
|
NathanZachary Moderator
Joined: 30 Jan 2007 Posts: 2605
|
Posted: Fri Aug 15, 2008 10:01 pm Post subject: |
|
|
Ah, I think I remember seeing this as a bug report, but it was a while back:
https://bugs.gentoo.org/show_bug.cgi?id=186876
Are you using the newest version of Portage? _________________ “Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio--- |
|
Back to top |
|
|
DigitalCorpus Apprentice
Joined: 30 Jul 2007 Posts: 283
|
Posted: Fri Aug 15, 2008 10:03 pm Post subject: |
|
|
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. |
|
Back to top |
|
|
DigitalCorpus Apprentice
Joined: 30 Jul 2007 Posts: 283
|
Posted: Fri Aug 15, 2008 10:06 pm Post subject: |
|
|
If it is of any consequence I'm also getting a warning each time I use emerge:
Code: | livecd / # emerge -p portage
WARNING: repository at /usr/local/portage is missing a repo_name entry |
|
|
Back to top |
|
|
NathanZachary Moderator
Joined: 30 Jan 2007 Posts: 2605
|
Posted: Fri Aug 15, 2008 10:07 pm Post subject: |
|
|
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. _________________ “Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio--- |
|
Back to top |
|
|
DigitalCorpus Apprentice
Joined: 30 Jul 2007 Posts: 283
|
Posted: Fri Aug 15, 2008 10:10 pm Post subject: |
|
|
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 |
|
Back to top |
|
|
NathanZachary Moderator
Joined: 30 Jan 2007 Posts: 2605
|
Posted: Fri Aug 15, 2008 10:15 pm Post subject: |
|
|
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: |
<=sys-apps/portage-2.1.4.4 amd64
|
_________________ “Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio---
Last edited by NathanZachary on Fri Aug 15, 2008 10:20 pm; edited 1 time in total |
|
Back to top |
|
|
DigitalCorpus Apprentice
Joined: 30 Jul 2007 Posts: 283
|
Posted: Fri Aug 15, 2008 10:18 pm Post subject: |
|
|
sorry, but shouldn't x86 be amd64? |
|
Back to top |
|
|
NathanZachary Moderator
Joined: 30 Jan 2007 Posts: 2605
|
Posted: Fri Aug 15, 2008 10:20 pm Post subject: |
|
|
You are certainly correct! I was doing too many things at one time; I apologise for the error. _________________ “Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio--- |
|
Back to top |
|
|
DigitalCorpus Apprentice
Joined: 30 Jul 2007 Posts: 283
|
Posted: Fri Aug 15, 2008 10:22 pm Post subject: |
|
|
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. |
|
Back to top |
|
|
NathanZachary Moderator
Joined: 30 Jan 2007 Posts: 2605
|
Posted: Fri Aug 15, 2008 10:25 pm Post subject: |
|
|
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. _________________ “Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio--- |
|
Back to top |
|
|
DigitalCorpus Apprentice
Joined: 30 Jul 2007 Posts: 283
|
Posted: Fri Aug 15, 2008 10:29 pm Post subject: |
|
|
I'll do that as soon as gcc is done compiling here. Thanks again for the help. |
|
Back to top |
|
|
NathanZachary Moderator
Joined: 30 Jan 2007 Posts: 2605
|
Posted: Fri Aug 15, 2008 10:30 pm Post subject: |
|
|
No problem at all. Let us know how the downgrade works out for you. _________________ “Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio--- |
|
Back to top |
|
|
DigitalCorpus Apprentice
Joined: 30 Jul 2007 Posts: 283
|
Posted: Fri Aug 15, 2008 10:55 pm Post subject: |
|
|
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: | <=sys-apps/portage-2.1.4.4 amd64
<=sys-devel/gcc-4.3.1_rc1 ~amd64 |
|
|
Back to top |
|
|
NathanZachary Moderator
Joined: 30 Jan 2007 Posts: 2605
|
Posted: Fri Aug 15, 2008 11:13 pm Post subject: |
|
|
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. _________________ “Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio--- |
|
Back to top |
|
|
cyrillic Watchman
Joined: 19 Feb 2003 Posts: 7313 Location: Groton, Massachusetts USA
|
Posted: Sat Aug 16, 2008 2:06 am Post subject: |
|
|
Code: | 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". |
|
Back to top |
|
|
DigitalCorpus Apprentice
Joined: 30 Jul 2007 Posts: 283
|
Posted: Sun Aug 17, 2008 6:11 pm Post subject: |
|
|
Thanks for the tip about adding the read only flag. Solves the extraneous output.
Last edited by DigitalCorpus on Mon Aug 18, 2008 8:53 am; edited 1 time in total |
|
Back to top |
|
|
NathanZachary Moderator
Joined: 30 Jan 2007 Posts: 2605
|
Posted: Mon Aug 18, 2008 4:00 am Post subject: |
|
|
If you are satisfied with this solution, please add [SOLVED] to the title of the original thread. Thanks. _________________ “Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio--- |
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 21835
|
Posted: Tue Aug 19, 2008 12:52 am Post subject: |
|
|
DigitalCorpus wrote: | 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. |
|
Back to top |
|
|
Dinini Apprentice
Joined: 11 Jun 2003 Posts: 236
|
Posted: Thu Aug 21, 2008 7:05 am Post subject: |
|
|
I realize the original problem is solved but this advice seems wrong. kalos wrote: | 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: |
<=sys-apps/portage-2.1.4.4 amd64
|
|
if ~amd64 is the default, I believe you need
Code: | >=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. _________________ "There are nine and sixty ways of constructing tribal lays,
And every single one of them is right!" - Rudyard Kipling "In the Neolithic Age" |
|
Back to top |
|
|
|