Hello
I'm experiencing a weird problem with htb and vservers. First, a bit
about my setup: the machine is a dual-core AMD64 (2.6.13.4, vserver
2.1.0-rc4) running 8 guests (where all but 3 are mostly idle). The 3
active guests are:
- d829 (a mysql server)
- v830
- v831 (two apache vservers)
The
(cross-post from: http://www.meulie.net/forum_viewtopic.php?94.4177 )
Hi all!
I'm attempting to install Nagios 2.x on a vserver. However, the build stops
with:
checking for ICMP ping syntax...
Has anyone else come across this problem before?
Regards,
Evert
On Mon, Nov 07, 2005 at 03:26:41PM +0100, Evert Meulie wrote:
(cross-post from: http://www.meulie.net/forum_viewtopic.php?94.4177 )
I'm attempting to install Nagios 2.x on a vserver. However, the build stops
with:
checking for ICMP ping syntax...
Has anyone else come across this
hmm, could you try with the mainline 0.30.209 please?
# vserver --version
vserver 0.30.209 -- manages the state of vservers
This program is part of util-vserver 0.30.209
Still:
$ ssh i386
Password:
Linux dusk 2.6.14-vs2.1.0-rc5+g3 #1 SMP Sat Nov 5 18:01:33 CET 2005 x86_64
GNU/Linux
Hi,
I think that this problem is related to the nonexisting 127.0.0.1
address. If I remeber correctly than nagios try to ping this address and
cant reach it
I think that I simply commented this check out in the scripts
Oliver
Evert Meulie wrote:
(cross-post from:
Given news like http://www.heise.de/newsticker/meldung/65815
I'd be interested in an informal comparison of Solaris zones
and VServer.
We actually discussed this several months ago at length. Check the archives
for the history of that conversation.
In a nutshell, here is my *opinion* [1] on
Hi all
I installed the kernel patches and utils successfully on my dual
xeon-ia32 fc4-x86_64 box now running
2.6.13-1.1532_FC4.vs2.0.1.0.pre2.1smp (after recompiling the SRPMS for
this arch). I use util-vserver 0.30.209-5.
Then, I adapted /etc/vservers/.distributions/fc4/apt/sources.list to
On Monday 07 November 2005 10:21 am, Oliver Welter wrote:
yes when I installed 1.2 on a guest I had to edit the configure file to change
all 127.0.0.1 to something like 127.0.0.3 which then passed the tests.
as a 'just in case' measure I also changed my hosts file to reflect this ip
for
On Mon, Nov 07, 2005 at 04:00:13PM +0100, Gilles wrote:
hmm, could you try with the mainline 0.30.209 please?
# vserver --version
vserver 0.30.209 -- manages the state of vservers
This program is part of util-vserver 0.30.209
Still:
$ ssh i386
Password:
Linux dusk
On Mon, Nov 07, 2005 at 01:58:09PM +0100, Grzegorz Nosek wrote:
Hello
I'm experiencing a weird problem with htb and vservers. First, a bit
about my setup: the machine is a dual-core AMD64 (2.6.13.4, vserver
2.1.0-rc4) running 8 guests (where all but 3 are mostly idle). The 3
active guests
On Mon, Nov 07, 2005 at 05:27:56PM +0100, Marcel Gsteiger wrote:
Hi all
I installed the kernel patches and utils successfully on my dual
xeon-ia32 fc4-x86_64 box now running
xeon-ia32 with x86_64 ? well, folks @ intel must
be drinking ...
2.6.13-1.1532_FC4.vs2.0.1.0.pre2.1smp (after
On Mon, 2005-11-07 at 13:58 +0100, Grzegorz Nosek wrote:
The test cases I've found are:
- no QoS at all
everything runs smoothly
- root qdisc on eth0 set to htb (or pfifo, or sfq)
still everything nice and smooth
- default class on eth0 set to htb (rate 1Gbit, so it's not true
bandwith
Hi.
lsattr: Inappropriate ioctl for device While reading flags on
/var/lib/vservers/
no idea, but sounds like your filesystem @ /var/lib/vservers
doesn't support the barrier ...
It's an LVM volume with reiserfs.
this means you forgot to specify the 'attrs' option
which
I have many ip addresses on each of 4 ethernet cards using iproute2.
one of my guests must absolutely always send and receive on a certain ip
address which is not the first ip on the card. I have bound the service
(radius) to that ip which is the only one the guest is given. I have not
proven
On Mon, Nov 07, 2005 at 11:50:39PM +0100, Gilles wrote:
Hello.
just for the record, on IRC we found out that:
- a guest script was setting the host name to dusk
I deactivated that script, so now it works but... It
seems as if the guest takes a little time to make up
its mind
On Mon, Nov 07, 2005 at 11:08:38PM +0100, Gilles wrote:
Hi.
lsattr: Inappropriate ioctl for device While reading flags on
/var/lib/vservers/
no idea, but sounds like your filesystem @ /var/lib/vservers
doesn't support the barrier ...
It's an LVM volume with
Linux dusk 2.6.14-vs2.1.0-rc5+g3 #1 SMP Sat Nov 5 18:01:33 CET 2005 i386
GNU/Linux
hmm, I'd assume this comes from /etc/issue .. while
From /etc/motd, which probably by coincidence contained the right (well,
wrong, in the case of the host) architecture specification. It must have
been
Do you mean CONFIG_REISERFS_FS_XATTR in the kernel config?
well, this might also be responsible, but, for
unknwon reasons, you need to _also_ specfiy the
'attrs' mount option if you want to use attributes
on resier filesystems ...
attrs seems to be enough:
# showattr
18 matches
Mail list logo