Is there a way to get more debugging output from the fencing agent fence_vmware_soap?

Solution Verified - Updated

Environment

  • Red Hat Enterprise Linux Server 5 (with the High Availability Add on)
  • Red Hat Enterprise Linux Server 6 (with the High Availability Add on)

Issue

  • Is there a way to get more debugging output from the fencing agent fence_vmware_soap?

Resolution

The following is some recommendations on how to get more debugging from the fence agent fence_vmware_soap to diagnose problems with the fencing agent.

  • A python script is attached to this article called fence_vmware_soap-wrapper.py(it is attached to the article as fence_vmware_soap-wrapper.py.txt) that is a wrapper for fence_vmware_soap. The script fence_vmware_soap-wrapper.py that will enable suds debugging(which is disabled by default with no option to enable suds debugging) then it will write the debug output to a file called: /tmp/fence_vmware_soap-debug.txt. Below is an example of listing of all the virtual machines with the script `fence_vmware_soap-wrapper.pyand without python tracing:
# mv  fence_vmware_soap-wrapper.py.txt  fence_vmware_soap-wrapper.py
# python ./fence_vmware_soap-wrapper.py -z -a 1.1.1.42 -l bob -p XXXX --action list
  • The fencing agent can be executed with python tracing enabled. This is useful to follow the code path for diagnosing which function generated an error:
# RHEL 5
# python -m trace -t /sbin/fence_vmware_soap [options] > /tmp/fence_vmware_soap.trace 2>&1

# RHEL 6
# python -m trace -t /usr/sbin/fence_vmware_soap [options] > /tmp/fence_vmware_soap.trace 2>&1
  • Use both methods to get more debugging out of the fencing agent fence_vmware_soap. When using thefence_vmware_soap wrapper fence_vmware_soap-wrapper.py and python tracing they will create two files: /tmp/fence_vmware_soap-debug.txt and /tmp/fence_vmware_soap.trace that can be analyzed.
# python -m trace -t ./fence_vmware_soap-wrapper.py -z -a 1.1.1.42 -l bob -p XXXX --action list > /tmp/fence_vmware_soap.trace 2>&1

Please note that there will be 2 files created that will need to be analyzed: /tmp/fence_vmware_soap.trace and /tmp/fence_vmware_soap-debug.txt.

Root Cause

The fencing agent fence_vmware_soap errors out when executed and only general error messages are returned.

Diagnostic Steps

SBR
Product(s)
Components
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.