lxc_create_network_priv: 3463 Success - Failed to create network device (SOLVED)

A

axel885

New Member
Jul 18, 2024
7
0
1
Hi to all!
i don't know if it is a correct section and i looking for a solution but i can't. I have this problem, if i add a second network interface ( in this case a linux bridge) the container doesn't starts and return this error:



run_buffer: 571 Script exited with status 255
lxc_create_network_priv: 3463 Success - Failed to create network device
lxc_spawn: 1847 Failed to create the network
TASK ERROR: startup for container '113' failed


Thank to all for the help!
 
Sure thanks,
i attached the results. It happends every time i try to add a linux bridge to 1 container. This is an example
 

Attachments

It is easier to access the text, if just the text is pasted here.

Code: 
root@pve:~# pct config 102
arch: amd64
cores: 2
description: <div align='center'><a href='https://Helper-Scripts.com' target='_blank' rel='noopener noreferrer'><img src='https://raw.githubusercontent.com/tteck/Proxmox/main/misc/images/logo-81x112.png'/></a>%0A%0A  # prova1 LXC%0A%0A  <a href='https://ko-fi.com/proxmoxhelperscripts'><img src='https://img.shields.io/badge/&#x2615;-Buy me a coffee-blue' /></a>%0A  </div>%0A%0A%0Ahttp://192.168.86.77%3A8989/%0A%0Aadmin prova1%0A
features: keyctl=1,nesting=1
hostname: prova1
memory: 1024
mp1: /mnt/nas/media/,mp=/mnt
net0: name=eth0,bridge=vmbr0,gw=192.168.86.1,hwaddr=BC:24:11:F4:8C:5D,ip=192.168.86.77/24,type=veth
net1: name=eth1,bridge=vmbr1,firewall=1,hwaddr=BC:24:11:BF:57:A4,type=veth
onboot: 1
ostype: debian
rootfs: local-lvm:vm-102-disk-0,size=4G
swap: 512
tags: proxmox-helper-scripts

Haven't seen an error like this before, but maybe someone else has:
Code: 
...
DEBUG    utils - ../src/lxc/utils.c:run_buffer:560 - Script exec /usr/share/lxc/lxcnetaddbr 102 net up veth  veth102i1 produced output: Undefined subroutine &PVE::Firewall::is_nftables called at /usr/share/perl5/PVE/LXC.pm line 1009.
ERROR    utils - ../src/lxc/utils.c:run_buffer:571 - Script exited with status 255
ERROR    network - ../src/lxc/network.c:lxc_create_network_priv:3463 - Success - Failed to create network device
...
 
fba said:
It is easier to access the text, if just the text is pasted here.

Code: 
root@pve:~# pct config 102
arch: amd64
cores: 2
description: <div align='center'><a href='https://Helper-Scripts.com' target='_blank' rel='noopener noreferrer'><img src='https://raw.githubusercontent.com/tteck/Proxmox/main/misc/images/logo-81x112.png'/></a>%0A%0A  # prova1 LXC%0A%0A  <a href='https://ko-fi.com/proxmoxhelperscripts'><img src='https://img.shields.io/badge/&#x2615;-Buy me a coffee-blue' /></a>%0A  </div>%0A%0A%0Ahttp://192.168.86.77%3A8989/%0A%0Aadmin prova1%0A
features: keyctl=1,nesting=1
hostname: prova1
memory: 1024
mp1: /mnt/nas/media/,mp=/mnt
net0: name=eth0,bridge=vmbr0,gw=192.168.86.1,hwaddr=BC:24:11:F4:8C:5D,ip=192.168.86.77/24,type=veth
net1: name=eth1,bridge=vmbr1,firewall=1,hwaddr=BC:24:11:BF:57:A4,type=veth
onboot: 1
ostype: debian
rootfs: local-lvm:vm-102-disk-0,size=4G
swap: 512
tags: proxmox-helper-scripts

Haven't seen an error like this before, but maybe someone else has:
Code: 
...
DEBUG    utils - ../src/lxc/utils.c:run_buffer:560 - Script exec /usr/share/lxc/lxcnetaddbr 102 net up veth  veth102i1 produced output: Undefined subroutine &PVE::Firewall::is_nftables called at /usr/share/perl5/PVE/LXC.pm line 1009.
ERROR    utils - ../src/lxc/utils.c:run_buffer:571 - Script exited with status 255
ERROR    network - ../src/lxc/network.c:lxc_create_network_priv:3463 - Success - Failed to create network device
...
Click to expand...
good to know, netx time i post in this way!
Anyway... any ideas?
Thanks
 
Hi everyone, I came across a similar issue when setting up a second bridge in Proxmox. Have you tried checking if the pve-firewall service is running properly?
 
rh8dohgnoidr said:
Hi everyone, I came across a similar issue when setting up a second bridge in Proxmox. Have you tried checking if the pve-firewall service is running properly?
Click to expand...
Thank you! that was the problem! removing the tick on firewall (when you add a new network interface )it worked
Thank you all!
 
fba said:
DEBUG utils - ../src/lxc/utils.c:run_buffer:560 - Script exec /usr/share/lxc/lxcnetaddbr 102 net up veth veth102i1 produced output: Undefined subroutine &PVE::Firewall::is_nftables called at /usr/share/perl5/PVE/LXC.pm line 1009. ERROR utils - ../src/lxc/utils.c:run_buffer:571 - Script exited with status 255 ERROR network - ../src/lxc/network.c:lxc_create_network_priv:3463 - Success - Failed to create network device
Click to expand...


This looks like a partial upgrade - can you send me the output of pveversion -v ?
 
Code: 
proxmox-ve: 8.3.0 (running kernel: 6.5.11-8-pve)
pve-manager: 8.1.4 (running version: 8.1.4/ec5affc9e41f1d79)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.5: 6.5.11-8
proxmox-kernel-6.5.11-8-pve-signed: 6.5.11-8
ceph-fuse: 18.2.4-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.0.5
libpve-network-perl: 0.10.0
libpve-rs-perl: 0.8.8
libpve-storage-perl: 8.0.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.3.2-1
proxmox-backup-file-restore: 3.3.2-2
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.3
pve-cluster: 8.0.10
pve-container: 5.2.3
pve-docs: 8.3.1
pve-edk2-firmware: 4.2023.08-4
pve-firewall: 5.0.3
pve-firmware: 3.14-2
pve-ha-manager: 4.0.6
pve-i18n: 3.3.2
pve-qemu-kvm: 9.0.2-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.0.10
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1
 
You have a very old pve-firewall version (5.0.3) from 2023, but a very recent pve-container version (december 2024). There error is because the outdated firewall doesn't yet contain the function used in pve-container.

How did you update the server? We require updates to be made via apt dist-upgrade
 
You must log in or register to reply here.
Top Bottom