At 10:47 PM -0500 2/9/00, Chris McDonough wrote:
I'm confused. When you say "I did manage to get an ftp client to talk on the port", which port do you mean? 8080 or 8021?
Sorry to be ambiguous. I was using Anarchie (Mac ftp client) that can be made to fetch things via http and just told it to go to http://192.168.0.1:8080 which resulted in the odd transcript entry. Telnet was also originally from a Mac and nothing echoed, but when I do it from the linux box, it does say it's connected, but won't do anything.
netstat -a -n|grep 8080
See if anything *else* is trying to listen on 8080. Repeat for "8021" and "8099"
Nothing else was listening and I had previously tried other port assignments.
I did notice that a new python z2.py process is being spawned with every hit, so it looks like it's tripping as it tries to do something. I was hoping that there would be something in the log, but it's empty.
z2.py is launched solely by the start script, AFAIK. I'm really confused.
Me too. To clarify, 2 processes are launched initially as expected, but 3 more pop up as soon as I try to access Zope from a browser and I've gotten yet another one to appear on a second attempt (but one of the bunch is always a zombie by then). Testing further just a minute ago, I find that the server machine is going into kernel panic when the browser tries to connect, so I suppose that there is something very sideways that may not even be related to Zope. I've got another linux box that I can try this stuff on, so I think that I'll resume my efforts there to see if this whole mess is just some kind of environmental thing. Thanks for your help and I'll let you know if I figure it out. Richard Gordon -------------------- Gordon Consulting & Design Database Design/Scripting Languages mailto:richard@richardgordon.net http://www.richardgordon.net 770.971.6887 (voice) 770.216.1829 (fax)