strange pcgi prob in FreeBSD
Hi all, While trying to update the zope port for the FreeBSD ports system I ran into a problem which kinda has me stumped. I looked thru the ML archives, but couldn't come up with anything, although I'm sure this has happened before. Everything runs normal when I just connect to ZServer. Running it thru Apache I get (sometimes): Temporarily Unavailable The resource you requested is temporarily unavailable - please try again later. (116) unable to connect, fd=4 <!-- Error receiving stdout pcgi-wrapper-version 2.0a5 --> on *some* documents. I.e. the ZopeButton in the default page will show this, but not the page itself. In the /manage screen, the left frame will be ok, but some of the right frames will show this behavior, while others won't. It seems ( I actually confirmed this) that it depends on the file size being served. I can make the left tree frame display "Temporary Unavailable" too if I open enough sub-tree elements. Here is the setup info : falcon# uname -a FreeBSD falcon.home.hentschel.net 3.4-STABLE FreeBSD 3.4-STABLE #1: Mon Apr 17 18:22:53 PDT 2000 thomas@falcon.home.hentschel.net:/usr/src/sys/compile/FALCON i386 Python 1.5.2 (#2, Jan 19 2000, 17:09:29) [GCC 2.7.2.3] on freebsd3 Zope-2.1.6 Any hints with that would be highly apreciated. Thanks -Th
Errr.. usually errors like this means that there's a misconfiguration in the Zope.cgi file somewhere. thomas@hentschel.net wrote:
Hi all,
While trying to update the zope port for the FreeBSD ports system I ran into a problem which kinda has me stumped. I looked thru the ML archives, but couldn't come up with anything, although I'm sure this has happened before.
Everything runs normal when I just connect to ZServer. Running it thru Apache I get (sometimes):
Temporarily Unavailable
The resource you requested is temporarily unavailable - please try again later.
(116) unable to connect, fd=4 <!-- Error receiving stdout pcgi-wrapper-version 2.0a5 -->
on *some* documents. I.e. the ZopeButton in the default page will show this, but not the page itself. In the /manage screen, the left frame will be ok, but some of the right frames will show this behavior, while others won't. It seems ( I actually confirmed this) that it depends on the file size being served. I can make the left tree frame display "Temporary Unavailable" too if I open enough sub-tree elements.
Here is the setup info : falcon# uname -a FreeBSD falcon.home.hentschel.net 3.4-STABLE FreeBSD 3.4-STABLE #1: Mon Apr 17 18:22:53 PDT 2000 thomas@falcon.home.hentschel.net:/usr/src/sys/compile/FALCON i386 Python 1.5.2 (#2, Jan 19 2000, 17:09:29) [GCC 2.7.2.3] on freebsd3 Zope-2.1.6
Any hints with that would be highly apreciated.
Thanks
-Th
_______________________________________________ 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 Publishers of Zope - http://www.zope.org
Well, you might be right, (attached Zope.cgi below), but no matter how hard I look at it, I can't seem to find anything odd. The funny part is if I start it manually [/usr/local/www/Zope-2.1.6/start -w '' -f '' -m '' -p /usr/local/share/apache/cgi -bin/Zope.cgi] it runs fine. Just if I have it starting it up by itself it shows that behavior. (and for some reason I seem to remember a FreeBSD <-> python oddity to that regard) Thanks for the quick reply, though ! -Th --- Zope.cgi --- #! /usr/local/share/apache/cgi-bin/pcgi-wrapper PCGI_NAME=Zope PCGI_MODULE_PATH=/usr/local/www/Zope-2.1.6/lib/python/Zope PCGI_PUBLISHER=/usr/local/www/Zope-2.1.6/pcgi/pcgi_publisher.py PCGI_EXE=/usr/local/bin/python1.5 PCGI_SOCKET_FILE=/usr/local/www/Zope-2.1.6/var/pcgi.soc PCGI_PID_FILE=/usr/local/www/Zope-2.1.6/var/pcgi.pid PCGI_ERROR_LOG=/usr/local/www/Zope-2.1.6/var/pcgi.log PCGI_DISPLAY_ERRORS=1 BOBO_REALM=/usr/local/www/Zope-2.1.6/Zope.cgi BOBO_DEBUG_MODE=1 INSTANCE_HOME=/usr/local/www/Zope-2.1.6 --- Zope.cgi --- On 7 May, Chris McDonough wrote:
Errr.. usually errors like this means that there's a misconfiguration in the Zope.cgi file somewhere.
thomas@hentschel.net wrote:
Hi all,
Everything runs normal when I just connect to ZServer. Running it thru Apache I get (sometimes):
Temporarily Unavailable
The resource you requested is temporarily unavailable - please try again later.
(116) unable to connect, fd=4 <!-- Error receiving stdout pcgi-wrapper-version 2.0a5 -->
on *some* documents. I.e. the ZopeButton in the default page will show this, but not the page itself. In the /manage screen, the left frame will be ok, but some of the right frames will show this behavior, while others won't. It seems ( I actually confirmed this) that it depends on the file size being served. I can make the left tree frame display "Temporary Unavailable" too if I open enough sub-tree elements.
thomas@hentschel.net wrote:
Well, you might be right, (attached Zope.cgi below), but no matter how hard I look at it, I can't seem to find anything odd. The funny part is if I start it manually
[/usr/local/www/Zope-2.1.6/start -w '' -f '' -m '' -p /usr/local/share/apache/cgi -bin/Zope.cgi]
it runs fine.
this is most likely a permissions problem. do you start it manually as the apache user.
Just if I have it starting it up by itself it shows that behavior. (and for some reason I seem to remember a FreeBSD <-> python oddity to that regard)
Hannu
participants (3)
-
Chris McDonough -
Hannu Krosing -
thomas＠hentschel.net