[SOLVED] PVE can no longer connect to PBS

SpinningRust

Active Member
Sep 25, 2019
43
3
28
35
Hello everyone,

Yesterday i replaced my motherboard to use a new CPU for my Proxmox Backup Server.
Therefore, the Network interface names changed and PCIe devices. No big deal, i made some changes to access the web interface.
However this morning i got an email from my PVE server that the backups failed. I forgot to edit the other network interfaces to match the new names/PCIe devices.

This is where my problem comes in: after a lot of back and forth, trying, etc., i just can not make the PVE server connect to the PBS (they're connected directly with an ethernet cable). They can ping each other on the correct interface, an nmap scan from the PVE server shows me the active PBS port 8007, so theoretically, i should be able to make it work, right?

Any thoughts or clues are welcome.

Thanks in advance,

John


P.S.: PBS and PVE info:

proxmox-backup: 1.0-4 (running kernel: 5.4.106-1-pve) proxmox-backup-server: 1.1.5-1 (running version: 1.1.5) pve-kernel-5.4: 6.4-1 pve-kernel-helper: 6.4-1 pve-kernel-5.4.106-1-pve: 5.4.106-1 pve-kernel-5.4.103-1-pve: 5.4.103-1 pve-kernel-5.4.65-1-pve: 5.4.65-1 ifupdown2: 3.0.0-1+pve3 libjs-extjs: 6.0.1-10 proxmox-backup-docs: 1.1.5-1 proxmox-backup-client: 1.1.5-1 proxmox-mini-journalreader: 1.1-1 proxmox-widget-toolkit: 2.5-2 pve-xtermjs: 4.7.0-3 smartmontools: 7.2-pve2 zfsutils-linux: 2.0.4-pve1

proxmox-ve: 6.4-1 (running kernel: 5.4.106-1-pve) pve-manager: 6.4-5 (running version: 6.4-5/6c7bf5de) pve-kernel-5.4: 6.4-1 pve-kernel-helper: 6.4-1 pve-kernel-5.3: 6.1-6 pve-kernel-5.0: 6.0-11 pve-kernel-5.4.106-1-pve: 5.4.106-1 pve-kernel-5.4.103-1-pve: 5.4.103-1 pve-kernel-5.3.18-3-pve: 5.3.18-3 pve-kernel-5.0.21-5-pve: 5.0.21-10 pve-kernel-5.0.15-1-pve: 5.0.15-1 ceph-fuse: 14.2.20-pve1 corosync: 3.1.2-pve1 criu: 3.11-3 glusterfs-client: 5.5-3 ifupdown: not correctly installed ifupdown2: 3.0.0-1+pve3 ksm-control-daemon: 1.3-1 libjs-extjs: 6.0.1-10 libknet1: 1.20-pve1 libproxmox-acme-perl: 1.0.8 libproxmox-backup-qemu0: 1.0.3-1 libpve-access-control: 6.4-1 libpve-apiclient-perl: 3.1-3 libpve-common-perl: 6.4-2 libpve-guest-common-perl: 3.1-5 libpve-http-server-perl: 3.2-1 libpve-storage-perl: 6.4-1 libqb0: 1.0.5-1 libspice-server1: 0.14.2-4~pve6+1 lvm2: 2.03.02-pve4 lxc-pve: 4.0.6-2 lxcfs: 4.0.6-pve1 novnc-pve: 1.1.0-1 proxmox-backup-client: 1.1.5-1 proxmox-mini-journalreader: 1.1-1 proxmox-widget-toolkit: 2.5-3 pve-cluster: 6.4-1 pve-container: 3.3-5 pve-docs: 6.4-1 pve-edk2-firmware: 2.20200531-1 pve-firewall: 4.1-3 pve-firmware: 3.2-2 pve-ha-manager: 3.1-1 pve-i18n: 2.3-1 pve-qemu-kvm: 5.2.0-6 pve-xtermjs: 4.7.0-3 pve-zsync: 2.0-4 qemu-server: 6.4-2 smartmontools: 7.2-pve2 spiceterm: 3.1-1 vncterm: 1.6-2 zfsutils-linux: 2.0.4-pve1

auto lo
iface lo inet loopback

auto eno1
iface eno1 inet static
address 192.168.2.154/24
gateway 192.168.2.1

iface enp5s0f0 inet manual

auto enp5s0f1
iface enp5s0f1 inet manual
#CCA
mtu 9000

auto vmbr0
iface vmbr0 inet static
address 10.0.2.2/24
#CCA PBS
bridge-ports enp5s0f0
mtu 9000


EDIT:
i ended up pulling the datastore.cfg off of the machine and reinstalled PBS. Afterwards everything worked as it should...
i'm marking this thread as solved but i'd still be curious if there is another solution to this weird problem. Maybe it could help someone else that stumbles over the same problem as me.
 

Attachments

  • Screenshot 2021-05-08 at 14.52.44.png
    Screenshot 2021-05-08 at 14.52.44.png
    14.5 KB · Views: 10
Last edited:

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!