Container can't start after reinstall ( Debian 8.8 )

BobLamarley

New Member
Apr 4, 2017
5
0
1
29
Hi,
I'm in front of a strange behaviour,
I reinstalled proxmox on the same server as before (a debian), I configured the same network and the same containers, except that it is impossible to start my containers.
I got this error :
root@ns3035176:~# systemctl status lxc@100.service
lxc@100.service - LXC Container: 100
Loaded: loaded (/lib/systemd/system/lxc@.service; disabled)
Drop-In: /usr/lib/systemd/system/lxc@.service.d
└─pve-reboot.conf
Active: failed (Result: exit-code) since Fri 2017-05-12 22:21:12 CEST; 11min ago
Docs: man:lxc-start
man:lxc
Process: 16462 ExecStopPost=/usr/share/lxc/lxc-pve-reboot-trigger %i (code=exited, status=0/SUCCESS)
Process: 16539 ExecStart=/usr/bin/lxc-start -n %i (code=exited, status=1/FAILURE)
Main PID: 15313 (code=exited, status=1/FAILURE)

May 12 22:21:12 ns3035176 lxc-start[16539]: lxc-start: tools/lxc_start.c: main: 366 The container failed to start.
May 12 22:21:12 ns3035176 lxc-start[16539]: lxc-start: tools/lxc_start.c: main: 368 To get more details, run ...mode.
May 12 22:21:12 ns3035176 lxc-start[16539]: lxc-start: tools/lxc_start.c: main: 370 Additional information ca...ions.
May 12 22:21:12 ns3035176 systemd[1]: lxc@100.service: control process exited, code=exited status=1
May 12 22:21:12 ns3035176 systemd[1]: Failed to start LXC Container: 100.
May 12 22:21:12 ns3035176 systemd[1]: Unit lxc@100.service entered failed state.

If someone can help me, it would be very grateful,
Thanks,
Thomas
 
Last edited:
I restarted my proxmox server based at OVH but he didn't restart, i can't join him by ping, so i can't get the debug log.
Before the crash, i've tried to create some other container with multiple configuration and I found that when the container was connected to the bridge vmbr2 I could not start it.
So, i think my problem is coming from the network configuration file, but it was working on my previous proxmox :
auto lo
iface lo inet loopback

iface eth0 inet manual

iface eth1 inet manual

auto vmbr0
iface vmbr0 inet static
address 51.255.80.74
netmask 255.255.255.0
gateway 51.255.80.254
broadcast 51.255.80.255
bridge_ports eth0
bridge_stp off
bridge_fd 0
network 51.255.80.0

iface vmbr0 inet6 static
address 2001:41d0:1004:104a::
netmask 64
post-up /sbin/ip -f inet6 route add 2001:41d0:1004:10ff:ff:ff:ff:ff dev vmbr0
post-up /sbin/ip -f inet6 route add default via 2001:41d0:1004:10ff:ff:ff:ff:ff
pre-down /sbin/ip -f inet6 route del default via 2001:41d0:1004:10ff:ff:ff:ff:ff
pre-down /sbin/ip -f inet6 route del 2001:41d0:1004:10ff:ff:ff:ff:ff dev vmbr0

auto vmbr2
iface vmbr2 inet static
address 192.168.0.254
netmask 255.255.255.0
bridge_ports none
bridge_stp off
bridge_fd 0

post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -o vmbr0 -j SNAT --to 51.255.80.74
post-down iptables -t nat -D POSTROUTING -s 192.168.0.0/24 -o vmbr0 -j SNAT --to 51.255.80.74

#grafana
post-up iptables -A FORWARD -p tcp -d 192.168.0.1 --dport 3000 -j ACCEPT
post-down iptables -A FORWARD -p tcp -d 192.168.0.1 --dport 3000 -j ACCEPT
#Influxdb
post-up iptables -A FORWARD -p tcp -d 192.168.0.2 --dport 8086 -j ACCEPT
post-down iptables -A FORWARD -p tcp -d 192.168.0.2 --dport 8086 -j ACCEPT

#Grafana
post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 3000 -j DNAT --to-destination 192.168.0.1:3000
post-down iptables -t nat -D PREROUTING -i vmbr0 -p tcp --dport 3000 -j DNAT --to-destination 192.168.0.1:3000
 

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!