OpenVZ Forum: Users » Problem comtainer

Home » Mailing lists » Users » Problem comtainer

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Problem comtainer [message #43387]

Sat, 03 September 2011 00:02

dowdle
Messages: 261
Registered: December 2005
Location: Bozeman, Montana

Senior Member

Greetings,

I just upgraded my main OpenVZ host to Scientific Linux 6.1 x86_64 running the OpenVZ RHEL6-based branch. I'm all updated.

I migrated all of my containers over to it and everything seems to be working great. I redid the configs to use vswap and it is nice.

I do have one problem, and I don't know if it is related to the change or not... but I just now noticed it... but I have one CentOS 5.6 32-bit container that is having the no pty problem. When I try to vzctl enter into it I get:

Unable to open pty: No such file or directory

If I try to ssh in I get:
PTY allocation request failed on channel 0

It has had udev installed in it for a long time without issue and oddly all of the /dev stuff IS there. I have restarted the container several times... I have turned off udev... and back on again... and yes the files are always there... and I have even regenerated them with the various MAKEDEV solutions... but even though the files are there, I still get the same errors.

Any ideas?

TYL,
--
Scott Dowdle
704 Church Street
Belgrade, MT 59714
(406)388-0827 [home]
(406)994-3931 [work]

--
TYL, Scott Dowdle
Belgrade, Montana, USA

Report message to a moderator

Re: Problem comtainer [message #43389 is a reply to message #43387]

Sat, 03 September 2011 00:59

samiam
Messages: 15
Registered: July 2011

Junior Member

What is the output of the following commands when this container is running:

vzctl exec ${NUMBER} ls -l /dev
vzctl exec ${NUMBER} ls -l /dev/pts
vzctl exec ${NUMBER} mount

Replace ${NUMBER} with the number of the container.

- Sam

2011/9/2 Scott Dowdle <dowdle@montanalinux.org>:
> Greetings,
>
> I just upgraded my main OpenVZ host to Scientific Linux 6.1 x86_64 running the OpenVZ RHEL6-based branch. I'm all updated.
>
> I migrated all of my containers over to it and everything seems to be working great. I redid the configs to use vswap and it is nice.
>
> I do have one problem, and I don't know if it is related to the change or not... but I just now noticed it... but I have one CentOS 5.6 32-bit container that is having the no pty problem. When I try to vzctl enter into it I get:
>
> Unable to open pty: No such file or directory
>
> If I try to ssh in I get:
> PTY allocation request failed on channel 0
>
> It has had udev installed in it for a long time without issue and oddly all of the /dev stuff IS there. I have restarted the container several times... I have turned off udev... and back on again... and yes the files are always there... and I have even regenerated them with the various MAKEDEV solutions... but even though the files are there, I still get the same errors.
>
> Any ideas?
>
> TYL,
> --
> Scott Dowdle
> 704 Church Street
> Belgrade, MT 59714
> (406)388-0827 [home]
> (406)994-3931 [work]

Report message to a moderator

Re: Problem comtainer [message #43390 is a reply to message #43387]

Sat, 03 September 2011 08:40

Einar S. Ids
Messages: 6
Registered: August 2011

Junior Member

On Sat, Sep 3, 2011 at 2:02 AM, Scott Dowdle <dowdle@montanalinux.org> wrote:
> I do have one problem, and I don't know if it is related to the change or not... but I just now noticed it... but I have one CentOS 5.6 32-bit container that is having the no pty problem. When I try to vzctl enter into it I get:
>
> Unable to open pty: No such file or directory

This sounds like the same problem I had when I recently moved some old
Gentoo-containers from Linux-Vserver to OpenVZ.

Try the following command:
vzctl exec CTID mount -t devpts none /dev/pts
then try to reenter:
vzctl enter CTID

If this works, then all you have to do is add the line "mount -t
devpts none /dev/pts" to the container's /etc/rc.local to make sure it
stays working after a restart. There may be more elegant solutions out
there, but this works for me.

Cheers,
Einar

Report message to a moderator

Re: Problem comtainer [message #43391 is a reply to message #43389]

Sat, 03 September 2011 11:59

dowdle
Messages: 261
Registered: December 2005
Location: Bozeman, Montana

Senior Member

Sam,

----- Original Message -----
> What is the output of the following commands when this container is
> running:
>
> vzctl exec ${NUMBER} ls -l /dev

As previously stated, what you'd expect.

> vzctl exec ${NUMBER} ls -l /dev/pts

As previously stated, what you'd expect.

> vzctl exec ${NUMBER} mount

Not much... and no /dev/pts so that's the problem with the fix given in the next email response.

TYL,
--
Scott Dowdle
704 Church Street
Belgrade, MT 59714
(406)388-0827 [home]
(406)994-3931 [work]

--
TYL, Scott Dowdle
Belgrade, Montana, USA

Report message to a moderator

Re: Problem comtainer [message #43392 is a reply to message #43390]

Sat, 03 September 2011 12:02

dowdle
Messages: 261
Registered: December 2005
Location: Bozeman, Montana

Senior Member

Einar,

----- Original Message -----
> Try the following command:
> vzctl exec CTID mount -t devpts none /dev/pts

That worked and I didn't have to add it to rc.local... as I discovered that /etc/fstab was missing. I promise I didn't delete /etc/fstab but I'm not the only person with root access to that container. :)

So, I copied an /etc/fstab from another container and restarted it and it works fine now.

Thanks,
--
Scott Dowdle
704 Church Street
Belgrade, MT 59714
(406)388-0827 [home]
(406)994-3931 [work]

--
TYL, Scott Dowdle
Belgrade, Montana, USA

Report message to a moderator

Previous Topic:	fuse filesystem inside a container?
Next Topic:	noatime, data=writeback

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Apr 02 06:05:28 GMT 2023

Total time taken to generate the page: 0.01289 seconds