Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 132603

Summary:	need fence info output to syslog
Product:	[Retired] Red Hat Cluster Suite	Reporter:	Corey Marthaler <cmarthal>
Component:	gfs	Assignee:	David Teigland <teigland>
Status:	CLOSED CURRENTRELEASE	QA Contact:	GFS Bugs <gfs-bugs>
Severity:	low	Docs Contact:
Priority:	medium
Version:	4	CC:	amanthei
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-09-27 21:33:07 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 Corey Marthaler 2004-09-14 23:04:50 UTC

Description of problem: 
When a node is fenced there is nothing reported in the syslog by the 
fencer. The only way I know who's fencing who is because I added 
debugging info to fence_apc. In 6.0 and 5.2.1 there were messages 
stating who was about to be fenced and then weither or not it was 
successful. The only way to know what's happening now is to run 
fenced with the debugging flag and in the foreground. 
 
How reproducible: 
Always 
 
Steps to Reproduce: 
1. attempt recovery senario

Comment 1 David Teigland 2004-09-17 04:09:54 UTC

How does this look?

RCS file: /cvs/cluster/cluster/fence/fenced/recover.c,v
retrieving revision 1.2
diff -r1.2 recover.c
181a182
>               syslog(LOG_INFO, "fencing node \"%s\"", node->name);
187a189,191
> 
>               syslog(LOG_INFO, "fence \"%s\" %s", node->name,
>                      error ? "failed" : "success");

Comment 2 Corey Marthaler 2004-09-17 18:53:35 UTC

looks good.  
 
fix verified.

Comment 3 Derek Anderson 2004-09-22 19:21:32 UTC

This is good, but it is also necessary for troubleshooting to have the
output of the fence agent in here, as it was for 6.0.0.  I'm currently
in a state where a log is reporting:

Sep 22 14:23:32 tng3-1 fenced[2267]: fencing node "tng3-3"
Sep 22 14:23:32 tng3-1 fenced[2267]: fence "tng3-3" failed

over and over again with no additional info on what's gone wrong.

Comment 4 David Teigland 2004-09-23 07:04:43 UTC

With today's checkin it worked with my test.

Comment 5 Corey Marthaler 2004-09-27 21:33:07 UTC

the output of the fence agent does now appear. fix verified.

Comment 6 Kiersten (Kerri) Anderson 2004-11-16 19:04:47 UTC

Updating version to the right level in the defects.  Sorry for the storm.