Error while updating

[Luciano Santos]

Has version 5.1.30 and when try to update to 5.2.10 just break web interface.

Try to use apt dist-upgrade, but doens't work.

Configurando pve-manager (5.2-10) ...
Job for pvestatd.service failed because the control process exited with error code.
See "systemctl status pvestatd.service" and "journalctl -xe" for details.
dpkg: erro ao processar o pacote pve-manager (--configure):
sub-processo script post-installation instalado retornou estado de saída de erro 1
dpkg: problemas com dependências impedem a configuração de proxmox-ve:
proxmox-ve depende de pve-manager; porém:
Pacote pve-manager não está configurado ainda.

dpkg: erro ao processar o pacote proxmox-ve (--configure):
problemas de dependência - deixando desconfigurado
Erros foram encontrados durante o processamento de:
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)​

 

[dcsapak]

See "systemctl status pvestatd.service" and "journalctl -xe" for details.

what does it say?

 

[Luciano Santos]

That's the reply:

● pvestatd.service - PVE Status Daemon
Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled)
Active: active (running) (Result: exit-code) since Thu 2018-05-24 05:32:00 -03; 5 months 21 days ago
Process: 15985 ExecReload=/usr/bin/pvestatd restart (code=exited, status=111)
Main PID: 1897 (pvestatd)
Tasks: 1 (limit: 4915)
Memory: 84.2M
CPU: 1d 10h 57min 40.120s
CGroup: /system.slice/pvestatd.service
└─1897 pvestatd

nov 13 13:15:24 pxmx-uno pvestatd[1897]: ipcc_send_rec[1] failed: Connection refused
nov 13 13:15:24 pxmx-uno pvestatd[1897]: ipcc_send_rec[2] failed: Connection refused
nov 13 13:15:24 pxmx-uno pvestatd[1897]: ipcc_send_rec[3] failed: Connection refused
nov 13 13:15:24 pxmx-uno pvestatd[1897]: ipcc_send_rec[4] failed: Connection refused
nov 13 13:15:24 pxmx-uno pvestatd[1897]: status update error: Connection refused
nov 13 13:15:34 pxmx-uno pvestatd[1897]: ipcc_send_rec[1] failed: Connection refused
nov 13 13:15:34 pxmx-uno pvestatd[1897]: ipcc_send_rec[2] failed: Connection refused
nov 13 13:15:34 pxmx-uno pvestatd[1897]: ipcc_send_rec[3] failed: Connection refused
nov 13 13:15:34 pxmx-uno pvestatd[1897]: ipcc_send_rec[4] failed: Connection refused
nov 13 13:15:34 pxmx-uno pvestatd[1897]: status update error: Connection refused​

 

[dcsapak]

is 'pve-cluster' running?

 

[Luciano Santos]

No! It's a standalone instalation.

root@pxmx-uno:~# ps axf | grep cluster
19431 pts/0 S+ 0:00 \_ grep cluster
​

 

[dcsapak]

pve-cluster is a service that must always run, since it provides the pmxcfs where all vm/ct configs are saved

what does 'systemctl status pve-cluster' say?

 

[Luciano Santos]

The cluster service was stopped.

root@pxmx-uno:~# systemctl start pve-cluster
Job for pve-cluster.service failed because the control process exited with error code.
See "systemctl status pve-cluster.service" and "journalctl -xe" for details.
root@pxmx-uno:~# systemctl status pve-cluster
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2018-11-13 13:46:37 -02; 3s ago
Process: 20664 ExecStart=/usr/bin/pmxcfs (code=exited, status=255)
Main PID: 1807 (code=killed, signal=KILL)
CPU: 10ms

nov 13 13:46:37 pxmx-uno systemd[1]: Starting The Proxmox VE cluster filesystem...
nov 13 13:46:37 pxmx-uno pmxcfs[20664]: [main] crit: Unable to get local IP address
nov 13 13:46:37 pxmx-uno systemd[1]: pve-cluster.service: Control process exited, code=exited status=255
nov 13 13:46:37 pxmx-uno systemd[1]: Failed to start The Proxmox VE cluster filesystem.
nov 13 13:46:37 pxmx-uno systemd[1]: pve-cluster.service: Unit entered failed state.
nov 13 13:46:37 pxmx-uno systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
​

