Problems After 5.0 upg. from 4.4

[umibozu]

Hi , i have two big problems after upgrading mi installation from 4.4 to 5.0

1) lvmetad had stopped working ... this is my syslog

Aug 24 22:11:41 pv lvmetad[17347]: Failed to accept connection errno 11.

2) Networking does not working ,though i stop and restart the service.

thisi is mi /etc/network/interfaces file


--------------------------------
auto lo
iface lo inet loopback

auto eth1
iface eth1 inet manual

auto eth0
iface eth0 inet manual

auto vmbr0
iface vmbr0 inet static
address 172.27.20.80
netmask 255.255.255.128
gateway 172.27.20.126
bridge_ports eth0
bridge_stp off
bridge_fd 0

auto vmbr1
iface vmbr1 inet manual
bridge_ports eth1
bridge_stp off
bridge_fd 0
---------------------------------

this is my jorunalctl -xe

-------------------
ago 25 06:45:17 pv kernel: IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
ago 25 06:45:18 pv kernel: r8169 0000:02:00.0: firmware: direct-loading firmware rtl_nic/rtl8168e-2.fw
ago 25 06:45:18 pv kernel: r8169 0000:02:00.0 eth0: link down
ago 25 06:45:18 pv kernel: r8169 0000:02:00.0 eth0: link down
ago 25 06:45:18 pv kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
ago 25 06:45:18 pv ifup[446]: Cannot find device "vmbr0"
ago 25 06:45:18 pv ifup[446]: ifup: failed to bring up vmbr0
ago 25 06:45:18 pv systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
ago 25 06:45:18 pv systemd[1]: Failed to start Raise network interfaces.
-- Subject: L'unità networking.service è fallita
-- Defined-By: systemd

-- L'unità networking.service è fallita.
--
-- Il risultato è failed.
ago 25 06:45:18 pv systemd[1]: networking.service: Unit entered failed state.
ago 25 06:45:18 pv systemd[1]: networking.service: Failed with result 'exit-code'.
ago 25 06:45:18 pv systemd[1]: Reached target Network.


-----------------------

any idea ?

Thanks
Pietro

 

[ONE FOTON]

Hello, look how proxmox 5
Does not name network interfaces like eth0 etc ... now uses another nomenclature https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
Maybe that's the problem

 

[fireon]

Same Error here. Network is working fine. But Service also not starting:

● networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2017-11-11 00:22:02 CET; 22h ago
     Docs: man:interfaces(5)
  Process: 9188 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
  Process: 9181 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment -
 Main PID: 9188 (code=exited, status=1/FAILURE)

Nov 11 00:21:48 tux01 ifup[9188]: run-parts: /etc/network/if-up.d/vzifup-post exited with return code 127
Nov 11 00:21:48 tux01 ifup[9188]: ifup: failed to bring up bond0
Nov 11 00:21:48 tux01 ifup[9188]: ifup: waiting for lock on /run/network/ifstate.vmbr0
Nov 11 00:22:02 tux01 ifup[9188]: Waiting for vmbr0 to get ready (MAXWAIT is 2 seconds).
Nov 11 00:22:02 tux01 ifup[9188]: RTNETLINK answers: File exists
Nov 11 00:22:02 tux01 ifup[9188]: ifup: failed to bring up vmbr0
Nov 11 00:22:02 tux01 systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Nov 11 00:22:02 tux01 systemd[1]: Failed to start Raise network interfaces.
Nov 11 00:22:02 tux01 systemd[1]: networking.service: Unit entered failed state.
Nov 11 00:22:02 tux01 systemd[1]: networking.service: Failed with result 'exit-code'.

Is there a solution?

Hello, look how proxmox 5
Does not name network interfaces like eth0 etc ... now uses another nomenclature https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
Maybe that's the problem

It is not depending on the names, because other server working fine.

 

[ONE FOTON]

