Launch error since reinstallation

MarioC.

New Member
Jun 28, 2018
6
0
1
23
Belgique
I currently have a problem when I create a VPS sa telling myself

Job for pve-container@100.service failed because the control process exited with error code.
See "systemctl status pve-container@100.service" and "journalctl -xe" for details.
TASK ERROR: command 'systemctl start pve-container@100' failed: exit code 1

Besides I can't update it the machine has been reinstalled it's the first time this happens
 
please post the debug output/log see https://pve.proxmox.com/wiki/Linux_...ers_with_tt_span_class_monospaced_pct_span_tt
chapter 'obtaining debug logs'


lxc-start 100 20180628093237.150 INFO lxc_lsm - lsm/lsm.c:lsm_init:46 - LSM security driver AppArmor
lxc-start 100 20180628093237.150 INFO lxc_seccomp - seccomp.c:parse_config_v2:585 - processing: .reject_force_umount # comment this to allow umount -f; not recommended
lxc-start 100 20180628093237.150 INFO lxc_seccomp - seccomp.c:parse_config_v2:761 - Adding native rule for reject_force_umount # comment this to allow umount -f; not recommended action 0(kill)
lxc-start 100 20180628093237.150 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:411 - Setting Seccomp rule to reject force umounts
lxc-start 100 20180628093237.150 INFO lxc_seccomp - seccomp.c:parse_config_v2:765 - Adding compat rule for reject_force_umount action 0(kill)
lxc-start 100 20180628093237.150 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:411 - Setting Seccomp rule to reject force umounts
lxc-start 100 20180628093237.150 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:411 - Setting Seccomp rule to reject force umounts
lxc-start 100 20180628093237.150 INFO lxc_seccomp - seccomp.c:parse_config_v2:585 - processing: .[all]
lxc-start 100 20180628093237.150 INFO lxc_seccomp - seccomp.c:parse_config_v2:585 - processing: .kexec_load errno 1
lxc-start 100 20180628093237.150 INFO lxc_seccomp - seccomp.c:parse_config_v2:761 - Adding native rule for kexec_load errno 1 action 327681(errno)
lxc-start 100 20180628093237.150 INFO lxc_seccomp - seccomp.c:parse_config_v2:765 - Adding compat rule for kexec_load action 327681(errno)
lxc-start 100 20180628093237.150 INFO lxc_seccomp - seccomp.c:parse_config_v2:585 - processing: .open_by_handle_at errno 1
lxc-start 100 20180628093237.150 INFO lxc_seccomp - seccomp.c:parse_config_v2:761 - Adding native rule for open_by_handle_at errno 1 action 327681(errno)
lxc-start 100 20180628093237.150 INFO lxc_seccomp - seccomp.c:parse_config_v2:765 - Adding compat rule for open_by_handle_at action 327681(errno)
lxc-start 100 20180628093237.150 INFO lxc_seccomp - seccomp.c:parse_config_v2:585 - processing: .init_module errno 1
lxc-start 100 20180628093237.150 INFO lxc_seccomp - seccomp.c:parse_config_v2:761 - Adding native rule for init_module errno 1 action 327681(errno)
lxc-start 100 20180628093237.150 INFO lxc_seccomp - seccomp.c:parse_config_v2:765 - Adding compat rule for init_module action 327681(errno)
lxc-start 100 20180628093237.150 INFO lxc_seccomp - seccomp.c:parse_config_v2:585 - processing: .finit_module errno 1
lxc-start 100 20180628093237.150 INFO lxc_seccomp - seccomp.c:parse_config_v2:761 - Adding native rule for finit_module errno 1 action 327681(errno)
lxc-start 100 20180628093237.150 INFO lxc_seccomp - seccomp.c:parse_config_v2:765 - Adding compat rule for finit_module action 327681(errno)
lxc-start 100 20180628093237.150 INFO lxc_seccomp - seccomp.c:parse_config_v2:585 - processing: .delete_module errno 1
lxc-start 100 20180628093237.150 INFO lxc_seccomp - seccomp.c:parse_config_v2:761 - Adding native rule for delete_module errno 1 action 327681(errno)
lxc-start 100 20180628093237.150 INFO lxc_seccomp - seccomp.c:parse_config_v2:765 - Adding compat rule for delete_module action 327681(errno)
lxc-start 100 20180628093237.150 INFO lxc_seccomp - seccomp.c:parse_config_v2:775 - Merging in the compat Seccomp ctx into the main one
lxc-start 100 20180628093237.150 INFO lxc_conf - conf.c:run_script_argv:368 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "100", config section "lxc"
lxc-start 100 20180628093237.801 DEBUG terminal - terminal.c:lxc_terminal_peer_default:701 - Using terminal "/dev/tty" as proxy
lxc-start 100 20180628093237.801 DEBUG terminal - terminal.c:lxc_terminal_signal_init:188 - Created signal fd 9
lxc-start 100 20180628093237.801 DEBUG terminal - terminal.c:lxc_terminal_winsz:85 - Set window size to 93 columns and 40 rows
lxc-start 100 20180628093237.801 INFO lxc_start - start.c:lxc_init:846 - Container "100" is initialized
lxc-start 100 20180628093237.802 INFO lxc_conf - conf.c:run_script:506 - Executing script "/usr/share/lxc/lxcnetaddbr" for container "100", config section "net"
lxc-start 100 20180628093238.170 DEBUG lxc_conf - conf.c:run_buffer:338 - Script exec /usr/share/lxc/lxcnetaddbr 100 net up veth veth100i0 with output: bridge 'vmbr0' does not exist
lxc-start 100 20180628093238.176 ERROR lxc_conf - conf.c:run_buffer:347 - Script exited with status 2
lxc-start 100 20180628093238.212 ERROR lxc_network - network.c:lxc_create_network_priv:2441 - Failed to create network device
lxc-start 100 20180628093238.212 ERROR lxc_start - start.c:lxc_spawn:1545 - Failed to create the network
lxc-start 100 20180628093238.212 ERROR lxc_start - start.c:__lxc_start:1883 - Failed to spawn container "100"
lxc-start 100 20180628093238.212 INFO lxc_conf - conf.c:run_script_argv:368 - Executing script "/usr/share/lxcfs/lxc.reboot.hook" for container "100", config section "lxc"
 
lxc-start 100 20180628093238.170 DEBUG lxc_conf - conf.c:run_buffer:338 - Script exec /usr/share/lxc/lxcnetaddbr 100 net up veth veth100i0 with output: bridge 'vmbr0' does not exist
it seems the bridge is missing?
 
[QUOTE = "dcsapak, post: 214560, membre: 36072"] il semble que le pont est manquant? [/ QUOTE]
How can I fix it because it's the first time I've ever had to add things etc.?
 
please post your container config (/etc/pve/lxc/ID.conf) and your network config (/etc/network/interfaces)
 
please post your container config (/etc/pve/lxc/ID.conf) and your network config (/etc/network/interfaces)

1530185154-telechargement.png
1530185234-screenshot-1.jpg
 
what does
Code:
ip addr
ip link
say?
 
the complete output would help (you can anonymize the ips of course)
 
please post the output of
Code:
ip addr
ip link

like so:
Code:
user@host:~$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
    inet 192.168.x.y/20 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::3b65/64 scope link
       valid_lft forever preferred_lft forever
user@host:~$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
 

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!