On 10/04/2013 12:05 PM, Joe Doss wrote:
On 10/03/2013 09:21 PM, Kir Kolyshkin wrote:
I went ahead and mocked up something. Please run the attached script on
your node
and share your results.
Great script Kir. I gave it a try and I don't think it is calculating
VSwap correctly:
Swap avail
On 10/03/2013 09:21 PM, Kir Kolyshkin wrote:
> I went ahead and mocked up something. Please run the attached script on
> your node
> and share your results.
Great script Kir. I gave it a try and I don't think it is calculating
VSwap correctly:
Swap available: 12G allocated: 32Z overse
On 10/03/2013 12:03 PM, Mark J. wrote:
On Thu, Oct 03, 2013 at 10:41:41AM -0700, Kir Kolyshkin wrote:
Also, I wonder how much RAM do you have on your server, and how
many such containers do you run on it?
Nodes have 32G on them, this particular node only allows up to 40 vm's due to
the cPanel
On Thu, Oct 03, 2013 at 10:41:41AM -0700, Kir Kolyshkin wrote:
> >>Also, I wonder how much RAM do you have on your server, and how
> >>many such containers do you run on it?
> >Nodes have 32G on them, this particular node only allows up to 40 vm's due
> >to the cPanel vm's having either 2, 3, or 4
On Thu, Oct 03, 2013 at 10:41:41AM -0700, Kir Kolyshkin wrote:
> As you can see, there are both ram (physpages) and swap fails.
> There is nothing wrong with the current behaviour -- if all RAM
> and swap is gone, there is absolutely no other way than to kill
> some process.
>
> So OOM killer conf
On 10/03/2013 07:26 AM, Mark J. wrote:
On Wed, Oct 02, 2013 at 03:47:48PM -0700, Kir Kolyshkin wrote:
On 10/02/2013 12:07 PM, Mark J. wrote:
On Wed, Oct 02, 2013 at 11:48:02AM -0700, Kir Kolyshkin wrote:
I suggest you to just put * as parent name then.
Will give that a try now that I have th
On Wed, Oct 02, 2013 at 03:47:48PM -0700, Kir Kolyshkin wrote:
> On 10/02/2013 12:07 PM, Mark J. wrote:
> >On Wed, Oct 02, 2013 at 11:48:02AM -0700, Kir Kolyshkin wrote:
> I suggest you to just put * as parent name then.
>
Will give that a try now that I have the other info you asked for below:
On 10/02/2013 12:07 PM, Mark J. wrote:
On Wed, Oct 02, 2013 at 11:48:02AM -0700, Kir Kolyshkin wrote:
15195 ?S 0:00 /bin/sh /usr/bin/mysqld_safe
--datadir=/var/lib/mysql --pid-file=/var/lib/mysql/server.noticias365.net.pid
31661 ?Sl 1:43 \_ /usr/sbin/mysqld --basedir=/
On Wed, Oct 02, 2013 at 11:48:02AM -0700, Kir Kolyshkin wrote:
> >15195 ?S 0:00 /bin/sh /usr/bin/mysqld_safe
> >--datadir=/var/lib/mysql --pid-file=/var/lib/mysql/server.noticias365.net.pid
> >31661 ?Sl 1:43 \_ /usr/sbin/mysqld --basedir=/usr
> >--datadir=/var/lib/mysql
On 10/02/2013 10:10 AM, Mark J. wrote:
On Tue, Oct 01, 2013 at 04:37:52PM -0700, Kir Kolyshkin wrote:
I'd suggest you to reproduce the bug on 081.3 kernel booted for real,
and if you succeed, file a kernel bug to bugzilla.openvz.org.
Will put in the request to try and get one upgraded (or next
On Tue, Oct 01, 2013 at 04:37:52PM -0700, Kir Kolyshkin wrote:
> I'd suggest you to reproduce the bug on 081.3 kernel booted for real,
> and if you succeed, file a kernel bug to bugzilla.openvz.org.
Will put in the request to try and get one upgraded (or next node build on the
new kernel)
> Also
On 10/01/2013 03:54 PM, Mark J. wrote:
I knew I was missing something in there, kernel is:
2.6.32-042stab068.8
We also use ksplice, so its currently patched to:
Effective kernel version is 2.6.32-042stab081.3
I'd suggest you to reproduce the bug on 081.3 kernel booted for real,
and if you su
I knew I was missing something in there, kernel is:
2.6.32-042stab068.8
We also use ksplice, so its currently patched to:
Effective kernel version is 2.6.32-042stab081.3
On Tue, Oct 01, 2013 at 03:25:58PM -0700, Roman Haefeli wrote:
> It's strongly advised to report the exact kernel version alo
It's strongly advised to report the exact kernel version along with a
problem report. It's not unlikely your problem is specific to the kernel
version, especially if you use an OpenVZ kernel from Debian Squeeze.
Roman
On Tue, 2013-10-01 at 14:45 -0400, Mark J. wrote:
> Hello,
>
> I have been try
14 matches
Mail list logo