Bug 241102

Summary: fence_apc works not
Product: [Retired] Red Hat Cluster Suite Reporter: Falk Hackenberger <f.hackenberger>
Component: fenceAssignee: Jim Parsons <jparsons>
Status: CLOSED WORKSFORME QA Contact: Cluster QE <mspqa-list>
Severity: urgent Docs Contact:
Priority: medium    
Version: 4CC: cluster-maint, qshen
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: 2008-02-27 14:30:01 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:
Attachments:
Description Flags
tcpump of communtication between host and fencing devic
none
strace output of fence apc none

Description Falk Hackenberger 2007-05-24 06:24:29 UTC
it try to use fence_apc with:

fence.strace fence_apc -a fence -l apc -p acp  -n 2

and i get this outpt:
---snip---
Traceback (most recent call last):
  File "/sbin/fence_apc", line 798, in ?
    main()
  File "/sbin/fence_apc", line 285, in main
    do_login(sock)
  File "/sbin/fence_apc", line 456, in do_login
    ndbuf = sock.read_eager() # Scoop up remainder
  File "/usr/lib/python2.3/telnetlib.py", line 377, in read_eager
    return self.read_very_lazy()
  File "/usr/lib/python2.3/telnetlib.py", line 400, in read_very_lazy
    raise EOFError, 'telnet connection closed'
EOFError: telnet connection closed
---snap---

the strace output of fence_apc is attached
also the tcpump of the communtication between host and fencing device

the fencing device is the apc ap7921

Comment 1 Falk Hackenberger 2007-05-24 06:28:18 UTC
Created attachment 155314 [details]
tcpump of communtication between host and fencing devic

Comment 2 Falk Hackenberger 2007-05-24 06:29:38 UTC
Created attachment 155315 [details]
strace output of fence apc

Comment 3 Bryn M. Reeves 2007-11-23 11:02:48 UTC
*** Bug 244610 has been marked as a duplicate of this bug. ***

Comment 4 Bryn M. Reeves 2007-11-23 11:18:52 UTC
This looks like a problem with the APC v.3 firmware, rather than anything
specific to the 7921 NPS. See bug 245675 for more infomation.

Comment 5 Jim Parsons 2008-02-27 14:30:01 UTC
The agent in current release was tested on an APC7921 a week ago, and worked
flawlessly. There were some issues with one of their 3.x firmware releases that
they have fixed in subsequent releases. I recommend upgrading to the latest apc
firmware if this condition persists.