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

From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Tue 17 Jun 2003 - 16:58:31 BST


On Tue, Jun 17, 2003 at 11:47:36AM -0400, Cathy Sarisky wrote:
> On Tue, 17 Jun 2003, Herbert Poetzl wrote:
>
> > On Tue, Jun 17, 2003 at 11:20:18AM -0400, Cathy Sarisky wrote:
> > >
> > > Ok, so that does resolve error message (/usr/sbin/vserver: virtual:
> > > command not found), but it appears my problem is larger.
> > >
> > > I'm still seeing a failure to bind to the second IP if the first has
> > > already been bound. For example, with Apache:
> > >
> > > [Tue Jun 17 11:06:27 2003] [crit] (98)Address already in use: make_sock:
> > > could not bind to port 80
> >
> > search for bound/active ports/programs ...
> >
> > (e.g. on physical do)
> > # chcontext --ctx 1 lsof -i -Pn | grep :80
>
> It shows nothing in use for the second IP on port 80, nor anything on
> 0.0.0.0.
>
> Here's something odd: If I start the service that binds port 80 on the
> second IP *first*, then I can start the service that binds port 80 on the
> first IP, and get both running correctly. However, if there's already
> something bound to port 80 on the first IP, I cannot bind the second IP.

hmm, how do you verify ...

I mean, which utility do you use to bind to port 80
on the second/first interface (alias) ...

and what does change in chcontext --ctx 1 lsof -i -Pn | grep :80
if you bind only to the first or second ...

best,
Herbert


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 Tue 17 Jun 2003 - 17:15:21 BST by hypermail 2.1.3