[SOLVED] Don't work interface

[JesusM]

pveversion -v



i try update and upgrade and don't work after reboot the system. (because when try update in interface don't work)

The problem occurred since the interface update from the updates that had, since the interfez not working.
The update did not work because novnc (console)

How can fix the problem?

Thanks

 

[t.lamprecht]

So the update didn't finished successful?
Log in to your host (via ssh) and rerun:

apt-get update
apt-get dist-upgrade
# and eventually
apt-get install --reinstall pve-manager

 

[JesusM]

we have some vms online
but the interface don't work

root@xxxx:~# apt-get update
Des:1 http://download.proxmox.com wheezy Release.gpg [198 B]
Des:2 http://download.proxmox.com wheezy Release [3.083 B]
Obj http://download.proxmox.com wheezy/pve-no-subscription amd64 Packages
Ign http://download.proxmox.com wheezy/pve-no-subscription Translation-es_ES
Ign http://download.proxmox.com wheezy/pve-no-subscription Translation-es
Ign http://download.proxmox.com wheezy/pve-no-subscription Translation-en
Ign https://enterprise.proxmox.com wheezy Release.gpg
Ign https://enterprise.proxmox.com wheezy Release
Err https://enterprise.proxmox.com wheezy/pve-enterprise amd64 Packages
The requested URL returned error: 401
Ign https://enterprise.proxmox.com wheezy/pve-enterprise Translation-es_ES
Ign https://enterprise.proxmox.com wheezy/pve-enterprise Translation-es
Ign https://enterprise.proxmox.com wheezy/pve-enterprise Translation-en
Obj http://ftp.debian.org wheezy Release.gpg
Obj http://security.debian.org wheezy/updates Release.gpg
Obj http://ftp.debian.org wheezy Release
Obj http://security.debian.org wheezy/updates Release
Obj http://ftp.debian.org wheezy/main amd64 Packages
Obj http://security.debian.org wheezy/updates/main amd64 Packages
Obj http://ftp.debian.org wheezy/contrib amd64 Packages
Obj http://security.debian.org wheezy/updates/contrib amd64 Packages
Obj http://security.debian.org wheezy/updates/contrib Translation-en
Obj http://ftp.debian.org wheezy/contrib Translation-en
Obj http://security.debian.org wheezy/updates/main Translation-en
Obj http://ftp.debian.org wheezy/main Translation-es
Obj http://ftp.debian.org wheezy/main Translation-en
Descargados 3.281 B en 1min. 3seg. (51 B/s)
W: Imposible obtener https://enterprise.proxmox.com/debian/dists/wheezy/pve-enterprise/binary-amd64/Packages The requested URL returned error: 401


E: Some index files failed to download. They have been ignored, or old ones used instead.

root@xxxxx:~# apt-get dist-upgradeLeyendo lista de paquetes... Hecho
Creando árbol de dependencias
Leyendo la información de estado... Hecho
Calculando la actualización... Listo
0 actualizados, 0 se instalarán, 0 para eliminar y 0 no actualizados.

Logs

root@xxxx:~# cat /var/log/kern.logAug 16 18:53:27 ns343478 kernel: vmbr0: port 5(tap104i0) entering disabled state
Aug 16 18:56:37 ns343478 kernel: device tap106i0 entered promiscuous mode
Aug 16 18:56:37 ns343478 kernel: vmbr0: port 5(tap106i0) entering forwarding state
Aug 16 18:56:37 ns343478 kernel: HTB: quantum of class 10001 is big. Consider r2q change.
Aug 16 18:56:48 ns343478 kernel: tap106i0: no IPv6 routers present
Aug 16 19:36:45 ns343478 kernel: waiting module removal not supported: please upgrade
Aug 16 19:36:45 ns343478 kernel: waiting module removal not supported: please upgrade
Aug 16 19:36:45 ns343478 kernel: waiting module removal not supported: please upgrade
Aug 16 19:36:46 ns343478 kernel: waiting module removal not supported: please upgrade
Aug 16 19:36:46 ns343478 kernel: waiting module removal not supported: please upgrade
Aug 16 19:36:46 ns343478 kernel: waiting module removal not supported: please upgrade
Aug 16 19:36:46 ns343478 kernel: waiting module removal not supported: please upgrade
Aug 16 19:36:46 ns343478 kernel: waiting module removal not supported: please upgrade

 

[t.lamprecht]

What does

apt-get install --reinstall pve-manager

say?

Maybe take also a look at http://forum.proxmox.com/threads/21...)-leading-to-not-correctly-installed-packages
pveversion -v says your on 3.3 but latest stable is 3.4, so you should get some updates.

 

[JesusM]

What does

apt-get install --reinstall pve-manager

