[Users] Unable to open pty

Galia Lisovskaya inbox at shaggy-cat.ru
Tue Mar 2 10:16:11 EST 2010


Hi! I'm don't find bug traker on your company site, and try send bug
report for any your officer, sorry.

CentOS 5.4, your rpm:

Name        : vzdump                       Relocations: (not relocatable)
Version     : 1.2                               Vendor: Proxmox
Release     : 5                             Build Date: Втр 10 Ноя 2009 09:47:17
Install Date: Втр 02 Мар 2010 17:58:02      Build Host: oahu.maurer-it.com
Group       : Utilities                     Source RPM: vzdump-1.2-5.src.rpm
Size        : 70592                            License: GPL
Signature   : (none)
Packager    : Proxmox Server Solutions GmbH <http://www.proxmox.com/>
URL         : http://www.proxmox.com/
Summary     : OpenVZ backup scripts
Description :
This package contains the vzdump script to backup and restore openvz images.

Does'nt work:

vzdump --snapshot 201
Can't locate PVE/VZDump.pm in @INC (@INC contains:
/usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl
/usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl
/usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .)
at /usr/sbin/vzdump line 27.
BEGIN failed--compilation aborted at /usr/sbin/vzdump line 27.

And, old vzdump (vzdump-1.1-2) does'nt work if VG or LV has numbers in name:

[root at ovz01 ~]# vzdump --snapshot 201
INFO: Starting new backup job - vzdump --snapshot 201
INFO: Starting Backup of VM 201 (openvz)
INFO: status = CTID 201 exist mounted running
ERROR: unable to detect lvm volume group, using 'suspend' mode
INFO: starting first sync /vz/private/201 to /var/tmp/vzdumptmp2111
ERROR: Backup of VM 201 failed - interrupted by signal
[root at ovz01 ~]#

[root at ovz01 ~]# lvs
  LV   VG    Attr   LSize   Origin Snap%  Move Log Copy%  Convert
  home ovz01 -wi-ao   1,94G
  root ovz01 -wi-ao   3,41G
  swap ovz01 -wi-ao   4,91G
  vz   ovz01 -wi-ao 443,19G
[root at ovz01 ~]# vgs
  VG    #PV #LV #SN Attr   VSize   VFree
  ovz01   1   4   0 wz--n- 454,09G 672,00M
[root at ovz01 ~]#

I think, it's bad regexp in get_lvm_device() or get_lvm_mapping.
Sorry, don't have skill of developing of Perl (i'm love Python and
bash :)) ), and don't may send patch.


2010/2/16 Dietmar Maurer <dietmar at proxmox.com>:
>> when i start my container i got an error "Unable to open pty: No such
>> file or directory."
>>
>> I tried to fix it with the following:
>>
>> - - copied /dev from a working comtainer
>> - - vzctl exec 600 update-rc.d -f udev remove
>> - - vzctl exec 600 'dpkg --force-depends --purge udev'
>>
>> - - vzctl exec 600 /sbin/MAKEDEV tty
>> - - vzctl exec 600 /sbin/MAKEDEV pty => /sbin/MAKEDEV: warning: can't
>> read
>> /proc/devices
>>
>> Copied /proc/devices from the hn to vm.
>> No error, but still does not work.
>>
>> The problems started after a dist upgrade in the vm from ubuntu 8.04.4
>> to 9.10.
>>
>> Any ideas ?
>
> Try to run MAKEDEV on the host (cd /var/lib/vz/private/...).
>
> ubuntu 9.10 is not very container friendly :-/
>
> - Dietmar
>
>
>
> _______________________________________________
> Users mailing list
> Users at openvz.org
> https://openvz.org/mailman/listinfo/users
>



-- 
Galina Lisovskaya



More information about the Users mailing list