Thanks Jeff...that was the problem...all of my Zope instances until now have been started by uid zope. Rather stupid mistake, but a learning experience nonetheless. Thanks again, -Brian

-----Original Message----- From: Jeff K. Hoffman [SMTP:jeff.hoffman@goingv.com] Sent: Monday, March 06, 2000 3:43 PM To: Pearson, Brian Edward (GEA, 056278) Cc: 'Michel Pelletier'; 'zope@zope.org' Subject: RE: [Zope] Listening on specific interfaces

On Mon, 6 Mar 2000, Pearson, Brian Edward (GEA, 056278) wrote:

[snip]

...

$ ./start -a 3.130.232.27 -w 80 -f 8021 -m 8099 Traceback (innermost last): File "/opt/devnet-zope/Zope-2.1.4-solaris-2.6-sparc/z2.py", line 493, in ? logger_object=lg) File

"/opt/devnet-zope/Zope-2.1.4-solaris-2.6-sparc/ZServer/medusa/http_server

...

.py", line 552, in __init__ self.bind ((ip, port)) File

"/opt/devnet-zope/Zope-2.1.4-solaris-2.6-sparc/ZServer/medusa/asyncore.py

...

", line 205, in bind return self.socket.bind (addr) socket.error: (13, 'Permission denied')

3.130.232.27 = hme0:4

If I specify an HTTP port that is not currently bound to the physical interface (hme0), such as 1234, Zope starts up properly.

Out of curiosity, are you running (lauching) Zope as root? The lower ports (below 1024?) are privelaged on UNIX, and require root permission to bind. Higher ports, such as 1234, are not; anyone has access to port 1234.

We have a Solaris 2.6 box here running Zope 2.1.4. We launch ZServer with the -a parameter specifying our interface, and it works like a charm. I suspect this is not interface related.

...

Thanks, -Brian

--Jeff

--- Jeff K. Hoffman 704.849.0731 x108 Chief Technology Officer mailto:jeff@goingv.com Going Virtual, L.L.C. http://www.goingv.com/