Here are some of the things I found in beating my head against this for a while: 1) make sure you have Python 1.5.2 on your system. For whatever reason many of my apache/Zope problems were solved (RH 6.0) when I compiled and installed 1.5.2 in place of 1.5.1 that comes with the RH dist. The Zope docs seem a little unclear on this to me. 2) Look at /usr/local/Zope-2.0.0b3-linux2-x86/var/pcgi.log for errors. 3) It seems to me that it doesn't work to do Zserver and apache at the same time. You may need ./stop in that directory. 4) When you first access the site it will start a process that remains between accesses (thus Persistent CGI). Do a ps aux and grep for python. You'll see your PCGI servers running. Kill them. the access file seemingly only gets read ONCE each time PCGI is started so if you change the file after PCGI is started you won't be able to access the file. 5) Send your pcgi.log and apache error log files 6) What Rewrite rules are you using in your httpd.conf 7) Does your access.conf allow EXEC in your Zope dir? Joshua At 12:15 PM -0400 8/12/99, James L. Hartwell wrote:
Here a copy of our Zope.cgi file, where-in we think the problem lies.
#### begin file listing ######
#!/usr/local/Zope-2.0.0b3-linux2-x86/pcgi/bin/pcgi-wrapper PCGI_NAME=Zope PCGI_MODULE_PATH=/usr/local/Zope-2.0.0b3-linux2-x86/lib/python/Zope PCGI_PUBLISHER=/usr/local/Zope-2.0.0b3-linux2-x86/pcgi/pcgi_publisher.py PCGI_EXE=/usr/local/Zope-2.0.0b3-linux2-x86/bin/python PCGI_SOCKET_FILE=/usr/local/Zope-2.0.0b3-linux2-x86/var/pcgi.soc PCGI_PID_FILE=/usr/local/Zope-2.0.0b3-linux2-x86/var/pcgi.pid PCGI_ERROR_LOG=/usr/local/Zope-2.0.0b3-linux2-x86/var/pcgi.log PCGI_DISPLAY_ERRORS=1 BOBO_REALM=/home/httpd/cgi-bin/Zope.cgi BOBO_DEBUG_MODE=1 INSTANCE_HOME=/usr/local/Zope-2.0.0b3-linux2-x86
#### end file listing ####
we installed ZOPE under: /usr/local/Zope-2.0.0b3-linux2-x86/ and our home cgi directory is: /home/httpd/cgi-bin
-- Thanks for any help!
-----Original Message----- From: James L. Hartwell <hartwelljl@hartwellconsulting.com> To: zope@zope.org <zope@zope.org> Date: Thursday, August 12, 1999 12:00 PM Subject: Fw: Apache and Zope
-----Original Message----- From: Paul Everitt <paul@digicool.com> To: James L. Hartwell <hartwelljl@hartwellconsulting.com> Cc: info@digicool.com <info@digicool.com> Date: Thursday, August 12, 1999 6:22 AM Subject: Re: Apache and Zope
Unfortunately you won't get as good answers sending email to info@digicool.com. This subject comes up repeatedly on the main zope@zope.org list and the folks there have pretty much seen it all, so I suggest sending your message there.
Apache, and mod_rewrite in particular, can be an *extreme* bear to configure. For instance the Apache that shipped with RedHat 5.2 silently failed to load the Apache mod_rewrite module, which was supplied as a dynamically linked extension. As soon as it was statically compiled in, it worked fine.
--Paul
"James L. Hartwell" wrote:
Hello,
We've been thorugh a number of stumbling blocks while attepting to get Zope to run with Apache.
We are using Zope2.0.0b3 which we have installed under /usr/local.
On one server we are unable to login when we execute the http:/server/cgi-bin/Zope.cgi/manage script. We have tried letting Zope set the password when it installs and we have tried setting our own password.
In either case, when we type in the super user id and the password, we keep getting permission denied. We have checked permissions on directories in the Zope directory.
We added the authorization pass through information in /etc/httpd/conf/httpd.conf based on the documentation. And we *believe* that is is correct. -- we used the rewriteengine scheme in httpd.conf rather than recompile Apache.
--------
We installed the same zope version on one web server. There we have repeatedly checked and double checked the apache *.conf files. They (except for the development virtual servers) are the same as the other conf files.
On one machine we get an error message saying that the resource we are trying to get is unavailable. We suspected permissions on the files and directories under Zope, but they seem ok.
On both machines, we cd into the Zope directory run ./start (we initially thought that that was strictly for running ZServer, but found that it got us p ast the temporarily unavailable message. So we are asusming that we need to run this.
Then we try accessing the cgi-bin/Zope.cgi/manage script as mentioned earlier.
Thanks for the help
_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope
(To receive general Zope announcements, see: http://www.zope.org/mailman/listinfo/zope-announce
For developer-specific issues, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )
# # # _____________________________________________ Joshua Brauer Box 915 http://www.brauer.org Fort Collins, CO 80522 Fax: (419) 793-4120 _____________________________________________ In flying I have learned that carelessness and overconfidence are usually far more dangerous than deliberately accepted risks. -- Wilbur Wright in a letter to his father, September 1900 _____________________________________________________