Bug 187578

Summary: Fence daemon calling custom fence method has strange behavior
Product: [Retired] Red Hat Cluster Suite Reporter: Henry Harris <henry.harris>
Component: fenceAssignee: Jim Parsons <jparsons>
Status: CLOSED NOTABUG QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: cluster-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-04-02 20:52:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Henry Harris 2006-04-01 05:00:54 UTC 
Description of problem:
We have implemented our own fence method which was working fine until the U3 
upgrade.  We have a perl script in /sbin which is called by the fence daemon.  
The perl script uses a system command to call a bash script.  Both the perl 
script and the bash script work fine if called from a command line.  If the 
perl script is called from the fence daemon, the bash script either hangs on a 
read command or exhibits other strange behavior such as logger will not print 
a message to the system log.

Version-Release number of selected component (if applicable):
fence-1.32.18-0

How reproducible:
Every time.

Steps to Reproduce:
1. Invoke perl script from fence daemon
2. Invoke bash script using system command in perl script
3. Have bash script issue logger "message" 
  
Actual results:
No logger message appears in system log

Expected results:
Logger message in system log

Additional info:
Comment 1 Henry Harris 2006-04-02 20:52:27 UTC 
Problem was in our own start up scipts for fenced.