Well I have that problem when I added the pass-through of the port pcie!
to fix it I disconnect the pass-through in the /etc/pve/qemu-server/vmid.conf
then I enter by novnv to the vm and in the file / etc / network / interfaces
I change the name of the network interface for one like this enp2s18
then I do an ifup enp2s18 and a reload the network with systemctl restart networking
and with that, it was solved.
best regards.

 

[fireon]

Well I have that problem when I added the pass-through of the port pcie!
to fix it I disconnect the pass-through in the /etc/pve/qemu-server/vmid.conf
then I enter by novnv to the vm and in the file / etc / network / interfaces
I change the name of the network interface for one like this enp2s18
then I do an ifup enp2s18 and a reload the network with systemctl restart networking
and with that, it was solved.
best regards.

Strange, on the other server this is working with the old names. And Pass-through was activated, but since month it is disabled. But yes, will change the name to the actual defaults.

 

[fireon]

I've changed the name and it did not help. Same issue on the networkservice.

 

[ONE FOTON]

Hi brother
pass me the network configuration of the VM (cat /etc/network/interfaces)
greetings from Argentina

 

[fireon]

auto lo
iface lo inet loopback

iface eno0 inet manual

iface eno1 inet manual

auto enp3s0
iface enp3s0 inet6 static
        address  fda0:22c2:9242:382e::1
        netmask  64

auto bond0
iface bond0 inet manual
        slaves eno0 eno1
        bond_miimon 100
        bond_mode 802.3ad
        bond_xmit_hash_policy layer2+3
#Verbindung zu HP Layer3 Switch

auto vmbr0
iface vmbr0 inet static
        address  77.234.60.120
        netmask  255.255.255.224
        gateway  77.234.60.121
        bridge_ports bond0
        bridge_stp off
        bridge_fd 0

iface vmbr0 inet6 static
        address  2001:470:1ff0:548:ef4:7aff:ae31:efa0
        netmask  64
        gateway  2001:470:1ff0:548::9

 

[ONE FOTON]

Hello
ok, there is something wrong there !.

the iface should be about enp3s0.
this is the configuration of my virtual machine

The primary network interface
auto enp6s18
iface enp6s18 inet static
address 192.168.0.xx
netmask 255.255.255.0
gateway 192.168.0.xx
network 192.168.0.0
broadcast 192.168.0.xx xx=your ip

and in my proxmox server the configuration is


auto lo
iface lo inet loopback

#allow-hotplug enp0s31f6

iface enp0s31f6 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.0.xx
netmask 255.255.255.0
gateway 192.168.0.xx
bridge_ports enp0s31f6
bridge_stp off
bridge_fd 0

Hope this can help you!

 

[fireon]

the iface should be about enp3s0.

No, eno is ok. eno is always the nic on the motherboard. enp... are pcie-slots. Your post that in your link.

What precisely has changed in v197?
With systemd 197 we have added native support for a number of different naming policies into systemd/udevd proper and made a scheme similar to biosdevname's (but generally more powerful, and closer to kernel-internal device identification schemes) the default. The following different naming schemes for network interfaces are now supported by udev natively:

1. Names incorporating Firmware/BIOS provided index numbers for on-board devices (example: eno1)
2. Names incorporating Firmware/BIOS provided PCI Express hotplug slot index numbers (example: ens1)
3. Names incorporating physical/geographical location of the connector of the hardware (example: enp2s0)
4. Names incorporating the interfaces's MAC address (example: enx78e7d1ea46da)
5. Classic, unpredictable kernel-native ethX naming (example: eth0)

 

[ONE FOTON]

well, according to what I understand
depending on what device it is the interface name assigned to it.
ej: eno1 assigns it to devices that are onboard.
ens1 Assigns it to devices that are PCI-e , etc...


that's why if you're trying to build an enp3s0 device, the iface should be on the same device.
always talking about the configuration in the virtual machine

 

[jcarnus]

Hi
I have the exact same issue, could you le me know has this has been resolved ?
Thanks