[Zope] Socket Problems

[Patrick Lewis]

Ok, I was able to solve my problem, so for future generations, here it
goes.  My loopback device (lo0) was not configured properly.  Apparently,
the monitor attaches to the localhost via the loopback device.  I fixed
lo0, and now everything works great.

Thanks to everyone who gave hints where to look.

On Sat, Mar 25, 2000 at 11:10:03AM -0800, Patrick Lewis wrote:
> I have kind of a stupid question about sockets.  When starting zope (using
> z2.py -D) I get:
> 
  <SNIP>
> ------
> 2000-03-25T18:56:54 INFO(0) ZServer PCGI Server started at Sat Mar 25
> 10:56:54 2000
>         Unix socket: /usr/local/src/Zope-2.1.4-src/var/pcgi.soc
> Traceback (innermost last):
>   File "/usr/local/src/Zope-2.1.4-src/z2.py", line 551, in ?
>     port=MONITOR_PORT)
>   File "/usr/local/src/Zope-2.1.4-src/ZServer/medusa/monitor.py", line
> 264, in __init__
>     monitor_server.__init__ (self, hostname, port)
>   File "/usr/local/src/Zope-2.1.4-src/ZServer/medusa/monitor.py", line
> 168, in __init__
>     self.bind ((hostname, port))
>   File "/usr/local/src/Zope-2.1.4-src/ZServer/medusa/asyncore.py", line
> 205, in bind
>     return self.socket.bind (addr)
> socket.error: (49, "Can't assign requested address")
> 
> Using z2.py -D -m '' (disabling the monitor), everything works fine.
> (Except no monitor, obviously).  Using -m with other socket numbers
> results in the same error. (49, "Can't... ).
> 
> FreeBSD 3.4, Zope 2.1.4, running as root.  Any ideas what to try?  I would
> like to use the monitor, if just for the coolness factor.