say?

Maybe take also a look at http://forum.proxmox.com/threads/21...)-leading-to-not-correctly-installed-packages
pveversion -v says your on 3.3 but latest stable is 3.4, so you should get some updates.

Now

root@xxxx:~# pveversion -vproxmox-ve-2.6.32: 3.4-160 (running kernel: 2.6.32-34-pve)
pve-manager: 3.4-9 (running version: 3.4-9/4b51d87a)
pve-kernel-2.6.32-40-pve: 2.6.32-160
pve-kernel-2.6.32-32-pve: 2.6.32-136
pve-kernel-2.6.32-34-pve: 2.6.32-140
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-3
pve-cluster: 3.0-18
qemu-server: 3.4-6
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-33
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-11
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

But the interface don't work.
If we reinstall pve-manager the vms is stopped or lose?

 

[t.lamprecht]

No, VMs won't get lost and normally also won't get stopped.

 

[JesusM]

Now see

root@xxxxx:~# apt-get install --reinstall pve-manager
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias
Leyendo la información de estado... Hecho
0 actualizados, 0 se instalarán, 1 reinstalados, 0 para eliminar y 0 no actualizados.
Se necesita descargar 0 B/3.880 kB de archivos.
Se utilizarán 0 B de espacio de disco adicional después de esta operación.
Preconfigurando paquetes ...
(Leyendo la base de datos ... 42805 ficheros o directorios instalados actualmente.)
Preparando para reemplazar pve-manager 3.4-9 (usando .../pve-manager_3.4-9_amd64.deb) ...
Desempaquetando el reemplazo de pve-manager ...
Procesando disparadores para pve-firewall ...
invoke-rc.d: -----------------------------------------------------
invoke-rc.d: WARNING: 'invoke-rc.d pve-firewall restart' called
invoke-rc.d: during shutdown sequence.
invoke-rc.d: enabling safe mode: initscript policy layer disabled
invoke-rc.d: -----------------------------------------------------
Restarting Proxmox VE firewall: pve-firewallipcc_send_rec failed: Connection refused
ipcc_send_rec failed: Connection refused
ipcc_send_rec failed: Connection refused
.
Procesando disparadores para man-db ...
Configurando pve-manager (3.4-9) ...
invoke-rc.d: -----------------------------------------------------
invoke-rc.d: WARNING: 'invoke-rc.d pvedaemon restart' called
invoke-rc.d: during shutdown sequence.
invoke-rc.d: enabling safe mode: initscript policy layer disabled
invoke-rc.d: -----------------------------------------------------
Restarting PVE Daemon: pvedaemon.
invoke-rc.d: -----------------------------------------------------
invoke-rc.d: WARNING: 'invoke-rc.d pveproxy restart' called
invoke-rc.d: during shutdown sequence.
invoke-rc.d: enabling safe mode: initscript policy layer disabled
invoke-rc.d: -----------------------------------------------------
Restarting PVE API Proxy Server: pveproxy.
invoke-rc.d: -----------------------------------------------------
invoke-rc.d: WARNING: 'invoke-rc.d spiceproxy restart' called
invoke-rc.d: during shutdown sequence.
invoke-rc.d: enabling safe mode: initscript policy layer disabled
invoke-rc.d: -----------------------------------------------------
Restarting PVE SPICE Proxy Server: spiceproxy.
invoke-rc.d: -----------------------------------------------------
invoke-rc.d: WARNING: 'invoke-rc.d pvestatd restart' called
invoke-rc.d: during shutdown sequence.
invoke-rc.d: enabling safe mode: initscript policy layer disabled
invoke-rc.d: -----------------------------------------------------
Restarting PVE Status Daemon: pvestatdipcc_send_rec failed: Connection refused
ipcc_send_rec failed: Connection refused
ipcc_send_rec failed: Connection refused
.

 

[t.lamprecht]

Hmm, i used it few times to repair messed up packages, no problems yet, sorry about that.
Did you reboot your node after the upgrade to lates PVE?
what does:

pvecm stat
service pve-cluster restart
/etc/init.d/cman restart

say? VMs still running?

 

[JesusM]

Now work the interface but 1 vm is offline and can't start

Starting VM 102
trying to aquire lock... OK
Starting VM 102 failed: status
Starting VM 104
TASK OK

 

[t.lamprecht]

Nothing else in the log, an specific error?

qm unlock 102

Else use

qm showcmd 102

to get the command that gets executed and run it manual to look which error it throws.

 

[JesusM]

Thanks now is fix.

I put solved in the post.


EDIT: u can delete the images Attached Thumbnails?

 

[t.lamprecht]

Your welcome.

You should be able to edit your own posts and remove them yourself?