PVE 9.2.11 - Can't "apt update" in one machine only after "apt upgrade"

[jamesbond07]

Hi Everyone,

I'm pretty new on proxmox virtual environment.
I have a small cluster (only 2 small machines - yeah I know it should be three and I'm working on that).
A few weeks ago I logged in to the dash board and did an apt update/upgrade for this 2 machines in order to keep them up to date.
I didn't get any errors and the cluster is running OK.
Now I discovered one of the machines (proxmox01 - 192.168.5.10) is no more capable to update.
I didn't change any configurations in the machine and in the network.
The promox01 can not ping the router gateway, the main vlan address or any other address outside like 1.1.1.1 but it can ping the other node (proxmox02 - 192.168.5.11).

Ping the router gateway address

root@proxmox01:~# ping -c 3 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
--- 192.168.0.1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2059ms

root@proxmox02:~# ping -c 3 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.588 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=5.17 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=4.59 ms
--- 192.168.0.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2059ms
rtt min/avg/max/mdev = 0.588/3.451/5.171/2.038 ms

Ping the main vlan address

root@proxmox01:~# ping -c 3 192.168.5.1
PING 192.168.5.1 (192.168.5.1) 56(84) bytes of data.
--- 192.168.5.1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2032ms

root@proxmox02:~# ping -c 3 192.168.5.1
PING 192.168.5.1 (192.168.5.1) 56(84) bytes of data.
64 bytes from 192.168.5.1: icmp_seq=1 ttl=64 time=0.366 ms
64 bytes from 192.168.5.1: icmp_seq=2 ttl=64 time=0.468 ms
64 bytes from 192.168.5.1: icmp_seq=3 ttl=64 time=10.9 ms
--- 192.168.5.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2081ms
rtt min/avg/max/mdev = 0.366/3.926/10.946/4.963 ms
3 packets transmitted, 0 received, 100% packet loss, time 2032ms

Proxmox1 can reach Proxmox02

root@proxmox01:~# ping -c 3 192.168.5.11
PING 192.168.5.11 (192.168.5.11) 56(84) bytes of data.
64 bytes from 192.168.5.11: icmp_seq=1 ttl=64 time=0.745 ms
64 bytes from 192.168.5.11: icmp_seq=2 ttl=64 time=10.9 ms
64 bytes from 192.168.5.11: icmp_seq=3 ttl=64 time=3.60 ms
--- 192.168.5.11 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2047ms
rtt min/avg/max/mdev = 0.745/5.092/10.938/4.293 ms

Ping 1.1.1.1

root@proxmox01:~# ping -c 3 1.1.1.1    
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
--- 1.1.1.1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2069ms

root@proxmox02:~# ping -c 3 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=57 time=25.8 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=57 time=20.5 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=57 time=23.9 ms
--- 1.1.1.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 20.472/23.380/25.792/2.200 ms

As we can see just the proxmox01 machine has problems.
Could someone help me to put it working again?

Thank you in advance.
Regards.

 

[LnxBil]

Never do an apt upgrade
For anything else, there is not enough information to even speculate. We need logs, pveversion etc.

 

[Onslow]

did an apt update/upgrade

Don't do.
Do
apt update ; apt full-upgrade

 

[smobbs]

Given that you can ping your second node, I'll venture a guess that it's *probably* not an issue with your first node.

Check firewall rules/ACLs on whatever 192.168.5.1 is. If it has any sort of live log or traffic monitor, see if you can see traffic from your first node hitting it and getting dropped.

 

[fba]

The output of

• ip a andcat /etc/network/interfaces of proxmox01 and
• cat /etc/pve/firewall/cluster.fw would be helpful too.