Home » General » Support » Unable to open pty: No such file or directory
Unable to open pty: No such file or directory [message #8974] |
Tue, 12 December 2006 12:42 |
disaster
Messages: 158 Registered: February 2006
|
Senior Member |
|
|
Hello!
I've an VPS which worked since a few month... since today i always receive: "Unable to open pty: No such file or directory"
I've also reinstalled the ubuntu template but it does not work always the same failure.
The funny thing is - if i create a new VPS the template works.
Kernel: 2.6.18 028test007.1
vzctl: 3.0.13-1
Stefan
Log:
# vzctl enter 185
enter into VE 185 failed
Unable to open pty: No such file or directory
strace vzctl enter 185
execve("/usr/sbin/vzctl", ["vzctl", "enter", "185"], [/* 16 vars */]) = 0
uname({sys="Linux", node="host-246-han", ...}) = 0
brk(0) = 0x509000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2b8f522c9000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.preload", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/lib/vzctl/lib/tls/x86_64/libvzctl.so.0.0.2", O_RDONLY) = -1 ENOENT (No such file or directory)
stat("/usr/lib/vzctl/lib/tls/x86_64", 0x7fff587f1a60) = -1 ENOENT (No such file or directory)
open("/usr/lib/vzctl/lib/tls/libvzctl.so.0.0.2", O_RDONLY) = -1 ENOENT (No such file or directory)
stat("/usr/lib/vzctl/lib/tls", 0x7fff587f1a60) = -1 ENOENT (No such file or directory)
open("/usr/lib/vzctl/lib/x86_64/libvzctl.so.0.0.2", O_RDONLY) = -1 ENOENT (No such file or directory)
stat("/usr/lib/vzctl/lib/x86_64", 0x7fff587f1a60) = -1 ENOENT (No such file or directory)
open("/usr/lib/vzctl/lib/libvzctl.so.0.0.2", O_RDONLY) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\300w\0\0"..., 640) = 640
fstat(3, {st_mode=S_IFREG|0755, st_size=743104, ...}) = 0
mmap(NULL, 1220008, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x2b8f523cb000
mprotect(0x2b8f523f1000, 1064360, PROT_NONE) = 0
mmap(0x2b8f524cb000, 172032, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0x2b8f524cb000
close(3) = 0
open("/usr/lib/vzctl/lib/libdl.so.2", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=32168, ...}) = 0
mmap(NULL, 32168, PROT_READ, MAP_PRIVATE, 3, 0) = 0x2b8f524f5000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/libdl.so.2", O_RDONLY) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\36\0\0"..., 640) = 640
fstat(3, {st_mode=S_IFREG|0644, st_size=12072, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2b8f524fd000
mmap(NULL, 1058728, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x2b8f524fe000
mprotect(0x2b8f52501000, 1046440, PROT_NONE) = 0
mmap(0x2b8f525fe000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0x2b8f525fe000
close(3) = 0
open("/usr/lib/vzctl/lib/libutil.so.1", O_RDONLY) = -1 ENOENT (No such file or directory)
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/libutil.so.1", O_RDONLY) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0@\24\0\0"..., 640) = 640
fstat(3, {st_mode=S_IFREG|0644, st_size=11344, ...}) = 0
mmap(NULL, 1057944, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x2b8f52601000
mprotect(0x2b8f52603000, 1049752, PROT_NONE) = 0
mmap(0x2b8f52701000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0x2b8f52701000
close(3) = 0
open("/usr/lib/vzctl/lib/libc.so.6", O_RDONLY) = -1 ENOENT (No such file or directory)
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/libc.so.6", O_RDONLY) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\340\324"..., 640) = 640
fstat(3, {st_mode=S_IFREG|0755, st_size=1295328, ...}) = 0
mmap(NULL, 2354760, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x2b8f52704000
mprotect(0x2b8f52826000, 1166920, PROT_NONE) = 0
mmap(0x2b8f52904000, 241664, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x100000) = 0x2b8f52904000
mmap(0x2b8f5293f000, 15944, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x2b8f5293f000
close(3) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2b8f52943000
arch_prctl(0x1002, 0x2b8f52943760) = 0
munmap(0x2b8f524f5000, 32168) = 0
brk(0) = 0x509000
brk(0x52a000) = 0x52a000
brk(0) = 0x52a000
rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
open("/etc/vz/vz.conf", O_RDONLY) = 3
stat("/etc/vz/vz.conf", {st_mode=S_IFREG|0644, st_size=699, ...}) = 0
fstat(3, {st_mode=S_IFREG|0644, st_size=699, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2b8f524f5000
read(3, "## Global parameters\nVIRTUOZZO=y"..., 4096) = 699
read(3, "", 4096) = 0
close(3) = 0
munmap(0x2b8f524f5000, 4096) = 0
open("/var/log/vzctl.log", O_WRONLY|O_APPEND|O_CREAT, 0666) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=768950, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2b8f524f5000
fstat(3, {st_mode=S_IFREG|0644, st_size=768950, ...}) = 0
lseek(3, 768950, SEEK_SET) = 768950
stat("/etc/vz/conf/185.conf", {st_mode=S_IFREG|0644, st_size=2026, ...}) = 0
open("/etc/vz/conf/185.conf", O_RDONLY) = 4
stat("/etc/vz/conf/185.conf", {st_mode=S_IFREG|0644, st_size=2026, ...}) = 0
fstat(4, {st_mode=S_IFREG|0644, st_size=2026, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2b8f524f6000
read(4, "# Copyright (C) 2000-2006 SWsof"..., 4096) = 2026
read(4, "", 4096) = 0
close(4) = 0
munmap(0x2b8f524f6000, 4096) = 0
fcntl(0, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE|0x8000)
fcntl(1, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE|0x8000)
fcntl(2, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE|0x8000)
open("/dev/vzctl", O_RDWR) = 4
ioctl(4, 0x400c2e05, 0x7fff587f1e20) = 0
close(3) = 0
munmap(0x2b8f524f5000, 4096) = 0
ioctl(4, 0x400c2e05, 0x7fff587f1de0) = 0
pipe([3, 5]) = 0
pipe([6, 7]) = 0
pipe([8, 9]) = 0
syscall_501(0xb9, 0x50a1f0, 0xffffffffffffffff, 0, 0x20, 0x20, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0) = 0
socket(PF_FILE, SOCK_STREAM, 0) = 10
connect(10, {sa_family=AF_FILE, path="/var/run/.nscd_socket"}, 110) = 0
writev(10, [{"\2\0\0\0\0\0\0\0\5\0\0\0", 12}, {"root\0", 5}], 2) = 17
read(10, "\2\0\0\0\1\0\0\0\5\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0\5\0\0"..., 36) = 36
read(10, "root\0x\0root\0/root\0/bin/bash\0", 28) = 28
close(10) = 0
socket(PF_FILE, SOCK_STREAM, 0) = 10
connect(10, {sa_family=AF_FILE, path="/var/run/.nscd_socket"}, 110) = 0
writev(10, [{"\2\0\0\0\2\0\0\0\5\0\0\0", 12}, {"root\0", 5}], 2) = 17
read(10, "\2\0\0\0\1\0\0\0\5\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0", 24) = 24
readv(10, [{"", 0}, {"root\0x\0", 7}], 2) = 7
read(10, NULL, 0) = 0
close(10) = 0
rt_sigaction(SIGCHLD, {0x405b58, [], SA_NOCLDSTOP|0x4000000}, NULL, 8) = 0
rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x2b8f529437f0) = 770
close(3) = 0
close(7) = 0
close(9) = 0
read(8, "\377\377\377\377", 4) = 4
fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 0), ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2b8f524f5000
write(1, "enter into VE 185 failed\n", 25enter into VE 185 failed
) = 25
fcntl(6, F_GETFL) = 0 (flags O_RDONLY|O_LARGEFILE)
fcntl(6, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
--- SIGCHLD (Child exited) @ 0 (0) ---
rt_sigreturn(0x11) = 0
read(6, "Unable to open pty: No such file"..., 10239) = 46
write(1, "Unable to open pty: No such file"..., 46Unable to open pty: No such file or directory
) = 46
read(6, "", 10239) = 0
wait4(770, [{WIFEXITED(s) && WEXITSTATUS(s) == 255}], 0, NULL) = 770
close(5) = 0
close(6) = 0
close(4) = 0
munmap(0x2b8f524f5000, 4096) = 0
exit_group(0xff00, 0xff00, 0x2b8f52926cc0, 0x2b8f52940e08, 0x2b8f52943760 <unfinished ... exit status 0>
|
|
|
Re: Unable to open pty: No such file or directory [message #8975 is a reply to message #8974] |
Tue, 12 December 2006 13:33 |
dim
Messages: 344 Registered: August 2005
|
Senior Member |
|
|
I don't understand, what do you mean under:
disaster wrote on Tue, 12 December 2006 07:42 |
I've also reinstalled the ubuntu template but it does not work always the same failure.
|
OpenVZ template is used only when VE is created. After VE is created, external package management operates with VE, not it's template.
Quote: |
The funny thing is - if i create a new VPS the template works.
|
Above states, that template was not updated, while VE was.
So, I think the issue is that you updated udev in VE and this udev version doesn't work over our kernel.
So, please, could you check is it true? Just check two udev versions, in broken VE and in a new one.
|
|
|
|
Re: Unable to open pty: No such file or directory [message #8982 is a reply to message #8977] |
Tue, 12 December 2006 14:09 |
dim
Messages: 344 Registered: August 2005
|
Senior Member |
|
|
`vzctl destroy VEID` should completely remove VE-related files, so, the followed `vzctl create VEID --ostemplate ...` should be equal to the creation of new one. I'm wonder, how is it possible to have issues in the first case and don't have them in the second.
So, I recommend you to destroy erroneous VE and check, do you have it's ID somewhere in /proc/mounts, /proc/user_beancounters or on the filesystem.
[Updated on: Tue, 12 December 2006 14:09] Report message to a moderator
|
|
|
|
|
|
|
|
Re: Unable to open pty: No such file or directory [message #34227 is a reply to message #34134] |
Mon, 15 December 2008 11:28 |
silenkov
Messages: 1 Registered: September 2008
|
Junior Member |
|
|
Ubuntu 8.04
vzctl exec VEID /sbin/MAKEDEV pty
vzctl exec VEID /sbin/MAKEDEV tty
theese commands make links to devices on / directory instead of /dev/
may be
vzctl exec VEID /sbin/MAKEDEV /dev/pty
vzctl exec VEID /sbin/MAKEDEV /dev/tty
?
On our installation we successfully fixed this error simply by executing
apt-get remove --purge udev
without creating any device by MAKEDEV.
What is the purpose of tihs package inside VE?
[Updated on: Mon, 15 December 2008 11:29] Report message to a moderator
|
|
|
Re: Unable to open pty: No such file or directory [message #34305 is a reply to message #8974] |
Mon, 22 December 2008 15:36 |
Pilat
Messages: 8 Registered: November 2006
|
Junior Member |
|
|
Quote: | Here's the Fix:
vzctl exec VEID /sbin/MAKEDEV pty
vzctl exec VEID /sbin/MAKEDEV tty
vzctl enter VEID
|
It`s don`t work in ubuntu
Ubuntu 9.04
vzctl exec 3333 '/sbin/MAKEDEV /pty'
/sbin/MAKEDEV: warning: can't read /proc/devices
/sbin/MAKEDEV: don't know how to make device "/pty"
Quote: |
On our installation we successfully fixed this error simply by executing
apt-get remove --purge udev
without creating any device by MAKEDEV.
|
FIX
vzctl exec 3333 'dpkg --force-depends --purge udev'
After entering in VE for resolve depends you may install udev and disable boot scripts in sysv - udev & udev-finish.
[Updated on: Tue, 23 December 2008 01:26] Report message to a moderator
|
|
|
|
Re: Unable to open pty: No such file or directory [message #43341 is a reply to message #8974] |
Fri, 26 August 2011 14:47 |
bereket
Messages: 3 Registered: August 2011
|
Junior Member |
|
|
i had similar problem. run the following commands on host node
you need to replace only <CTID> with the container id and make the .../etc/devices and .../dev if the don't exit
if your virtual machines are installed in /vz/privae/
/sbin/MAKEDEV -d /vz/private/<CTID>/dev -x {p,t}ty{a,p}{0,1,2,3,4,5,6,7,8,9,a,b,c,d,e,f} console core full kmem kmsg mem null port ptmx random urandom zero ram0
/sbin/MAKEDEV -d /vz/private/<CTID>/etc/devices -x {p,t}ty{a,p}{0,1,2,3,4,5,6,7,8,9,a,b,c,d,e,f} console core full kmem kmsg mem null port ptmx random urandom zero ram0
but if your virtual machines are installed in /var/lib/vz/privae/
/sbin/MAKEDEV -d /var/lib/vz/private/<CTID>/dev -x {p,t}ty{a,p}{0,1,2,3,4,5,6,7,8,9,a,b,c,d,e,f} console core full kmem kmsg mem null port ptmx random urandom zero ram0
/sbin/MAKEDEV -d /var/lib/vz/private/<CTID>/etc/devices -x {p,t}ty{a,p}{0,1,2,3,4,5,6,7,8,9,a,b,c,d,e,f} console core full kmem kmsg mem null port ptmx random urandom zero ram0
let me know if it works for you. it worked for me
|
|
|
Re: Unable to open pty: No such file or directory [message #44714 is a reply to message #8974] |
Fri, 23 December 2011 21:04 |
votsalo
Messages: 26 Registered: December 2011 Location: Greece
|
Junior Member |
|
|
I ran into the pty problem when I tried to create a container from a template that I had created from a git repository, using git export. I wanted to use git to keep track of my unpacked templates, but apparently git does not handle device files. So I recreated my template using tar on my stopped template container, and I was able to use it to create other containers.
|
|
|
Goto Forum:
Current Time: Fri Sep 27 04:52:52 GMT 2024
Total time taken to generate the page: 0.04297 seconds
|