Re: [Vserver] Error -- E: Couldn't find package glibc

2005-08-12 Thread Roderick A. Anderson
On Sat, 13 Aug 2005, Herbert Poetzl wrote:

> it is missing on the repository/in the rpm list
> to get the guest installed from not on your host
> system ...

I was thinking this but it seemd strange that such an important package 
would be missing.  When I looked in the sources.list in 
/etc/vservers/.distributions/fc3/apt/ I see what looks like all the sites 
as being commented out.  In fact they look _really_ broken in comparison 
to /etc/apt/sources.list.d/mirror-select.list file.

Is there a fairly easy method to build a guest using yum ( or straight rpm 
) since I know they are working?

> where, and how did you get the rpms for your tests?

Built from the sources --  util-vserver-0.30.208.tar.bz2

As I was driving home this evening I realized I might have had some
artifacts from a previous install ( months ago -- that has sat around as I
waited the vs2 release and some time to work on the server ) that were
polluting the set up.  I read in one of the threads that Enrico had made
this change already.  More research to do.


Rod
-- 
"Open Source Software - You usually get more than you pay for..."
 "Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL"


___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


Re: [Vserver] utils' fix01 : build problem

2005-08-12 Thread intrigeri
Hello,

Herbert Poetzl wrote (12 Aug 2005 17:37:02 +0200) :
> On Fri, Aug 12, 2005 at 03:58:15PM +0200, intrigeri wrote:
>> Hello,
>> 
>> on a Debian Sarge PPC box (gcc 3.3.5), compiling and running
>> util-vserver 0.30.208 works perfectly, but after applying the fix01
>> patch on a fresh source tree & configuring as usual, "make" fails :
>
> ist this PPC or PPC64?

It's PPC.

> could you arrange an account there for me?

I'm sorry, I can't.

P.S.: I read the list, no need to Cc: me :)

Ciao,
-- 
  intrigeri <[EMAIL PROTECTED]>
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


Re: [Vserver] Inconsitent handling of mounts with 2.4.31-vs1.2.10 on Fedora 1

2005-08-12 Thread Herbert Poetzl
On Fri, Aug 12, 2005 at 09:03:39PM -0400, Stephen Harris wrote:
> On Fri, Aug 12, 2005 at 01:55:30AM +0200, Herbert Poetzl wrote:
> > On Thu, Aug 11, 2005 at 09:56:20AM -0400, Stephen Harris wrote:
> > > 
> > >   [root]/home/sweh
> > >   backup.pts/2% mount -r backup:/RedHat/updates/core1 
> > > /vservers/webssh/RedHat
> > 
> > no idea 'what' filesystem you did mount here, but to me
> > it looks like a network filesystem (i.e. nfs)
> 
> Yes, it is. In fact it's an NFS mount from myself to myself; I can't
> use bind mounts because I want the vservers to only have read-only
> access to the filesystem, and bind mounts don't (or didn't, last time
> I tried) allow changes in permissions between the original location
> and the bound location.

yeah, right, that's where my BME (Bind Mount Extension)
patches come into play (fixing this mainline 'bug/feature')

> > >   backup.pts/2% vserver webssh enter
> > >   SIOCSIFBRDADDR: Cannot assign requested address
> > >   SIOCSIFFLAGS: Cannot assign requested address
> > 
> > this is a good sign of a broken config (network wise)
> 
> Network wise, it actually works. I had thought this had come from the
> guest OS trying to do stuff, but I'm a vserver newbie. Hmm.
> 
> Ah... maybe it's because I'm using a 10.* address but have a
> 255.255.255.0 netmask; I left IPROOTMASK and IPROOTBCAST unset, so
> _maybe_ it's attempting to calculate based on a 255.0.0.0 mask, and
> failing to set them. Hmm, no, that's not it. I just tried.
> 
> Could this be ipv6, perhaps?  I'm not using ipv6.
> 
> I had noticed that inside the vserver, an "ifconfig -a" shows _all_
> the hosts IP addresses, and not just the one in the vserver.
> 
> But otherwise it all works.
> 
> > >   ipv4root is now 10.0.0.2
> 
> This is the correct address.
> 
> > >   New security context is 49173
> > 
> > and just as sidenote, you should avoid dynamic context
> > ids, unless you are looking for trouble :)
> 
> OK; I'm new vserver newbie and just took the defaults which said
> 
>   # Select an unused context (this is optional)
>   # The default is to allocate a free context on the fly
>   # In general you don't need to force a context

what defaults are those? 

> but I'll take your advice and have assigned fixed contexts now (10001
> and 10002).
> 
> > >   bash: ulimit: core file size: cannot modify limit: Invalid argument
> > 
> > this looks evem more like a debian^Wconfig issue, where
> > you specified a limit (maybe -H or -S) without raising
> > the proper other limit (specify -HS to solve that)
> 
> No, it appears to be from my .profile inside the guest. For historical
> reasons I had "ulimit -Sc unlimited" for my own account, and this
> seems to be read when entering the guest.
> 
> > this is a different IP than the one before, NFS isn't
> > handled that well on 2.4, but of course, the guest 
> > will send requests with 10.0.0.3 now, which, in turn
> > might lead to the Permission denied (if your server 
> > does not allow 10.0.0.3 to access the share)
> 
> The server allows the whole 10.0.0.* network (my home network).
> 
> Will the guest make a request? The guest hasn't actually made the
> mount; the host has made the mount and has made it available to the
> guest. So will the request come from the guest's IP address, or will
> it fall through to the host, and the host make the request.

the host will make the request, but with the guest's ip
(NFS isn't really supported with 2.4/1.2.x)

> Ah, OK... some network snooping... the request comes from the guest IP
> address. That's... broken! The mount came from the host IP address but
> the nfs requests came from the guest IP adrress. Hmm.. I'm surprised
> it ever worked!

well, it is how networking works right now :)

> OK, what's the best way of providing a filesystem to the guest with
> read-only privs? Clearly NFS is a kludge.

see BME note above ...

> Huh.. that's odd... I just shut down _all_ vservers and restarted them
> and now the mount works in both vserver instances that seems like
> something confused, but I can probably live with it; my mounts have so
> far worked.
>
> But it does look like I need better solution; how to make a filesystem
> available to a vserver with differnt permissions than the host has?
> 
> > hmm, and IDE hotswapping did work with 2.4 but does
> > not with 2.6? interesting ...
> 
> Yeah, it's very annoying.  Alan Cox has a lot to say about it!

he probably has ... fixing it would be better, though :)

best,
Herbert

> -- 
> 
> rgds
> Stephen
> ___
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


Re: [Vserver] Inconsitent handling of mounts with 2.4.31-vs1.2.10 on Fedora 1

2005-08-12 Thread Stephen Harris
On Fri, Aug 12, 2005 at 01:55:30AM +0200, Herbert Poetzl wrote:
> On Thu, Aug 11, 2005 at 09:56:20AM -0400, Stephen Harris wrote:
> > 
> >   [root]/home/sweh
> >   backup.pts/2% mount -r backup:/RedHat/updates/core1 
> > /vservers/webssh/RedHat
> 
> no idea 'what' filesystem you did mount here, but to me
> it looks like a network filesystem (i.e. nfs)

Yes, it is.   In fact it's an NFS mount from myself to myself; I can't use
bind mounts because I want the vservers to only have read-only access to
the filesystem, and bind mounts don't (or didn't, last time I tried) allow
changes in permissions between the original location and the bound location.

> >   backup.pts/2% vserver webssh enter
> >   SIOCSIFBRDADDR: Cannot assign requested address
> >   SIOCSIFFLAGS: Cannot assign requested address
> 
> this is a good sign of a broken config (network wise)

Network wise, it actually works.  I had thought this had come from the guest
OS trying to do stuff, but I'm a vserver newbie.  Hmm.

Ah... maybe it's because I'm using a 10.* address but have a 255.255.255.0
netmask; I left IPROOTMASK and IPROOTBCAST unset, so _maybe_ it's attempting
to calculate based on a 255.0.0.0 mask, and failing to set them.  Hmm, no,
that's not it.  I just tried.

Could this be ipv6, perhaps?  I'm not using ipv6.

