Jeff - Thanks for the help. I had fogotten about pcgifile.py. Testing with it did point out some problems: Python couldn't find cgi_module_publisher or CGIResponse. So I fixed things up till pcgifile.py said it all looked OK. Still no luck. I was getting the same error. The error log said nothing more: interuppted system call (102) Failure during connect. I was thinking maybe the user Nobody was having a problem creating the files in /tmp. It could create the err log, but nothing else. So I changed the pcgi info file to move things around and put the three files (err, pid, and socket) in a different place. No help. Same error. Then I thought, well maybe if I create the files and make them world read/writeable, that might help. It didn't of course, but it did change the error message: Interrupted system call (115) connection refused. I can import the module to be published. The pcgiinfo file checks out, I'm lost here; I know this should work, and I've not had any problems doing this on Linux. I just don't seem to have enough info to track down the problem. Thanks again for any insight, Bill -----Original Message----- From: Jeff Bauer To: Scherer, Bill Cc: 'zope@zope.org' Sent: 5/14/99 7:45 AM Subject: Re: [Zope] pcgi on Solaris 2.6 Bill, Your pcgi should work okay on Solaris 2.6 because it's my primary development system. ;-) Check your log files and possibly run pcgifile.py against Zope.cgi. For details on the sanity checker: http://starship.python.net/crew/jbauer/persistcgi/pcgifile/ Good luck. Jeff Bauer Rubicon, Inc.
I'm trying to move a pcgi application from Linux to Solaris. The app works fine under pcgi on Linux, and also works fine using ZopeHTTPServer on either Linux or Solaris. However, when I try to start it under pcgi on Solaris, I get the following relevant bits from the html source:
(102) failure during connect <!-- Interrupted system call pcgi-wrapper-version 2.0a5 -->
Any ideas, everyone?
_______________________________________________ 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 )