Have a strange vm issues.
Getting the following errors on a vm's boot:
/bin/bash: line 616: /dev/null: No such device or address
/bin/bash: line 588: /dev/null: No such device or address
/bin/bash: line 593: /dev/null: No such device or address
/bin/bash: line 559: /dev/null: No such device or ad
/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1258280k)
> devpts on /dev/pts type devpts
> (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
>
> root@fwd1:~# swapoff -av
> swapoff on /dev/null
> swapoff: Not superuser.
>
>
>
> On 08/22/2013 10:54
Hello,
I have been trying to tweak the OOM killer to prevent some database corruption
thats been happening in the VM's when the oom killer kills off mysql. Based on
what i have read online and in the conf file itself I am a bit confused on why
its not killing other things off before mysql.
Bas
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 ha
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 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 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
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 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
Noticing that the write counter is not incrementing in the beancounter file,
nor is it allowing the cgroups to limit the writes either (guessing since the
counter isn't changing the cgroup isn't being applied since its not seeing a
change).
This is what I am setting for a test:
echo "9:1 10485
On Mon, Oct 28, 2013 at 11:29:05AM -0400, Simon Boulet wrote:
> Hi Mark,
>
> On Thu, Oct 17, 2013 at 5:02 PM, Mark J. wrote:
> > Noticing that the write counter is not incrementing in the beancounter
> > file, nor is it allowing the cgroups to limit the writes either (gu
11 matches
Mail list logo
