Bug 200931

Summary: newhidups not working with APC Back-UPS
Product: [Fedora] Fedora Reporter: Sergio Pascual <sergio.pasra>
Component: nutAssignee: Tomas Smetana <tsmetana>
Status: CLOSED WONTFIX QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 5   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-08-15 11:41:37 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
Output of upsc none

Description Sergio Pascual 2006-08-01 17:37:43 UTC 
Description of problem:
I have an APC Back-UPS 500 SC and I configured ups.conf this way:

[apc-backups500]
driver = newhidups
port = auto

upsmon.conf has this line:
MONITOR apc-backups500@localhost 1 ups-obs passw master

when I start ups and upsmon starts to read, I get the following line:
Poll UPS [apc-backups500@localhost] failed - Variable not supported by UPS

Doing strace with /usr/sbin/upsd I get lines like the follwoing:

read(6, "GET VAR apc-backups500 ups.statu"..., 512) = 34
write(6, "ERR VAR-NOT-SUPPORTED\n", 22) = 221

It seems that ups is asking for ups.status and newhidups does nor provide it.
It is not in the ouput of upsc



Version-Release number of selected component (if applicable):
nut-2.0.3-0.1.fc5

How reproducible:
Always

Steps to Reproduce:
1. Configure the ups with newhidups
2. /sbin/service ups start
3.
  
Actual results:
Messages:
UPS apc-backups500@localhost is unavailable

Expected results:
upsd can speak with newhidups 

Additional info:
Comment 1 Sergio Pascual 2006-08-01 17:37:43 UTC 
Created attachment 133419 [details]
Output of upsc
Comment 2 Tomas Smetana 2007-08-15 11:41:37 UTC 
Sorry but FC-5 is discontinued. If the problem remains in the recent Fedora
versions please reopen the bug.