[PVE-User] Proxmox 6 loses network every 24 hours

Gianni Milo gianni.milo22 at gmail.com
Thu Apr 16 17:07:37 CEST 2020


Maybe you can find some clues in syslogs during the time it goes off ?
Check for either enp1s0 or vmbr0 for example.

G.


On Thu, 16 Apr 2020 at 14:32, Gerald Brandt <gbr at majentis.com> wrote:

> Hi,
>
> I have a Proxmox 6 server at SoYouStart https://www.soyoustart.com. I've
> been running a server there for years, running Proxmox 4. Instead of
> upgrading, I backed up all my VMs, did a fresh Proxmox 6 install, and
> restored my VMs. It works well, except for NFS, but that's another topic.
>
>
> Every 24 hours, vmbr0 disappears. The SoYouStart staff can't ping the
> machine, assume it's gone down, and hard reboot the server. 24 hours
> after it's up, the cycle repeats. I'm not sure what is going on.
>
> One weird thing, is that vmbr0 isn't configured in Proxmox, SoYouStart
> has it configured some other way. Could this be part of the problem? It
> looks like vmbr0 gets its IP via DHCP. (Yup, check in
> /etc/network/interfaces)
>
> Apr 15 21:32:32 ns500184 ifup[695]: DHCPDISCOVER on vmbr0 to
> 255.255.255.255 port 67 interval 7
> Apr 15 21:32:32 ns500184 dhclient[744]: Sending on
>  LPF/vmbr0/00:25:90:7b:a2:b8
> Apr 15 21:32:32 ns500184 dhclient[744]: DHCPDISCOVER on vmbr0 to
> 255.255.255.255 port 67 interval 7
> Apr 15 21:32:32 ns500184 dhclient[744]: DHCPDISCOVER on vmbr0 to
> 255.255.255.255 port 67 interval 13
> Apr 15 21:32:32 ns500184 ifup[695]: DHCPDISCOVER on vmbr0 to
> 255.255.255.255 port 67 interval 13
> Apr 15 21:32:32 ns500184 ifup[695]: DHCPREQUEST for x.x.x.x on vmbr0 to
> 255.255.255.255 port 67
> Apr 15 21:32:32 ns500184 dhclient[744]: DHCPREQUEST for x.x.x.x on vmbr0
> to 255.255.255.255 port 67
> Apr 15 21:32:32 ns500184 cloud-init[819]: ci-info: | vmbr0  |  True |
>    x.x.x.x        | 255.255.255.0 | global | 00:25:90:7b:a2:b8 |
> Apr 15 21:32:32 ns500184 cloud-init[819]: ci-info: | vmbr0  |  True |
> xxxxxxxxxxxxxxxxxxx/64 |       .       |  link  | 00:25:90:7b:a2:b8 |
> Apr 15 21:32:32 ns500184 cloud-init[819]: ci-info: |   0   |    0.0.0.0
> | x.x.x.254 |    0.0.0.0    |   vmbr0   |   UG  |
> Apr 15 21:32:32 ns500184 cloud-init[819]: ci-info: |   1   |   x.x.x.0  |
>  0.0.0.0    | 255.255.255.0 |   vmbr0   |   U   |
> Apr 15 21:32:32 ns500184 cloud-init[819]: ci-info: |   1   |  fe80::/64
> |    ::   |   vmbr0   |   U   |
> Apr 15 21:32:32 ns500184 cloud-init[819]: ci-info: |   3   |    local
> |    ::   |   vmbr0   |   U   |
> Apr 15 21:32:32 ns500184 cloud-init[819]: ci-info: |   4   |   ff00::/8
> |    ::   |   vmbr0   |   U   |
> Apr 15 21:32:32 ns500184 ntpd[891]: Listen normally on 3 vmbr0 x.x.x.x:123
> Apr 15 21:32:32 ns500184 ntpd[891]: Listen normally on 5 vmbr0
> [xxxxxxxxxx]:123
> Apr 15 21:32:32 ns500184 kernel: [   12.212574] vmbr0: port 1(enp1s0)
> entered blocking state
> Apr 15 21:32:32 ns500184 kernel: [   12.212639] vmbr0: port 1(enp1s0)
> entered disabled state
> Apr 15 21:32:32 ns500184 kernel: [   15.603713] vmbr0: port 1(enp1s0)
> entered blocking state
> Apr 15 21:32:32 ns500184 kernel: [   15.603773] vmbr0: port 1(enp1s0)
> entered forwarding state
> Apr 15 21:32:32 ns500184 kernel: [   15.603914] IPv6:
> ADDRCONF(NETDEV_CHANGE): vmbr0: link becomes ready
> Apr 15 21:32:47 ns500184 kernel: [   35.452560] vmbr0: port 2(tap5000i0)
> entered blocking state
> Apr 15 21:32:47 ns500184 kernel: [   35.452608] vmbr0: port 2(tap5000i0)
> entered disabled state
> Apr 15 21:32:47 ns500184 kernel: [   35.452772] vmbr0: port 2(tap5000i0)
> entered blocking state
> Apr 15 21:32:47 ns500184 kernel: [   35.452819] vmbr0: port 2(tap5000i0)
> entered forwarding state
>
> Gerald
>
>
>
> proxmox-ve: 6.1-2 (running kernel: 5.3.18-3-pve)
> pve-manager: 6.1-8 (running version: 6.1-8/806edfe1)
> pve-kernel-helper: 6.1-8
> pve-kernel-5.3: 6.1-6
> pve-kernel-5.0: 6.0-11
> pve-kernel-5.3.18-3-pve: 5.3.18-3
> pve-kernel-5.0.21-5-pve: 5.0.21-10
> ceph-fuse: 12.2.11+dfsg1-2.1+b1
> corosync: 3.0.3-pve1
> criu: 3.11-3
> glusterfs-client: 5.5-3
> ifupdown: 0.8.35
> libjs-extjs: 6.0.1-10
> libknet1: 1.15-pve1
> libpve-access-control: 6.0-6
> libpve-apiclient-perl: 3.0-3
> libpve-common-perl: 6.0-17
> libpve-guest-common-perl: 3.0-5
> libpve-http-server-perl: 3.0-5
> libpve-storage-perl: 6.1-5
> libqb0: 1.0.5-1
> libspice-server1: 0.14.2-4~pve6+1
> lvm2: 2.03.02-pve4
> lxc-pve: 3.2.1-1
> lxcfs: 4.0.1-pve1
> novnc-pve: 1.1.0-1
> proxmox-mini-journalreader: 1.1-1
> proxmox-widget-toolkit: 2.1-3
> pve-cluster: 6.1-4
> pve-container: 3.0-23
> pve-docs: 6.1-6
> pve-edk2-firmware: 2.20200229-1
> pve-firewall: 4.0-10
> pve-firmware: 3.0-7
> pve-ha-manager: 3.0-9
> pve-i18n: 2.0-4
> pve-qemu-kvm: 4.1.1-4
> pve-xtermjs: 4.3.0-1
> pve-zsync: 2.0-3
> qemu-server: 6.1-7
> smartmontools: 7.1-pve2
> spiceterm: 3.1-1
> vncterm: 1.6-1
> zfsutils-linux: 0.8.3-pve1
>
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>


More information about the pve-user mailing list