[PVE-User] Kill LXC...
gilberto.nunes32 at gmail.com
Wed Jan 23 20:46:19 CET 2019
Oh OMG! We'll planne for that! I mean we'll reboot the system! Sad!
Gilberto Nunes Ferreira
(47) 99676-7530 - Whatsapp / Telegram
Em qua, 23 de jan de 2019 às 17:22, Stephan Leemburg <
sleemburg at it-functions.nl> escreveu:
> It could be you are looking at a bug we are experiencing weekly for months.
> It is some race condition on copying namespaces in netns.
> I posted earlier on it, but no reaction.
> This seems to be solved in kernel 4.17 and up, so that needs an ubuntu
> 18.10 kernel.
> The only way to resolve it is - as far as we know - to reboot the system.
> Met vriendelijke groet,
> Stephan Leemburg
> IT Functions
> e: sleemburg at it-functions.nl
> p: +31 (0)71 889 23 33
> m: +31(0)6 83 22 30 69
> kvk: 27313647
> On 23-01-19 19:28, Thomas Lamprecht wrote:
> > Hi,
> > On 1/23/19 7:03 PM, Gilberto Nunes wrote:
> >> I am facing some trouble with 2 LXC that cannot access either kill it.
> >> Already try lxc-stop -k -n <name> but no effect.
> >> Any advice will be welcome...
> > does it have processes in the "D" (uninterruptible) state?
> > Probably because some network mount where it has IO pending.
> > In this case, where whatever storage device/mount does not comes
> > back to complete the IO your single way out may be a reboot...
> > You could check with ps either on the host (lots of processes) or from
> > inside the container, e.g. with:
> > # pct exec VMID ps faux
> > cheers,
> > Thomas
> > _______________________________________________
> > pve-user mailing list
> > pve-user at pve.proxmox.com
> > https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
> pve-user mailing list
> pve-user at pve.proxmox.com
More information about the pve-user