[Checkins] SVN: zope2book/trunk/source/InstallingZope.rst Manually apply patches lost in rename; move troubleshooting to the end of the file.
Tres Seaver
tseaver at palladion.com
Tue Feb 10 12:09:10 EST 2009
Log message for revision 96393:
Manually apply patches lost in rename; move troubleshooting to the end of the file.
Changed:
U zope2book/trunk/source/InstallingZope.rst
-=-
Modified: zope2book/trunk/source/InstallingZope.rst
===================================================================
--- zope2book/trunk/source/InstallingZope.rst 2009-02-10 17:01:05 UTC (rev 96392)
+++ zope2book/trunk/source/InstallingZope.rst 2009-02-10 17:09:09 UTC (rev 96393)
@@ -418,7 +418,7 @@
Zope, and browse to the URL `http://localhost:8080/
<http://localhost:8080/>`_.
-If your Zope instance has beens installed properly, and you're visiting the
+If your Zope instance has been properly installed, and you're visiting the
correct URL, you will be presented with the Zope "QuickStart" screen.
.. figure:: ../Figures/quickstart.png
@@ -485,7 +485,7 @@
Controlling the Zope Process from the Command Line
--------------------------------------------------
-To stop a manually-run Zope on Windows, press "Ctrl+C" while in the console
+To stop a manually-run Zope on Windows, press "Ctrl+C" while the console
window under which Zope is running is selected. To stop a Zope on Windows
that was run as a service, find the service with the name you assigned to
your Zope in the Services Control Panel application, and stop the service.
@@ -505,84 +505,7 @@
$ kill `cat var/Z2.pid`
-Troubleshooting and Caveats
----------------------------
-Running zopectl returns with an OSError
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-When running Zope on a 2.6.x Linux kernel, Solaris or Mac OS X, zopectl
-returns an error ``OSError: [Errno 10] No child processes``. This is due to
-a bug in Zope 2.7.0. You have the following options:
-
-- Install a patch currently in CVS. See http://zope.org/Collectors/Zope/1235
- for the collector log and a small patch. The patch file is named
- ``zdctl.diff``. Download it to a temporary directory, e.g., ``/tmp``. Then
- 'cd' to the directory ``$ZOPE_HOME/lib/python/zdaemon`` (continuing our
- previous example, this would be ``~/myzope/zope2.7/lib/python/zdaemon``)
- and run the patch command, e.g.::
-
- $ cd ~/myzope/zope2.7/lib/python/zdaemon
- $ patch < /tmp/zdctl.diff'.
-
- The patch program should respond with an output similar to ``patching
- file zdctl.py``.
-
-- If running on Linux: downgrade to a 2.4.x kernel
-
-- Work around this issue by placing Zope in the background manually with::
-
- $ nohup ~/myzope/instance/bin/runzope &
-
-Note though that your Zope instance will not be automatically restarted by
-'zdaemon' this way, and that this method should not be used on a production
-server.
-
-Browser cannot connect to port 8080
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-If your browser fails to connect with anything on TCP port 8080, your Zope
-instance may be running on a non-standard TCP port (for example, some
-versions of Debian Linux ship with Zope's default TCP port as 9673). To
-find out exactly which URL to use, look at the logging information Zope
-prints as it starts up when started in the foreground, i.e., when started
-with ``./runzope`` or ``./zopectl fg``. For example::
-
- ...
- ------
- 2004-04-21T21:48:27 INFO(0) ZServer HTTP server started at Wed Apr 21 21:48:27 2004
- Hostname: arod
- Port: 9673
- ------
- 2004-04-21T21:48:27 INFO(0) ZServer FTP server started at Wed Apr 21 21:48:27 2004
- Hostname: arod
- Port: 8021
- ...
-
-The first log entry indicates that Zope's web server is listening on port
-9673 on host ``arod``. This means that the management URL is
-http://arod:9673/manage.
-
-As mentioned previously, Zope only prints to the console when started in
-the foreground, with ``./runzope`` or ``runzope.bat``. This logging
-information can be found in the ``log/event.log`` file in your
-``INSTANCE_HOME`` directory.
-
-Certain versions of Microsoft Internet Explorer 5.0.1 and 5.5 are
-incompatible with the ZMI in some respects, which manifest themselves as an
-inability to properly log in. If you have trouble logging in with IE 5.0.1
-or IE 5.5, try a different browser or upgrade to a later version.
-
-Forgot administrative password
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-If you forget or lose your initial Zope user name and password, shut Zope
-down, change the initial user password with the *zpasswd.py* script, and
-restart Zope. See the chapter entitled `Users and Security
-<Security.html>`_ for more information about configuring the initial user
-account.
-
-
Customizing your Zope instance
------------------------------
@@ -653,10 +576,10 @@
This directive causes Zope to ``setuid(2)`` to the specified user when run
as root on a UNIX system. This method boosts system security, as a
-compromised Zope instance would not lend itself to enable a compromised
-user to easily damage an entire system. One motivation for running Zope as
-root in the first place is to be able to bind to *privileged* ports, or
-ports with values below 1024.
+compromised Zope instance would not enable a compromised user to damage
+easily an entire system. One motivation for running Zope as root in the
+first place is to be able to bind to *privileged* ports, or ports with
+values below 1024.
Configuring the Session machinery
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -694,8 +617,85 @@
For further documentation, see the inline comments in ``zope.conf``.
+Troubleshooting and Caveats
+---------------------------
+
+Running zopectl returns with an OSError
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+When running Zope on a 2.6.x Linux kernel, Solaris or Mac OS X, zopectl
+returns an error ``OSError: [Errno 10] No child processes``. This is due to
+a bug in Zope 2.7.0. You have the following options:
+
+- Install a patch currently in CVS. See http://zope.org/Collectors/Zope/1235
+ for the collector log and a small patch. The patch file is named
+ ``zdctl.diff``. Download it to a temporary directory, e.g., ``/tmp``. Then
+ 'cd' to the directory ``$ZOPE_HOME/lib/python/zdaemon`` (continuing our
+ previous example, this would be ``~/myzope/zope2.7/lib/python/zdaemon``)
+ and run the patch command, e.g.::
+
+ $ cd ~/myzope/zope2.7/lib/python/zdaemon
+ $ patch < /tmp/zdctl.diff'.
+
+ The patch program should respond with an output similar to ``patching
+ file zdctl.py``.
+
+- If running on Linux: downgrade to a 2.4.x kernel
+
+- Work around this issue by placing Zope in the background manually with::
+
+ $ nohup ~/myzope/instance/bin/runzope &
+
+Note though that your Zope instance will not be automatically restarted by
+'zdaemon' this way, and that this method should not be used on a production
+server.
+
+Browser cannot connect to port 8080
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+If your browser fails to connect with anything on TCP port 8080, your Zope
+instance may be running on a non-standard TCP port (for example, some
+versions of Debian Linux ship with Zope's default TCP port as 9673). To
+find out exactly which URL to use, look at the logging information Zope
+prints as it starts up when started in the foreground, i.e., when started
+with ``./runzope`` or ``./zopectl fg``. For example::
+
+ ...
+ ------
+ 2004-04-21T21:48:27 INFO(0) ZServer HTTP server started at Wed Apr 21 21:48:27 2004
+ Hostname: arod
+ Port: 9673
+ ------
+ 2004-04-21T21:48:27 INFO(0) ZServer FTP server started at Wed Apr 21 21:48:27 2004
+ Hostname: arod
+ Port: 8021
+ ...
+
+The first log entry indicates that Zope's web server is listening on port
+9673 on host ``arod``. This means that the management URL is
+http://arod:9673/manage.
+
+As mentioned previously, Zope only prints to the console when started in
+the foreground, with ``./runzope`` or ``runzope.bat``. This logging
+information can be found in the ``log/event.log`` file in your
+``INSTANCE_HOME`` directory.
+
+Certain versions of Microsoft Internet Explorer 5.0.1 and 5.5 are
+incompatible with the ZMI in some respects, which manifest themselves as an
+inability to properly log in. If you have trouble logging in with IE 5.0.1
+or IE 5.5, try a different browser or upgrade to a later version.
+
+Forgot administrative password
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+If you forget or lose your initial Zope user name and password, shut Zope
+down, change the initial user password with the *zpasswd.py* script, and
+restart Zope. See the chapter entitled `Users and Security
+<Security.html>`_ for more information about configuring the initial user
+account.
+
When All Else Fails
--------------------
+~~~~~~~~~~~~~~~~~~~
If there's a problem with your installation that you just cannot solve, do
not despair. You have many places to turn for help, including the Zope
More information about the Checkins
mailing list