I had noticed that inside the vserver, an "ifconfig -a" shows _all_
the hosts IP addresses, and not just the one in the vserver.

But otherwise it all works.

> >   ipv4root is now 10.0.0.2

This is the correct address.

> >   New security context is 49173
> 
> and just as sidenote, you should avoid dynamic context
> ids, unless you are looking for trouble :)

OK; I'm new vserver newbie and just took the defaults which said

  # Select an unused context (this is optional)
  # The default is to allocate a free context on the fly
  # In general you don't need to force a context

but I'll take your advice and have assigned fixed contexts now (10001
and 10002).

> >   bash: ulimit: core file size: cannot modify limit: Invalid argument
> 
> this looks evem more like a debian^Wconfig issue, where
> you specified a limit (maybe -H or -S) without raising
> the proper other limit (specify -HS to solve that)

No, it appears to be from my .profile inside the guest.  For historical
reasons I had "ulimit -Sc unlimited" for my own account, and this seems
to be read when entering the guest.

> this is a different IP than the one before, NFS isn't
> handled that well on 2.4, but of course, the guest 
> will send requests with 10.0.0.3 now, which, in turn
> might lead to the Permission denied (if your server 
> does not allow 10.0.0.3 to access the share)

The server allows the whole 10.0.0.* network (my home network).

Will the guest make a request?  The guest hasn't actually made the mount;
the host has made the mount and has made it available to the guest.
So will the request come from the guest's IP address, or will it fall
through to the host, and the host make the request.

Ah, OK... some network snooping... the request comes from the guest
IP address.  That's... broken!  The mount came from the host IP address
but the nfs requests came from the guest IP adrress.  Hmm.. I'm surprised
it ever worked!

OK, what's the best way of providing a filesystem to the guest with
read-only privs?  Clearly NFS is a kludge.

Huh.. that's odd... I just shut down _all_ vservers and restarted them and now
the mount works in both vserver instances  that seems like something
confused, but I can probably live with it; my mounts have so far worked.

But it does look like I need better solution; how to make a filesystem
available to a vserver with differnt permissions than the host has?

> hmm, and IDE hotswapping did work with 2.4 but does
> not with 2.6? interesting ...

Yeah, it's very annoying.  Alan Cox has a lot to say about it!

-- 

rgds
Stephen
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


Re: [Vserver] Error -- E: Couldn't find package glibc

2005-08-12 Thread Herbert Poetzl
On Fri, Aug 12, 2005 at 02:31:16PM -0700, Roderick A. Anderson wrote:
> I'm still playing and have backed out the OpenVPS rpms to see what it 
> takes to run vservers with vs2.0 and the util-vserver commands
> 
> While trying to build a new guest I'm having problems.
> 
> # vserver ref build -m apt-rpm --hostname=ref.tsmg.us --interface 
> eth1:192.168.25.69/24 -- -d fc3
> 
> Renamed '/vservers/ref' to '/vservers/ref.~1123881581~'
> Renamed '/usr/local/etc/vservers/ref' to 
> '/usr/local/etc/vservers/ref.~1123881581~'
> Renamed '/vservers/.pkg/ref' to '/vservers/.pkg/ref.~1123881581~'
> Reading Package Lists... Done
> Building Dependency Tree... Done
> Reading Package Lists... Done
> Building Dependency Tree... Done
> E: Couldn't find package glibc
> rm -rf /vservers/ref /usr/local/etc/vservers/ref /vservers/.pkg/ref
> 
> I've checked, updated, and re-updates to include glibc.  Is there another 
> package that goes by a similar name that I'm missing?  Here is what I've 
> got.

it is missing on the repository/in the rpm list
to get the guest installed from not on your host
system ...

> # rpm -qa | grep glibc
> 
> glibc-common-2.3.5-0.fc3.1
> glibc-headers-2.3.5-0.fc3.1
> glibc-2.3.5-0.fc3.1
> glibc-devel-2.3.5-0.fc3.1
> glibc-kernheaders-2.4-9.1.87
> 
> And one lst thing.  How in the do I get util-vserver to use /etc/vservers
> instead lf /usr/local/etc/vservers?  

usually that is specified with --prefix and other 
path related options, for sure the mandrake rpms
I provide do place them in /etc and /vservers but
other distros might handle that differently ...

> I tried by modifying the spec file but that appears to no be working.  
> Is there a switch I can use with rpmbuild?

maybe, usually this kind of information is hardcoded
into the distribution, but I doubt that your distro
places config files in //usr/local/etc so something
seems wrong ... 

where, and how did you get the rpms for your tests?

best,
Herbert

> Rod
> -- 
> "Open Source Software - You usually get more than you pay for..."
>  "Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL"
> 
> 
> ___
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


Re: [Vserver] tagxid redux?

2005-08-12 Thread Herbert Poetzl
On Fri, Aug 12, 2005 at 10:42:45AM -0700, Roderick A. Anderson wrote:
> Well my questions 
> ( which I'm shooting all over as I find a new place to ask :-) are:
> 
> "What is tagxid?"

a mount option, required to utilize the persistant
context file tagging ...

http://linux-vserver.org/Linux-VServer-Paper-04
(section 04.5 Filesystem XID Tagging)

> "Are there any problems with using this on a single partition ( well
> there is also a swap partition but no /vservers) hardware RAID cause
> any problems?"

yes, because context creation happens between
host and guest context, and files written at this
time might easily mess up your host system ...

so let me tell you: an xid tagged rootfs is not
a good idea ... unless you are looking for trouble

> There was a thread last November/December on tagxid but it dealt with
> why it was used/needed.

well, that's something :)

best,
Herbert

> TIA,
> Rod
> -- 
> "Open Source Software - You usually get more than you pay for..."
>  "Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL"
> 
> 
> ___
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


Re: [Vserver] clone-srcipt?

2005-08-12 Thread Gilles

> Did anyone already create a sript that copies an existing guest to a new 
> name and changes ip/context/name etc. within (for debian in my case)?
> 

The tools/utils provide a "vserver-copy" command.


Best regards.
Gilles
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


[Vserver] clone-srcipt?

2005-08-12 Thread Andreas John

Hello!

Did anyone already create a sript that copies an existing guest to a new 
name and changes ip/context/name etc. within (for debian in my case)?


Rgds,
Andreas




___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


[Vserver] Error -- E: Couldn't find package glibc

2005-08-12 Thread Roderick A. Anderson
I'm still playing and have backed out the OpenVPS rpms to see what it 
takes to run vservers with vs2.0 and the util-vserver commands

While trying to build a new guest I'm having problems.

# vserver ref build -m apt-rpm --hostname=ref.tsmg.us --interface 
eth1:192.168.25.69/24 -- -d fc3

Renamed '/vservers/ref' to '/vservers/ref.~1123881581~'
Renamed '/usr/local/etc/vservers/ref' to 
'/usr/local/etc/vservers/ref.~1123881581~'
Renamed '/vservers/.pkg/ref' to '/vservers/.pkg/ref.~1123881581~'
Reading Package Lists... Done
Building Dependency Tree... Done
Reading Package Lists... Done
Building Dependency Tree... Done
E: Couldn't find package glibc
rm -rf /vservers/ref /usr/local/etc/vservers/ref /vservers/.pkg/ref

I've checked, updated, and re-updates to include glibc.  Is there another 
package that goes by a similar name that I'm missing?  Here is what I've 
got.

# rpm -qa | grep glibc

glibc-common-2.3.5-0.fc3.1
glibc-headers-2.3.5-0.fc3.1
glibc-2.3.5-0.fc3.1
glibc-devel-2.3.5-0.fc3.1
glibc-kernheaders-2.4-9.1.87

And one lst thing.  How in the do I get util-vserver to use /etc/vservers
instead lf /usr/local/etc/vservers?  I tried by modifying the spec file
but that appears to no be working.  Is there a switch I can use with 
rpmbuild?


Rod
-- 
"Open Source Software - You usually get more than you pay for..."
 "Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL"


___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


Re: [Vserver] tagxid redux?

2005-08-12 Thread Roderick A. Anderson
On Fri, 12 Aug 2005, Roderick A. Anderson wrote:

I have an answer.

