After a power loss I am no longer able to access the web GUI.
VIMs are up and running, SSH access is available, but GUI will not respond.
Server has 2 IP addresses. Eg. 10.1.1.5 with default gateway and eg. 10.10.0.5. I am trying to connect from 10.10.0.x myself so a direct layer 2 connection.
Connecting to 10.10.1.5 address (through FW) also times out.
Browsers throw up "connection has timed out". Tested firefox and chrome. Also tested incognito mode to rule out cache.
Running
Restarting the server
It seems some commands hang up the SSH session too. Eg. I simply can not run
Looking closer at this output I can see nothing wrong with it.
Likewise for 10.10.1.5.
Well.. I am no ProxmoxVE specialist, but the above seems pretty darn weird to me.
Hopefully someone here can help me fix this issue?
VIMs are up and running, SSH access is available, but GUI will not respond.
Server has 2 IP addresses. Eg. 10.1.1.5 with default gateway and eg. 10.10.0.5. I am trying to connect from 10.10.0.x myself so a direct layer 2 connection.
Connecting to 10.10.1.5 address (through FW) also times out.
Bash:
# pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.15.74-1-pve)
pve-manager: 7.2-11 (running version: 7.2-11/b76d3178)
pve-kernel-5.15: 7.2-14
pve-kernel-helper: 7.2-14
pve-kernel-5.13: 7.1-9
pve-kernel-5.11: 7.0-10
pve-kernel-5.15.74-1-pve: 5.15.74-1
pve-kernel-5.15.35-3-pve: 5.15.35-6
pve-kernel-5.15.35-1-pve: 5.15.35-3
pve-kernel-5.15.30-2-pve: 5.15.30-3
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-1-pve: 5.13.19-3
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-5-pve: 5.11.22-10
pve-kernel-5.11.22-4-pve: 5.11.22-9
ceph-fuse: 15.2.14-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-4
libpve-guest-common-perl: 4.1-4
libpve-http-server-perl: 4.1-5
libpve-storage-perl: 7.2-10
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.7-1
proxmox-backup-file-restore: 2.2.7-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-2
pve-container: 4.2-3
pve-docs: 7.2-2
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-6
pve-firmware: 3.5-6
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 7.0.0-4
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-5
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+2
vncterm: 1.7-1
zfsutils-linux: 2.1.6-pve1
Browsers throw up "connection has timed out". Tested firefox and chrome. Also tested incognito mode to rule out cache.
Running
# service pveproxy restart
does not help.Restarting the server
systemctl reboot
did not help eitherjournalctl -f
does not give any useful infoIt seems some commands hang up the SSH session too. Eg. I simply can not run
cat /etc/network/interfaces
without locking up the SSH session? If I try using nano to view the same / cat /etc/network/interfaces
it says [ Read 81 lines ] but displays less (how many varies) than that and again freezes the SSH session. Doing a more /etc/network/interfaces
does give the correct and complete output... WEIRD.Looking closer at this output I can see nothing wrong with it.
Bash:
nmap -p 8006 10.10.0.5
Starting Nmap 7.80 ( https://nmap.org ) at 2022-12-08 06:08 CET
Nmap scan report for 10.10.0.5
Host is up (0.000035s latency).
PORT STATE SERVICE
8006/tcp open wpl-analytics
Nmap done: 1 IP address (1 host up) scanned in 0.09 seconds
Well.. I am no ProxmoxVE specialist, but the above seems pretty darn weird to me.
Hopefully someone here can help me fix this issue?