Container affects Host's Network

[G-Known]

I'm running a Debian container to try to setup an VPN server but I'm having problems getting the virtual machine to shutdown properly as this is the message it displays:

Code: Select all

Broadcast message from root@debvpn (console) (Mon Jul 21 22:57:09 2014):

The system is going down for system halt NOW!
INIT: Switching to runlevel: 0
INIT: Sending processes the TERM signal
[info] Using makefile-style concurrent boot in runlevel 0.
mount: / is busy
[ ok ] Asking all remaining processes to terminate...done.
[ ok ] All processes ended within 1 seconds...done.
[....] Deconfiguring network interfaces...Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/60:eb:69:0a:22:4a
Sending on   LPF/eth0/60:eb:69:0a:22:4a
Sending on   Socket/fallback
done.
[info] Will now halt.
INIT: no more processes left in this runlevel

As there's no error messages, it just hangs without going back to the host's console and I need to kill it. This also screw up my internet connection as I have to reset it. Running the container again results in:

Code: Select all

lxc-start: failed (98) to create the command service point /var/lib/lxc/debvpn/command
lxc-start: ##
lxc-start: # The container appears to be already running!
lxc-start: ##
lxc-start: failed to add command handler to mainloop
lxc-start: mainloop exited with an error

Is there something wrong with the container itself or with LXC's configurations? Trying to halt, stop, freeze, destroy or kill the container will leave these commands hanging.

[G-Known]

The wiki page has made me overlook their statement of starting/stopping containers. Thus, LXC is experiencing some limited capabilities at this point, does anyone have any idea why the console just hangs whenever I start the container in daemon mode?