> Well my questions ( which I'm shooting all over as I find a new place to 
> ask :-) are:
> 
> "What is tagxid?"
> 
> "Are there any problems with using this on a single partition ( well there
> is also a swap partition but no /vservers) hardware RAID cause any
> problems?"
> 
> There was a thread last November/December on tagxid but it dealt with why 
> it was used/needed.
> 
> 
> TIA,
> Rod
> 

-- 
"Open Source Software - You usually get more than you pay for..."
 "Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL"


___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


[Vserver] Re: util-vserver 0.30.208 debs?

2005-08-12 Thread John Goerzen
On 2005-08-12, Micah Anderson <[EMAIL PROTECTED]> wrote:
> On Fri, 12 Aug 2005, John Goerzen wrote:
>> 1) Has anyone made 0.30.208 debs?
>
> The debian maintainer is working on .208 debs now:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=321659

It was really trivial (<5 min) to take the 207 and make 208 debs.  I've
posted my source packages at http://www.complete.org/~jgoerzen/vs/ for
anyone that wants them.

They include fix1.

-- John

___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


[Vserver] tagxid redux?

2005-08-12 Thread Roderick A. Anderson
Well my questions ( which I'm shooting all over as I find a new place to 
ask :-) are:

"What is tagxid?"

"Are there any problems with using this on a single partition ( well there
is also a swap partition but no /vservers) hardware RAID cause any
problems?"

There was a thread last November/December on tagxid but it dealt with why 
it was used/needed.


TIA,
Rod
-- 
"Open Source Software - You usually get more than you pay for..."
 "Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL"


___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


Re: [Vserver] util-vserver 0.30.208 debs?

2005-08-12 Thread Andreas John

Hi!

HAve you considered the libbeecrypt problem I reported this night, might 
be debian specific?


And I get the following problem when buildinf vashify:

> checking for sys/capability.h... yes
> checking beecrypt/beecrypt.h usability... yes
> checking beecrypt/beecrypt.h presence... yes
> checking for beecrypt/beecrypt.h... yes
> checking for hashFunctionContextInit in -lbeecrypt... no
> configure: WARNING:
> 
>  'beecrypt' could not be found;
>  this will disable the build of 'vhashify'
> 

Bertl told that he can compile it von -mdk versions .

I didn't file a bug anywhere, because I am not sure what's the right 
place  debian or savannah 


rgds,
j.



Micah Anderson wrote:

On Fri, 12 Aug 2005, John Goerzen wrote:



Hi,

Herbert was advising me on IRC to not use 0.30.207 with a new vs2.0
installation because 207 is broken upstream, and because the Debian
package adds some additional brokenness.

So I have two questions:

1) Has anyone made 0.30.208 debs?



The debian maintainer is working on .208 debs now:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=321659



2) Does anyone know what this additional brokenness in the Debian
packages is?



Part of the problem is .207 is several months old, and many things were
fixed between that release and .208, in fact there are additional fixes that
Bertl have done for .208. 


I am not aware of Debian specific package brokenness, but I would like to
know if there are such things so we can file bugs and get those fixed, poste
haste.

micah

___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver




--
Andreas John
net-lab GmbH
Luisenstrasse 30b
63067 Offenbach
Tel: +49 69 85700331

http://www.net-lab.net
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


Re: [Vserver] util-vserver 0.30.208 debs?

2005-08-12 Thread Micah Anderson
On Fri, 12 Aug 2005, John Goerzen wrote:

> Hi,
> 
> Herbert was advising me on IRC to not use 0.30.207 with a new vs2.0
> installation because 207 is broken upstream, and because the Debian
> package adds some additional brokenness.
> 
> So I have two questions:
> 
> 1) Has anyone made 0.30.208 debs?

The debian maintainer is working on .208 debs now:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=321659

> 2) Does anyone know what this additional brokenness in the Debian
> packages is?

Part of the problem is .207 is several months old, and many things were
fixed between that release and .208, in fact there are additional fixes that
Bertl have done for .208. 

I am not aware of Debian specific package brokenness, but I would like to
know if there are such things so we can file bugs and get those fixed, poste
haste.

micah

___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


[Vserver] util-vserver 0.30.208 debs?

2005-08-12 Thread John Goerzen
Hi,

Herbert was advising me on IRC to not use 0.30.207 with a new vs2.0
installation because 207 is broken upstream, and because the Debian
package adds some additional brokenness.

So I have two questions:

1) Has anyone made 0.30.208 debs?

2) Does anyone know what this additional brokenness in the Debian
packages is?

Thanks,

-- John

___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


Re: [Vserver] utils' fix01 : build problem

2005-08-12 Thread Herbert Poetzl
On Fri, Aug 12, 2005 at 03:58:15PM +0200, intrigeri wrote:
> Hello,
> 
> on a Debian Sarge PPC box (gcc 3.3.5), compiling and running
> util-vserver 0.30.208 works perfectly, but after applying the fix01
> patch on a fresh source tree & configuring as usual, "make" fails :

ist this PPC or PPC64?

could you arrange an account there for me?

TIA,
Herbert

> make[2]: Entering directory 
> `/home/intrigeri/vserver/util-vserver-0.30.208+fix01'
> if diet -Os gcc -DHAVE_CONFIG_H -I. -I. -I.  -I ./lib -I ./ensc_wrappers 
> -D_GNU_SOURCE -D_REENTRANT  -DNDEBUG   -g -O2 -std=c99 -Wall -pedantic -W -MT 
> lib/lib_libvserver_a-syscall.o -MD -MP -MF 
> "lib/.deps/lib_libvserver_a-syscall.Tpo" -c -o lib/lib_libvserver_a-syscall.o 
> `test -f 'lib/syscall.c' || echo './'`lib/syscall.c; \
> then mv -f "lib/.deps/lib_libvserver_a-syscall.Tpo" 
> "lib/.deps/lib_libvserver_a-syscall.Po"; else rm -f 
> "lib/.deps/lib_libvserver_a-syscall.Tpo"; exit 1; fi
> In file included from lib/syscall.c:40:
> lib/syscall-legacy.hc: In function `set_ipv4root_rev0':
> lib/syscall-legacy.hc:84: warning: asm operand 0 probably doesn't match 
> constraints
> lib/syscall-legacy.hc: In function `set_ipv4root_rev1':
> lib/syscall-legacy.hc:85: warning: asm operand 0 probably doesn't match 
> constraints
> lib/syscall-legacy.hc: In function `set_ipv4root_rev2':
> lib/syscall-legacy.hc:86: warning: asm operand 0 probably doesn't match 
> constraints
> lib/syscall-legacy.hc: In function `set_ipv4root_rev3':
> lib/syscall-legacy.hc:87: warning: asm operand 0 probably doesn't match 
> constraints
> lib/syscall-legacy.hc: In function `new_s_context_rev0':
> lib/syscall-legacy.hc:103: warning: asm operand 0 probably doesn't match 
> constraints
> lib/syscall-legacy.hc: In function `set_ipv4root_rev0':
> lib/syscall-legacy.hc:84: error: impossible constraint in `asm'
> make[2]: *** [lib/lib_libvserver_a-syscall.o] Error 1
> make[2]: Leaving directory 
> `/home/intrigeri/vserver/util-vserver-0.30.208+fix01'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory 
> `/home/intrigeri/vserver/util-vserver-0.30.208+fix01'
> make: *** [all] Error 2
> 
> 
> Any idea ?
> 
> Ciao,
> -- 
>   intrigeri <[EMAIL PROTECTED]>



> ___
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver

___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


Re: [Vserver] My adventures with vs2.0 ... :-)

2005-08-12 Thread Roderick A. Anderson
On Fri, 12 Aug 2005, Herbert Poetzl wrote:

> > > maybe a lot .. don't you have an existing, well
> > > tuned config for your server? if not, a .config
> > > file would be helpful here ...
> > 
> > The old .config would have been for vs1.9.4.  This Ok?  
> 
> should be fine, copy it over into the new kernel
> tree (as .config) and run 'make oldconfig' ...
> the script will ask you for new options, in case
> of doubt, use the default ...

YES!!!

