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

J

jamesbond07

New Member
Aug 24, 2026
3
0
1
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
Bash: 
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

Bash: 
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
Bash: 
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

Bash: 
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
Bash: 
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
Bash: 
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

Bash: 
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.
 
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.
 
  • Like
Reactions: jamesbond07
fba said:
The output of
  • ip a andcat /etc/network/interfaces of proxmox01 and
  • cat /etc/pve/firewall/cluster.fw would be helpful too.
Click to expand...
Here you have the info:

proxmox01
Bash: 
root@proxmox01:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbr0 state UP group default qlen 1000
    link/ether e8:ff:1e:da:d9:9e brd ff:ff:ff:ff:ff:ff
    altname enxe8ff1edad99e
3: wlo1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether dc:90:09:5d:4f:12 brd ff:ff:ff:ff:ff:ff
    altname wlp0s20f3
    altname wlxdc90095d4f12
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether e8:ff:1e:da:d9:9e brd ff:ff:ff:ff:ff:ff
    inet 192.168.5.10/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::eaff:1eff:feda:d99e/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever
5: veth100i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr100i0 state UP group default qlen 1000
    link/ether fe:a5:32:20:d8:ac brd ff:ff:ff:ff:ff:ff link-netnsid 0
6: fwbr100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 9e:d0:28:de:21:46 brd ff:ff:ff:ff:ff:ff
7: fwpr100p0@fwln100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 92:2c:e2:14:d0:24 brd ff:ff:ff:ff:ff:ff
8: fwln100i0@fwpr100p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr100i0 state UP group default qlen 1000
    link/ether 9e:d0:28:de:21:46 brd ff:ff:ff:ff:ff:ff

Bash: 
root@proxmox01:~# cat /etc/network/interfaces                                                                                                                            
auto lo                                                                                                                                                                  
iface lo inet loopback                                                                                                                                                                                                                                             
iface enp1s0 inet manual                                                                                                                                                 
auto vmbr0                                                                                                                                                               
iface vmbr0 inet static                                                                                                                                                  
        address 192.168.5.10/24                                                                                                                                          
        gateway 192.168.5.1                                                                                                                                              
        bridge-ports enp1s0                                                                                                                                              
        bridge-stp off                                                                                                                                                   
        bridge-fd 0                                                                                                                                                      
iface wlo1 inet manual                                                                                                                                                   
source /etc/network/interfaces.d/*

There is no cluster.fw file or other files (both machines).
Bash: 
root@proxmox01:~# ls -la /etc/pve/firewall/                                                                                                                              
total 0                                                                                                                                                                  
drwxr-xr-x 2 root www-data 0 Jan 12  2026 .                                                                                                                              
drwxr-xr-x 2 root www-data 0 Jan  1  1970 ..

Thank you for your help.
 
smobbs said:
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.
Click to expand...

Hi.
Both machines are in a VLAN where 192.168.5.1 is the gateway.
I'll try to check if there is something blocking even though the VLAN/gateway servers both machines.
Thank you.
 
192.168.5.1 is in the same subnet as your node, pinging it involves no routing. Two possibilities: ARP for .1 isn't completing, or it is and something is dropping the ICMP.

On proxmox01:
ip -4 neigh show
ip r

Then in one session run this, and ping 192.168.5.1 from another:
tcpdump -ni vmbr0 arp or icmp

Also useful if you can post:

cat /etc/pve/nodes/proxmox01/host.fw
pve-firewall status
ip a and ip r from proxmox02, for comparison
 
You must log in or register to reply here.
Top Bottom
Back