Hi Nick,
i haven't found a jira issue from you, have you filed it?
On 01/29/2016 05:04 AM, Nick Knutov wrote:
Yes, the question is about ploop of course.
How to get metadata of ploop image? `man what`?
If you are ok with a Container downtime, it's easy:
# e2image -r /dev/ploopXp1 - | bz
Hi there,
We are having issues with one container that cannot be stopped/suspended
or killed, all commands remain in Sleep or Running Sleep.
Any ideea how to stop this container withour rebooting the main machine?
We did try to kill all proceeses, they do not die.
CTID NPROC STATUS
Hi Bogdan,
This looks very much like a cpu scheduler lockup, as many of the processes
belonging to the container are in R state but not running.
Can you try resetting the cpulimit for the container in question,
something like
vzctl set $CTID --cpulimit 0
and see if anything changes?
Also, t
Greetings,
- Original Message -
> Hi there,
>
> We are having issues with one container that cannot be
> stopped/suspended
> or killed, all commands remain in Sleep or Running Sleep.
> Any ideea how to stop this container withour rebooting the main
> machine?
> We did try to kill all proc
I saw similar situation when container had configured cpu limit=0 via cgroup
interface.
As result container never get CPU and but their processes was in Running state.
On 04.02.2016 22:02, Kir Kolyshkin wrote:
> Hi Bogdan,
>
> This looks very much like a cpu scheduler lockup, as many of the proc
> On 04 Feb 2016, at 22:24, Vasily Averin wrote:
>
> I saw similar situation when container had configured cpu limit=0 via cgroup
> interface.
> As result container never get CPU and but their processes was in Running
> state.
My client says that at the time of the server crash he had been r
> On 04 Feb 2016, at 21:02, Kir Kolyshkin wrote:
>
> Hi Bogdan,
Hi!
>
> This looks very much like a cpu scheduler lockup, as many of the processes
> belonging to the container are in R state but not running.
>
> Can you try resetting the cpulimit for the container in question, something
> li
> On 04 Feb 2016, at 20:06, Scott Dowdle wrote:
>
> If you can get a pid list of what remains within the container, you can try
> to kill -9 it from the host node. You can use vzpid to map container pid
> references to host node pid references.
>
I did try to kill all of processes belonging
OK, I filed a bug about this:
https://bugs.openvz.org/browse/OVZ-6678
As my workaround worked for you too, I believe you hit the same bug.
Can you check CT config for CPU-related parameters (CPUS, CPUUNITS,
and CPULIMIT)?
On 02/04/2016 01:21 PM, Bogdan-Stefan Rotariu wrote:
On 04 Feb 2016, at