I got it built and it boots.  I fell back to using ( actually I finally
remembered how I'd build the vs1.9.4 kernel ) the instructions at
OpenVPS.org.

I found two differences there.  One was covered -- vdlimit is now part of 
util-vserver but the option to build for other than i386 was incorrect and 
I couldn't find a solution.  A task for later.  For now I have a running 
2.6.12.4vs2.0 kernel and I'm going to run the test Herbert has when I get 
into work.

A special thanks to Herbert for having so much patience with my less than
clue-full questions and to the OpenVPS folks for a great set of
instructions.


Rod
-- 
"Open Source Software - You usually get more than you pay for..."
 "Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL"


___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


Re: [Vserver] you should not use dynamic contexts for guests ...

2005-08-12 Thread Herbert Poetzl
On Fri, Aug 12, 2005 at 02:49:36PM +0200, Francois Duchatelet wrote:
>  
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Hi all vserver freaks :-),
> 
> Since the use of the alpha tools, I see this sentence everywhere.

no basically since the first release vs1.00 the dynamic
contexts are deprecated (you only use them for on-the-fly
isolation and testing)

> Why is this so?

because certain things are connected with a context
and sooner or later folks start using the shared disk
limits (or similar) which involves context file tagging
and *bang* you end up with all kind of strange issues ...

