Quoting Chris West (1391...@bugs.launchpad.net):
> Public bug reported:
>
> The presence of "/var/lock/lxc-net" causes "service lxc-net start" to
> claim success but actually just do nothing useful.
>
> When the system goes down hard, /var/lock/lxc-net is not removed, fair
/var/lock should be a tmpfs. This sounds like a local misconfiguration.
Can you show what /var/lock looks like?
cat /proc/self/mountinfo
df -h /var/lock
ls -ld /var/lock
df -h /run/lock
status: incomplete
** Changed in: lxc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1391452
Title:
lxc-net fails to start properly after system crash: lock file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1391452/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