This box had the hostname changed. I rollback the hostname and the pve-cluster service started.

root@pxmx-uno:~# systemctl start pve-cluster
root@pxmx-uno:~# systemctl status pve-cluster
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2018-11-13 13:48:00 -02; 1s ago
Process: 20849 ExecStartPost=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
Process: 20825 ExecStart=/usr/bin/pmxcfs (code=exited, status=0/SUCCESS)
Main PID: 20836 (pmxcfs)
Tasks: 5 (limit: 4915)
Memory: 4.0M
CPU: 446ms
CGroup: /system.slice/pve-cluster.service
└─20836 /usr/bin/pmxcfs

nov 13 13:47:59 server1 systemd[1]: Starting The Proxmox VE cluster filesystem...
nov 13 13:48:00 server1 systemd[1]: Started The Proxmox VE cluster filesystem.
​

Then tried again to upgrade, but have an alert that apt do not make all changes:

root@pxmx-uno:~# apt-get upgrade
Lendo listas de pacotes... Pronto
Construindo árvore de dependências
Lendo informação de estado... Pronto
Calculando atualização... Pronto
0 pacotes atualizados, 0 pacotes novos instalados, 0 a serem removidos e 0 não atualizados.
2 pacotes não totalmente instalados ou removidos.
Depois desta operação, 0 B adicionais de espaço em disco serão usados.
Você quer continuar? [S/n] S
Configurando pve-manager (5.2-10) ...
Configurando proxmox-ve (5.2-2) ...
W: APT had planned for dpkg to do more than it reported back (3 vs 7).
Affected packages: pve-manager:amd64

​

Restarted the pvestatd:

root@pxmx-uno:~# systemctl status pvestatd​

● pvestatd.service - PVE Status Daemon
Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2018-11-13 13:55:05 -02; 1s ago
Process: 22171 ExecStop=/usr/bin/pvestatd stop (code=exited, status=0/SUCCESS)
Process: 20962 ExecReload=/usr/bin/pvestatd restart (code=exited, status=0/SUCCESS)
Process: 22179 ExecStart=/usr/bin/pvestatd start (code=exited, status=0/SUCCESS)
Main PID: 22205 (pvestatd)
Tasks: 1 (limit: 4915)
Memory: 66.5M
CPU: 631ms
CGroup: /system.slice/pvestatd.service
└─22205 pvestatd

nov 13 13:55:04 server1 systemd[1]: Starting PVE Status Daemon...
nov 13 13:55:05 server1 pvestatd[22205]: starting server
nov 13 13:55:05 server1 systemd[1]: Started PVE Status Daemon.

But still without web interface. Thanks for the support until now.

​

 

[Luciano Santos]

How can I debug the web interface? Or reinstall the proxmox-ve?

 

[dcsapak]

what does 'systemctl status pveproxy pvedaemon' say?
what does 'ss -tlpn' say?

 

[Luciano Santos]

what does 'systemctl status pveproxy pvedaemon' say?
what does 'ss -tlpn' say?

Thanks, @dcsapak ! Was the pveproxy that was stopped. Just restarted and the web access was restored.

 

[antton]

Hi I'm having the same problem, and my /etc/pve/ folder files dissapear after reboot. At the same time something rename my servername to ubuntu2 and the only thing I was using with this name was the new cloud-init service.

Any ideas what's going on?

 

[mira]

Did you install and start cloud-init on your host instead of a VM?

 

[Luciano Santos]

Hi I'm having the same problem, and my /etc/pve/ folder files dissapear after reboot. At the same time something rename my servername to ubuntu2 and the only thing I was using with this name was the new cloud-init service.

Any ideas what's going on?

But your PROXMOX doesn't run under Debian?

If you use cloud-init, is need to change a parameter to set hostname persistently. Is the /etc/cloud/cloud.cfg file, and you need to change the preserver_hostname directive to true, as:

preserve_hostname: true​

Try to reconfigure the old hostname with:

hostnamectl set-hostname YOURHOSTNAME
​

 

[antton]

Did you install and start cloud-init on your host instead of a VM?

That's what I did And the problem was that.

I remove cloud-init from the proxmox server and then add again my IP on /etc/hosts change the hostname and add pve and pvelocalhost on the same file and reboot.

now everything is working fine! And I learn where not install cloud-init package

Thanks!