Jeff Bauer wrote:
Tim Hawes wrote:
If I start ZPublisher manually within python (import ZPublisher, Main) the page works, if it is started from a connection through the web (Zope.cgi) I get the (116) unable to connect, fd=3 error. Are we getting warmer?
Tim,
Good sleuthing. The current version of pcgi attempts to launch the LRP and connect via dead reckoning. Digital Creations agrees with (even encourages) the idea that process launch should be moved out of pcgi. We have even added an out-of-band byte to the protocol to facilitate LRP <-> pcgi negotiation.
Question: When you started ZPublisher manually, did you get any spewed output to stdout/stderr?
Best regards,
Jeff Bauer Rubicon, Inc.
_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope
(For developer-specific issues, use the companion list, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )
Update on this problem: I copied the database file to another instance of Zope (same version) on the same machine. pcgi returned a corrupt database error (the other instance did not). I truncated the database to the the block with the reported problem, and I no longer get this error when pcgi is started with Zope.cgi. I recompiled the initial instance (with the latest ZPublisher module) and copied the truncated database back, and all seems well. Hmmm. . . . I am becoming more eager to see the database management stuff promised in the next release.