[Vserver] vs2.0 and the tools

2005-08-11 Thread Roderick A. Anderson
I have built and installed a new kernel and nd getting ready to build the 
tools but have one question I've not seen asked or seen mentioned before.  
It is probably falls somewhere below stupid on the question scale.

Do I have to have the new kernel running to build the tools?  I can't
reboot right now ( it's nearly 4:00am and I'm 35 miles from the NOC where
the box is :-).  That is, is there anything in the tools that requires the
vServer to be running for them to build correctly?  The system is
currently running 2.6.10-vs1.9.4 installed from OpenVPS rpms but using the
legacy tools/configuration.  I'm trying to get as much done while my
portion of the world sleeps.


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] vs2.0 and the tools

2005-08-11 Thread Herbert Poetzl
On Thu, Aug 11, 2005 at 04:00:03AM -0700, Roderick A. Anderson wrote:
 I have built and installed a new kernel and nd getting ready to build the 
 tools but have one question I've not seen asked or seen mentioned before.  
 It is probably falls somewhere below stupid on the question scale.
 
 Do I have to have the new kernel running to build the tools?  I can't
 reboot right now ( it's nearly 4:00am and I'm 35 miles from the NOC where
 the box is :-).  That is, is there anything in the tools that requires the
 vServer to be running for them to build correctly?  The system is
 currently running 2.6.10-vs1.9.4 installed from OpenVPS rpms but using the
 legacy tools/configuration.  I'm trying to get as much done while my
 portion of the world sleeps.

given you do not disable legacy support, you can still use
the legacy tools for your shiny new vs2.0 kernel ...

if you compile and install the 0.30.208 (+fix) tools, they
should also work fine with your existing kernel, so ...

whatever you do, it is supposed to just work :)

HTH,
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] vs2.0 and the tools

2005-08-11 Thread Roderick A. Anderson
On Thu, 11 Aug 2005, Herbert Poetzl wrote:

I probably wasn't clear on this.

 given you do not disable legacy support, you can still use
 the legacy tools for your shiny new vs2.0 kernel ...

There is a vServer 2.6.10-vs1.94 kernel running but nothing important 
guest-wise in on the system. 

 if you compile and install the 0.30.208 (+fix) tools, they
 should also work fine with your existing kernel, so ...

Will they then work with the new vs2.0 kernel, ie. the build doesn't look 
at running kernel and make decisions about what/hoe to build the utils.

 whatever you do, it is supposed to just work :)

Famous last words.  Yes I am hoping this is so.


Follow up question.

I went ahead and started building the utils as RPMs and ran into a couple 
of dependency issues.  This is probably more an Enrico question.

Why tetex-latex?  Is it  Redhat ( RPM ) build-documentation requirement?

Why xalan-j ( Java? )  Is this also a Redhat-ism?

I like RPMs but I'd prefer a really clean Vserver host.  ( I'll try a 
straight tarball build next. )


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] vs2.0 and the tools

2005-08-11 Thread Herbert Poetzl
On Thu, Aug 11, 2005 at 04:43:09AM -0700, Roderick A. Anderson wrote:
 On Thu, 11 Aug 2005, Herbert Poetzl wrote:
 
 I probably wasn't clear on this.
 
  given you do not disable legacy support, you can still use
  the legacy tools for your shiny new vs2.0 kernel ...
 
 There is a vServer 2.6.10-vs1.94 kernel running but nothing important 
 guest-wise in on the system. 
 
  if you compile and install the 0.30.208 (+fix) tools, they
  should also work fine with your existing kernel, so ...
 
 Will they then work with the new vs2.0 kernel, ie. the build doesn't look 
 at running kernel and make decisions about what/hoe to build the utils.

they are not supposed to do so ...

  whatever you do, it is supposed to just work :)
 
 Famous last words.  Yes I am hoping this is so.

well, I guess you will let us know, right?

 Follow up question.
 
 I went ahead and started building the utils as RPMs and ran into a couple 
 of dependency issues.  This is probably more an Enrico question.

yep, building docu and such stuff ...

 Why tetex-latex?  Is it  Redhat ( RPM ) build-documentation requirement?
 
 Why xalan-j ( Java? )  Is this also a Redhat-ism?

hmm, you obviously didn't use the (mandrake) rpms from
my page ... because they disable most of those ...

 I like RPMs but I'd prefer a really clean Vserver host.  ( I'll try a 
 straight tarball build next. )

good luck,
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] vs2.0 and the tools

