Hide Forgot
+++ This bug was initially created as a clone of Bug #716458 +++ Description of problem: This issue was discovered during testing of BZ682815, please see Bug 682815 for more details. A timeout exception on the Broker can be seen while running the issue reproducer. cluster_tests.LongTests.test_management ................................. fail Error during test: Traceback (most recent call last): File "./qpid-python-test", line 311, in run phase() File "/root/pematous/bz682815/run_cluster_tests2/cluster_tests.py", line 830, in test_management cluster.start() File "/root/pematous/bz682815/run_cluster_tests2/brokertest.py", line 458, in start self._brokers.append(self.test.broker(self.args+args, name, expect, wait, port=port)) File "/root/pematous/bz682815/run_cluster_tests2/brokertest.py", line 525, in broker raise RethrownException("Failed to start broker %s(%s): %s" % (b.name, b.log, e)) RethrownException: Failed to start broker cluster0-7(cluster0-7.log): Timed out waiting for broker cluster0-7: 2011-06-11 13:04:39 notice Cluster store state: empty 2011-06-11 13:04:39 notice cluster(10.34.45.2:9210 PRE_INIT) configuration change: 10.34.45.2:7122 10.34.45.2:7388 10.34.45.2:9210 2011-06-11 13:04:39 notice cluster(10.34.45.2:9210 PRE_INIT) Members joined: 10.34.45.2:9210 2011-06-11 13:04:39 debug cluster(10.34.45.2:9210 PRE_INIT) received initial status from 10.34.45.2:9210 2011-06-11 13:04:39 debug cluster(10.34.45.2:9210 PRE_INIT) received initial status from 10.34.45.2:7122 Traceback (most recent call last): File "/root/pematous/bz682815/run_cluster_tests2/brokertest.py", line 523, in broker try: b.ready() File "/root/pematous/bz682815/run_cluster_tests2/brokertest.py", line 418, in ready raise Exception( Exception: Timed out waiting for broker cluster0-7: 2011-06-11 13:04:39 notice Cluster store state: empty 2011-06-11 13:04:39 notice cluster(10.34.45.2:9210 PRE_INIT) configuration change: 10.34.45.2:7122 10.34.45.2:7388 10.34.45.2:9210 2011-06-11 13:04:39 notice cluster(10.34.45.2:9210 PRE_INIT) Members joined: 10.34.45.2:9210 2011-06-11 13:04:39 debug cluster(10.34.45.2:9210 PRE_INIT) received initial status from 10.34.45.2:9210 2011-06-11 13:04:39 debug cluster(10.34.45.2:9210 PRE_INIT) received initial status from 10.34.45.2:7122 Error during teardown: Traceback (most recent call last): File "./qpid-python-test", line 311, in run phase() File "/root/pematous/bz682815/run_cluster_tests2/brokertest.py", line 506, in tearDown if err: raise Exception("Unexpected process status:\n "+"\n ".join(err)) Exception: Unexpected process status: Wait failed testagent-7293: [Errno 10] No child processes Wait failed qpid-queue-stats-7295: [Errno 10] No child processes Wait failed testagent-7895: [Errno 10] No child processes Version-Release number of selected component (if applicable): qpid-cpp-mrg-0.10-8 How reproducible: Unknown - please see Bug 682815 for details Steps to Reproduce: Please follow the 'Steps to Reproduce' in Bug 682815 to reproduce this issue Actual results: Timeout exception on the Broker Expected results: Test passes repeatedly. Additional info: test log+data can be found: mrg-qe-02.lab.eng.brq.redhat.com:/root/pematous/bz682815_data
This defect is also valid for 1.3.x This was seen on RHEL5.7 i386, packages installed: python-qpid-0.7.946106-15.el5 qpid-cpp-client-0.7.946106-33.el5 qpid-cpp-client-devel-0.7.946106-33.el5 qpid-cpp-client-devel-docs-0.7.946106-33.el5 qpid-cpp-client-ssl-0.7.946106-33.el5 qpid-cpp-server-0.7.946106-33.el5 qpid-cpp-server-cluster-0.7.946106-33.el5 qpid-cpp-server-devel-0.7.946106-33.el5 qpid-cpp-server-ssl-0.7.946106-33.el5 qpid-cpp-server-store-0.7.946106-33.el5 qpid-cpp-server-xml-0.7.946106-33.el5 qpid-java-client-0.10-6.el5 qpid-java-common-0.10-6.el5 qpid-java-example-0.10-6.el5 qpid-tools-0.7.946106-12.el5