Re: [Zope] ZEO troubles on RedHat EL4 Linux
Jens Vagelpohl schrieb: > On 18 Aug 2005, at 07:50, Andreas Krasa // WUW wrote: > >> Is that worth submitting a bug to RedHat? Or is ist more like a >> "feature"? ;) > > > Why would RedHat care? They will just throw it back at you and say > "sorry, Zope is not one of our supported packages". > > By the way, I hope you are not running Zope on the system-installed > Python? If you do, then change your setups to build and install your > own Python just for Zope and test again. > > jens Hi Jens, no, we've rebuilt python (2.3.5) from sources, and, as our main Zope product Silva requires this, also libxml2 and libxslt (of course with pointing to our own python). This stuff all resides in /usr/local. We've compiled Zope pointing to /usr/local/bin/python23, so I guess that RedHat's own python RPM does not interfere with Zope, at least I hope so. As I understood Dieter's mail, this strange behavior is caused by the way RedHat Enterprise Linux 4 system libraries handle SIG_IGN/SIGCHLD. If this problem was due to some improper Zope methods, most people would have this sort of problems. Which is not the case. That makes me believe that the failure of ZEO tests actually is caused by some uncommon or improper implementation of those two handles - which, in my opinion, makes it something RedHat should take a look at. Anyway - how severe are those testing failures for actually USING a ZEO client/server on that particular OS as a production system? Cheers, Andreas ___ 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] ZEO troubles on RedHat EL4 Linux
Dieter Maurer schrieb: > Andreas Krasa // WUW wrote at 2005-8-16 18:37 +0200: > >>... >>== >>ERROR: checkMultipleAddresses >>(ZEO.tests.testConnection.MappingStorageConnectionTests) >>-- >>Traceback (most recent call last): >> File >>"/usr/local/src/__zope__/Zope-2.7.7-final/lib/python/ZEO/tests/ConnectionTests.py", >>line 121, in tearDown >> os.waitpid(pid, 0) >>OSError: [Errno 10] No child processes > > > I have seen similar errors happening non deterministically > in the presence of a "SIGCHLD" handler set to "SIG_IGN". > Such a handler causes the operating system to reap away > so called zombie processes and if the zombie no longer exists, > "waitpid" will fail. > > > Some *nix variants automatically pass the "SIG_IGN" down to child processes. > Our Debian and SuSE Linux versions do. > I had to change "Zope.Startup.run" not to use "SIG_IGN" as > "SIGCHLD" handler in order to avoid such problems. > > In case, you run your tests with "zopectl test", you may > see this problem... > Hi Dieter! Thanks very much for your help! I will give this one a try! Btw. since this also happens on 5 other machines - all natively installed with RHEL4 - there actually might really be something wrong within the OS. Is that worth submitting a bug to RedHat? Or is ist more like a "feature"? ;) Thanks again, Andreas ___ 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] ZEO troubles on RedHat EL4 Linux
Tim Peters schrieb: > [Andreas Krasa] > >>We are encountering some really strange problems with Zope 2.7.7 on our >>RedHat EL 4 Linux machines. >> >>During the Zope 2.7.7 compilation works - however most of the time "make >>test" returns a random number of errors (somewhere between 20 and 30) >>ALL related to ZEO. >> >>The funny thing is, we've managed to do a "make test" without any >>failures - however after doing a "make distclean" and compiling >>everything again "make test" produces the above mentioned errors (using >>*exactly* the same source code!). >> >>I have absolutely no idea how this can happen - ANY hints are >>appreciated! Is this a known issue? > > > No. For example, it doesn't happen in the daily overnight testrunner reports. > > >>What could it be related to? > > > ZEO ? You'll have to give more info about which tests fail, and > precisely how they fail. Because many of the ZEO tests create > multiple processes, and try to assign sockets so that these processes > can communicate, they're vulnerable to vagaries of OS process > scheduling and socket use by other apps. For example, on a slow or > overburdened (with other simultaneous work) machine, some ZEO tests > can fail due to not getting enough cycles soon enough. The worst > tests of that sort wait as long as a minute now for another process to > "do something" they're waiting for before failing, but not even > waiting a minute can _guarantee_ success. > > Might be informative to run the tests on an otherwise-quiet machine. Thank you Tim for the feedback! Our system is a Intel Xeon 3 GHz Dual-CPU with 2.5 GB RAM running RedHat Enterprise Linux 4 (SElinux disabled). As this is a test-machine it doesn't run any CPU-consuming tasks I can think of - the server load is usually somewhere between 0.00 and 0.10. But I'll check that nevertheless! Best regards Andreas ___ 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] ZEO troubles on RedHat EL4 Linux
Jens Vagelpohl schrieb: >> During the Zope 2.7.7 compilation works - however most of the time "make >> test" returns a random number of errors (somewhere between 20 and 30) >> ALL related to ZEO. > > > Maybe someone can help if you actually *tell us* what these errors are. > At least my own crystal ball is in the shop for repairs right now... :) > > jens > Hi! Oops, almost forgot about those - the errors are as follows. They are always related to ZEO and an OSError "No child processes". Thanks & best regards, Andreas Krasa --- == ERROR: checkMultipleAddresses (ZEO.tests.testConnection.MappingStorageConnectionTests) -- Traceback (most recent call last): File "/usr/local/src/__zope__/Zope-2.7.7-final/lib/python/ZEO/tests/ConnectionTests.py", line 121, in tearDown os.waitpid(pid, 0) OSError: [Errno 10] No child processes == ERROR: checkMultipleServers (ZEO.tests.testConnection.MappingStorageConnectionTests) -- Traceback (most recent call last): File "/usr/local/src/__zope__/Zope-2.7.7-final/lib/python/ZEO/tests/ConnectionTests.py", line 121, in tearDown os.waitpid(pid, 0) OSError: [Errno 10] No child processes == ERROR: checkReadOnlyClient (ZEO.tests.testConnection.MappingStorageConnectionTests) -- Traceback (most recent call last): File "/usr/local/src/__zope__/Zope-2.7.7-final/lib/python/ZEO/tests/ConnectionTests.py", line 121, in tearDown os.waitpid(pid, 0) OSError: [Errno 10] No child processes == ERROR: checkReadOnlyFallbackReadOnlyServer (ZEO.tests.testConnection.MappingStorageConnectionTests) -- Traceback (most recent call last): File "/usr/local/src/__zope__/Zope-2.7.7-final/lib/python/ZEO/tests/ConnectionTests.py", line 121, in tearDown os.waitpid(pid, 0) OSError: [Errno 10] No child processes == ERROR: checkReadOnlyFallbackWritable (ZEO.tests.testConnection.MappingStorageConnectionTests) -- Traceback (most recent call last): File "/usr/local/src/__zope__/Zope-2.7.7-final/lib/python/ZEO/tests/ConnectionTests.py", line 121, in tearDown os.waitpid(pid, 0) OSError: [Errno 10] No child processes == ERROR: checkReconnectWritable (ZEO.tests.testConnection.MappingStorageConnectionTests) -- Traceback (most recent call last): File "/usr/local/src/__zope__/Zope-2.7.7-final/lib/python/ZEO/tests/ConnectionTests.py", line 121, in tearDown os.waitpid(pid, 0) OSError: [Errno 10] No child processes == ERROR: checkReconnection (ZEO.tests.testConnection.MappingStorageConnectionTests) -- Traceback (most recent call last): File "/usr/local/src/__zope__/Zope-2.7.7-final/lib/python/ZEO/tests/ConnectionTests.py", line 121, in tearDown os.waitpid(pid, 0) OSError: [Errno 10] No child processes == ERROR: checkTimeout (ZEO.tests.testConnection.MappingStorageTimeoutTests) -- Traceback (most recent call last): File "/usr/local/src/__zope__/Zope-2.7.7-final/lib/python/ZEO/tests/ConnectionTests.py", line 121, in tearDown os.waitpid(pid, 0) OSError: [Errno 10] No child processes == ERROR: checkTimeoutAfterVote (ZEO.tests.testConnection.MappingStorageTimeoutTests) -- Traceback (most recent call last): File "/usr/local/src/__zope__/Zope-2.7.7-final/lib/python/ZEO/tests/ConnectionTests.py", line 121, in tearDown os.waitpid(pid, 0) OSError: [Errno 10] No child processes == ERROR: checkTimeoutOnAbortNoLock (ZEO.tests.testConnection.MappingStorageTimeoutTests) -- Traceback (most recent call last): File "/usr/local/src/__zope__/Zope-2.7.7-final/lib/python/ZEO/tests/ConnectionTests.py", line 121, in tearDown os.waitpid(pid, 0) OSError: [Errno 10] No child processes =
