[SOLVED] how to debug proxmox not being responsive

[hengly]

hello, I have been running proxmox on-premises for my company for just little over a year and I have this issue happens after I move the servers to another office location. Everything is working fine for few days after office moving then proxmox starting to become un-responsive, first I tried rebooting, then It just resolve itself eventually then the rebooting trick stopped working as well(It still works I think but seems to be requiring luck, but now 90% of the time does not work), I tried checking `pve-cluster`, `pvedaemon`, `pveproxy` and `corosync` those services look fine on all node sometime, sometime `pveproxy` shows `client problem, connection reset by peer` but networking seems fine and no firewall seems to be blocking, I can reach the proxmox web ui but not able to login, it just hanging there after enter the credential and timeout eventually and running `pvecm updatecerts -f` always result in `got timeout`.

The new office location already have networking setup, so the proxmox servers just connecting to another vlan with same ip cidr, ssh between each proxmox nodes is working fine, when proxmox is working, communication between nodes and each vm itself also fine, I can also access to services within vm from outside using public ip fine, except I notice an issue, all vm created within promox before now has wrong default route, eventhou I check the config from `/etc/network/interfaces` it looks like it is correct but vm gets the wrong one but I add the default route in manually afterward and it solve the issues but anyway those are issue that I notice after moving to new office which before does not happened.

so currently I am not sure how to debug and fix this issue so I any advice would be appreciated, and thanks for your time reading this.

 

[hengly]

so I managed to pinpoint the problem, althou pinging ip address of each proxmox node works, but the hostname does not, so I added each host to each proxmox /etc/hosts and now it is all working fine, except that the default gateway within vm is still wrong, it is showing differently from what has configured on the bridge network why is that?

# one of proxmox host
# cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface eno2 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.88.61/24
        gateway 192.168.88.1
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0

# one of VM
# ip route
default via 192.168.1.14 dev ens18 proto dhcp src 192.168.88.20 metric 100
192.168.1.14 dev ens18 proto dhcp scope link src 192.168.88.20 metric 100
192.168.88.0/24 dev ens18 proto kernel scope link src 192.168.88.20 metric 100

 

[leesteken]

so I managed to pinpoint the problem, althou pinging ip address of each proxmox node works, but the hostname does not, so I added each host to each proxmox /etc/hosts and now it is all working fine

I don't have much experience with this but I thought this was a requirement but I could be wrong.

, except that the default gateway within vm is still wrong, it is showing differently from what has configured on the bridge network why is that?

Only network configurations of containers are (partially) managed by Proxmox. The network settings inside any VM are not under the control of Proxmox. Maybe you need to change them manually or change a setting on your DHCP server?

 

[hengly]

hello @leesteken , thanks for the reply, the issue is fixed now, this was a typo in default gateway address and it all working now once corrected