No access to the proxmox 6 web interface

[y7oel]

Esta mañana cuando ingresé a la consola web de mi servidor proxmox, ¡oh sorpresa! No se abrió, hay ping que las máquinas virtuales continúan funcionando pero no puedo acceder a / etc / pve, el ftp tampoco funciona. alguna solución.

root @ pve: / etc # cd pve
-bash: cd: pve: el punto final de transporte no está conectado

 

[Stefan_R]

Please keep conversations on this forum in english, so others can follow along

From what I can gather from your question it seems to be a network problem with your cluster? What does 'pvecm status' say? More info (again, in english please) would be necessary to diagnose further...

 

[y7oel]

Hello! thanks for answering
the code 'pvecm status' bring back:


root@pve:/# pvecm status
ipcc_send_rec[1] failed: Connection refused
ipcc_send_rec[2] failed: Connection refused
ipcc_send_rec[3] failed: Connection refused
Unable to load access control list: Connection refused

 

[Stefan_R]

Yeah, that looks like your network is down. Please check your network connectivity (e.g. ping between nodes/internet/etc...) and post relevant logs (e.g. 'journalctl -e', 'dmesg', etc...). Also, please post the output of 'pveversion -v'.

 

[y7oel]

Hello!

The cluster was already created, but there were no added nodes


PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=51 time=43.6 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=51 time=43.7 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=51 time=43.5 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=51 time=43.5 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=51 time=43.4 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=51 time=43.6 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=51 time=43.6 ms
^C
--- 8.8.8.8 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 16ms
rtt min/avg/max/mdev = 43.369/43.545/43.702/0.184 ms

dmesg
[1887600.216691] systemd-journald[584]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
[1887669.993635] EXT4-fs (dm-6): error count since last fsck: 4
[1887669.993655] EXT4-fs (dm-6): initial error at time 1589219213: ext4_journal_check_start:61
[1887669.993662] EXT4-fs (dm-6): last error at time 1589219215: ext4_discard_preallocations:4067
[1887669.993676] EXT4-fs: 2 callbacks suppressed
[1887669.993687] EXT4-fs (dm-11): error count since last fsck: 6
[1887669.993695] EXT4-fs (dm-11): initial error at time 1589219214: kmmpd:177
[1887669.993703] EXT4-fs (dm-11): last error at time 1589219215: ext4_journal_check_start:61
[1887690.507335] systemd-journald[584]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
[1887781.139864] systemd-journald[584]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
[1887871.777120] systemd-journald[584]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
[1887962.411152] systemd-journald[584]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
[1888053.046580] systemd-journald[584]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
[1888143.679273] systemd-journald[584]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
[1888234.317525] systemd-journald[584]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected

journalctl -e

May 13 20:55:57 pve pveproxy[13618]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key)
May 13 20:56:01 pve cron[1559]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
May 13 20:56:02 pve pveproxy[13617]: worker exit
May 13 20:56:02 pve pveproxy[1613]: worker 13617 finished
May 13 20:56:02 pve pveproxy[1613]: starting 2 worker(s)
May 13 20:56:02 pve pveproxy[1613]: worker 13620 started
May 13 20:56:02 pve pveproxy[1613]: worker 13621 started
May 13 20:56:02 pve pveproxy[13620]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key)
May 13 20:56:02 pve pveproxy[13621]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key)
May 13 20:56:02 pve pveproxy[13618]: worker exit
May 13 20:56:02 pve pveproxy[1613]: worker 13618 finished
May 13 20:56:02 pve pveproxy[1613]: starting 1 worker(s)
May 13 20:56:02 pve pveproxy[1613]: worker 13622 started
May 13 20:56:02 pve pveproxy[13622]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key)
May 13 20:56:07 pve pveproxy[13620]: worker exit
May 13 20:56:07 pve pveproxy[13621]: worker exit
May 13 20:56:07 pve pveproxy[1613]: worker 13620 finished
May 13 20:56:07 pve pveproxy[1613]: starting 1 worker(s)
May 13 20:56:07 pve pveproxy[1613]: worker 13621 finished
May 13 20:56:07 pve pveproxy[1613]: worker 13625 started
May 13 20:56:07 pve pveproxy[13625]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key)
May 13 20:56:07 pve pveproxy[13622]: worker exit
May 13 20:56:07 pve pveproxy[1613]: worker 13622 finished
May 13 20:56:07 pve pveproxy[1613]: starting 2 worker(s)
May 13 20:56:07 pve pveproxy[1613]: worker 13626 started
May 13 20:56:07 pve pveproxy[1613]: worker 13627 started
May 13 20:56:07 pve pveproxy[13626]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key)
May 13 20:56:07 pve pveproxy[13627]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key)

pveversion -v

proxmox-ve: 6.1-2 (running kernel: 5.3.10-1-pve)
pve-manager: 6.1-3 (running version: 6.1-3/37248ce6)
pve-kernel-5.3: 6.0-12
pve-kernel-helper: 6.0-12
pve-kernel-5.3.10-1-pve: 5.3.10-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.2-pve4
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.13-pve1
libpve-access-control: 6.0-5
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-9
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-3
libpve-storage-perl: 6.1-2
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve3
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-1
pve-cluster: 6.1-2
pve-container: 3.0-14
pve-docs: 6.1-3
pve-edk2-firmware: 2.20191002-1
pve-firewall: 4.0-9
pve-firmware: 3.0-4
pve-ha-manager: 3.0-8
pve-i18n: 2.0-3
pve-qemu-kvm: 4.1.1-2
pve-xtermjs: 3.13.2-1
qemu-server: 6.1-2
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.2-pve2

 

[Stefan_R]

The cluster was already created, but there were no added nodes

So this is on a single node cluster?

Maybe a silly solution, but looking at your current uptime in the logs, have you tried rebooting? Potentially also do a full upgrade, you might be missing some fixes from newer package versions.

 

[y7oel]

Hi. I was absolutely right I restarted it and ran. As the server is in production, just today I was able to restart it. Thanks for your attention...