From: Bill Brigden (bill_at_baghead.co.uk)
Date: Tue 17 Dec 2002 - 15:12:54 GMT
It could have been that an IP bind or something had got "stuck" (good
explanation I know!) I have found that mounts in VPS were getting stuck in
the startup/shutdown scripts for a time - then I realised the current
directory problem, and a cd / fixed it!
Bill.
----- Original Message -----
From: "Dinesh Mistry" <dmistry_at_yourhostdirect.com>
To: <vserver_at_solucorp.qc.ca>
Sent: Tuesday, December 17, 2002 2:52 PM
Subject: RE: [vserver] multiple ips 2.4.20 ctx16
> Ok this had to be a 'stop trying to configure VPS's at 3;00am" type
> thing
>
> I just tried to duplicate the problems I have was having last night and
> now everything works just fine.
>
> Sorry folks
>
> -----------------------------------
> Dinesh Mistry
> YourHostDirect
>
> http://www.yourhostdirect.com
> -----------------------------------
>
>
> -----Original Message-----
> From: Paul Sladen [mailto:vserver_at_paul.sladen.org]
> Sent: Tuesday, December 17, 2002 8:07 AM
> To: VServer Patch List
> Subject: Re: [vserver] multiple ips 2.4.20 ctx16
>
> On Tue, 17 Dec 2002, Dinesh Mistry wrote:
> > > 1- .183 is the root server's primary IP.
> > > 2- .183 isn't assigned to eth0 (or whichever interface is
> appropriate)
> > > 3- .183 is already assigned to another vserver.
> > > What error message (if any) are you getting? That's certainly the
> right
> > Looks like its only on debian vserver under a redhat 7.3 it works
> > werid??
>
> Could you explain what you mean--lots of people /don't/ use that
> combination (and don't have problems...) !
>
> -Paul
> --
> Nottingham, GB
>
>
>