I recently downloaded Zope to pay with on mkLinux and have yet to actually get it to run. Somewhere along the line, I did determine that I needed to rebuild Python 1.5.2 with threading enabled and got that done, so the Zope installation process went ok. The problem is: When I do ./start, things churn around for a bit, then visibly start to happen- first I get a PROBLEM(100) ZServer computing default hostname message, but then Medusa starts using hostname: localhost (this is just my little lan) and claims 8080, then ftp starts and claims 8021, then PCGI creates a socket. So far I guess we are ok, but then I get: "...ZServer Monitor Server (1.5) started on port 8099" and nothing else like "at Wed Feb 9" etc and things just sit there. When I try to log in to the server at 8080, the browser is "connecting" but eventually times out. FTP doesn't work either. If I do a port scan, it shows an unknown tcp service is on 8021, http is on 8080, and nothing is on 8099. I'd really like to experiment with Zope but haven't gotten anywhere thus far. Any help would be appreciated. Thanks.
All of what you're seeing is an entirely normal startup process. I would suggest trying to troubleshoot at the HTTP level. For example, see if you can use telnet to connect to port 8080. While in telnet, do something like: GET / HTTP/1.0 And see if it returns a page. If so, you know it's a browser issue of some kind. If not... well... um... not sure. Richard Gordon wrote:
I recently downloaded Zope to pay with on mkLinux and have yet to actually get it to run. Somewhere along the line, I did determine that I needed to rebuild Python 1.5.2 with threading enabled and got that done, so the Zope installation process went ok.
The problem is: When I do ./start, things churn around for a bit, then visibly start to happen- first I get a PROBLEM(100) ZServer computing default hostname message, but then Medusa starts using hostname: localhost (this is just my little lan) and claims 8080, then ftp starts and claims 8021, then PCGI creates a socket. So far I guess we are ok, but then I get: "...ZServer Monitor Server (1.5) started on port 8099" and nothing else like "at Wed Feb 9" etc and things just sit there.
When I try to log in to the server at 8080, the browser is "connecting" but eventually times out. FTP doesn't work either. If I do a port scan, it shows an unknown tcp service is on 8021, http is on 8080, and nothing is on 8099.
I'd really like to experiment with Zope but haven't gotten anywhere thus far. Any help would be appreciated. Thanks.
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
-- Chris McDonough - Digital Creations, Inc. Publishers of Zope - http://www.zope.org
Thanks for the suggestions, but I'm still stuck as described below: At 6:22 PM -0500 2/9/00, Chris McDonough wrote:
I would suggest trying to troubleshoot at the HTTP level. For example, see if you can use telnet to connect to port 8080. While in telnet, do something like:
GET / HTTP/1.0
And see if it returns a page. If so, you know it's a browser issue of some kind. If not... well... um... not sure.
Telnet wouldn't connect, but I did manage to get an ftp client to talk on the port. The transcript indicated that it got a response back from Apache (which is only supposed to be on *80*), so I figured something was pretty hosed up. I disabled httpd and started over, but the best I could do is either "server busy" or no "document contained no data" when using a browser and nothing happened when I went back to using ftp client. Same results whether I try from across the lan or from the same machine as zope is running on. At 4:48 PM -0800 2/9/00, Sam Gendler wrote:
For a quick hack, read the comments at the top of z2.py (in the root folder). This gives the list of flags that you can provide to enable/disable certain features. I know that providing a blank port number ot the monitor server disables it. Perhaps that is all you need. I suppose it is something like " -m '' " .You can add these flags to the code in the start script and it will be passed in to z2.py
I had previously attempted this, but took another swing at your suggestion. Nothing but server busy or not accepting connections messages, but 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. Have I missed something in the configuration process that has to do with privileges maybe? I am running zope as root and have chmod'ed everything in sight to 0755 just to see if it made any difference. Any additional thoughts will be welcome. Thanks. 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)
Richard Gordon wrote:
Thanks for the suggestions, but I'm still stuck as described below:
At 6:22 PM -0500 2/9/00, Chris McDonough wrote:
I would suggest trying to troubleshoot at the HTTP level. For example, see if you can use telnet to connect to port 8080. While in telnet, do something like:
GET / HTTP/1.0
And see if it returns a page. If so, you know it's a browser issue of some kind. If not... well... um... not sure.
Telnet wouldn't connect, but I did manage to get an ftp client to talk on the port. The transcript indicated that it got a response back from Apache (which is only supposed to be on *80*), so I figured something was pretty hosed up. I disabled httpd and started over, but the best I could do is either "server busy" or no "document contained no data" when using a browser and nothing happened when I went back to using ftp client. Same results whether I try from across the lan or from the same machine as zope is running on.
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? If you meant 8080, I'm surprised an ftp client would even give you *any* useful information, as an ftp client by nature can't successfully talk to an HTTP server. (Although, come to think of it, I've never tried it, and have no idea what it would actually do.) The fact that you say the ftp client returned something about *Apache* is even more puzzling. All that underscored by the fact you say you *can't* talk to 8080 with telnet really leaves me scratching my head. Can you show me the command you're trying to use to access Zope via 8080 with telnet? And the ftp command you're using to try to get in? In the meantime... How about this. Dsiable any Zope startup in any of your startup scripts. Reboot so we get to a known state. Do not start Zope. Issue the command: netstat -a -n|grep 8080 See if anything *else* is trying to listen on 8080. Repeat for "8021" and "8099" If you see anything show up as LISTENING on any of those ports, either kill the offending processes or adjust the z2.py "*_PORT=" directives to different ports (ex: HTTP_PORT='9880'). Repeat for each effected service. Then retry the "start" script to start Zope and test.
At 4:48 PM -0800 2/9/00, Sam Gendler wrote:
For a quick hack, read the comments at the top of z2.py (in the root folder). This gives the list of flags that you can provide to enable/disable certain features. I know that providing a blank port number ot the monitor server disables it. Perhaps that is all you need. I suppose it is something like " -m '' " .You can add these flags to the code in the start script and it will be passed in to z2.py
I had previously attempted this, but took another swing at your suggestion. Nothing but server busy or not accepting connections messages, but 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.
Have I missed something in the configuration process that has to do with privileges maybe? I am running zope as root and have chmod'ed everything in sight to 0755 just to see if it made any difference. Any additional thoughts will be welcome. Thanks.
-- Chris McDonough Digital Creations, Inc. Zope - http://www.zope.org
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)
----- Original Message ----- From: Richard Gordon <maccgi@bellsouth.net>
Have I missed something in the configuration process that has to do with privileges maybe? I am running zope as root and have chmod'ed everything in sight to 0755 just to see if it made any difference.
Ah. Does the 'nobody' user own your 'Zope/var'? When you run Zope as root, by default it changes to running as 'nobody', who not only needs read access to everything but write access to all of 'var'. Cheers, Evan @ digicool
At 9:52 PM -0600 2/9/00, Evan Simpson wrote:
Ah. Does the 'nobody' user own your 'Zope/var'? When you run Zope as root, by default it changes to running as 'nobody', who not only needs read access to everything but write access to all of 'var'.
Thanks for the suggestion- 'nobody' owned the var/Z2.pid, but other stuff was either root or 506 (ok, I'll ask- who/what is 506?). I did chown on every directory & file that have anything to do with Zope to place everything under nobody's ownership. Didn't help, but I appreciate the try and suspect that I may have some other things going on machine-wise that are involved in this. 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)
For a quick hack, read the comments at the top of z2.py (in the root folder). This gives the list of flags that you can provide to enable/disable certain features. I know that providing a blank port number ot the monitor server disables it. Perhaps that is all you need. I suppose it is something like " -m '' " .You can add these flags to the code in the start script and it will be passed in to z2.py --sam Richard Gordon wrote:
I recently downloaded Zope to pay with on mkLinux and have yet to actually get it to run. Somewhere along the line, I did determine that I needed to rebuild Python 1.5.2 with threading enabled and got that done, so the Zope installation process went ok.
The problem is: When I do ./start, things churn around for a bit, then visibly start to happen- first I get a PROBLEM(100) ZServer computing default hostname message, but then Medusa starts using hostname: localhost (this is just my little lan) and claims 8080, then ftp starts and claims 8021, then PCGI creates a socket. So far I guess we are ok, but then I get: "...ZServer Monitor Server (1.5) started on port 8099" and nothing else like "at Wed Feb 9" etc and things just sit there.
When I try to log in to the server at 8080, the browser is "connecting" but eventually times out. FTP doesn't work either. If I do a port scan, it shows an unknown tcp service is on 8021, http is on 8080, and nothing is on 8099.
I'd really like to experiment with Zope but haven't gotten anywhere thus far. Any help would be appreciated. Thanks.
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
-- Sam Gendler Chief Technology Officer - Impossible, Inc. 1222 State St. Suite 250 Santa Barbara CA. 93101 w: 805-560-0508 f: 805-560-0608 c: 805-689-1191 e: sgendler@impossible.com
participants (4)
-
Chris McDonough -
Evan Simpson -
Richard Gordon -
Sam Gendler