[thelist] Networking, Webservers, Zope & OS X

[Martin]

On Thursday, January 3, 2002, at 11:21  pm, Patti Ames wrote:

> If you can't access the mac's web server by IP, then it is not public 
> (since you can hit other services on the mac).
>
> Open up a terminal on the mac, and type:
>   netstat -na | grep '\.80' (show the status of the open sockets on 
> port 80)
>
> If you get something like
>      tcp        0      0  *.80                   *.*                    
> LISTEN
> then your win box _should_ be able to hit it.
> but if you get something like
>      tcp        0      0  127.0.0.1.80         *.*                    
> LISTEN
> then your web server is only serving itself. You need to update your 
> Zope config.

Ok, that's the problem, right enough - I've got the config set
up as
# This is the IP address of the network interface you want your servers 
to
# be visible from.  This can be changed to '' to listen on all 
interfaces.
IP_ADDRESS='127.0.0.1'

Problem is, if I leave it as '' or change it to the box's IP
(192.168.1.100) then the Server won't load - it just dies
on me:

	  File /Applications/Zope/lib/python2.1/asyncore.py, line 298, in bind
	error: host not found
	------
	2002-01-04T01:50:02 PROBLEM(100) zdaemon zdaemon: Fri Jan  4 
01:50:02 2002: The kid, 491, died on me.

It only ever works if I have 127.0.0.1 in there.


[some time later]

Oh ok - if I change the machine settings in Netinfo Manager to
the following:

	ip address: 192.168.1.100, 127.0.0.1
	name: mull, localhost

(adding the 192 ip and mull name) plus adding a line for
mull to the Windows box hosts.sam file then both boxes
can get to the Zope served pages from http://mull/ and
I'm getting netstat results of:

tcp        0      0  192.168.1.100.8021     *.*                    LISTEN
tcp        0      0  192.168.1.100.8081     *.*                    LISTEN
tcp        0      0  192.168.1.100.8080     *.*                    LISTEN
tcp        0      0  *.80                   *.*                    LISTEN

And by putting Zope back to listening on 8080, 8443
etc, I can have both Apache *and* Zope running, which
is nice because I can then have Apache as a staging
environment for the publication, mirroring what's in the
production environment

The fun things *now* are that:
1) Zope is still serving FTP from hostname mac (wtf?)
2) If I try to turn off FTP, Zope dies very dramatically and
    won't restart without a partial reinstall
3) Possibly because of (1), Zope claims to be permanently
     'Loading' rather than running... although it works fine
     apart from (1) and (2) above.

ho hum - if it were easy, anyone could do it...

Martin
_______________________________________________
email: martin at easyweb.co.uk             PGP ID:	0xA835CCCB
	martin at members.evolt.org      snailmail:	30 Shandon Place
   tel:	+44 (0)774 063 9985				Edinburgh,
   url:	http://www.easyweb.co.uk			Scotland