On Nov 29, 2011, at 18:13, Hubert Krause
(by way of HubertKrause ) (by way of
HubertKrause ) wrote:
> Hello,
>
> my environment is a Debian squeeze host with a few debian squeeze
> guests. The private and root filesystems of the guest are locatet on
> the same raid device (raid5)
maybe offto
> On May 18, 2014, at 11:30, Denis Zinevich wrote:
>
> juts got fresh info which narrows problem:
> I was comparing normal and faulty containers, and found that they are using
> different kernels (on one server containers were not restarted after yum
> upgrade)
> so normal one was using 2.6.32
On 5/18/2014 11:41 PM, Kir Kolyshkin wrote:
Please always file bugs to https://bugzilla.openvz.org/ for such stuff.
I recommend not to use kernel 2.6.32-042stab085.20.
The latest stable kernel is currently 042stab088.4, released a month
ago.
I suggest everyone to use the latest stable ke
On 5/19/2014 7:17 AM, Kir Kolyshkin wrote:
Do you have any real issues, or is it just these messages that bug you?
If it's just messages, add nohz=off option to the kernel.
As I've stated two mails bellow, we had strange oops, io and clock
issues with 042stab085.20and with 042stab088.4
As 2.
Hi there,
We’ve done an maintenance for one server, and during the vz stop we saw this
errors in syslog.
Dec 22 02:31:45 vs4 kernel: [24023142.154143] CPT ERR: 8800bf6cb000,110
:unsupported deleted submount: (deleted)/var/named/chroot/etc/named.conf
Dec 22 02:32:48 vs4 kernel: [24023204.99
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
> 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
ng or two about our fair cpu
> scheduler.
Sorry, forgot to retrieve the info before setting cpulimit
Thank you Sir, you saved me from a reboot!
>
> Kir.
>
> On 02/04/2016 05:48 AM, Bogdan-Stefan Rotariu wrote:
>> Hi there,
>>
>> We are having issues with on
> 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I got a strange issue related to CentOS, kernel
2.6.18-53.1.13.el5.028stab053.10, and even 2.6.24.
I got a P4/3Ghz machine, which has vlans, and a ipv6 tunnel to he.net.
The problem with the 2.6.18 modified CentOS kernel, is that the ipv6,
does
Hi,
> Debian 6.0.1
> kernel 2.6.32-5-openvz-amd64
> tools vzctl version 3.0.24
>
This command is correct, the template must be without the archive extension
> # vzctl create 101 --ostemplate debian-6.0-amd64-minimal --config basic
>
> root@ispy2:/var/lib/vz/template/cache# vzctl create 102 --os
> Hi,
>
[...]
> I'm able to make the md/fuse devices but I've been unable to configure
> a container to additionally include fuse filesystem capability.
>
> vzctl set $id --devices b:9:2:rw c:10:229:rw --save
>
> then after starting the containers,
>
> vzctl exec $id mknod /dev/fuse c 10 229
> vz
12 matches
Mail list logo
