About this list Date view Thread view Subject view Author view Attachment view

From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Wed 01 Dec 2004 - 11:23:12 GMT


On Wed, Dec 01, 2004 at 09:47:13AM +0100, Lars E. D. Jensen wrote:
> Hi Herbert
>
> Helpful as always :)
>
> Tirsdag den 30. november 2004 18:22 skrev Herbert Poetzl:
> > On Tue, Nov 30, 2004 at 01:59:43PM +0100, Lars E. D. Jensen wrote:
> > > Hi list
> > >
> > > I have access to IP address space x.x.x.114 -> x.x.x.118
> > >
> > > But I can only catch x.x.x.118 with one virtual server.
> > >
> > > x.x.x.116 can't be allocated. Is this a configuration issue at my ISP or
> > > is it a misconfiguration of my vservers?
> >
> > sorry my magic glass ball is in repair _again_ ;)
> >
> > need some details first like:
> >
> > - what kernel, patches, what tools?
>
> Host server -> Debian 3.0r3 (stable)
> Vservers -> Latest Debian Sarge
> Kernel 2.4.28
> Linux-VServer Stable 1.29 (no extra patches)
> util-vserver 0.30
> All found here: http://www.13thfloor.at/vserver/s_release/v1.29/
>
> > - what does 'catch' mean?
> The vservers don't get assigned with an IP address, only one IP address get
> assigned and that's xxx.xxx.132.118.
> When I try to use the .118 address with different vservers it also works fine,
> but other IP addresses like xxx.xxx.132.116 for instance doesn't get
> assigned.
>
> Host server /etc/network/interfaces:
> auto eth0
> iface eth0 inet static
> address xxx.xxx.134.227
> netmask 255.255.255.248
> network xxx.xxx.134.224
> broadcast xxx.xxx.134.231
> gateway xxx.xxx.134.225
>
> Is it because of a misconfiguration of the vservers or the network maybe?
> The host server is using xxx.xxx.134.xxx and the vservers use xxx.xxx.132.xxx,
> could that influence on anything?

well, yes, but if xxx.xxx.132.118 is working fine, then
the same setup for the others should work fine too ...

I would assume that the following scenario:

 - the xxx.xxx.134.227/29 has a default gateway, which is
   the attached router xxx.xxx.134.225 ...
 - the xxx.xxx.132/24 would use some different default gw
 - you have only one gateway configured
 - the router does only accept the 132.118 on the 'wrong'
   xxx.xxx.134.225 gateway ...

in any case, this can easily be debugged by somebody
who can check (or mirror) the router port ...

HTH,
Herbert

> > - do you get any error messages, or just no data?
>
> There's no error messages when starting/stopping the vservers. It just looks
> like they get assigned the right IP-address. Like this:
>
> Starting:
> ./vserver vswwwe1 start
> Starting the virtual server vswwwe1
> Server vswwwe1 is not running
> ipv4root is now xxx.xxx.132.116
> Host name is now vswwwe1
> Domain name is now vswwwe1.dcmedia.biz
> New security context is 1003
> Starting system logging: syslog-ng.
> Starting MTA: exim4.
> Starting internet superserver: inetd.
> Starting OpenBSD Secure Shell server: sshd.
> Starting deferred execution scheduler: atd.
> Starting periodic command scheduler: cron.
>
> Stopping:
> ./vserver vswwwe1 stop
> Stopping the virtual server vswwwe1
> Server vswwwe1 is running
> ipv4root is now xxx.xxx.132.116
> New security context is 1003
> Stopping periodic command scheduler: cron.
> Stopping MTA: exim4.
> Stopping internet superserver: inetd.
> Stopping OpenBSD Secure Shell server: sshd.
> Stopping deferred execution scheduler: atd.
> Stopping system logging: syslog-ng.
> Sending all processes the TERM signal...done.
> Sending all processes the KILL signal...done.
> Unmounting remote and non-toplevel virtual filesystems...done.
> Rebooting... sleeping 5 seconds
> Killing all processes
>
> Thanks
> >
> > > ---cut---
> > > vservers.conf:
> > > # Configuration file for the vservers service
> > > # BACKGROUND=yes
> > > # start the vservers on tty9, in background so the rest of the
> > > # boot process end early
> > > BACKGROUND=no
> > >
> > > # Where are all your child-servers living?
> > > VSERVERS_ROOT=/vservers
> > > # When starting or entering a vserver, its /etc/mtab is generated on
> > > # the fly so it matches the various volumes mounted inside the vserver
> > > GENERATEMTAB=yes
> > >
> > > hostname1.conf:
> > > IPROOT="x.x.x.116"
> > > S_HOSTNAME="hostname1"
> > > S_DOMAINNAME="hostname1.domain.com"
> > > S_CONTEXT="1003"
> > >
> > > hostname2.conf:
> > > IPROOT="x.x.x.118"
> > > S_HOSTNAME="hostname2"
> > > S_DOMAINNAME="hostname2.domain.com"
> > > S_CONTEXT="1002"
> > >
> > > ---cut---
> > >
> > > I can only use x.x.x.118 :I
> >
> > config looks fine so far ...
> >
> > best,
> > Herbert
> >
> > > Thanks.
> > > --
> > > Med venlig hilsen / Best regards
> > >
> > > Lars E. D. Jensen
> > > lars_at_dangvard.dk
> > > _______________________________________________
> > > Vserver mailing list
> > > Vserver_at_list.linux-vserver.org
> > > http://list.linux-vserver.org/mailman/listinfo/vserver
>
> --
> Med venlig hilsen / Best regards
>
> Lars E. D. Jensen
> lars_at_dangvard.dk
_______________________________________________
Vserver mailing list
Vserver_at_list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


About this list Date view Thread view Subject view Author view Attachment view
[Next/Previous Months] [Main vserver Project Homepage] [Howto Subscribe/Unsubscribe] [Paul Sladen's vserver stuff]
Generated on Wed 01 Dec 2004 - 11:23:31 GMT by hypermail 2.1.3