Hide Forgot
Description of problem: This issue was discovered during testing of BZ682815, please see Bug 682815 for more details. A core dump in the testagent client can be seen when running the 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 834, in test_management c.stop() File "/root/pematous/bz682815/run_cluster_tests2/cluster_tests.py", line 777, in stop StoppableThread.stop(self) File "/root/pematous/bz682815/run_cluster_tests2/brokertest.py", line 565, in stop if self.error: raise self.error RethrownException: Error in ClientLoop.run Traceback (most recent call last): File "/root/pematous/bz682815/run_cluster_tests2/cluster_tests.py", line 760, in run self.process.unexpected( File "/root/pematous/bz682815/run_cluster_tests2/brokertest.py", line 194, in unexpected raise BadProcessStatus("%s %s%s" % (self.pname, msg, err)) BadProcessStatus: testagent-31028 client of cluster0-6 exit code -11 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 qpid-tool-31737: [Errno 10] No child processes Wait failed qpid-perftest-31738: [Errno 10] No child processes Wait failed qpid-queue-stats-31739: [Errno 10] No child processes Wait failed testagent-31742: [Errno 10] No child processes Wait failed qpid-txtest-31740: [Errno 10] No child processes Wait failed qpid-perftest-31774: [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: Core dump in the testagent client Expected results: Test passes repeatedly. Additional info: test log+data can be found: mrg-qe-01.lab.eng.brq.redhat.com:/root/pematous/bz682815_data
The log messages indicate that the "testagent" client seg-faulted. This is a client side bug rather than a broker bug. There is no core file in the data directory - are the tests run with ulimit -c unlimited? If possible get a stack trace if this happens again.
Since the issue is valid for 1.3 as well, the bug was cloned for 1.3.x, please see Bug 723812. Client stack trace is available in the cloned bug.