OpenVZ Forum


Home » General » Support » Fedora 15 broken Unable to open pty: No such file or directory (Every release of Fedora has the same problem)
Fedora 15 broken Unable to open pty: No such file or directory [message #42766] Tue, 24 May 2011 16:34 Go to next message
mperkel is currently offline  mperkel
Messages: 253
Registered: December 2006
Senior Member
Tried the usual things like deleting several startup file in /etc/init, deleted /sbin/udevd, etc.

This is somewhat frustrating in that every new release of Fedora has the same problem. It would be nice if there were some sort of fix it script to fix the pty problem.

When I run vzlist from the host there's only one process running in the ve.



Re: Fedora 15 broken Unable to open pty: No such file or directory [message #42776 is a reply to message #42766] Wed, 25 May 2011 20:11 Go to previous messageGo to next message
steveh is currently offline  steveh
Messages: 6
Registered: June 2010
Location: Atlanta, GA USA
Junior Member

Same thing here with Fedora 14.
Do not yum update the upstart package.
Only use the Fedora 14 template "as-is" until more information is available.
Good Luck,
Steve H.
Re: Fedora 15 broken Unable to open pty: No such file or directory [message #42780 is a reply to message #42766] Thu, 26 May 2011 14:40 Go to previous messageGo to next message
mperkel is currently offline  mperkel
Messages: 253
Registered: December 2006
Senior Member
I need to use yum. That's how I update.

Re: Fedora 15 broken Unable to open pty: No such file or directory [message #42781 is a reply to message #42780] Thu, 26 May 2011 14:52 Go to previous messageGo to next message
steveh is currently offline  steveh
Messages: 6
Registered: June 2010
Location: Atlanta, GA USA
Junior Member

I also use yum to update inside containers.

A "yum update" inside a FC14 VE will update it including the "upstart" module and then you will have a broken container ;(

Unfortunately "upstart" is considered to be a dependency for a lot of other packages and it is difficult to exclude it from any sort of update or package installation.

I've switched back to using good old, static FC12 for now as the basis for the Asterisk VoIP containers I build and deploy. I will try SL6 to see if this bug is present there.

Cheers,
Steven H.
Re: Fedora 15 broken Unable to open pty: No such file or directory [message #42782 is a reply to message #42766] Thu, 26 May 2011 15:05 Go to previous messageGo to next message
mperkel is currently offline  mperkel
Messages: 253
Registered: December 2006
Senior Member
I wonder if we could get the Fedora folks interested in making Fedora OpenVZ container aware/friendly?

Re: Fedora 15 broken Unable to open pty: No such file or directory [message #42783 is a reply to message #42782] Thu, 26 May 2011 15:11 Go to previous messageGo to next message
steveh is currently offline  steveh
Messages: 6
Registered: June 2010
Location: Atlanta, GA USA
Junior Member

I've spoken with one of their policy makers and I doubt it.
They really like KVM. Even LXC doesn't get the attention it deserves.
Re: Fedora 15 broken Unable to open pty: No such file or directory [message #42808 is a reply to message #42766] Mon, 30 May 2011 16:46 Go to previous messageGo to next message
mperkel is currently offline  mperkel
Messages: 253
Registered: December 2006
Senior Member
I have opened a Fedora 15 bug. Here is a link for anyone who is interested in following it. Maybe one of you can help the process along.

https://bugzilla.redhat.com/show_bug.cgi?id=708629



Re: Fedora 15 broken Unable to open pty: No such file or directory [message #42823 is a reply to message #42766] Wed, 01 June 2011 05:37 Go to previous messageGo to next message
mperkel is currently offline  mperkel
Messages: 253
Registered: December 2006
Senior Member
Unless they change it systemd now requires kernel 2.6.35 or greater.

Re: Fedora 15 broken Unable to open pty: No such file or directory [message #42824 is a reply to message #42766] Wed, 01 June 2011 10:34 Go to previous messageGo to next message
Ales is currently offline  Ales
Messages: 330
Registered: May 2009
Senior Member
Hm. Perhaps OpenVZ team could add the needed functionality if we find out exactly what is it that is missing from the kernel (if that really is the reason).

Perhaps you could add to the bug report that OpenVZ uses an additionally modified RHEL 6 kernel - that's not a stock 2.6.32. RHEL backports functionality too, not just bugfixes.

Apart from that - since Red Hat invests a lot of effort into KVM, they might not be that much interested in pushing OpenVZ (or lxc) compatibility changes into Fedora. But any community member could do it, as long as it's accepted by them...
Re: Fedora 15 broken Unable to open pty: No such file or directory [message #42836 is a reply to message #42766] Sat, 04 June 2011 14:51 Go to previous message
mperkel is currently offline  mperkel
Messages: 253
Registered: December 2006
Senior Member
This is the feature that wants a 2.6.35 kernel for systemd. I copied it from a comment in the bugzilla I filed.



What's the kernel version? There is a known problem related to capabilities when running on kernel < 2.6.38. If it's that, try commenting out all "CapabilityBoundingSet=" lines in /etc/systemd/system/*


Previous Topic: Can the root user break out of a container?
Next Topic: Zentyal on Proxmox (openvz)
Goto Forum:
  


Current Time: Tue Nov 05 18:49:26 GMT 2024

Total time taken to generate the page: 0.03586 seconds