Mis saludos;
actualizo mi Proxmox 4 desde http://download.jovenclub.cu/repos/proxmox-ve/
en la sección pve-no-subscription y hasta ahor ano he tenido problemas, pero
luego de la actualización que hice hoy todos los contenedores dejaron de
trabajar (todos están apagados) y ninguno inicia. La maquina virtual que tengo
si está trabajando sin problemas; fueron los contenedores (de CentOS7)
Esta es la traza de los paquetes que actualizó (según /var/log/aptitude):
Aptitude 0.6.11: log report
Thu, Dec 10 2015 10:31:43 -0500
IMPORTANT: this log only lists intended actions; actions which fail due to
dpkg problems may not be completed.
Will install 22 packages, and remove 0 packages.
2,270 kB of disk space will be used
===============================================================================
[INSTALL, DEPENDENCIES] pve-kernel-4.2.6-1-pve:amd64
[HOLD] libpve-common-perl:amd64
[UPGRADE] corosync-pve:amd64 2.3.5-1 -> 2.3.5-2
[UPGRADE] dmeventd:amd64 2:1.02.93-pve1 -> 2:1.02.93-pve2
[UPGRADE] dmsetup:amd64 2:1.02.93-pve1 -> 2:1.02.93-pve2
[UPGRADE] libcorosync4-pve:amd64 2.3.5-1 -> 2.3.5-2
[UPGRADE] libdevmapper-event1.02.1:amd64 2:1.02.93-pve1 -> 2:1.02.93-pve2
[UPGRADE] libdevmapper1.02.1:amd64 2:1.02.93-pve1 -> 2:1.02.93-pve2
[UPGRADE] liblvm2app2.2:amd64 2.02.116-pve1 -> 2.02.116-pve2
[UPGRADE] liblvm2cmd2.02:amd64 2.02.116-pve1 -> 2.02.116-pve2
[UPGRADE] libpve-access-control:amd64 4.0-9 -> 4.0-10
[UPGRADE] libpve-storage-perl:amd64 4.0-29 -> 4.0-37
[UPGRADE] lvm2:amd64 2.02.116-pve1 -> 2.02.116-pve2
[UPGRADE] lxc-pve:amd64 1.1.4-3 -> 1.1.5-5
[UPGRADE] lxcfs:amd64 0.10-pve2 -> 0.13-pve1
[UPGRADE] proxmox-ve:amd64 4.0-22 -> 4.1-25
[UPGRADE] pve-cluster:amd64 4.0-24 -> 4.0-29
[UPGRADE] pve-container:amd64 1.0-21 -> 1.0-32
[UPGRADE] pve-firewall:amd64 2.0-13 -> 2.0-14
[UPGRADE] pve-ha-manager:amd64 1.0-13 -> 1.0-14
[UPGRADE] pve-manager:amd64 4.0-57 -> 4.0-64
[UPGRADE] pve-qemu-kvm:amd64 2.4-12 -> 2.4-16
[UPGRADE] qemu-server:amd64 4.0-35 -> 4.0-39
===============================================================================
Log complete.
Cuando hago un lxc-start -n # -F tengo un error como este (que no entiendo
nada)
root@proxmox:~# lxc-start -n 100 -F
Undefined subroutine &PVE::Network::is_ip_in_cidr called at
/usr/share/perl5/PVE/LXC/Setup/Redhat.pm line 203.
error in setup task PVE::LXC::Setup::pre_start_hook
lxc-start: conf.c: run_buffer: 342 Script exited with status 1
lxc-start: start.c: lxc_init: 436 failed to run pre-start hooks for container
'100'.
lxc-start: start.c: __lxc_start: 1170 failed to initialize the container
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by
setting the --logfile and --logpriority options.
Si uso una salva de algún contenedor me da error a la hora de restaurarla;
aquí lo que me dan las trazas:
Formatting '/var/lib/vz/almacenamiento/images/102/vm-102-disk-1.raw', fmt=raw
size=42949672960
mke2fs 1.42.12 (29-Aug-2014)
Discarding device blocks: 4096/10485760 done
Creating filesystem with 10485760 4k blocks and 2621440 inodes
Filesystem UUID: e1333059-3acb-441d-9906-5c073ade9ac0
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624
Allocating group tables: 0/320 done
Writing inode tables: 0/320 done
Creating journal (32768 blocks): done
Multiple mount protection is enabled with update interval 5 seconds.
Writing superblocks and filesystem accounting information: 0/320 done
TASK ERROR: invalid key: type at /usr/share/perl5/PVE/JSONSchema.pm line 581.
Que mas puedo hacer? o que puede estar sucediendo?
La actualización fastidió todos mis contenedores?
--
Rommel Rodriguez Toirac
Administrador de red ONAT Guantánamo
Teléfono (pizarra): 327444,326625,326376,327677,326576
Extensión: 120
______________________________________________________________________
Lista de correos del Grupo de Usuarios de Tecnologías Libres de Cuba.
Gutl-l@jovenclub.cu
https://listas.jovenclub.cu/cgi-bin/mailman/listinfo/gutl-l
