Bug 705722 - condor_triggerd segfault after initialization using the condor_trigger_config on RHEL6
Summary: condor_triggerd segfault after initialization using the condor_trigger_config...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: condor
Version: Development
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: 2.0
: ---
Assignee: Robert Rati
QA Contact: Tomas Rusnak
URL:
Whiteboard:
Depends On: 705343
Blocks: 602766
TreeView+ depends on / blocked
 
Reported: 2011-05-18 09:29 UTC by Tomas Rusnak
Modified: 2011-06-27 15:32 UTC (History)
2 users (show)

Fixed In Version: condor-7.6.1-0.5
Doc Type: Bug Fix
Doc Text:
Clone Of: 705343
Environment:
Last Closed: 2011-06-27 15:32:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 3 Tomas Rusnak 2011-05-25 14:53:20 UTC
Retested over RHEL6 with:

# rpm -qa | egrep '(qpid|sesame|matahari)' | sort
python-qpid-0.10-1.el6.noarch
python-qpid-qmf-0.10-7.el6.x86_64
qpid-cpp-client-0.10-5.el6.x86_64
qpid-cpp-client-devel-0.10-5.el6.x86_64
qpid-cpp-client-devel-docs-0.10-5.el6.noarch
qpid-cpp-client-rdma-0.10-5.el6.x86_64
qpid-cpp-client-ssl-0.10-5.el6.x86_64
qpid-cpp-server-0.10-5.el6.x86_64
qpid-cpp-server-cluster-0.10-5.el6.x86_64
qpid-cpp-server-devel-0.10-5.el6.x86_64
qpid-cpp-server-rdma-0.10-5.el6.x86_64
qpid-cpp-server-ssl-0.10-5.el6.x86_64
qpid-cpp-server-store-0.10-5.el6.x86_64
qpid-cpp-server-xml-0.10-5.el6.x86_64
qpid-java-client-0.10-6.el6.noarch
qpid-java-common-0.10-6.el6.noarch
qpid-java-example-0.10-6.el6.noarch
qpid-java-jca-0.10-6.el6.noarch
qpid-qmf-0.10-7.el6.x86_64
qpid-tests-0.10-1.el6.noarch
qpid-tools-0.10-4.el6.noarch
rh-qpid-cpp-tests-0.10-5.el6.x86_64
ruby-qpid-0.7.946106-2.el6.x86_64
ruby-qpid-qmf-0.10-7.el6.x86_64
sesame-debuginfo-0.10-1.el6.x86_64

qpid: list
Summary of Objects by Type:
    Package                 Class                 Active  Deleted
    ===============================================================
    com.redhat.grid         slot                  1       0
    org.apache.qpid.broker  binding               63      0
    org.apache.qpid.broker  subscription          21      0
    com.redhat.grid         master                1       0
    org.apache.qpid.broker  queue                 21      0
    org.apache.qpid.broker  broker                1       0
    org.apache.qpid.broker  system                1       0
    com.redhat.grid         negotiator            1       0
    com.redhat.grid         submission            243     0
    org.apache.qpid.broker  connection            11      0
    org.apache.qpid.broker  session               11      0
    org.apache.qpid.broker  exchange              8       0
    com.redhat.grid         jobserver             1       0
    com.redhat.grid         condortriggerservice  1       0
    org.apache.qpid.broker  vhost                 1       0
    org.apache.qpid.broker  agent                 1       0
    com.redhat.grid         collector             1       0


# /usr/sbin/condor_trigger_config -i localhost
Connecting to broker 'localhost'...
Initializing, adding default triggers...
Adding trigger 'High CPU Usage'...
Adding trigger 'Low Free Mem'...
Adding trigger 'Low Free Disk Space (/)'...
Adding trigger 'Busy and Swapping'...
Adding trigger 'Busy but Idle'...
Adding trigger 'Idle for long time'...
Adding trigger 'Logs with ERROR entries'...
Adding trigger 'Logs with error entries'...
Adding trigger 'Logs with DENIED entries'...
Adding trigger 'Logs with denied entries'...
Adding trigger 'Logs with WARNING entries'...
Adding trigger 'Logs with warning entries'...
Adding trigger 'dprintf Logs'...
Adding trigger 'Logs with stack dumps'...
Adding trigger 'Core Files'...

TriggerLog (repeated for each trigger):
05/25/11 17:40:40 Triggerd::ManagementMethod called
05/25/11 17:40:40 Triggerd::AddTrigger called
05/25/11 17:40:40 Triggerd::AddTriggerToCollection called
05/25/11 17:40:40 Triggerd::AddTriggerToCollection exited with return value 0
05/25/11 17:40:40 Triggerd::AddTrigger exited with return value 0

No crash found.

>>> VERIFIED


Note You need to log in before you can comment on or make changes to this bug.