also context creation with dynamic contexts is racy by
design, and does move policy into the kernel (where
it definitely doesn't belong)

> Using static contexts forces us to manage them, just like ip adresses.

once, when you create a guest, yes, but that's about it

as benefit you get a 'stable' environment, where you
always _know_ which process/file/socket belongs to what
context, regardless of the guest state

here an example:

 guest 'hansi' starts with dynamic context 49152, it
 then opens a few network connections and dies a horribly
 death, because the administrator did a vkill/shutdown
 but, what about the network connections? of course, they
 will linger around until certain timeouts are met (which
 is how linux systems behave)

I guess you can imagine what happens if a different
guest starts with xid = 49152 or the same guest (now with
xid = 49153) tries to use those addresses/sockets ...

> This is specially annoying for master/backup vservers running on
> different machines.

why? nothing stops you from using 'unique' context IDs
for each guest, regardless of master or backup ...

on the contrary, this would allow for a real backup guest
even if you are using a shared disk or nfs volume ...

best,
Herbert

> Cheers
> 
> François Duchatelet,
> Ariane Services
> Rue du Verregat, 12
> B-1020 Brussels
> TEL:+32(2)479.37.59 - FAX:+32(2)478.14.20
> Mobile:+32(486)13.07.85 - +31 (6) 47044881 
> GPS: 4°19'59" E 50°54'03" N
> 
> -BEGIN PGP SIGNATURE-
> Version: PGP 8.0.3
> 
> iQA/AwUBQvya3+Xix9dFBcbpEQJ+xgCfdDYy2cgGdCg1dNCEUq4DoG6sYvoAoN0e
> STPn/Z3fSVLJA75d7SyJY37i
> =xVqh
> -END PGP SIGNATURE-
> 
> 
> ___
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


[Vserver] utils' fix01 : build problem

2005-08-12 Thread intrigeri
Hello,

on a Debian Sarge PPC box (gcc 3.3.5), compiling and running
util-vserver 0.30.208 works perfectly, but after applying the fix01
patch on a fresh source tree & configuring as usual, "make" fails :

make[2]: Entering directory 
`/home/intrigeri/vserver/util-vserver-0.30.208+fix01'
if diet -Os gcc -DHAVE_CONFIG_H -I. -I. -I.  -I ./lib -I ./ensc_wrappers 
-D_GNU_SOURCE -D_REENTRANT  -DNDEBUG   -g -O2 -std=c99 -Wall -pedantic -W -MT 
lib/lib_libvserver_a-syscall.o -MD -MP -MF 
"lib/.deps/lib_libvserver_a-syscall.Tpo" -c -o lib/lib_libvserver_a-syscall.o 
`test -f 'lib/syscall.c' || echo './'`lib/syscall.c; \
then mv -f "lib/.deps/lib_libvserver_a-syscall.Tpo" 
"lib/.deps/lib_libvserver_a-syscall.Po"; else rm -f 
"lib/.deps/lib_libvserver_a-syscall.Tpo"; exit 1; fi
In file included from lib/syscall.c:40:
lib/syscall-legacy.hc: In function `set_ipv4root_rev0':
lib/syscall-legacy.hc:84: warning: asm operand 0 probably doesn't match 
constraints
lib/syscall-legacy.hc: In function `set_ipv4root_rev1':
lib/syscall-legacy.hc:85: warning: asm operand 0 probably doesn't match 
constraints
lib/syscall-legacy.hc: In function `set_ipv4root_rev2':
lib/syscall-legacy.hc:86: warning: asm operand 0 probably doesn't match 
constraints
lib/syscall-legacy.hc: In function `set_ipv4root_rev3':
lib/syscall-legacy.hc:87: warning: asm operand 0 probably doesn't match 
constraints
lib/syscall-legacy.hc: In function `new_s_context_rev0':
lib/syscall-legacy.hc:103: warning: asm operand 0 probably doesn't match 
constraints
lib/syscall-legacy.hc: In function `set_ipv4root_rev0':
lib/syscall-legacy.hc:84: error: impossible constraint in `asm'
make[2]: *** [lib/lib_libvserver_a-syscall.o] Error 1
make[2]: Leaving directory `/home/intrigeri/vserver/util-vserver-0.30.208+fix01'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/intrigeri/vserver/util-vserver-0.30.208+fix01'
make: *** [all] Error 2


Any idea ?

Ciao,
-- 
  intrigeri <[EMAIL PROTECTED]>


pgp76VCghKBsp.pgp
Description: PGP signature
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


[Vserver] you should not use dynamic contexts for guests ...

2005-08-12 Thread Francois Duchatelet
 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi all vserver freaks :-),

Since the use of the alpha tools, I see this sentence everywhere.

Why is this so ?
Using static contexts forces us to manage them, just like ip adresses.

This is specially annoying for master/backup vservers running on different
machines.

Cheers


François Duchatelet,
Ariane Services
Rue du Verregat, 12
B-1020 Brussels
TEL:+32(2)479.37.59 - FAX:+32(2)478.14.20
Mobile:+32(486)13.07.85 - +31 (6) 47044881 
GPS: 4°19'59" E 50°54'03" N

-BEGIN PGP SIGNATURE-
Version: PGP 8.0.3

iQA/AwUBQvya3+Xix9dFBcbpEQJ+xgCfdDYy2cgGdCg1dNCEUq4DoG6sYvoAoN0e
STPn/Z3fSVLJA75d7SyJY37i
=xVqh
-END PGP SIGNATURE-


___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


Re: [Vserver] Tools segfault and kernel oops with 2.4.25-vs1.26

2005-08-12 Thread Herbert Poetzl
On Fri, Aug 12, 2005 at 02:40:11PM +0200, Francois Deppierraz wrote:
> On Fri, Aug 12, 2005 at 12:58:15PM +0200, Herbert Poetzl wrote:
> 
> > hmm ... sounds like sudden memory corruption (or well,
> > maybe not so sudden) but it looks more like a hardware
> > issue to me (maybe overheating, or dying cpu/memory)
> 
> I already changed the memory without effect...
> 
> Do you know a way to test the CPU without shutdown ?

compile a known working kernel several times ... if
that succeeds without any segfaulting, then cpu and
memory are probably fine ...
(on the host)

> The strange thing is that everything else is running well (apache,
> qmail, mysql, etc.). I restarted them on the host using chroot, the box
> was hosting a single important vserver.

hmm, maybe your box was rooted, and the segfaults are 
because some kernel exploit isn't working as expected
(because of the changed structures) ...

(just something which came to my mind :)

best,
Herbert

> Thanks for your help
> ___
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


Re: [Vserver] Tools segfault and kernel oops with 2.4.25-vs1.26

2005-08-12 Thread Francois Deppierraz
On Fri, Aug 12, 2005 at 12:58:15PM +0200, Herbert Poetzl wrote:

> hmm ... sounds like sudden memory corruption (or well,
> maybe not so sudden) but it looks more like a hardware
> issue to me (maybe overheating, or dying cpu/memory)

I already changed the memory without effect...

Do you know a way to test the CPU without shutdown ?

The strange thing is that everything else is running well (apache,
qmail, mysql, etc.). I restarted them on the host using chroot, the box
was hosting a single important vserver.

Thanks for your help
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


Re: [vserver]problems in vserver starting

2005-08-12 Thread Herbert Poetzl
On Fri, Aug 12, 2005 at 11:50:38AM +0100, naga sudha wrote:
> Hi
>  
> This is the first time to start vserver.when i start my vserver i got
> the following errors.can any body help me?
>
> i am using redhat 9 distribution,my kernel is 2.4.26 with vs1.28.one
> more thing is i m unable to connect interface also.I m not able to
> understand the problem.
> here is the logs
>  
> vserver vs1 start
>  
> Starting the virtual server vs1
> Server vs1 is not running
> SIOCSIFADDR: File exists
> SIOCSIFFLAGS: Cannot assign requested address
> SIOCSIFNETMASK: Cannot assign requested address
> SIOCSIFBRDADDR: Cannot assign requested address
> SIOCSIFFLAGS: Cannot assign requested address

looks like your config (which I do not know) is wrong
in that way that it uses an existing ip/alias but
tries to create it ...

> ipv4root is now 192.168.1.147
> Host name is now vs1.tervela.com
> New security context is 49153

you should not use dynamic contexts for guests ...

> Checking for new hardware  [  OK  ]
> Updating /etc/fstab unexpected file type for /dev/hdv1

probably a funny fstab entry?

>[FAILED]
> Flushing all current rules and user defined chains:iptables v1.2.7a: can't 
> initialize iptables table `filter': Permission denied (you must be root)
> Perhaps iptables or your kernel needs to be upgraded.
> iptables v1.2.7a: can't initialize iptables table `filter': Permission denied 
> (you must be root)
> Perhaps iptables or your kernel needs to be upgraded.
>[FAILED]
> Clearing all current rules and user defined chains:iptables v1.2.7a: can't 
> initialize iptables table `filter': Permission denied (you must be root)
> Perhaps iptables or your kernel needs to be upgraded.
> iptables v1.2.7a: can't initialize iptables table `filter': Permission denied 
> (you must be root)
> Perhaps iptables or your kernel needs to be upgraded.
>[FAILED]
> iptables v1.2.7a: can't initialize iptables table `filter': Permission denied 
> (you must be root)
> Perhaps iptables or your kernel needs to be upgraded.
> Applying iptables firewall rules: iptables-restore v1.2.7a: iptables-restore: 
> unable to initializetable 'filter'
> Try `iptables-restore -h' or 'iptables-restore --help' for more information.

all those are not really useful on a guest, so the 
runlevel entries should be removed ...

>[FAILED]
> Setting network parameters:[  OK  ]
> Bringing up loopback interface:  arping: socket: Operation n  
>  [FAILED]
> Bringing up interface eth0:  arping: socket: Operation not permitted
> Error, some other host already uses address 192.168.1.146.
>[FAILED]
> Bringing up interface eth1:  SIOCSIFFLAGS: Permission denied
> Failed to bring up eth1.

same here ...

> Starting system logger:[  OK  ]
> Starting kernel logger:[  OK  ]
> Starting portmapper:   [  OK  ]
> Starting NFS statd:[  OK  ]
> Starting keytable:  Loading keymap:[FAILED]
> Loading system font: /etc/rc5.d/S17keytable: line 26: /dev/tty0: No such file 
> or directory
> Couldnt get a file descriptor referring to the console
> Couldnt get a file descriptor referring to the console
> Couldnt get a file descriptor referring to the console
> Couldnt get a file descriptor referring to the console

and again ...

>[FAILED]
>[FAILED]
> Initializing random number generator:  [  OK  ]
> Starting pcmcia:   [  OK  ]
> Mounting other filesystems:  mount: mount point /boot does not exist
> mount: permission denied
> mount: permission denied
> mount: permission denied
> mount: mount point /dev/shm does not exist
> mount: permission denied
>[FAILED]
> Starting up APM daemon:[  OK  ]
> Starting automount:Cannot create temp file /tmp/autofs.sjT1fZ
> could not make temp file
> Starting ipsec:[  OK  ]
> Generating SSH1 RSA host key:  [FAILED]
> Starting xinetd:   [  OK  ]
> Starting NFS services: [  OK  ]
> Starting NFS quotas: rpc.rquotad: unable to register (RQUOTAPROG, RQUOTAVERS, 
> udp).
> ot permittedStarting NFS daemon:   
> [FAILED]
> Starting NFS mountd

Re: [Vserver] Tools segfault and kernel oops with 2.4.25-vs1.26

2005-08-12 Thread Herbert Poetzl
On Fri, Aug 12, 2005 at 11:37:52AM +0200, Francois Deppierraz wrote:
> Hi,
> 
> On a server with 2.4.25-vs1.26 running for more than one year, vserver
> tools (vserver, vserver-stat and chbind) suddenly began to crash with a
> segmentation fault. Each time a program segfaults, the following oops
> is produced.
> 
> I'll try an upgrade to 2.4.30-vs1.2.10 as soon as i can.
> 
> Any idea ? Thanks !

hmm ... sounds like sudden memory corruption (or well,
maybe not so sudden) but it looks more like a hardware
issue to me (maybe overheating, or dying cpu/memory)

> Decoded Oops
> 
> 
> ksymoops 2.4.5 on i686 2.4.25-vs1.26.  Options used
>  -V (default)
>  -k /proc/ksyms (default)
>  -l /proc/modules (default)
>  -o /lib/modules/2.4.25-vs1.26/ (default)
>  -m /boot/System.map-2.4.25-vs1.26 (default)
> 
> Warning: You did not tell me where to find symbol information.  I will
> assume that the log matches the kernel and modules that are running
> right now and I'll use the default options above for symbol resolution.
> If the current kernel and/or modules do not match the log, you can get
> more accurate output by telling me the kernel version and where to find
> map, modules, ksyms etc.  ksymoops -h explains the options.
> 
> No modules in ksyms, skipping objects
> Warning (read_lsmod): no symbols in lsmod, is /proc/modules a valid lsmod 
> file?
>  <1>Unable to handle kernel paging request at virtual address 1186
> 1186
> *pde = 
> Oops: 
> CPU:1
> EIP:0010:[<1186>]Not tainted
> Using defaults from ksymoops -t elf32-i386 -a i386
> EFLAGS: 00010297
> eax: 0111   ebx: ec26c000   ecx:    edx: 0018
> esi: 400135cc   edi:    ebp: bd1c   esp: ec26dfc0
> ds: 0018   es: 0018   ss: 0018
> Process vserver-stat (pid: 4027, stackpage=ec26d000)
> Stack: c0106e63    400135cc  bd1c 0111
>002b 002b 0111 08049801 0023 0286 bcf4 002b
> Call Trace:[]
> Code:  Bad EIP value.

second that :)

best,
Herbert

> >>EIP; 1186 Before first symbol   <=
> 
> >>ebx; ec26c000 
> >>esi; 400135cc Before first symbol
> >>ebp; bd1c Before first symbol
> >>esp; ec26dfc0 
> 
> Trace; c0106e63 
> 
> 
> 2 warnings issued.  Results may not be reliable.
> 
> strace -f chbind --ip 1.1.1.1 /bin/sh
> #
> 
> 21548 execve("/usr/sbin/chbind", ["chbind", "--ip", "1.1.1.1", "/bin/sh"], 
> [/* 17 vars */]) = 0
> 21548 uname({sys="Linux", node="lycopersicum", ...}) = 0
> 21548 brk(0)= 0x804ded4
> 21548 open("/etc/ld.so.preload", O_RDONLY) = -1 ENOENT (No such file or 
> directory)
> 21548 open("/etc/ld.so.cache", O_RDONLY) = 3
> 21548 fstat64(3, {st_mode=S_IFREG|0644, st_size=7071, ...}) = 0
> 21548 old_mmap(NULL, 7071, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40014000
> 21548 close(3)  = 0
> 21548 open("/usr/lib/libstdc++-libc6.2-2.so.3", O_RDONLY) = 3
> 21548 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0P\233\1"..., 
> 1024) = 1024
> 21548 fstat64(3, {st_mode=S_IFREG|0644, st_size=288540, ...}) = 0
> 21548 old_mmap(NULL, 296708, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 
> 0x40016000
> 21548 mprotect(0x4004c000, 75524, PROT_NONE) = 0
> 21548 old_mmap(0x4004c000, 69632, PROT_READ|PROT_WRITE, 
> MAP_PRIVATE|MAP_FIXED, 3, 0x36000) = 0x4004c000
> 21548 old_mmap(0x4005d000, 5892, PROT_READ|PROT_WRITE, 
> MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x4005d000
> 21548 close(3)  = 0
> 21548 open("/lib/libm.so.6", O_RDONLY)  = 3
> 21548 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\2007\0"..., 
> 1024) = 1024
> 21548 fstat64(3, {st_mode=S_IFREG|0644, st_size=130088, ...}) = 0
> 21548 old_mmap(NULL, 132708, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 
> 0x4005f000
> 21548 mprotect(0x4007f000, 1636, PROT_NONE) = 0
> 21548 old_mmap(0x4007f000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 
> 3, 0x1f000) = 0x4007f000
> 21548 close(3)  = 0
> 21548 open("/lib/libc.so.6", O_RDONLY)  = 3
> 21548 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\30\222"..., 
> 1024) = 1024
> 21548 fstat64(3, {st_mode=S_IFREG|0755, st_size=1153784, ...}) = 0
> 21548 old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, 
> -1, 0) = 0x4008
> 21548 old_mmap(NULL, 1166560, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 
> 0x40081000
> 21548 mprotect(0x40194000, 40160, PROT_NONE) = 0
> 21548 old_mmap(0x40194000, 24576, PROT_READ|PROT_WRITE, 
> MAP_PRIVATE|MAP_FIXED, 3, 0x113000) = 0x40194000
> 21548 old_mmap(0x4019a000, 15584, PROT_READ|PROT_WRITE, 
> MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x4019a000
> 21548 close(3)  = 0
> 21548 munmap(0x40014000, 7071)  = 0
> 21548 brk(0)= 0x804ded4
> 21548 brk(0x804e054)= 0x804e054
> 21548 brk(0x804f000) 

Re: [Vserver] Network interface problem

2005-08-12 Thread Gilles
Hello.
 
> > if i restart my network interface i get this msg:
> > Setting up IP spoofing protection: /etc/init.d/networking: line
> > 17: /proc/sys/net/ipv4/conf/all/rp_filter: Operation not permitted
> > /etc/init.d/networking: line
> > 17: /proc/sys/net/ipv4/conf/default/rp_filter: Operation not permitted
> > /etc/init.d/networking: line 17: /proc/sys/net/ipv4/conf/eth0/rp_filter:
> > Operation not permitted
> > /etc/init.d/networking: line 17: /proc/sys/net/ipv4/conf/eth1/rp_filter:
> > Operation not permitted
> > /etc/init.d/networking: line 17: /proc/sys/net/ipv4/conf/lo/rp_filter:
> > Operation not permitted
> > rp_filter.
> > Reconfiguring network interfaces...SIOCSIFADDR: Permission denied
> > SIOCSIFFLAGS: Permission denied
> > SIOCSIFFLAGS: Permission denied
> > Failed to bring up lo.
> > Ignoring unknown interface eth0=eth0.
> 
> which is expected, as the guests are not allowed
> to mess with the network config, only the host is ...
> 
> > and when i shut down the vserver i get this msg:
> > 
> > Deactivating swap...umount: none: not found
> > umount: /tmp: must be superuser to umount
> > Not superuser.
> > done.
> > Unmounting local filesystems...umount: none: not found
> > umount: /tmp: must be superuser to umount
> > umount: /dev/hdv1: not found
> > umount: /: not mounted
> > done.
> > mount: permission denied
> > Rebooting... ifdown: shutdown eth0: Permission denied
> > ifdown: shutdown eth0: Permission denied
> > ifdown: shutdown eth1: Permission denied
> 
> which is harmless, but if you want it to go away,
> just remove the hardware related shutdown scripts
> (symlinks) so that the guest will not attempt to
> do hardware stuff on shutdown ...
> 

Here below is a simplistic script which I've used in order
to get rid of the hardware-related packages (and some others:
check the list to be sure you don't need those) which were
installed by 'debootstrap':


#!/bin/bash

#
#
# This script is intended to be run inside a Debian vserver
# (after being installed through the "debootstrap" method)
# in order to fix various things:
#
# - Remove spurious (i.e. hardware-related) links in the
#   /etc/rc[S1-5].d directories
# - Remove unnecessary packages (aiming at a minimal system)
# - Adding some useful missing packages
#
#

set -e

#
# Remove hardware, kernel, network, mail packages
#
REMOVE_PACKAGES="
  pciutils fdutils
  makedev base-config klogd sysklogd modutils
  logrotate cron at
  ppp pppconfig pppoe pppoeconf
  console-common console-data console-tools
  telnet netkit-inetd netbase tcpd ifupdown wget ipchains dhcp-client
  exim4 exim4-base exim4-config exim4-daemon-light
  cpio nvi tasksel manpages iptables
"
ADD_PACKAGES="
 less ssh screen netcat
"

apt-get -u remove $REMOVE_PACKAGES
apt-get -u install $ADD_PACKAGES



HTH,
Gilles
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


[vserver]problems in vserver starting

2005-08-12 Thread naga sudha
Hi
 
This is the first time to start vserver.when i start my vserver i got the following errors.can any body help me?
 
i am using redhat 9 distribution,my kernel is 2.4.26 with vs1.28.one more thing is i m unable to connect interface also.I m not able to understand the problem.
 
here is the logs
 
vserver vs1 start
 
Starting the virtual server vs1Server vs1 is not runningSIOCSIFADDR: File existsSIOCSIFFLAGS: Cannot assign requested addressSIOCSIFNETMASK: Cannot assign requested addressSIOCSIFBRDADDR: Cannot assign requested addressSIOCSIFFLAGS: Cannot assign requested addressipv4root is now 192.168.1.147Host name is now vs1.tervela.comNew security context is 49153Checking for new hardware  [  OK  ]Updating /etc/fstab unexpected file type for
 /dev/hdv1   [FAILED]Flushing all current rules and user defined chains:iptables v1.2.7a: can't initialize iptables table `filter': Permission denied (you must be root)Perhaps iptables or your kernel needs to be upgraded.iptables v1.2.7a: can't initialize iptables table `filter': Permission denied (you must be root)Perhaps iptables or your kernel needs to be
 upgraded.   [FAILED]Clearing all current rules and user defined chains:iptables v1.2.7a: can't initialize iptables table `filter': Permission denied (you must be root)Perhaps iptables or your kernel needs to be upgraded.iptables v1.2.7a: can't initialize iptables table `filter': Permission denied (you must be root)Perhaps iptables or your kernel needs to be
 upgraded.   [FAILED]iptables v1.2.7a: can't initialize iptables table `filter': Permission denied (you must be root)Perhaps iptables or your kernel needs to be upgraded.Applying iptables firewall rules: iptables-restore v1.2.7a: iptables-restore: unable to initializetable 'filter'
Try `iptables-restore -h' or 'iptables-restore --help' for more information.   [FAILED]Setting network parameters:    [  OK  ]Bringing up loopback interface:  arping: socket: Operation
 n   [FAILED]Bringing up interface eth0:  arping: socket: Operation not permittedError, some other host already uses address 192.168.1.146.   [FAILED]Bringing up interface eth1:  SIOCSIFFLAGS: Permission deniedFailed to bring up
 eth1.   [FAILED]Starting system logger:    [  OK  ]Starting kernel logger:    [  OK  ]Starting
 portmapper:   [  OK  ]Starting NFS statd:    [  OK  ]Starting keytable:  Loading keymap:    [FAILED]Loading system font: /etc/rc5.d/S17keytable: line 26: /dev/tty0: No such file or directoryCouldnt get a file descriptor referring to the consoleCouldnt get a file descriptor referring to the consoleCouldnt get a file descriptor referring to the
 consoleCouldnt get a file descriptor referring to the console   [FAILED]   [FAILED]Initializing random number generator:  [  OK  ]Starting
 pcmcia:   [  OK  ]Mounting other filesystems:  mount: mount point /boot does not existmount: permission deniedmount: permission deniedmount: permission deniedmount: mount point /dev/shm does not existmount: permission denied   [FAILED]Starting up APM
 daemon:    [  OK  ]Starting automount:Cannot create temp file /tmp/autofs.sjT1fZcould not make temp fileStarting ipsec:    [  OK  ]Generating SSH1 RSA host key:  [FAILED]Starting
 xinetd:   [  OK  ]Starting NFS services: [  OK  ]Starting NFS quotas: rpc.rquotad: unable to register (RQUOTAPROG, RQUOTAVERS, udp).ot permittedStarting NFS daemon:   [FAILED]Starting NFS
 mountd:   [FAILED]Starting vsftpd for vsftpd:    [  OK  ]Starting dhcpd: Internet Software Consortium DHCP Server V3.0pl1Copyright 1995-2001 Internet Software Consortium.All rights reserved.For info, please visit http://www.isc.org/products/DHCPunable to create icmp socket: Operation not permittedWrote 0 deleted host decls to leases file.Wrote 0 new dynamic host decls to leases file.Wrote 0 leases to leases file.
Not configured to listen on any interfaces!
If you did not get this software from ftp.isc.or

Re: [Vserver] Unable to start vserver

2005-08-12 Thread Herbert Poetzl
On Fri, Aug 12, 2005 at 11:40:35AM +0300, Yuriy Levin wrote:
> Hello,
> 
> I have fallowing troubles starting vserver: after executing "vserver 
>  start" I get error message:
> 
> -begin-
> save_ctxinfo: execv(): No such file or directory
> 
> An error occurred while executing the vserver startup sequence; when
> there are no other messages, it is very likely that the init-script
> (/etc/init.d/rc 3) failed.
> 
> Common causes are:
> * /etc/rc.d/rc on Fedora Core 1 and RH9 fails always; the 'apt-rpm' build
>   method knows how to deal with this, but on existing installations,
>   appending 'true' to this file will help.
> -end-

hmm, check that your /etc/rc.d/rc inside the guest
can be executed when you chroot-ed into the guest

e.g. chroot /path/to/guest /etc/rc.d/rc
(but be careful, because of the side effects)

> I run FC3 box with kernel 2.6.11-vs1.9.5-rc1 and
> util-vserver-0.30.204.

updating to recent patches (vs2.0) and utils would
not hurt I'd say ...

> Vprocunhide and vshelper scripts starts without any errors during
> system startup. Vserver was built with skeleton method, then Debian
> working OS template was used as guest OS.

maybe it isn't that working at all, check for
libraries and such ... 

> Also I would like to read about building vservers. There are lot of
> faqs and howtos at project website, but I couldn't find anything about
> building methods and initstyles. Does somebody knows useful links?

http://linux-vserver.org/alpha+util-vserver
(large section about vserver creation)

http://www.nongnu.org/util-vserver/doc/conf/configuration.html
(all ugly details about the config)

http://linux-vserver.org/InitStyles
(a first start on describing the init styles)

HTH,
Herbert

> Thanks in advance.
> 
> ___
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


Re: [Vserver] Network interface problem

2005-08-12 Thread Herbert Poetzl
On Fri, Aug 12, 2005 at 10:06:20AM +0200, Marvin Stark wrote:
> Good morning,
> 
> I got a problem with my network interface.
> I installed my vServer with this commandline:
> 
> vserver vs1 build -m debootstrap --hostname vs1 --netdev eth0 --netbcast
> 192.168.3.255 --netmask 255.255.255.0 --interface eth0 -- -d sarge

that's a little weird for a start ... 

> After that i set my network settings:
> 
> echo "eth0" > /etc/vservers/vs1/interfaces/dev
> echo "192.168.3.5" > /etc/vservers/vs1/interfaces/0/ip
> echo "vserver1" > /etc/vservers/vs1/uts/nodename

hmm, why not specify those things in the first
place? e.g.

vserver vs1 build -m debootstrap --hostname vserver1
  --interface eth0:192.168.3.5/24 -- -d sarge

> than i started my vServer:
> vserver vs1 start
> 
> than all is working fine:
> 
> Starting system log daemon: syslogd.
> Starting kernel log daemon: klogd.
> Starting MTA: exim4.
> Starting internet superserver: inetd.
> Starting deferred execution scheduler: atd.
> Starting periodic command scheduler: cron.
> 
> Now i enter the vServer:
> 
> vserver vs1 enter
> 
> now i look at my network settings(ifconfig):
> 
> 
> eth0  Link encap:Ethernet  HWaddr 00:E0:7D:DE:6E:3D  
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:348 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:327 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000 
>   RX bytes:34742 (33.9 KiB)  TX bytes:31143 (30.4 KiB)
>   Interrupt:12 Base address:0xd400 
> 
> so, there is no ip set.

wrong, there is no alias configured, and you are
not allowed to use the ip from the host ...

using 'ip addr ls' instead of the ancient ifconfig
you will _see_ the configured (and allowed) ips ...

if you prefer an alias, you have to tell the system
which can be done by:

echo "hansi" > /etc/vservers/vs1/interfaces/name

or by specifying --interface hansi=eth0:192.168.3.5/24


> if i restart my network interface i get this msg:
> Setting up IP spoofing protection: /etc/init.d/networking: line
> 17: /proc/sys/net/ipv4/conf/all/rp_filter: Operation not permitted
> /etc/init.d/networking: line
> 17: /proc/sys/net/ipv4/conf/default/rp_filter: Operation not permitted
> /etc/init.d/networking: line 17: /proc/sys/net/ipv4/conf/eth0/rp_filter:
> Operation not permitted
> /etc/init.d/networking: line 17: /proc/sys/net/ipv4/conf/eth1/rp_filter:
> Operation not permitted
> /etc/init.d/networking: line 17: /proc/sys/net/ipv4/conf/lo/rp_filter:
> Operation not permitted
> rp_filter.
> Reconfiguring network interfaces...SIOCSIFADDR: Permission denied
> SIOCSIFFLAGS: Permission denied
> SIOCSIFFLAGS: Permission denied
> Failed to bring up lo.
> Ignoring unknown interface eth0=eth0.

which is expected, as the guests are not allowed
to mess with the network config, only the host is ...

> and when i shut down the vserver i get this msg:
> 
> Deactivating swap...umount: none: not found
> umount: /tmp: must be superuser to umount
> Not superuser.
> done.
> Unmounting local filesystems...umount: none: not found
> umount: /tmp: must be superuser to umount
> umount: /dev/hdv1: not found
> umount: /: not mounted
> done.
> mount: permission denied
> Rebooting... ifdown: shutdown eth0: Permission denied
> ifdown: shutdown eth0: Permission denied
> ifdown: shutdown eth1: Permission denied

which is harmless, but if you want it to go away,
just remove the hardware related shutdown scripts
(symlinks) so that the guest will not attempt to
do hardware stuff on shutdown ...

> I dont know how to fix this and i hope you can help me.
> 
> The hostmaschine is running with Debian GNU/LINUX 3.1 ('Sarge')
> and Kernel 2.6.8. Iam using the debian vserver packages.

which in general is not the best idea, but I hope
this will change soon ...

HTH,
Herbert

> best regards,
> 
> Marvin
> 
> ___
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


[Vserver] Unable to start vserver

2005-08-12 Thread Yuriy Levin

Hello,

I have fallowing troubles starting vserver: after executing "vserver 
 start" I get error message:


-begin-
save_ctxinfo: execv(): No such file or directory

An error occurred while executing the vserver startup sequence; when
there are no other messages, it is very likely that the init-script
(/etc/init.d/rc 3) failed.

Common causes are:
* /etc/rc.d/rc on Fedora Core 1 and RH9 fails always; the 'apt-rpm' build
  method knows how to deal with this, but on existing installations,
  appending 'true' to this file will help.
-end-

I run FC3 box with kernel 2.6.11-vs1.9.5-rc1 and util-vserver-0.30.204. 
 Vprocunhide and vshelper scripts starts without any errors during 
system startup. Vserver was built with skeleton method, then Debian 
working OS template was used as guest OS.


Also I would like to read about building vservers. There are lot of faqs 
and howtos at project website, but I couldn't find anything about 
building methods and initstyles. Does somebody knows useful links?


Thanks in advance.

___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


[Vserver] Tools segfault and kernel oops with 2.4.25-vs1.26

2005-08-12 Thread Francois Deppierraz
Hi,

On a server with 2.4.25-vs1.26 running for more than one year, vserver
tools (vserver, vserver-stat and chbind) suddenly began to crash with a
segmentation fault. Each time a program segfaults, the following oops
is produced.

I'll try an upgrade to 2.4.30-vs1.2.10 as soon as i can.

Any idea ? Thanks !

Decoded Oops


ksymoops 2.4.5 on i686 2.4.25-vs1.26.  Options used
 -V (default)
 -k /proc/ksyms (default)
 -l /proc/modules (default)
 -o /lib/modules/2.4.25-vs1.26/ (default)
 -m /boot/System.map-2.4.25-vs1.26 (default)

Warning: You did not tell me where to find symbol information.  I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc.  ksymoops -h explains the options.

No modules in ksyms, skipping objects
Warning (read_lsmod): no symbols in lsmod, is /proc/modules a valid lsmod file?
 <1>Unable to handle kernel paging request at virtual address 1186
1186
*pde = 
Oops: 
CPU:1
EIP:0010:[<1186>]Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010297
eax: 0111   ebx: ec26c000   ecx:    edx: 0018
esi: 400135cc   edi:    ebp: bd1c   esp: ec26dfc0
ds: 0018   es: 0018   ss: 0018
Process vserver-stat (pid: 4027, stackpage=ec26d000)
Stack: c0106e63    400135cc  bd1c 0111
   002b 002b 0111 08049801 0023 0286 bcf4 002b
Call Trace:[]
Code:  Bad EIP value.


>>EIP; 1186 Before first symbol   <=

>>ebx; ec26c000 
>>esi; 400135cc Before first symbol
>>ebp; bd1c Before first symbol
>>esp; ec26dfc0 

Trace; c0106e63 


2 warnings issued.  Results may not be reliable.

strace -f chbind --ip 1.1.1.1 /bin/sh
#

21548 execve("/usr/sbin/chbind", ["chbind", "--ip", "1.1.1.1", "/bin/sh"], [/* 
17 vars */]) = 0
21548 uname({sys="Linux", node="lycopersicum", ...}) = 0
21548 brk(0)= 0x804ded4
21548 open("/etc/ld.so.preload", O_RDONLY) = -1 ENOENT (No such file or 
directory)
21548 open("/etc/ld.so.cache", O_RDONLY) = 3
21548 fstat64(3, {st_mode=S_IFREG|0644, st_size=7071, ...}) = 0
21548 old_mmap(NULL, 7071, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40014000
21548 close(3)  = 0
21548 open("/usr/lib/libstdc++-libc6.2-2.so.3", O_RDONLY) = 3
21548 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0P\233\1"..., 
1024) = 1024
21548 fstat64(3, {st_mode=S_IFREG|0644, st_size=288540, ...}) = 0
21548 old_mmap(NULL, 296708, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 
0x40016000
21548 mprotect(0x4004c000, 75524, PROT_NONE) = 0
21548 old_mmap(0x4004c000, 69632, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 
3, 0x36000) = 0x4004c000
21548 old_mmap(0x4005d000, 5892, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x4005d000
21548 close(3)  = 0
21548 open("/lib/libm.so.6", O_RDONLY)  = 3
21548 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\2007\0"..., 
1024) = 1024
21548 fstat64(3, {st_mode=S_IFREG|0644, st_size=130088, ...}) = 0
21548 old_mmap(NULL, 132708, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 
0x4005f000
21548 mprotect(0x4007f000, 1636, PROT_NONE) = 0
21548 old_mmap(0x4007f000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 
3, 0x1f000) = 0x4007f000
21548 close(3)  = 0
21548 open("/lib/libc.so.6", O_RDONLY)  = 3
21548 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\30\222"..., 
1024) = 1024
21548 fstat64(3, {st_mode=S_IFREG|0755, st_size=1153784, ...}) = 0
21548 old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 
0) = 0x4008
21548 old_mmap(NULL, 1166560, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 
0x40081000
21548 mprotect(0x40194000, 40160, PROT_NONE) = 0
21548 old_mmap(0x40194000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 
3, 0x113000) = 0x40194000
21548 old_mmap(0x4019a000, 15584, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x4019a000
21548 close(3)  = 0
21548 munmap(0x40014000, 7071)  = 0
21548 brk(0)= 0x804ded4
21548 brk(0x804e054)= 0x804e054
21548 brk(0x804f000)= 0x804f000
21548 open("/proc/net/dev", O_RDONLY)   = 3
21548 fstat64(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
21548 old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 
0) = 0x40014000
21548 read(3, "Inter-|   Receive   "..., 4096) = 574
21548 read(3, "", 4096) = 0
21548 close(3)  = 0
21548 munmap(0x40014000, 4096)  = 0
21548 gettimeofday({1123831642, 795934}, NULL) = 0
21548 getpid()   

[Vserver] Network interface problem

2005-08-12 Thread Marvin Stark
Good morning,

I got a problem with my network interface.
I installed my vServer with this commandline:

vserver vs1 build -m debootstrap --hostname vs1 --netdev eth0 --netbcast
192.168.3.255 --netmask 255.255.255.0 --interface eth0 -- -d sarge

After that i set my network settings:

echo "eth0" > /etc/vservers/vs1/interfaces/dev
echo "192.168.3.5" > /etc/vservers/vs1/interfaces/0/ip
echo "vserver1" > /etc/vservers/vs1/uts/nodename

than i started my vServer:
vserver vs1 start

than all is working fine:

Starting system log daemon: syslogd.
Starting kernel log daemon: klogd.
Starting MTA: exim4.
Starting internet superserver: inetd.
Starting deferred execution scheduler: atd.
Starting periodic command scheduler: cron.

Now i enter the vServer:

vserver vs1 enter

now i look at my network settings(ifconfig):


eth0  Link encap:Ethernet  HWaddr 00:E0:7D:DE:6E:3D  
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:348 errors:0 dropped:0 overruns:0 frame:0
  TX packets:327 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:34742 (33.9 KiB)  TX bytes:31143 (30.4 KiB)
  Interrupt:12 Base address:0xd400 

so, there is no ip set.

if i restart my network interface i get this msg:
Setting up IP spoofing protection: /etc/init.d/networking: line
17: /proc/sys/net/ipv4/conf/all/rp_filter: Operation not permitted
/etc/init.d/networking: line
17: /proc/sys/net/ipv4/conf/default/rp_filter: Operation not permitted
/etc/init.d/networking: line 17: /proc/sys/net/ipv4/conf/eth0/rp_filter:
Operation not permitted
/etc/init.d/networking: line 17: /proc/sys/net/ipv4/conf/eth1/rp_filter:
Operation not permitted
/etc/init.d/networking: line 17: /proc/sys/net/ipv4/conf/lo/rp_filter:
Operation not permitted
rp_filter.
Reconfiguring network interfaces...SIOCSIFADDR: Permission denied
SIOCSIFFLAGS: Permission denied
SIOCSIFFLAGS: Permission denied
Failed to bring up lo.
Ignoring unknown interface eth0=eth0.

and when i shut down the vserver i get this msg:

Deactivating swap...umount: none: not found
umount: /tmp: must be superuser to umount
Not superuser.
done.
Unmounting local filesystems...umount: none: not found
umount: /tmp: must be superuser to umount
umount: /dev/hdv1: not found
umount: /: not mounted
done.
mount: permission denied
Rebooting... ifdown: shutdown eth0: Permission denied
ifdown: shutdown eth0: Permission denied
ifdown: shutdown eth1: Permission denied

I dont know how to fix this and i hope you can help me.

The hostmaschine is running with Debian GNU/LINUX 3.1 ('Sarge')
and Kernel 2.6.8. Iam using the debian vserver packages.

best regards,

Marvin

___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver