[Zope-Checkins] SVN: Zope/branches/2.12/ Prepare Zope2 2.12.10.
Log message for revision 114862: Prepare Zope2 2.12.10. Changed: U Zope/branches/2.12/doc/CHANGES.rst U Zope/branches/2.12/setup.py U Zope/branches/2.12/versions.cfg -=- Modified: Zope/branches/2.12/doc/CHANGES.rst === --- Zope/branches/2.12/doc/CHANGES.rst 2010-07-20 07:06:50 UTC (rev 114861) +++ Zope/branches/2.12/doc/CHANGES.rst 2010-07-20 09:28:44 UTC (rev 114862) @@ -5,7 +5,7 @@ Change information for previous versions of Zope can be found at http://docs.zope.org/zope2/releases/. -2.12.10 (unreleased) +2.12.10 (2010-07-20) Bugs Fixed Modified: Zope/branches/2.12/setup.py === --- Zope/branches/2.12/setup.py 2010-07-20 07:06:50 UTC (rev 114861) +++ Zope/branches/2.12/setup.py 2010-07-20 09:28:44 UTC (rev 114862) @@ -16,7 +16,7 @@ from setuptools import setup, find_packages, Extension setup(name='Zope2', -version='2.12.10dev', +version='2.12.10', url='http://www.zope.org', license='ZPL 2.1', description='Zope2 application server / web framework', Modified: Zope/branches/2.12/versions.cfg === --- Zope/branches/2.12/versions.cfg 2010-07-20 07:06:50 UTC (rev 114861) +++ Zope/branches/2.12/versions.cfg 2010-07-20 09:28:44 UTC (rev 114862) @@ -2,7 +2,7 @@ versions = versions [versions] -Zope2 = +Zope2 = 2.12.10 Acquisition = 2.13.3 buildout.dumppickedversions = 0.4 ClientForm = 0.2.10 ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/2.12/ Bump version
Log message for revision 114864: Bump version Changed: U Zope/branches/2.12/doc/CHANGES.rst U Zope/branches/2.12/setup.py U Zope/branches/2.12/versions.cfg -=- Modified: Zope/branches/2.12/doc/CHANGES.rst === --- Zope/branches/2.12/doc/CHANGES.rst 2010-07-20 09:28:57 UTC (rev 114863) +++ Zope/branches/2.12/doc/CHANGES.rst 2010-07-20 09:29:52 UTC (rev 114864) @@ -5,6 +5,13 @@ Change information for previous versions of Zope can be found at http://docs.zope.org/zope2/releases/. +2.12.11 (unreleased) + + +Bugs Fixed +++ + + 2.12.10 (2010-07-20) Modified: Zope/branches/2.12/setup.py === --- Zope/branches/2.12/setup.py 2010-07-20 09:28:57 UTC (rev 114863) +++ Zope/branches/2.12/setup.py 2010-07-20 09:29:52 UTC (rev 114864) @@ -16,7 +16,7 @@ from setuptools import setup, find_packages, Extension setup(name='Zope2', -version='2.12.10', +version='2.12.11dev', url='http://www.zope.org', license='ZPL 2.1', description='Zope2 application server / web framework', Modified: Zope/branches/2.12/versions.cfg === --- Zope/branches/2.12/versions.cfg 2010-07-20 09:28:57 UTC (rev 114863) +++ Zope/branches/2.12/versions.cfg 2010-07-20 09:29:52 UTC (rev 114864) @@ -2,7 +2,7 @@ versions = versions [versions] -Zope2 = 2.12.10 +Zope2 = Acquisition = 2.13.3 buildout.dumppickedversions = 0.4 ClientForm = 0.2.10 ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-dev] Zope Tests: 40 OK, 13 Failed, 1 Unknown
Summary of messages to the zope-tests list. Period Mon Jul 19 12:00:00 2010 UTC to Tue Jul 20 12:00:00 2010 UTC. There were 54 messages: 6 from Zope Tests, 1 from buildbot at enfoldsystems.com, 4 from buildbot at pov.lt, 17 from buildbot at winbot.zope.org, 13 from ccomb at free.fr, 13 from jdriessen at thehealthagency.com. Test failures - Subject: FAILED : Bluebream / Python2.4.6 32bit linux From: ccomb at free.fr Date: Mon Jul 19 22:04:08 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016989.html Subject: FAILED : Bluebream / Python2.6.4 32bit linux From: ccomb at free.fr Date: Mon Jul 19 22:05:50 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016990.html Subject: FAILED : Bluebream / Python2.5.2 32bit linux From: ccomb at free.fr Date: Mon Jul 19 22:05:51 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016991.html Subject: FAILED : winbot / ztk_dev py_270_win32 From: buildbot at winbot.zope.org Date: Mon Jul 19 22:58:23 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016998.html Subject: FAILED : winbot / ztk_dev py_270_win64 From: buildbot at winbot.zope.org Date: Mon Jul 19 23:10:44 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016999.html Subject: FAILED : winbot / ztk_10 py_244_win32 From: buildbot at winbot.zope.org Date: Mon Jul 19 23:19:26 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017000.html Subject: FAILED : winbot / ztk_10 py_270_win32 From: buildbot at winbot.zope.org Date: Mon Jul 19 23:47:40 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017004.html Subject: FAILED : winbot / ztk_10 py_270_win64 From: buildbot at winbot.zope.org Date: Mon Jul 19 23:54:22 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017005.html Subject: FAILED : ZTK 1.0dev / Python2.7.0 Linux 32bit From: ccomb at free.fr Date: Tue Jul 20 00:18:04 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017007.html Subject: FAILED : ZTK 1.0 / Python2.7.0 Linux 32bit From: ccomb at free.fr Date: Tue Jul 20 01:53:33 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017015.html Subject: FAILED : winbot / ZODB_dev py_270_win32 From: buildbot at winbot.zope.org Date: Tue Jul 20 03:41:56 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017019.html Subject: FAILED : winbot / ZODB_dev py_270_win64 From: buildbot at winbot.zope.org Date: Tue Jul 20 04:37:26 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017021.html Subject: FAILED : Zope Buildbot / ztk_win slave-win From: jdriessen at thehealthagency.com Date: Tue Jul 20 07:16:23 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017025.html Unknown --- Subject: [zodb-tests] buildbot failure in Enfold Systems on zodb-trunk-python-2.6-maestro From: buildbot at enfoldsystems.com Date: Tue Jul 20 04:15:56 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017020.html Tests passed OK --- Subject: OK : Zope 3.4 Known Good Set / py2.4-64bit-linux From: buildbot at pov.lt Date: Mon Jul 19 21:09:06 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016981.html Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Mon Jul 19 21:35:11 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016982.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon Jul 19 21:37:14 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016983.html Subject: OK : Zope-2.12 Python-2.6.5 : Linux From: Zope Tests Date: Mon Jul 19 21:39:14 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016984.html Subject: OK : Zope-2.12-alltests Python-2.6.5 : Linux From: Zope Tests Date: Mon Jul 19 21:41:14 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016985.html Subject: OK : Zope-trunk Python-2.6.5 : Linux From: Zope Tests Date: Mon Jul 19 21:43:14 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016986.html Subject: OK : Zope-trunk-alltests Python-2.6.5 : Linux From: Zope Tests Date: Mon Jul 19 21:45:14 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016987.html Subject: OK : Zope 3.4 Known Good Set / py2.4-32bit-linux From: buildbot at pov.lt Date: Mon Jul 19 21:54:34 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016988.html Subject: OK : Zope 3.4 Known Good Set / py2.5-64bit-linux From: buildbot at pov.lt Date: Mon Jul 19 22:09:22 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016992.html Subject: OK : winbot / ztk_dev py_244_win32 From: buildbot at winbot.zope.org Date: Mon Jul 19 22:13:27 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016993.html Subject: OK : winbot / ztk_dev py_254_win32 From: buildbot at winbot.zope.org Date: Mon Jul 19 22:25:05 EDT 2010 URL:
[Zope-dev] Doodle for August bug day
Hi everyone, here's the Doodle for our next bug day: http://www.doodle.com/6gydequztpac3xud I'd like to see many people there, so if you have any questions that need answering before you can join us on the bug day: ask them! Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Help review #181754
Hi, I just rejected issue https://bugs.edge.launchpad.net/zope.app.testing/+bug/181754 There might be room for different oppinions and if anyone would like to veto the decision, I'd welcome a discussion. Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Help review #181754
On 2010-7-20 17:39, Christian Theune wrote: Hi, I just rejected issue https://bugs.edge.launchpad.net/zope.app.testing/+bug/181754 There might be room for different oppinions and if anyone would like to veto the decision, I'd welcome a discussion. Your rejection contains an assumption that the request won't make it to the application. Is that assumption testable? Wichert. -- Wichert Akkerman wich...@wiggy.net It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Help review #181754
On 07/20/2010 06:01 PM, Wichert Akkerman wrote: On 2010-7-20 17:39, Christian Theune wrote: Hi, I just rejected issue https://bugs.edge.launchpad.net/zope.app.testing/+bug/181754 There might be room for different oppinions and if anyone would like to veto the decision, I'd welcome a discussion. Your rejection contains an assumption that the request won't make it to the application. Is that assumption testable? I guess so. I think it's relatively clear that the application server should insulate the application from malignant requests. The details probably depend on the HTTP implementation. zope.server, zope.app.twisted, Paster and others might deal with this differently. Looking at the interfaces between those parts of the application it makes no sense to have syntactially invalid requests end up on the application level. At least, WRT this bug, I don't think it's a good idea to ask explicitly for bad requests to go to the application as the test layer should model real server behaviour as closely as possible. And again it wouldn't make sense anyway as you can't pass an unparsable request to the application. Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope.testing / zope.testrunner path forward:
I'd like to put down some effort this week during the EuroPython sprint to go forward with zope.testing for Python 3. zope.testing 3.9.5 is already deprecating zope.testing.testrunner, but I need to remove it so that I can port zope.testing to Python 3 without going mad. (zope.testrunner runs on Python 3 already, although installing it fails, because it tries to install zope.testing 3.9.5.) The questions are (some have been discussed before, but I don't remember the outcome): 1. Should there be BBB imports of zope.testrunner into zope.testing? We can do that to get a longer deprecation period, a couple of months isn't very long). 2. Should I release the testrunner-free version before I port to Python 3, or should we do both at once?Doing both at once of course risks more problems than one at a time. On the other hand we might want all changes at once to lessen annoyance. 3. It should be zope.testing 4.0.0, right? -- Lennart Regebro: http://regebro.wordpress.com/ Python 3 Porting: http://python3porting.com/ +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ./bin/test failing with trunk zope.testing
On Sun, Jul 18, 2010 at 16:58, Jonathan Lange j...@mumak.net wrote: Actually, it turned out to be something of a pebkac. Happy to hear it, zope.testrunner and zope.testing.testrunner *should* be compatible, and if they aren't that is probably a bug. -- Lennart Regebro: http://regebro.wordpress.com/ Python 3 Porting: http://python3porting.com/ +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Help review #181754
On 2010-7-20 18:15, Christian Theune wrote: At least, WRT this bug, I don't think it's a good idea to ask explicitly for bad requests to go to the application as the test layer should model real server behaviour as closely as possible. And again it wouldn't make sense anyway as you can't pass an unparsable request to the application. I'm not sure I agree. Like everything else servers have bugs, so it can't hurt to test how your application would behave given certain server bugs. Wichert. -- Wichert Akkerman wich...@wiggy.net It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.testing / zope.testrunner path forward:
On Tue, Jul 20, 2010 at 23:57, Marius Gedminas mar...@gedmin.as wrote: I'm for two separate releases. Release early, release often. Oh, that's not a problem. svn://svn.zope.org/repos/main/zope.testing/branches/regebro-400 Is testrunner free and runs on Python 3 already. It's purely a question of if we want both changes at once or not. :-) -- Lennart Regebro, Colliberty: http://www.colliberty.com/ Python, Zope, Plone blog: http://regebro.wordpress.com/ Telephone: +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Help review #181754
On 07/20/2010 07:28 PM, Wichert Akkerman wrote: On 2010-7-20 18:15, Christian Theune wrote: At least, WRT this bug, I don't think it's a good idea to ask explicitly for bad requests to go to the application as the test layer should model real server behaviour as closely as possible. And again it wouldn't make sense anyway as you can't pass an unparsable request to the application. I'm not sure I agree. Like everything else servers have bugs, so it can't hurt to test how your application would behave given certain server bugs. Right. IMHO this specific bug asked for would usually mean that the server breaks and can pass anything to the application. Whatever happens: the server needs to prepare a data structure to hand over to the application. If it can't do that, then there's nothing to test what happens with the application. I guess this kind of test (what happens with the application if it receives invalid data) needs to work around server/publisher components and inject data directly to application methods. Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.testing / zope.testrunner path forward:
On 07/21/2010 06:40 AM, Lennart Regebro wrote: On Tue, Jul 20, 2010 at 23:57, Marius Gedminasmar...@gedmin.as wrote: I'm for two separate releases. Release early, release often. Oh, that's not a problem. svn://svn.zope.org/repos/main/zope.testing/branches/regebro-400 Is testrunner free and runs on Python 3 already. It's purely a question of if we want both changes at once or not. :-) I myself prefer having more releases. I like Marius' idea: 3.10 would be good for removing the test runner then 4.0 can be Py3 compatibility. Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Help review #181754
* Wichert Akkerman wich...@wiggy.net [2010-07-20 19:28]: On 2010-7-20 18:15, Christian Theune wrote: At least, WRT this bug, I don't think it's a good idea to ask explicitly for bad requests to go to the application as the test layer should model real server behaviour as closely as possible. And again it wouldn't make sense anyway as you can't pass an unparsable request to the application. I'm not sure I agree. Like everything else servers have bugs, so it can't hurt to test how your application would behave given certain server bugs. I don't think it is usually a productive assumption that lower layers fail to uphold their end of the contract. Maybe an extrapolation/hyperbole illustrates my opinion: Cosmic rays might also flip bits in your computer's RAM or disk, but I don't think it's worthwile to test how your application reacts when the python interpreter (or whoever, really) presents it with mangled data structures or objects or whatnot. To put it differently, yes, servers have bugs, but the place to fix them is in the server. If we can't rely on our layers/abstractions to hold, I feel we lose most if not all benefits of having them in the first place. Wolfgang ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope] zope timeouts
Hello I'm running an old version of Zope which is required by our corporate design using also an older version of the CMS Silva: Linux Distribution: Red Hat Enterprise Linux Server release 5.5 Linux Kernel: 2.6.18-194.8.1.el5PAE Zope: 2.8.9.1 Python: 2.3.6 (with several modules, like: ldap, pil, mysql, pyxml, ...) Silva: 1.5.13 My problem ist that my zope server hat timeouts on displaying pages after a while that it has been started (currently this while is approx. 15 minutes). The only thing that helps is restarting zope. By accident I discovered about two month ago, that running an strace -f on the zope process, reactivated it... so I could live with this hack until yesterday. Now I'm running strace permanently (with all the disadvantages) and zope works fine for about 1 to 1.5 hours. Here is a short recurring output of strace: [pid 13408] ... futex resumed ) = 0 [pid 13406] futex(0xbcc12c0, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ... [pid 13405] futex(0xbcc12c0, FUTEX_WAKE_PRIVATE, 1 unfinished ... [pid 13408] futex(0xbcc12c0, FUTEX_WAKE_PRIVATE, 1 unfinished ... [pid 13407] ... futex resumed ) = 0 [pid 13405] ... futex resumed ) = 1 [pid 13408] ... futex resumed ) = 1 [pid 13405] futex(0xbcc12c0, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ... [pid 13408] futex(0xbcc12c0, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ... [pid 13406] ... futex resumed ) = 0 [pid 13406] futex(0xbcc12c0, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ... [pid 13407] futex(0xbcc12c0, FUTEX_WAKE_PRIVATE, 1) = 1 [pid 13405] ... futex resumed ) = 0 [pid 13407] futex(0xbcc12c0, FUTEX_WAKE_PRIVATE, 1 unfinished ... [pid 13405] futex(0xbcc12c0, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ... [pid 13408] ... futex resumed ) = 0 [pid 13407] ... futex resumed ) = 1 [pid 13407] futex(0xbcc12c0, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ... [pid 13405] ... futex resumed ) = -1 EAGAIN (Resource temporarily unavailable) I need definitively help... Any idea? Thx, Michele -- ETH Zürich Michele Marcionelli IT Support Gruppe D-MATH HG G 32.1 Rämistrasse 101 CH–8092 Zürich michele.marcione...@math.ethz.ch http://www.math.ethz.ch/~michele +41 44 632 6193 Telefon +41 44 632 1354 Fax ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] zope timeouts
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Michele, I would consider the coincience with strace reviving the process a red herring. When strace runs it does not influence the process you are watching with it, except for telling you what OS-level calls are made. The most common reason for such timeouts are problems with software that tries to use other network resources during the running request to talk to services like RDBMS systems, LDAP, etc. If these background connections hang for some reason you'll end up with a hanging Zope thread. Enough of them and Zope itself appears to hang. When your process hangs you should be able to attach to it using gdb and printing a stack trace for each thread. That may give you a big clue where the problem is. jens On 7/20/10 13:53 , Michele Marcionelli wrote: Hello I'm running an old version of Zope which is required by our corporate design using also an older version of the CMS Silva: Linux Distribution: Red Hat Enterprise Linux Server release 5.5 Linux Kernel: 2.6.18-194.8.1.el5PAE Zope: 2.8.9.1 Python: 2.3.6 (with several modules, like: ldap, pil, mysql, pyxml, ...) Silva: 1.5.13 My problem ist that my zope server hat timeouts on displaying pages after a while that it has been started (currently this while is approx. 15 minutes). The only thing that helps is restarting zope. By accident I discovered about two month ago, that running an strace -f on the zope process, reactivated it... so I could live with this hack until yesterday. Now I'm running strace permanently (with all the disadvantages) and zope works fine for about 1 to 1.5 hours. Here is a short recurring output of strace: [pid 13408] ... futex resumed ) = 0 [pid 13406] futex(0xbcc12c0, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ... [pid 13405] futex(0xbcc12c0, FUTEX_WAKE_PRIVATE, 1 unfinished ... [pid 13408] futex(0xbcc12c0, FUTEX_WAKE_PRIVATE, 1 unfinished ... [pid 13407] ... futex resumed ) = 0 [pid 13405] ... futex resumed ) = 1 [pid 13408] ... futex resumed ) = 1 [pid 13405] futex(0xbcc12c0, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ... [pid 13408] futex(0xbcc12c0, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ... [pid 13406] ... futex resumed ) = 0 [pid 13406] futex(0xbcc12c0, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ... [pid 13407] futex(0xbcc12c0, FUTEX_WAKE_PRIVATE, 1) = 1 [pid 13405] ... futex resumed ) = 0 [pid 13407] futex(0xbcc12c0, FUTEX_WAKE_PRIVATE, 1 unfinished ... [pid 13405] futex(0xbcc12c0, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ... [pid 13408] ... futex resumed ) = 0 [pid 13407] ... futex resumed ) = 1 [pid 13407] futex(0xbcc12c0, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ... [pid 13405] ... futex resumed ) = -1 EAGAIN (Resource temporarily unavailable) I need definitively help... Any idea? Thx, Michele -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxFnHQACgkQRAx5nvEhZLIZTgCfdU00UhqXAwXxsXxypv+wSsPR VSEAn3UXIACBeAuClfi23jo/+MSWDdJB =Cvv7 -END PGP SIGNATURE- ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Disabling Server Signature for Zope
Is there a way I can disable ServerSignature in Zope. ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Disabling Server Signature for Zope
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tapas Mishra wrote: Is there a way I can disable ServerSignature in Zope. Monkey-patching is your friend: from ZServer import zhttp_server http_server.SERVER_IDENT = 'Who wants to know that?'$ - -aj - -- ZOPYX Limited | zopyx group Charlottenstr. 37/1 | The full-service network for Zope Plone D-72070 Tübingen| Produce Publish www.zopyx.com | www.produce-and-publish.com - E-Publishing, Python, Zope Plone development, Consulting -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxFvTcACgkQCJIWIbr9KYwK2wCfUJ7/HDPz5VnwNNb5wtJNE0Ey EpcAn3m4aKB6goAaEZksrWfnMVktlfLL =xc9v -END PGP SIGNATURE- attachment: lists.vcf___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] zope timeouts
Hm, just some quick ideas -- thread 3 is busy doing a stat64() , should usually done quickly. And thread 4 is doing some kind of string operation (comparison), which also shouldn't take long except if you have a huge dataset. Is this backtrace repeatable, ie. does it hang in the same syscalls? Are you maybe running on NFS or something like that? hth, peter. On Tue, 2010-07-20 at 17:00 +0200, Michele Marcionelli wrote: Ciao Jens thank you for your answer. Now since I'm new with gdb I have some questions. I did following. I created a file called gdb_batch with following content: info threads thread 1 bt thread 2 bt thread 3 bt thread 4 bt thread 5 bt and run the gdb command like this gdb python $(cat Z2.pid) --batch -x gdb_batch gdb_bt.log 21 Can you maybe help me to decode the output (see attachment)? For instance: what does this mean? (gdb) info threads 5 Thread 0xb712bb90 (LWP 7532) 0x005fd410 in __kernel_vsyscall () 4 Thread 0xb672ab90 (LWP 7533) lookdict_string (mp=0xb78c4714, key=0xb7c19db8, hash=1293002269) at Objects/dictobject.c:331 3 Thread 0xb5d29b90 (LWP 7534) 0x005fd410 in __kernel_vsyscall () 2 Thread 0xb5328b90 (LWP 7535) 0x005fd410 in __kernel_vsyscall () * 1 Thread 0xb7fc16c0 (LWP 7174) 0x005fd410 in __kernel_vsyscall () What does mean the *? And what is the difference between the threads 1,2,3,5 (with the __kernel_vsyscall) and the 4? What should I look for? Thank you, Michele On Jul 20, 2010, at 14:54 , Jens Vagelpohl wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Michele, I would consider the coincience with strace reviving the process a red herring. When strace runs it does not influence the process you are watching with it, except for telling you what OS-level calls are made. The most common reason for such timeouts are problems with software that tries to use other network resources during the running request to talk to services like RDBMS systems, LDAP, etc. If these background connections hang for some reason you'll end up with a hanging Zope thread. Enough of them and Zope itself appears to hang. When your process hangs you should be able to attach to it using gdb and printing a stack trace for each thread. That may give you a big clue where the problem is. jens On 7/20/10 13:53 , Michele Marcionelli wrote: Hello I'm running an old version of Zope which is required by our corporate design using also an older version of the CMS Silva: Linux Distribution: Red Hat Enterprise Linux Server release 5.5 Linux Kernel: 2.6.18-194.8.1.el5PAE Zope: 2.8.9.1 Python: 2.3.6 (with several modules, like: ldap, pil, mysql, pyxml, ...) Silva: 1.5.13 My problem ist that my zope server hat timeouts on displaying pages after a while that it has been started (currently this while is approx. 15 minutes). The only thing that helps is restarting zope. By accident I discovered about two month ago, that running an strace -f on the zope process, reactivated it... so I could live with this hack until yesterday. Now I'm running strace permanently (with all the disadvantages) and zope works fine for about 1 to 1.5 hours. Here is a short recurring output of strace: [pid 13408] ... futex resumed ) = 0 [pid 13406] futex(0xbcc12c0, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ... [pid 13405] futex(0xbcc12c0, FUTEX_WAKE_PRIVATE, 1 unfinished ... [pid 13408] futex(0xbcc12c0, FUTEX_WAKE_PRIVATE, 1 unfinished ... [pid 13407] ... futex resumed ) = 0 [pid 13405] ... futex resumed ) = 1 [pid 13408] ... futex resumed ) = 1 [pid 13405] futex(0xbcc12c0, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ... [pid 13408] futex(0xbcc12c0, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ... [pid 13406] ... futex resumed ) = 0 [pid 13406] futex(0xbcc12c0, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ... [pid 13407] futex(0xbcc12c0, FUTEX_WAKE_PRIVATE, 1) = 1 [pid 13405] ... futex resumed ) = 0 [pid 13407] futex(0xbcc12c0, FUTEX_WAKE_PRIVATE, 1 unfinished ... [pid 13405] futex(0xbcc12c0, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ... [pid 13408] ... futex resumed ) = 0 [pid 13407] ... futex resumed ) = 1 [pid 13407] futex(0xbcc12c0, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ... [pid 13405] ... futex resumed ) = -1 EAGAIN (Resource temporarily unavailable) I need definitively help... Any idea? Thx, Michele ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev ) signature.asc Description: This is a digitally signed message part
