Description of problem: ======================= RHEL 5.4 Condor Version: 7.4.3-0.11.el5 There are actually 2 issues but they both seem related to each other... Running `condor_q -bet` on host #1 results in "Segmentation fault (core dumped)" Running `condor_q -bet` on any other hosts while there are MPI jobs in the queue results in the following output: error: no operator/attribute found error: found NULL ptr in expr error: problem with ExprToProfile error in ExprToMultiProfile error in AnalyzeAttributes --- 2770.000: Run analysis summary. Of 12 machines, 0 are rejected by your job's requirements 4 reject your job because of their own requirements 0 match but are serving users with a better priority in the pool 8 match but reject the job for unknown reasons 0 match but will not currently preempt their existing job 0 match but are currently offline 0 are available to run your job error: no operator/attribute found error: found NULL ptr in expr error: problem with ExprToProfile error in ExprToMultiProfile error in AnalyzeAttributes Regardless of the different job types in the queue on machine #1 always segfaults... Core was generated by `condor_q -bet'. Program terminated with signal 11, Segmentation fault. (gdb) bt #0 0x000000317209c8c8 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string () from /usr/lib64/libstdc++.so.6 #1 0x000000000048495f in std::_Rb_tree<std::string, std::string, std::_Identity<std::string>, classad::CaseIgnLTStr, std::allocator<std::string> >::_M_insert () #2 0x0000000000484a4a in std::_Rb_tree<std::string, std::string, std::_Identity<std::string>, classad::CaseIgnLTStr, std::allocator<std::string> >::insert_unique () #3 0x00000000004836d2 in AddExplicitTargets () #4 0x00000000004654da in ClassAdAnalyzer::MakeResourceGroup () #5 0x000000000046e19f in ClassAdAnalyzer::AnalyzeJobAttrsToBuffer () #6 0x0000000000461e35 in ?? () #7 0x000000000046472b in ?? () #8 0x0000000000463d25 in main ()
It reminds me of BZ595706 - isn't this the same bug?
s/../BZ571804/
*** This bug has been marked as a duplicate of bug 571804 ***