2005-08-11 Thread Roderick A. Anderson
On Thu, 11 Aug 2005, Herbert Poetzl wrote:

 hmm, you obviously didn't use the (mandrake) rpms from
 my page ... because they disable most of those ...

It would be a first :-( for me ) to have a Mandrake RPM work on a 
non-Mandrake system.  But I'm game.  I'll give them a try.

I read the README file a little closer and discovered --without xalan so 
the RPMs are building as I type.  A ./configure, make, make installed 
worked also.


Best,
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] vs2.0 and the tools

2005-08-11 Thread Herbert Poetzl
On Thu, Aug 11, 2005 at 05:06:36AM -0700, Roderick A. Anderson wrote:
 On Thu, 11 Aug 2005, Herbert Poetzl wrote:
 
  hmm, you obviously didn't use the (mandrake) rpms from
  my page ... because they disable most of those ...
 
 It would be a first :-( for me ) to have a Mandrake RPM work on a 
 non-Mandrake system.  But I'm game.  I'll give them a try.

true, probably you encounter different dependancies
because of different package naming ... anyway, keep
me informed ...

 I read the README file a little closer and discovered --without xalan so 
 the RPMs are building as I type.  A ./configure, make, make installed 
 worked also.

yup, TIA,
Herbert

 Best,
 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] vs2.0 and the tools

2005-08-11 Thread Enrico Scholz
[EMAIL PROTECTED] (Roderick A. Anderson) writes:

 I went ahead and started building the utils as RPMs and ran
 into a couple of dependency issues.  This is probably more an
 Enrico question.

 Why tetex-latex?  Is it  Redhat ( RPM ) build-documentation
 requirement?

It is only a build-requirement and used to build the API doc of
the library. I never tried whether it builds with '--nodeps'
also.


 Why xalan-j ( Java? )  Is this also a Redhat-ism?

Can be disabled by '--without xalan' at rpmbuild.



Enrico


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


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

2005-08-11 Thread Roderick A. Anderson
Well it seems I've found the same problem others have but no solution.  It 
seems to be something about Fedora Core 3, SMP, and later kernels from 
pristine sources ( or in the case vs2.0 patched ).  There were a couple of 
mentions of SCSI RAID devices also.

This is a quad Xenon system with a Mylex Corporation DAC960PG host RAID
controller.

I followed the the instructions from
http://linux-vserver.org/Step-by-Step+Guide+2.6 with the exception I did a 
make modules_install followed by a make install.

The first error that comes back is:

Unable to find device-mapper major/minor
Reading all physical volumes.  This may take a while.
...
Kernel panic - not syncing: Attempting to kill init

I did not make any changes during make menuconfig -- accepting the 
defaults.  Any ideas as to what I missed?


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] Inconsitent handling of mounts with 2.4.31-vs1.2.10 on Fedora 1

2005-08-11 Thread Herbert Poetzl
On Thu, Aug 11, 2005 at 09:56:20AM -0400, Stephen Harris wrote:
 The 2.4.30 patch applied cleanly to 2.4.31 (except the top Makefile, of
 course) so I'm guessing it should work...
 
 It all seems good, but sometimes I get errors when trying to mount stuff
 into a vserver tree
 
 This works:
 
   [root]/home/sweh
   backup.pts/2% vserver webssh status
   Server webssh is running
   13 processes running
   Vserver uptime: 13:01
 
   [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)

   [root]/home/sweh
   backup.pts/2% ls /vservers/webssh/RedHat
   MIRROR*  MIRROR.o*  f*  f.o*  updates/
 
   [root]/home/sweh
   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)

   ipv4root is now 10.0.0.2
   New security context is 49173

