[Zope] Zope Temporarily Unavailable

[Martijn Pieters]

At 10:20 11-9-99 , Jonathan Nathan wrote:
>hello,
>
>i'm struggling with a zope install.  trying to use zserver with pcgi on
>top of apache 1.3.6 (mod_rewrite compiled in, the rewrite rule put into
>httpd.conf). it's zope 2.0.0 and python 1.5.2
>
>i get the infamous temporarily unavailable message, which comments:
>Error parsing pcgi info file
>pcgi-wrapper-version 2.0a5
>
>if i run python pcgifile.py Zope.cgi i get
>jon@w1:/web/zope# python pcgifile.py Zope.cgi
>PCGI_SOCKET_FILE write permission error: /web/zope/var/pcgi.soc
>
>the files look like so:
>
>jon@w1:/web/zope# ls -al var/
>total 160
>drwxrwxrwx   3 zopesrv  nobody    512 Sep 11 04:12 .
>drwxr-xr-x  10 zopesrv  nobody    512 Sep 11 04:16 ..
>-rw-r--r--   1 zopesrv  nobody     84 Mar 26 16:44 .cvsignore
>-rw-------   1 zopesrv  nobody  78463 Sep 11 02:18 Data.fs
>-rw-r--r--   1 zopesrv  nobody  76750 Jun 23 19:03 Data.fs.in
>-rw-r--r--   1 zopesrv  nobody      5 Sep 11 04:16 Data.fs.lock
>-rw-r--r--   1 zopesrv  nobody      0 Sep 11 02:28 Data.fs.tmp
>-rw-r--r--   1 zopesrv  nobody      0 Sep 11 02:18 Z2.log
>-rw-rw-rw-   1 zopesrv  nobody     11 Sep 11 04:16 Z2.pid
>drwxr-xr-x   3 zopesrv  nobody    512 Sep 11 02:18 gadfly
>-rw-r--r--   1 zopesrv  nobody      0 Sep 11 02:45 pcgi.log
>-rw-r--r--   1 zopesrv  nobody      5 Sep 11 04:16 pcgi.pid
>srwxrwxrwx   1 root     nobody      0 Sep 11 04:12 pcgi.soc
>-rw-r--r--   1 zopesrv  nobody      5 Sep 11 04:16 zProcessManager.pid
>jon@w1:/web/zope#
>
>yes, i created a user and called him zopesrv and put him in the same group
>as nobody.  figured this would ease apache/zope permissions problems.
>
>i'm running the start and stop scripts as root - it seems like zope
>creates the pcgi.soc file upon a connection.  if it's root owned and s777,
>why am i getting permissions errors on it?
>
>here's my Zope.cgi:
>
>jon@w1:/web/zope# more Zope.cgi
>#!/web/zope/pcgi/pcgi-wrapper
>PCGI_NAME=Zope
>PCGI_PORT=8079
>PCGI_MODULE_PATH=/web/zope/lib/python/Main.py
>PCGI_PUBLISHER=/web/zope/pcgi/pcgi_publisher.py
>PCGI_EXE=/usr/bin/python
>PCGI_SOCKET_FILE=/web/zope/var/pcgi.soc
>PCGI_PID_FILE=/web/zope/var/pcgi.pid
>PCGI_ERROR_LOG=/web/zope/var/pcgi.log
>PCGI_DISPLAY_ERRORS=1
>BOBO_REALM=/web/zope/Zope.cgi
>BOBO_DEBUG_MODE=1
>INSTANCE_HOME=/web/zope
>
>do i need the PCGI_PORT ?  what's the deal with PCGI_MODULE_PATH ?  it
>defaulted to /web/zope/lib/python/Zope but the pcgifile.py didn't like
>that. i changed it to Main.py because i saw a few other posters do that in
>the list archives.

PCGI_PORT should go. It specifies a port on a machine (default to 
localhost, set by PCGI_HOST directive) on which the PCGI directive will 
communicate with the long-running-process (in our case Zope), in case you 
want to use INET sockets. Leave it out, and it will (as it should) use a 
named pipe, the PCGI_SOCKET_FILE.

When I set up PCGI, I found Jeff Bauers pcgifile.py invaluable. It is a 
PCGI info file sanity checker. You run it as a CGI file with your Zope.cgi 
as a parameter, and it will tell you wether or not it will run, and if not, 
what you could do to make it work.

--
Martijn Pieters, Web Developer
| Antraciet http://www.antraciet.nl
| T: +31 35 7502100 F: +31 35 7502111
| mj@antraciet.nl http://www.antraciet.nl/~mj
| PGP: http://wwwkeys.nl.pgp.net:11371/pks/lookup?op=get&search=0xA8A32149
---------------------------------------------