[Zope-dev] Zope, Apache and FastCGI
hi, I try to setup Zope-2.1.4 with apache 3.3.12 and fastcgi 2.2.4. on a redhat 6.1 system. After following the instructions in WEBserver.txt, and in: http://www.zope.org/Members/kedai/apache_zope_fcgi I still can`t connect to Zope. I get the following error in the apache error-log: [Wed Jun 14 09:52:37 2000] [notice] FastCGI: process manager initialized (pid 16174) [Wed Jun 14 09:52:37 2000] [notice] Apache/1.3.12 (Unix) mod_fastcgi/2.2.4 configured -- resuming normal operations [Wed Jun 14 09:53:00 2000] [error] [client 10.2.1.1] (111)Connection refused: FastCGI: failed to connect to server "/usr/local/apache_1.3.12/htdocs/aixzope": connect() failed I tried it with unix-domain socket and the TCP-port. Any hint is welcome. Mit freundlichen Grüßen Joachim Schmitz Email: [EMAIL PROTECTED] Telefon: +49-2464-8851 FAX: +49-2464-905163 ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Zope, Apache and FastCGI
responding to my own mail: I just found out, that it does work with the TCP-port configuration. I first tried the socket configuration, and that does not work and results in the error below. I only changed it to use the TCP-port config and it worked. Mit freundlichen Grüßen Joachim Schmitz Email: [EMAIL PROTECTED] Telefon: +49-2464-8851 FAX: +49-2464-905163 On Wed, 14 Jun 2000, Joachim Schmitz wrote: > hi, > > I try to setup Zope-2.1.4 with apache 3.3.12 and fastcgi 2.2.4. on a > redhat 6.1 system. After following the instructions in WEBserver.txt, and > in: > > http://www.zope.org/Members/kedai/apache_zope_fcgi > > I still can`t connect to Zope. I get the following error in the apache > error-log: > > [Wed Jun 14 09:52:37 2000] [notice] FastCGI: process manager initialized > (pid 16174) > [Wed Jun 14 09:52:37 2000] [notice] Apache/1.3.12 (Unix) mod_fastcgi/2.2.4 > configured -- resuming normal operations > [Wed Jun 14 09:53:00 2000] [error] [client 10.2.1.1] (111)Connection > refused: FastCGI: failed to connect to server > "/usr/local/apache_1.3.12/htdocs/aixzope": connect() failed > > I tried it with unix-domain socket and the TCP-port. Any hint is welcome. > > > Mit freundlichen Grüßen > > Joachim Schmitz > > > Email: [EMAIL PROTECTED] > Telefon: +49-2464-8851 > FAX: +49-2464-905163 > > ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope, Apache and FastCGI
Joachim Schmitz <[EMAIL PROTECTED]> wrote: > I just found out, that it does work with the TCP-port configuration. I > first tried the socket configuration, and that does not work and results > in the error below. I only changed it to use the TCP-port config and it > worked. i'd be interested in your long-time experience. i've had the problem that i got timeouts (to be reported in syslog) in the apache-fastcgi- zserver communication esp. with redhat 6.x ... that's why i had to switch back to zserver-standalone. i couldn't use fastcgi in a production system. i'd be very glad to hear from you... cheers thilo -- [EMAIL PROTECTED] E-Business Manager innominate AG networking people fon: +49-30-308806-0 fax: -77 web: http://innominate.de pgp: /pgp/tm ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Problem importing Membership alpha
I created it using the CVS version of Zope... I didn't *think* there was anything 2.2 specific going on, but apparently there is. I just took a look around. It appears that the current version of LoginManager uses the Owned module to import "UnownableOwner". I guess that's so it can create the default methods. It looks like the current LoginManager is 2.2 only then. Kevin - Original Message - From: "Bill Anderson" <[EMAIL PROTECTED]> To: "Kevin Dangoor" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, June 14, 2000 12:25 AM Subject: Problem importing Membership alpha > By any chance is this for Zope 2.2? > (Traceback didn't reveal much of anything, FWICS) > > 8<=== > Zope Error > Zope has encountered an error while publishing this resource. > Error Type: ImportError > Error Value: No module named Owned > ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Problem importing Membership alpha
In article <001301bfd606$ad3a7320$7b5addc7@laptop>, Kevin Dangoor <[EMAIL PROTECTED]> wrote: > I created it using the CVS version of Zope... I didn't *think* there was > anything 2.2 specific going on, but apparently there is. > > I just took a look around. It appears that the current version of > LoginManager uses the Owned module to import "UnownableOwner". I guess > that's so it can create the default methods. > > It looks like the current LoginManager is 2.2 only then. ?? It does: # Support Zope-2.2a1 onwership foo try: from AccessControl.Owned import UnownableOwner except ImportError: UnownableOwner=None Specifically to be compatible with both, and we're using it on 2.1.6! ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Problem importing Membership alpha
- Original Message - From: "Ty Sarna" <[EMAIL PROTECTED]> Newsgroups: zope.dev To: <[EMAIL PROTECTED]> Sent: Wednesday, June 14, 2000 1:05 PM Subject: Re: [Zope-dev] Re: Problem importing Membership alpha > In article <001301bfd606$ad3a7320$7b5addc7@laptop>, > Kevin Dangoor <[EMAIL PROTECTED]> wrote: > > I created it using the CVS version of Zope... I didn't *think* there was > > anything 2.2 specific going on, but apparently there is. > > > > I just took a look around. It appears that the current version of > > LoginManager uses the Owned module to import "UnownableOwner". I guess > > that's so it can create the default methods. > > > > It looks like the current LoginManager is 2.2 only then. > > ?? It does: > > # Support Zope-2.2a1 onwership foo > try: > from AccessControl.Owned import UnownableOwner > except ImportError: > UnownableOwner=None > > Specifically to be compatible with both, and we're using it on 2.1.6! D'oh! That's what I get for doing a grep and not looking at the context... I had looked at the .zexp file using less, and didn't see "Owned" anywhere... using vi I found a reference to AccessControl.Owned, however... So, it looks like it's the MembershipZ Product that requires 2.2. Unfortunately, I don't know that there is any way to change this, despite the fact that I'm not really using 2.2 features... I've updated the page for the Product to reflect this requirement. Kevin ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] FWIW, ZCVSMixin now at 0.1.1... and rising. ;-)
Hi Folks,
I don't know if anyone out there is actually trying to
*use* my ZCVSMixin/ZCVS Folder stuff, but if you are you certainly
want to get the latest release, ZCVSMixin-0.1.1.tgz from
the zope.org site:
http://www.zope.org/Members/sspickle/ZCVSMixin
I put some screenshots up there so you can
see what it looks like at:
http://www.zope.org/Members/sspickle
I've also found it useful for managing Python products and other
software through the web! I have had a couple of minor 'breakthrough's
that *seem* cool, but I might just be fooling myself. If an object is
not folderish I guess that it's 'simple' so I export it as XML with
the following code:
def doExport( conn, oid, file=None):
counter=0
if file is None: file=TemporaryFile()
elif type(file) is StringType: file=open(file,'w+b')
write=file.write
write('\012\012')
version=''
ref=referencesf
oids=[oid]
done_oids={}
done=done_oids.has_key
load=conn._storage.load
while oids:
oid=oids[0]
del oids[0]
if done(oid): continue
done_oids[oid]=1
try: p, serial = load(oid, version)
except: pass # Ick, a broken reference
else:
ref(p, oids)
write(conn.XMLrecord(buildOID(counter),len(p),p))
counter = counter + 1
write('\n')
return file
def buildOID( value ):
return '\000\000\000\000' + struct.pack('!l', value)
This way the XML always starts with '0' as a base oid. I experimented
a little and the xmlimport stuff doesn't seem to use the 'oid' unless
an object is 'complex' (i.e., self references etc... ). Anyway this
has the happy effect of making the xml for a simple object the same
every time it is exported so diff's make sense etc...
If objects are 'folderish' or 'complex' (and the user is permitted to
dictate this when objects are added to CVS), they are exported as
'zexp' files and cvs adds them as 'binary'. I was having trouble with
certain kinds of object's xml representation. I decided that this was
really an xml implementation problem, since I couldn't reliably export
these as xml through the normal Zope export mechanism either. Anyway..
let me know what you think if you are using this stuff!
Finally I'm aware that there are also security issues with the way
this works now. I need to look at all the things a user might need to
do and eliminate some of the 'type in' arguments that are in the
product now. These arguments wind up on 'os.system' calls, and could
be abused by a ill-meaning user (with access to the CVS Admin page!)
Any thoughts there?
thanks,
-steve
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] ZScheduler runs on Unix!
I just got a chance to try out ZScheduler 0.0.5 on Solaris 2.6 and some version of Linux -- and it works. I've changed the CHANGES.txt file to reflect that fact without incrementing the product version number. It should now be safe to try the product out on Unix development systems. It remains, however, alpha software. http://www.zope.org/Members/lstaffor/ZScheduler Let me know how it works for you. -- Thanks -- Loren ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Logging for ZScheduler?
I need some advise for designing a flexible system for logging the activities of scheduled events. One of the motivations for developing ZScheduler was to have a platform independent means for scheduling Zope tasks. The lask of a cron on Windows platforms was a part of the problem. ZScheduler achieves this independence by using Python's threading.Wait method for all time measurement. But ZScheduler also needs to be ISP independent. That is, you should have complete scheduling capabilities for your cohosted Zope applications without having to call up the ISP and ask for system configuration changes. ZScheduler partially achieves this level of independence, by eliminating the need for cron. But, as I installed ZScheduler under my personal account at CodeIt Computing, I realized that an ISP-dependence still exists, and it has nothing to do with cron -- it has to do with the configuration of the Scheduler's logging activity. When you have a Scheduler executing applications tasks on your website behind your back, you definitely want it to keep a log of what it is doing. For ZScheduler, I chose to use the STUPID_LOG_FILE feature of Zope. However, STUPID_LOG_FILE is an environment variable. Zope accounts at CodeIt (and probably at any other Zope ISP) cannot set environmet variables. And if they could, is anyone certain how STUPID_LOG_FILE would behave in their custom cohosting adaptation of Zope? So, I need a more flexible structure for the logging aspect of ZScheduler. While the ZEvent class is subclassable by users, I haven't made the Scheduler class instantiable -- there should be only one instance -- so it's not subclassable either, and therefore you can't override its logging method. Do you see the problem? Having little experience with Python and OO applications, I don't know how others solve this problem. Can you give me any pointers? Perhaps I've identified a typical application of RIPP? -- Thanks -- Loren ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Logging for ZScheduler?
On Wed, 14 Jun 2000, Loren Stafford wrote: > I need some advise for designing a flexible system for logging the > activities of scheduled events. You could just call Zope's logging system and move it out of the scope of your product. Have a look at zLOG.py or LOGGING.txt if you havn't already. Means people can extend their logging system to their hearts content with no effect on your product. > But ZScheduler also needs to be ISP independent. That is, you should have > complete scheduling capabilities for your cohosted Zope applications without > having to call up the ISP and ask for system configuration changes. > ZScheduler partially achieves this level of independence, by eliminating the > need for cron. This could be achieved with a seperate product. A product that ties into Zope's logging infrastructure and allows viewing the log files through the web. All it would have to do is append itself to the ZLogger.loggers tuple, and the interface is pretty trivial. And of course, it means that other products can use it without modification (Logger product, Zope itself etc.) and can be extended as required without having to submit patches to you for inclusion in ZScheduler. It would be a good idea if there was a field in the ZEvent that defined the subsystem used in the zLOG call. > So, I need a more flexible structure for the logging aspect of ZScheduler. > While the ZEvent class is subclassable by users, I haven't made the > Scheduler class instantiable -- there should be only one instance -- so it's > not subclassable either, and therefore you can't override its logging > method. Do you see the problem? > Having little experience with Python and OO applications, I don't know how > others solve this problem. Can you give me any pointers? Its not a problem with ZScheduler, it a problem that no one has written a plug-in logging system that is good enough for what you are trying to do. The existing zLOG API is fine (well - it could be better), but just needs someone to write the relevant modules. Hmm... I think I'll add a section to the Interfaces Wiki... -- Stuart Bishop Work: [EMAIL PROTECTED] Senior Systems Alchemist Play: [EMAIL PROTECTED] Computer Science, RMIT University ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Logging for ZScheduler?
At 01:58 PM 6/15/00 +1000, Stuart 'Zen' Bishop wrote: > >Its not a problem with ZScheduler, it a problem that no one has written >a plug-in logging system that is good enough for what you are trying to >do. The existing zLOG API is fine (well - it could be better), but just >needs someone to write the relevant modules. Hmm... I think I'll >add a section to the Interfaces Wiki... Hm... this could work well with Observer->Observable, too. Imagine firing ObservableEvents, and subscribing a "Log" object to them... ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