and just as sidenote, you should avoid dynamic context
ids, unless you are looking for trouble :)

   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)

   [EMAIL PROTECTED]:webssh /]ls /RedHat/
   MIRROR  MIRROR.o  f  f.o  updates
 
 The /RedHat tree inside the vserver matches what is seen outside the
 vserver.
 
 However, this fails:
 
   [root]/home/sweh
   backup.pts/2% vserver mailgate status
   Server mailgate is running
   6 processes running
   Vserver uptime: 13:01
 
   [root]/home/sweh
   backup.pts/2% mount -r backup:/RedHat/updates/core1 
 /vservers/mailgate/RedHat
 
   [root]/home/sweh
   backup.pts/2% ls /vservers/mailgate/RedHat
   MIRROR*  MIRROR.o*  f*  f.o*  updates/
 
   [root]/home/sweh
   backup.pts/2% vserver mailgate enter
   SIOCSIFBRDADDR: Cannot assign requested address
   SIOCSIFFLAGS: Cannot assign requested address
   ipv4root is now 10.0.0.3

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)

   New security context is 49172
   bash: ulimit: core file size: cannot modify limit: Invalid argument
   [EMAIL PROTECTED]:mailgate /]ls /RedHat
   ls: /RedHat: Permission denied
 
 The XXX.sh files are the same and the XXX.conf files only differ in IPROOT
 and S_HOSTNAME and are otherwise identical.  The underlying mount point
 is OK:
 
   [root]/home/sweh
   backup.pts/2% ls -ld /vservers/*/RedHat
   drwxr-xr-x  2 root root 4096 Aug  9 10:22 /vservers/mailgate/RedHat/
   drwxr-xr-x  2 root root 4096 Aug  9 10:22 /vservers/webssh/RedHat/

is okay from the host, which probably uses a third
IP (!= 10.0.0.2 and 10.0.0.3), which, of course, is
a completely different story :)

 The vservers are otherwise running happily and are running the daemons
 they should be running.  I'm essentially using vservers as bastion host
 gateways into my network from the outside world.
 
 Any ideas?  I can't move to a 2.6 kernel since I need IDE hotswapping...

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

 (BTW, excellent documentation: setting up the initial fc1 minimal vserver
 was simplicity!)

glad to hear that ...

HTH,
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] My adventures with vs2.0 ... :-)

2005-08-11 Thread Herbert Poetzl
On Thu, Aug 11, 2005 at 03:51:25PM -0700, Roderick A. Anderson wrote:
 Well it seems I've found the same problem others have but no solution.
 It seems to be something about Fedora Core 3, SMP, and later kernels
 from pristine sources ( or in the case vs2.0 patched ). There were a
 couple of mentions of SCSI RAID devices also.

 This is a quad Xenon system with a Mylex Corporation DAC960PG host
 RAID controller.
 
 I followed the the instructions from
 http://linux-vserver.org/Step-by-Step+Guide+2.6 with the exception I
 did a make modules_install followed by a make install.
 
 The first error that comes back is:
 
 Unable to find device-mapper major/minor
 Reading all physical volumes.  This may take a while.

sounds like either you are using lvm1 or you
somehow forced fixed major/minor for device mapper,
which are not available any longer (i.e. used by
other devices) ...

 ...

ah, here is the important part ... unfortunately
it seems that your mailer did cut it out :/

 Kernel panic - not syncing: Attempting to kill init

result of kernel not being able to find your root
device, which can actually have many causes ...

 I did not make any changes during make menuconfig -- accepting the 
 defaults.  Any ideas as to what I missed?

maybe a lot .. don't you have an existing, well
tuned config for your server? if not, a .config
file would be helpful here ...

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] My adventures with vs2.0 ... :-)

2005-08-11 Thread Herbert Poetzl
On Thu, Aug 11, 2005 at 05:52:41PM -0700, Roderick A. Anderson wrote:
 On Fri, 12 Aug 2005, Herbert Poetzl wrote:
 
   Unable to find device-mapper major/minor
   Reading all physical volumes.  This may take a while.
  
  sounds like either you are using lvm1 or you
  somehow forced fixed major/minor for device mapper,
  which are not available any longer (i.e. used by
  other devices) ...
 
 Hum.  The lvm sounds like the problem.

if you are using fixed major/minor you can remove
them with the lvchange --persistent n option ...
(see the --help for more details)

   ...
  
  ah, here is the important part ... unfortunately
  it seems that your mailer did cut it out :/
 
 Not I was too lazy to type it in.  Here is the rest.
 
 No volume groups found

hmm, this could also point to the real scsi
hardware not being detected properly ... a 
complete bootup log could shed some light on
it ...

 umount /sys failed: 16
 mount: error 19 mounting ext3
 mount: error 2 mounting none
 switchroot: mount failed: 22
 umount /initrd/dev failed: 2
 
   Kernel panic - not syncing: Attempting to kill init
  
  result of kernel not being able to find your root
  device, which can actually have many causes ...
 
 Been ther done that lots of tee-shirts.
 
   I did not make any changes during make menuconfig -- accepting the 
   defaults.  Any ideas as to what I missed?
  
  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 ...

 (Do you ever get sleep? It must be after midnight in Austria and you
 were answering questions early this AM. :-)

yeah, well, some things I can answer in my sleep :)

 I'm going to look at the lvm settings and try my other working .config
 later tonight or tomorrow AM.

k, let me know how it goes ...

best,
Herbert

 Thanks for the ideas,
 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