Stopping PCGI publisher from starting
Sorry if this is all easily understood by studying the source code -- and I'm sure it is -- but please help me out anyway. If ZServer is running, it seems the PCGI wrapper -- or mod_pcgi? -- is able to connect directly to ZServer, without the need of pcgi-wrapper/pcgi_publisher.py. This is fine, and it is our current scenario, which works great. Unfortunately, if ZServer is _not_ up and running, the PCGI wrapper will kick in and start serving stuff itself. This is annoying when doing maintenance that involves stopping ZServer. Is fixing this as trivial as commenting out stuff from Zope.cgi? The main reason for my trouble is that occasionally I find the Zope OFS is behaving oddly -- SQL connections suddenly being closed and refusing to open, for example -- and in these cases I often find pcgi-wrapper running. This happened again just five minutes ago, and the process list looked like this: [...] 16947 ? S 0:00 /usr/local/apache/bin/httpd 16968 ? S 0:00 /usr/local/apache/bin/httpd 17111 ? S 0:00 /usr/local/apache/bin/httpd 17128 ? S 0:00 /usr/local/apache/bin/httpd 17153 ? S 0:00 /usr/local/apache/bin/httpd 17274 ? S 0:00 /usr/local/apache/bin/httpd 17275 ? S 0:00 /usr/local/apache/bin/httpd 17276 ? S 0:00 /usr/local/apache/bin/httpd 17278 ? S 0:00 /usr/local/apache/bin/httpd 17322 ? S 0:00 /usr/local/apache/bin/httpd 17327 ? S 0:00 /usr/local/apache/bin/httpd 17328 ? S 0:00 /usr/local/apache/bin/httpd 17375 ? S 0:00 /usr/local/apache/bin/httpd 17383 ? S 0:00 /usr/local/apache/bin/httpd 17415 ? S 0:00 pcgi-wrapper /usr/local/apache/cgi-bin/Zope.cgi 17416 ? S 0:00 pcgi-wrapper /usr/local/apache/cgi-bin/Zope.cgi 17417 ? S 0:00 pcgi-wrapper /usr/local/apache/cgi-bin/Zope.cgi 17418 ? S 0:00 pcgi-wrapper /usr/local/apache/cgi-bin/Zope.cgi 17419 ? S 0:00 pcgi-wrapper /usr/local/apache/cgi-bin/Zope.cgi 17420 ? Z 0:00 (Zope.cgi <zombie>) 17425 ? S 0:00 pcgi-wrapper /usr/local/apache/cgi-bin/Zope.cgi 17431 ? S 0:00 pcgi-wrapper /usr/local/apache/cgi-bin/Zope.cgi 17434 ? S 0:00 pcgi-wrapper /usr/local/apache/cgi-bin/Zope.cgi 17435 ? S 0:00 /usr/local/apache/bin/httpd 31764 ? S 0:00 ftpd: firewall.mop.no: zope: STOR 1c.gif 17414 ? S N 0:06 /usr/local/bin/python /usr/src/Zope-2.0.0b5-src/z2.py -p /usr/local/apache/cgi-bin/Zope.cgi -t1 - 17440 ? S N 0:00 /usr/local/bin/python /usr/src/Zope-2.0.0b5-src/z2.py -p /usr/local/apache/cgi-bin/Zope.cgi -t1 - 17441 ? S N 0:00 /usr/local/bin/python /usr/src/Zope-2.0.0b5-src/z2.py -p /usr/local/apache/cgi-bin/Zope.cgi -t1 - Should this ever happen? -- Alexander Staubo http://www.mop.no/~alex/ "`Ford, you're turning into a penguin. Stop it.'" --Douglas Adams, _The Hitchhiker's Guide to the Galaxy_
At 20:00 6-9-99 , Alexander Staubo wrote:
Sorry if this is all easily understood by studying the source code -- and I'm sure it is -- but please help me out anyway.
If ZServer is running, it seems the PCGI wrapper -- or mod_pcgi? -- is able to connect directly to ZServer, without the need of pcgi-wrapper/pcgi_publisher.py. This is fine, and it is our current scenario, which works great.
Unfortunately, if ZServer is _not_ up and running, the PCGI wrapper will kick in and start serving stuff itself. This is annoying when doing maintenance that involves stopping ZServer.
Is fixing this as trivial as commenting out stuff from Zope.cgi?
Yup, just take out PCGI_MODULE_PATH. -- 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 ---------------------------------------------
participants (2)
-
Alexander Staubo -
Martijn Pieters