[Zope-dev] Zope Tests: 5 OK
Summary of messages to the zope-tests list. Period Tue May 8 12:00:00 2007 UTC to Wed May 9 12:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Tue May 8 20:55:55 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007699.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Tue May 8 20:57:26 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007700.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue May 8 20:58:57 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007701.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue May 8 21:00:28 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007702.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue May 8 21:02:00 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007703.html ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [ZWeb] wiki.zope.org is still unreachable
PS to be clear - wiki.zope.org has been running much better on the Amaze server than it did on mine. Perhaps we can get it added to the Amaze monitoring/quick-response system ? That would be awesome. ___ Zope-web maillist - Zope-web@zope.org http://mail.zope.org/mailman/listinfo/zope-web
Re: [ZWeb] wiki.zope.org is still unreachable
Simon Michael wrote: Unfortunately, wiki.zope.org has been unreachable for more than 24 hours now. What is the status now ? Regards, Baiju M ___ Zope-web maillist - Zope-web@zope.org http://mail.zope.org/mailman/listinfo/zope-web
[Zope] MailingLogger 3.0.0 Released!
Mailinglogger enables log entries to be emailed either as the entries are logged or as a summary at the end of the running process. This pair of enhanced emailing handlers for the python logging framework is now available as a standard python package and as an egg. The handlers have the following features: - customisable and dynamic subject lines for emails sent - emails sent with an X-Mailer header for easy filtering - flood protection to ensure the number of emails sent is not excessive - fully documented and tested In addition, extra support is provided for configuring the handlers when using ZConfig, Zope 2 or Zope 3. Installation is as easy as: easy_install mailinglogger For more information, please see: http://www.simplistix.co.uk/software/python/mailinglogger cheers, Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Scaling problems, or something else?
Just a quick call for ideas on this problem we have... Setup: Zope 2.7.5 (~180 sites) - apache (- varnish for 1 high profile site) Most noticeable symtoms: Takes 30 sec. or more to serve a page, or times out. Sporadic problem, but allways during general high load. Lasts less than 1 hour. Restarting zope does not help. Lots of apache processes in '..reading..' state Apache accesses and volume is down. Server load is unchanged, and 2.0 Apache processes is way up (~250 aganinst 40) Netstat established connections is WAY up (~650 aganist 50) Is this zope hitting some sort of limit and just letting Apache hang? Would setting up ZEO on the same box make a difference, or would it be better to extend varnish coverage? What would you do to pinpoint the problem? Any ideas are welcome! Regards Gaute Amundsen ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Scaling problems, or something else?
On Wed, May 09, 2007 at 12:07:54PM +0200, Gaute Amundsen wrote: Just a quick call for ideas on this problem we have... Setup: Zope 2.7.5 (~180 sites) - apache (- varnish for 1 high profile site) Most noticeable symtoms: Takes 30 sec. or more to serve a page, or times out. Sporadic problem, but allways during general high load. Lasts less than 1 hour. Restarting zope does not help. Lots of apache processes in '..reading..' state Apache accesses and volume is down. Server load is unchanged, and 2.0 Apache processes is way up (~250 aganinst 40) Netstat established connections is WAY up (~650 aganist 50) The increase in netstat connections and apache processes indicates lots of simultaneous traffic, but it's interesting that Apache accesses is down. Since hits are logged only on completion, it may be that many of the requests are hung. Is this zope hitting some sort of limit and just letting Apache hang? Would setting up ZEO on the same box make a difference, ZEO doesn't buy you any performance unless you have multiple Zope clients reading from it, and a load balancer in front. This will help IF your application is CPU-bound, which yours is not (I assume by server load you mean CPU). ZEO can actually *hurt* if you're IO-bound, because it adds network overhead to ZODB reads and writes. It's very bad if you have large Image or File objects (which you probably shouldn't have in the ZODB anyway). or would it be better to extend varnish coverage? Probably a good idea anyway... but you want to find out what the problem really is. What would you do to pinpoint the problem? I'd first try hitting Zope directly during the problem to see if the slowdown is there. If so, I'd then try either: - DeadlockDebugger may be informative. http://www.zope.org/Members/nuxeo/Products/DeadlockDebugger - Enable Zope's trace log and use requestprofiler.py to see if there is a pattern to the requests that trigger the problem. Eg. maybe all your zope worker threads are waiting on some slow IO task. See the logger section of zope.conf. -- Paul Winkler http://www.slinkp.com ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] apache rewrite quit working
I've just now been able to get back to this. netstat was listening on appropriate ports. Two things appear to be the issue here. The user for apache was the default user apache and this user does not exist on my server, I changed it to the username I made for apache to run under. Then there was a firewall issue. error log for virtual host had this: [Wed May 09 13:23:29 2007] [error] (13)Permission denied: proxy: HTTP: attempt to connect to 127.0.0.1:8086 (*) failed [Wed May 09 13:25:55 2007] [error] (13)Permission denied: proxy: HTTP: attempt to connect to 127.0.0.1:8086 (*) failed [Wed May 09 13:26:02 2007] [error] (13)Permission denied: proxy: HTTP: attempt to connect to 127.0.0.1:8086 (*) failed until allowed port 8086 on firewall and then this: [Wed May 09 13:32:50 2007] [error] [client 86.120.184.161] Directory index forbidden by Options directive: /var/www/html/ [Wed May 09 13:32:50 2007] [error] [client 86.120.184.161] Directory index forbidden by Options directive: /var/www/html/ [Wed May 09 13:33:04 2007] [error] [client 152.10.156.23] File does not exist: /var/www/html/vdb, referer: http://www.library.appstate .edu/ which is Apache serving from its own document root. I commented out the DocumentRoot setting in httpd.conf and it started working. I don't remember ever having to comment that part out. As a matter of fact I have an older linux, apache, and zope with apache rewriting to zope and serving from the file system through redirects. Any thing I have obviously missed here? Thanks for the replies, Thomas On Thursday 26 April 2007 03:18, John Snowdon wrote: What did `netstat -an` say about your listening ports? John Snowdon - IT Support Specialist -==- School of Medical Education Development Faculty of Medical Sciences Computing University of Newcastle Email : [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Bennett Sent: 25 April 2007 22:44 To: zope@zope.org Subject: Re: [Zope] apache rewrite quit working Don't think that is it because it works fine if I change Zope to port 80. And, I was accessing apache on port 80 using the ip number, localhost, the machine's real name, and the URL domain it just wouldn't rewrite to 8086. nslookup showed name was still set to my ip number. Thomas On Wednesday 25 April 2007 15:50, Jonathan wrote: - Original Message - From: Thomas Bennett [EMAIL PROTECTED] To: zope@zope.org Sent: Wednesday, April 25, 2007 4:15 PM Subject: Re: [Zope] apache rewrite quit working web-dav server is listening on 9800 http server is now listening on 80 http was listening on 8086 until rewrite quit working, explained below. Thanks anyway, Any chance your nameserver settings got changed? Jonathan -- Thomas McMillan Grant BennettAppalachian State University Computer Consultant III P O Box 32026 University Library Boone, North Carolina 28608 (828) 262 6587 If it's not as simple as possible to try it, then the barrier to entry is too high. Library Systems Help Desk: http://www.library.appstate.edu/help/ ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev ) ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev ) -- Thomas McMillan Grant Bennett Appalachian State University Computer Consultant III P O Box 32026 University Library Boone, North Carolina 28608 (828) 262 6587 If it's not as simple as possible to try it, then the barrier to entry is too high. Library Systems Help Desk: http://www.library.appstate.edu/help/ ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] apache rewrite quit working
Forget the previous reply about it working. I found I was accessing the web server with the 8086 port number on the end of the URL which did work. Thomas On Thursday 26 April 2007 03:18, John Snowdon wrote: What did `netstat -an` say about your listening ports? John Snowdon - IT Support Specialist -==- School of Medical Education Development Faculty of Medical Sciences Computing University of Newcastle Email : [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Bennett Sent: 25 April 2007 22:44 To: zope@zope.org Subject: Re: [Zope] apache rewrite quit working Don't think that is it because it works fine if I change Zope to port 80. And, I was accessing apache on port 80 using the ip number, localhost, the machine's real name, and the URL domain it just wouldn't rewrite to 8086. nslookup showed name was still set to my ip number. Thomas On Wednesday 25 April 2007 15:50, Jonathan wrote: - Original Message - From: Thomas Bennett [EMAIL PROTECTED] To: zope@zope.org Sent: Wednesday, April 25, 2007 4:15 PM Subject: Re: [Zope] apache rewrite quit working web-dav server is listening on 9800 http server is now listening on 80 http was listening on 8086 until rewrite quit working, explained below. Thanks anyway, Any chance your nameserver settings got changed? Jonathan -- Thomas McMillan Grant BennettAppalachian State University Computer Consultant III P O Box 32026 University Library Boone, North Carolina 28608 (828) 262 6587 If it's not as simple as possible to try it, then the barrier to entry is too high. Library Systems Help Desk: http://www.library.appstate.edu/help/ ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev ) ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev ) -- Thomas McMillan Grant Bennett Appalachian State University Computer Consultant III P O Box 32026 University Library Boone, North Carolina 28608 (828) 262 6587 If it's not as simple as possible to try it, then the barrier to entry is too high. Library Systems Help Desk: http://www.library.appstate.edu/help/ ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] method call pre-attribute access
I've got product where it would be very beneficial to me if I could have
a method called prior to any attribute access. For example:
thing.foo
thing.getProperty('foo')
Either of these should trigger a call to a method which could allow or
deny access to the attribute.
Any thoughts?
--
Brian Brinegar
Web Systems Developer
Engineering Computer Network
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] method call pre-attribute access
- Original Message -
From: Brian Brinegar [EMAIL PROTECTED]
To: zope@zope.org
Sent: Wednesday, May 09, 2007 4:24 PM
Subject: [Zope] method call pre-attribute access
I've got product where it would be very beneficial to me if I could have
a method called prior to any attribute access. For example:
thing.foo
thing.getProperty('foo')
Either of these should trigger a call to a method which could allow or
deny access to the attribute.
Create a new object class (subclassing some other standard object class if
you like), then create a getProperty method in the new object class which
does your security checking prior to allowing access to the attribute.
Jonathan
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: method call pre-attribute access
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian Brinegar wrote:
I've got product where it would be very beneficial to me if I could have
a method called prior to any attribute access. For example:
thing.foo
thing.getProperty('foo')
Either of these should trigger a call to a method which could allow or
deny access to the attribute.
Any thoughts?
You can define a method, '__allow_access_to_unprotected_subobjects__',
which will be called by the Zope security policy, passing the name and
value being accessed; if the method returns a true value, then access
is granted.
Tres.
- --
===
Tres Seaver +1 540-429-0999 [EMAIL PROTECTED]
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGQkFe+gerLs4ltQ4RAuTLAJ0eyG7Ww0cdXbMXv/HuxEiRmT0PfACgt2RZ
346CGPQVbWdNFfGxE/nzRAs=
=VWvU
-END PGP SIGNATURE-
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Scaling problems, or something else?
On Wednesday 09 May 2007 16:41, Paul Winkler wrote: On Wed, May 09, 2007 at 12:07:54PM +0200, Gaute Amundsen wrote: Just a quick call for ideas on this problem we have... Setup: Zope 2.7.5 (~180 sites) - apache (- varnish for 1 high profile site) Most noticeable symtoms: Takes 30 sec. or more to serve a page, or times out. Sporadic problem, but allways during general high load. Lasts less than 1 hour. Restarting zope does not help. Lots of apache processes in '..reading..' state Apache accesses and volume is down. Server load is unchanged, and 2.0 Apache processes is way up (~250 aganinst 40) Netstat established connections is WAY up (~650 aganist 50) The increase in netstat connections and apache processes indicates lots of simultaneous traffic, but it's interesting that Apache accesses is down. Since hits are logged only on completion, it may be that many of the requests are hung. That was my reasoning too. Is this zope hitting some sort of limit and just letting Apache hang? Would setting up ZEO on the same box make a difference, ZEO doesn't buy you any performance unless you have multiple Zope clients reading from it, and a load balancer in front. This will help IF your application is CPU-bound, which yours is not (I assume by server load you mean CPU). So there is no other possible limit in a zope instance than IO or CPU? If cpu was the limiting factor I would see the 2 python processes running 90% and dozens of httpd's taking up the rest? Can You think of any good parameters I can get at with a small script that would be good to graph with all the rest to shed som light on this? (we are using munin) Something out of Control_Panel/Database/main/manage_activity perhaps? Is there a way to get that data out without going through port 8080? How about something out of /proc/`cat /home/zope/sites/site1/var/Z2.pid`/XXX? Need to read up on procfs I guess. ZEO can actually *hurt* if you're IO-bound, because it adds network overhead to ZODB reads and writes. It's very bad if you have large Image or File objects (which you probably shouldn't have in the ZODB anyway). Good to hear. I ws not particularly relishing the thought of the nescesary load balancing on that single box either :-/ or would it be better to extend varnish coverage? Probably a good idea anyway... but you want to find out what the problem really is. What would you do to pinpoint the problem? I'd first try hitting Zope directly during the problem to see if the slowdown is there. If so, I'd then try either: Should be possible with lynx on localhost. Have done that before for other purpose, Should have thought of that. Maybe I wil start logging the responstime directly like that! Hm.. good idea :) - DeadlockDebugger may be informative. http://www.zope.org/Members/nuxeo/Products/DeadlockDebugger Sounds a little drastic on a production server, but it may stil come to that.. Ought to test it out on another server I guess. - Enable Zope's trace log and use requestprofiler.py to see if there is a pattern to the requests that trigger the problem. Eg. maybe all your zope worker threads are waiting on some slow IO task. See the logger section of zope.conf. That looks interesting, except that it can take 15 minutes or more to restart zope when load is at the worst. I could try it outside of peak ours I guess. Thanks for the innput. Really helped get me unstuck, as you can see :) Regards Gaute ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] How to add properties? No Add button visible
I am unable to Add properties. When I look at the Zope book, there is an Add button available, but I don't see that in my environment. For example. under the root folder, properties tab, I have a Save Changes button, but no Add or Delete buttons. Does anyone have any suggestions as to why this is the case? Zope 2.8.7 Regards Cameron ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
