Zope content not available
We have a Linux server that is running Apache and Zope for some web content. This server/system was set up some time ago by a person who is no longer at the company. As a further complication, we don't even have anyone on staff anymore who is a capable Linux admin. We have me. I know just enough to be able to make changes to web content, DNS and Firewall, but not true administration of this box or its services. Today the Zope-managed content is not available on the web. I have logged on to the host server and have restarted both Zope and Apache without effect. I know Zope is running because I can FTP to it on Port 8021 and can see the content there. I know this is a very vague request, but can someone help me with where to begin looking for the problem? Any assistance would be much appreciated. Thanks. Rob
Some help: 1) Take a look at the start script "start" in the root of your Zope directory. It is what controls the web, ftp and monitor servers. It is possible it is just not starting up the webserver. Look at the "z2.py" for documentation on the start script parameters. It will also tell you what port it is started on. 2) Try pinging it from the machine > ping localhost:8080 or > lynx localhost:8080, localhost:80 3) Run top from the command line. Look for "python". BZ -- http://www.zopezone.com http://www.bluewildfire.com
We have a Linux server that is running Apache and Zope for some web content. This server/system was set up some time ago by a person who is no longer at the company. As a further complication, we don't even have anyone on staff anymore who is a capable Linux admin. We have me. I know just enough to be able to make changes to web content, DNS and Firewall, but not true administration of this box or its services.
Today the Zope-managed content is not available on the web. I have logged on to the host server and have restarted both Zope and Apache without effect. I know Zope is running because I can FTP to it on Port 8021 and can see the content there. I know this is a very vague request, but can someone help me with where to begin looking for the problem? Any assistance would be much appreciated. Thanks.
Rob
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
I would reboot the server first off. With any luck the guy set it up to come up automatically. Try: shutdown -r now logged in as root and see if it will come up. If you still have problems, try going to: http://yourdomain.com/manage and send the error, if any, to the list. Rick Rob Harville wrote:
We have a Linux server that is running Apache and Zope for some web content. This server/system was set up some time ago by a person who is no longer at the company. As a further complication, we don't even have anyone on staff anymore who is a capable Linux admin. We have me. I know just enough to be able to make changes to web content, DNS and Firewall, but not true administration of this box or its services.
Today the Zope-managed content is not available on the web. I have logged on to the host server and have restarted both Zope and Apache without effect. I know Zope is running because I can FTP to it on Port 8021 and can see the content there. I know this is a very vague request, but can someone help me with where to begin looking for the problem? Any assistance would be much appreciated. Thanks.
*/Rob/*
------------------------------------------------------------------------
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
On Mon, Oct 13, 2003 at 10:29:55AM -0700, D. Rick Anderson wrote:
I would reboot the server first off. With any luck the guy set it up to come up automatically. Try:
shutdown -r now
I would NOT do that if it's a remote box. I recently got bit HARD by rebooting a box that I didn't have local access to. It came back up without sshd :-0 furthermore, rebooting will give you no clue about what caused the problem, and you can bet it will happen again. -- Paul Winkler http://www.slinkp.com Look! Up in the sky! It's THE GOAT! (random hero from isometric.spaceninja.com)
Hi D, D. Rick Anderson wrote:
I would reboot the server first off. With any luck the guy set it up to come up automatically. Try:
shutdown -r now
Wah! Reboot a *nix server just for restarting a service? Shame on you! :))) (Chances are, beside reducing the uptime, the server is not reachable after that) Regards Tino
participants (5)
-
BZ -
D. Rick Anderson -
Paul Winkler -
Rob Harville -
Tino Wildenhain