Could not generate persistent MAC address for

schlawiner

Well-Known Member
Mar 12, 2018
38
3
48
49
Hallo,

ich habe seit gestern immer wieder folgendes Problem

Nov 28 14:57:29 pve-23 systemd-udevd[7197]: Could not generate persistent MAC address for veth242i0: No such file or directory



proxmox-ve: 5.4-2 (running kernel: 4.15.18-12-pve)
pve-manager: 5.4-3 (running version: 5.4-3/0a6eaa62)
pve-kernel-4.15: 5.3-3
pve-kernel-4.15.18-12-pve: 4.15.18-36
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-12
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-55
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-7
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-28
pve-cluster: 5.0-38
pve-container: 2.0-41
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-22
pve-firmware: 2.0-7
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-54
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
 
hi,

Nov 28 14:57:29 pve-23 systemd-udevd[7197]: Could not generate persistent MAC address for veth242i0: No such file or directory

diese kann einfach ignoriert werden. (ist wegen komischer systemd-udevd defaults, MACAddressPolicy=persistent)
 
nun ich habe den Beitrag aus der Problematik hin aufgemacht, einige CT`s ode VM`s bekommen eine Verbindung außerhalb des Vlan`s andere nur Innerhalb
 
Last edited:
Gut, dass der Fehler gefunden und behoben wurde - Bitte den Thread als 'SOLVED' markieren - das hilft anderen Usern in einer ähnlichen Situation vl. auch mal auf die Router/Switchconfigs zu schauen.

Danke!
 
Tengo el siguiente problema, tengo una máquina pfsense y un contenedor sophos, el equipo funciona pero hace que las caídas se arrepientan de las interacciones atraves del tiempo, no se si es una incompatibilidad o falla de la versión 6 de PROXMOX. desconecta la tarjeta de red del firewall aveces la lan o la wan

May 10 10:51:35 E-FENNIX-BAY-01 systemd-udevd[61080]: Using default interface naming scheme 'v240'.
May 10 10:51:35 E-FENNIX-BAY-01 systemd-udevd[61080]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
May 10 10:51:35 E-FENNIX-BAY-01 systemd-udevd[61080]: Could not generate persistent MAC address for tap103i0: No such file or directory
May 10 10:51:36 E-FENNIX-BAY-01 kernel: device tap103i0 entered promiscuous mode
May 10 10:51:36 E-FENNIX-BAY-01 kernel: vmbr4: port 2(tap103i0) entered blocking state
May 10 10:51:36 E-FENNIX-BAY-01 kernel: vmbr4: port 2(tap103i0) entered disabled state
May 10 10:51:36 E-FENNIX-BAY-01 kernel: vmbr4: port 2(tap103i0) entered blocking state
May 10 10:51:36 E-FENNIX-BAY-01 kernel: vmbr4: port 2(tap103i0) entered forwarding state
May 10 10:51:36 E-FENNIX-BAY-01 kernel: HTB: quantum of class 10001 is big. Consider r2q change.
May 10 10:51:36 E-FENNIX-BAY-01 systemd-udevd[61080]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
May 10 10:51:36 E-FENNIX-BAY-01 systemd-udevd[61080]: Could not generate persistent MAC address for tap103i1: No such file or directory
May 10 10:51:37 E-FENNIX-BAY-01 kernel: device tap103i1 entered promiscuous mode
May 10 10:51:37 E-FENNIX-BAY-01 kernel: vmbr6: port 3(tap103i1) entered blocking state
May 10 10:51:37 E-FENNIX-BAY-01 kernel: vmbr6: port 3(tap103i1) entered disabled state
May 10 10:51:37 E-FENNIX-BAY-01 kernel: vmbr6: port 3(tap103i1) entered blocking state
May 10 10:51:37 E-FENNIX-BAY-01 kernel: vmbr6: port 3(tap103i1) entered forwarding state
May 10 10:51:37 E-FENNIX-BAY-01 kernel: HTB: quantum of class 10001 is big. Consider r2q change.
May 10 10:51:37 E-FENNIX-BAY-01 systemd-udevd[61080]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
May 10 10:51:37 E-FENNIX-BAY-01 systemd-udevd[61080]: Could not generate persistent MAC address for tap103i3: No such file or directory
May 10 10:51:38 E-FENNIX-BAY-01 kernel: device tap103i3 entered promiscuous mode
May 10 10:51:38 E-FENNIX-BAY-01 kernel: vmbr0: port 3(tap103i3) entered blocking state
May 10 10:51:38 E-FENNIX-BAY-01 kernel: vmbr0: port 3(tap103i3) entered disabled state
May 10 10:51:38 E-FENNIX-BAY-01 kernel: vmbr0: port 3(tap103i3) entered blocking state
May 10 10:51:38 E-FENNIX-BAY-01 kernel: vmbr0: port 3(tap103i3) entered forwarding state
May 10 10:51:38 E-FENNIX-BAY-01 kernel: HTB: quantum of class 10001 is big. Consider r2q change.
May 10 10:51:39 E-FENNIX-BAY-01 kernel: vmbr0: port 3(tap103i3) entered disabled state
May 10 10:51:39 E-FENNIX-BAY-01 kernel: vmbr6: port 3(tap103i1) entered disabled state
May 10 10:51:40 E-FENNIX-BAY-01 kernel: vmbr4: port 2(tap103i0) entered disabled state
May 10 10:51:40 E-FENNIX-BAY-01 systemd[1]: 103.scope: Succeeded.
 
Tengo el siguiente problema, tengo una máquina pfsense y un contenedor sophos, el equipo funciona pero hace que las caídas se arrepientan de las interacciones atraves del tiempo, no se si es una incompatibilidad o falla de la versión 6 de PROXMOX. desconecta la tarjeta de red del firewall aveces la lan o la wan
please:
* open a new thread instead of replying to one from half a year ago
* post in english - else only very few of our users will be ably to try to help you
 

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!