randomly and repeatedly grey question mark and network issues

kisiel

New Member
May 13, 2023
17
0
1
Hi,
Something happened with my proxmox installation and i cannot find what is going on
generally works, the containers seem to be up
but the node and the containers are marked with grey question mark, then after a whole things go back to normal and again, and again

I assume that's something with the network as I see those weird messages in the syslog
including pve having random problems connecting to my influx

----
Nov 05 10:44:16 pve.xxx.tld sshd[2693644]: Received disconnect from 15.204.56.97 port 42664:11: Bye Bye [preauth]
Nov 05 10:44:16 pve.xxx.tld sshd[2693644]: Disconnected from authenticating user root 15.204.56.97 port 42664 [preauth]
Nov 05 10:44:16 pve.xxx.tld kernel: eth1: renamed from veth25ecac7
Nov 05 10:44:16 pve.xxx.tld kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth19e3e4b: link becomes ready
Nov 05 10:44:16 pve.xxx.tld kernel: br-a56c1f2c4a6a: port 4(veth19e3e4b) entered blocking state
Nov 05 10:44:16 pve.xxx.tld kernel: br-a56c1f2c4a6a: port 4(veth19e3e4b) entered forwarding state
Nov 05 10:44:17 pve.xxx.tld kernel: br-3ea8f01ddba1: port 1(veth22b1ac0) entered disabled state
Nov 05 10:44:17 pve.xxx.tld kernel: veth4e7a45c: renamed from eth0
Nov 05 10:44:17 pve.xxx.tld kernel: br-3ea8f01ddba1: port 1(veth22b1ac0) entered disabled state
Nov 05 10:44:17 pve.xxx.tld kernel: device veth22b1ac0 left promiscuous mode
Nov 05 10:44:17 pve.xxx.tld kernel: br-3ea8f01ddba1: port 1(veth22b1ac0) entered disabled state
Nov 05 10:44:17 pve.xxx.tld kernel: br-a56c1f2c4a6a: port 4(veth19e3e4b) entered disabled state
Nov 05 10:44:17 pve.xxx.tld kernel: veth25ecac7: renamed from eth1
Nov 05 10:44:17 pve.xxx.tld kernel: br-a56c1f2c4a6a: port 4(veth19e3e4b) entered disabled state
Nov 05 10:44:17 pve.xxx.tld kernel: device veth19e3e4b left promiscuous mode
Nov 05 10:44:17 pve.xxx.tld kernel: br-a56c1f2c4a6a: port 4(veth19e3e4b) entered disabled state
Nov 05 10:45:01 pve.xxx.tld CRON[2872575]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Nov 05 10:45:01 pve.xxx.tld CRON[2872684]: (root) CMD (which zfs-auto-snapshot > /dev/null || exit 0 ; zfs-auto-snapshot --quiet --syslog --label=frequent --keep=8 //)
Nov 05 10:45:01 pve.xxx.tld CRON[2872573]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Nov 05 10:45:01 pve.xxx.tld CRON[2872811]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Nov 05 10:45:01 pve.xxx.tld CRON[2872573]: pam_unix(cron:session): session closed for user root
Nov 05 10:45:11 pve.xxx.tld zfs-auto-snap[2905105]: @zfs-auto-snap_frequent-2023-11-05-1045, 3 created, 3 destroyed, 0 warnings.
Nov 05 10:45:11 pve.xxx.tld CRON[2872575]: pam_unix(cron:session): session closed for user root
Nov 05 10:45:17 pve.xxx.tld kernel: br-3ea8f01ddba1: port 1(vetha9ef89c) entered blocking state
Nov 05 10:45:17 pve.xxx.tld kernel: br-3ea8f01ddba1: port 1(vetha9ef89c) entered disabled state
Nov 05 10:45:17 pve.xxx.tld kernel: device vetha9ef89c entered promiscuous mode
Nov 05 10:45:17 pve.xxx.tld kernel: br-a56c1f2c4a6a: port 4(veth4f2f6cb) entered blocking state
Nov 05 10:45:17 pve.xxx.tld kernel: br-a56c1f2c4a6a: port 4(veth4f2f6cb) entered disabled state
Nov 05 10:45:17 pve.xxx.tld kernel: device veth4f2f6cb entered promiscuous mode
Nov 05 10:45:17 pve.xxx.tld kernel: br-a56c1f2c4a6a: port 4(veth4f2f6cb) entered blocking state
Nov 05 10:45:17 pve.xxx.tld kernel: br-a56c1f2c4a6a: port 4(veth4f2f6cb) entered forwarding state
Nov 05 10:45:17 pve.xxx.tld kernel: eth0: renamed from vethaf73c0a
Nov 05 10:45:17 pve.xxx.tld kernel: eth1: renamed from veth466815f
Nov 05 10:45:17 pve.xxx.tld kernel: br-a56c1f2c4a6a: port 4(veth4f2f6cb) entered disabled state
Nov 05 10:45:17 pve.xxx.tld kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vetha9ef89c: link becomes ready
Nov 05 10:45:17 pve.xxx.tld kernel: br-3ea8f01ddba1: port 1(vetha9ef89c) entered blocking state
Nov 05 10:45:17 pve.xxx.tld kernel: br-3ea8f01ddba1: port 1(vetha9ef89c) entered forwarding state
Nov 05 10:45:17 pve.xxx.tld kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth4f2f6cb: link becomes ready
Nov 05 10:45:17 pve.xxx.tld kernel: br-a56c1f2c4a6a: port 4(veth4f2f6cb) entered blocking state
Nov 05 10:45:17 pve.xxx.tld kernel: br-a56c1f2c4a6a: port 4(veth4f2f6cb) entered forwarding state
Nov 05 10:45:18 pve.xxx.tld kernel: br-3ea8f01ddba1: port 1(vetha9ef89c) entered disabled state
Nov 05 10:45:18 pve.xxx.tld kernel: vethaf73c0a: renamed from eth0
Nov 05 10:45:18 pve.xxx.tld kernel: br-3ea8f01ddba1: port 1(vetha9ef89c) entered disabled state
Nov 05 10:45:18 pve.xxx.tld kernel: device vetha9ef89c left promiscuous mode
Nov 05 10:45:18 pve.xxx.tld kernel: br-3ea8f01ddba1: port 1(vetha9ef89c) entered disabled state
Nov 05 10:45:18 pve.xxx.tld kernel: br-a56c1f2c4a6a: port 4(veth4f2f6cb) entered disabled state
Nov 05 10:45:18 pve.xxx.tld kernel: veth466815f: renamed from eth1
Nov 05 10:45:18 pve.xxx.tld kernel: br-a56c1f2c4a6a: port 4(veth4f2f6cb) entered disabled state
Nov 05 10:45:18 pve.xxx.tld kernel: device veth4f2f6cb left promiscuous mode
Nov 05 10:45:18 pve.xxx.tld kernel: br-a56c1f2c4a6a: port 4(veth4f2f6cb) entered disabled state
Nov 05 10:45:31 pve.xxx.tld sshd[2975382]: Received disconnect from 15.204.56.97 port 51300:11: Bye Bye [preauth]
Nov 05 10:45:31 pve.xxx.tld sshd[2975382]: Disconnected from authenticating user root 15.204.56.97 port 51300 [preauth]
Nov 05 10:45:32 pve.xxx.tld sshd[2976226]: Received disconnect from 49.247.25.198 port 45258:11: Bye Bye [preauth]
Nov 05 10:45:32 pve.xxx.tld sshd[2976226]: Disconnected from authenticating user root 49.247.25.198 port 45258 [preauth]
Nov 05 10:46:07 pve.xxx.tld pvestatd[3101976]: metrics send error 'xxx': 500 Can't connect to influxdb.xxx.tld:443 (Temporary failure in name resolution)
Nov 05 10:46:08 pve.xxx.tld pvestatd[3101976]: status update time (393.654 seconds)
Nov 05 10:46:18 pve.xxx.tld kernel: br-3ea8f01ddba1: port 1(vethb30a24f) entered blocking state
Nov 05 10:46:18 pve.xxx.tld kernel: br-3ea8f01ddba1: port 1(vethb30a24f) entered disabled state
Nov 05 10:46:18 pve.xxx.tld kernel: device vethb30a24f entered promiscuous mode
Nov 05 10:46:18 pve.xxx.tld kernel: br-a56c1f2c4a6a: port 4(veth3cfd8e5) entered blocking state
Nov 05 10:46:18 pve.xxx.tld kernel: br-a56c1f2c4a6a: port 4(veth3cfd8e5) entered disabled state
Nov 05 10:46:18 pve.xxx.tld kernel: device veth3cfd8e5 entered promiscuous mode
Nov 05 10:46:18 pve.xxx.tld kernel: br-a56c1f2c4a6a: port 4(veth3cfd8e5) entered blocking state
Nov 05 10:46:18 pve.xxx.tld kernel: br-a56c1f2c4a6a: port 4(veth3cfd8e5) entered forwarding state
Nov 05 10:46:18 pve.xxx.tld kernel: eth0: renamed from vethf8278a5
Nov 05 10:46:19 pve.xxx.tld kernel: eth1: renamed from vethde673a6
Nov 05 10:46:19 pve.xxx.tld kernel: br-a56c1f2c4a6a: port 4(veth3cfd8e5) entered disabled state
Nov 05 10:46:19 pve.xxx.tld kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethb30a24f: link becomes ready
Nov 05 10:46:19 pve.xxx.tld kernel: br-3ea8f01ddba1: port 1(vethb30a24f) entered blocking state
Nov 05 10:46:19 pve.xxx.tld kernel: br-3ea8f01ddba1: port 1(vethb30a24f) entered forwarding state
Nov 05 10:46:19 pve.xxx.tld kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth3cfd8e5: link becomes ready
Nov 05 10:46:19 pve.xxx.tld kernel: br-a56c1f2c4a6a: port 4(veth3cfd8e5) entered blocking state
Nov 05 10:46:19 pve.xxx.tld kernel: br-a56c1f2c4a6a: port 4(veth3cfd8e5) entered forwarding state
Nov 05 10:46:19 pve.xxx.tld kernel: br-3ea8f01ddba1: port 1(vethb30a24f) entered disabled state
Nov 05 10:46:19 pve.xxx.tld kernel: vethf8278a5: renamed from eth0
Nov 05 10:46:19 pve.xxx.tld kernel: br-3ea8f01ddba1: port 1(vethb30a24f) entered disabled state
Nov 05 10:46:19 pve.xxx.tld kernel: device vethb30a24f left promiscuous mode
Nov 05 10:46:19 pve.xxx.tld kernel: br-3ea8f01ddba1: port 1(vethb30a24f) entered disabled state
Nov 05 10:46:19 pve.xxx.tld kernel: br-a56c1f2c4a6a: port 4(veth3cfd8e5) entered disabled state
---

# pveversion -v
proxmox-ve: 7.4-1 (running kernel: 5.15.111-1-pve)
pve-manager: not correctly installed (running version: 7.4-17/513c62be)
pve-kernel-5.15.111-1-pve: 5.15.111-1
pve-kernel-5.15.108-1-pve: 5.15.108-2
pve-kernel-5.15.102-1-pve: 5.15.102-1
ceph-fuse: 15.2.17-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx4
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4.1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.4-2
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-3
libpve-network-perl: 0.7.3
libpve-rs-perl: 0.7.7
libpve-storage-perl: 7.4-3
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.3-1
proxmox-backup-file-restore: 2.4.3-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.7.3
pve-cluster: 7.3-3
pve-container: 4.4-6
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-4~bpo11+1
pve-firewall: 4.3-5
pve-firmware: not correctly installed
pve-ha-manager: 3.6.1
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-2
qemu-server: 7.4-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.11-pve1
 
this happens on all my other machines so it would mean that either influx ct actually goes down or becomes temporarily unreachable
Code:
metrics send error 'xxx': 500 Can't connect to influxdb.xxx.tld:443 (Connection timed out)
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!