-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of beno Sent: Tuesday, October 01, 2002 9:55 AM To: Charlie Reiman Cc: zope@zope.org Subject: RE: [Zope] Port 8021 Malfunction
At 09:16 AM 10/1/2002 -0700, you wrote:
"netstat -n -a" will tell you if there is something LISTENING on that port. Try it before you start zope, the port may already be busy. If not, try it after and make sure it is listening.
I ran that before shutting down Zope and the port is not in use.
I'm pretty sure Zope makes it abundantly clear on startup if it can or can't get the ports it wants.
I forget what problem I had once upon a time that caused me to do this, but now I always start zctl.py with a nuhup command.
That's good. nohup should capture all output. What version of Zope are you running? From looking at CVS, it looks like zctl.py was 'temporarily' removed about two years ago. http://cvs.zope.org/Zope/?hideattic=0
There is also a bug with zope and ftp that you may be running into. If you run in debug mode, zope prints to the console when it gets an incoming connection. If stdout is not dumped someplace (a file, tty, or /dev/null), zope will hang. The work around is to put stdout someplace useful or run in production mode.
Could you be more specific? TIA, beno
Not really. Nohup should already capture output. If you've read the help z2.py you know as much as I do.