Nut upsdev - Jan 2006 - newhidups (2.03-pre2) not working with APC Back-UPS 500

Hi there,

I'm trying to track down a problem with said combination. 

 Broadcast message from nut (Thu Jan 26 13:22:06 2006):

 Communications with UPS UPS@localhost lost

 Broadcast message from nut (Thu Jan 26 13:22:11 2006):

 UPS UPS@localhost is unavailable

"newhidups -DDD hiddev0" seems happy enough, as does "upsd -DDD
-f" - at
least until I start upsmon. Then I see:

...
[root@test7 ups]# /usr/sbin/upsmon -D
Network UPS Tools upsmon 2.0.3-pre2
UPS: UPS@localhost (slave) (power value 1)
Using power down flag file /etc/killpower

Trying to connect to UPS [UPS@localhost]
Logged into UPS UPS@localhost
polling ups: UPS@localhost
get_var: UPS@localhost / status
Poll UPS [UPS@localhost] failed - Variable not supported by UPS
do_notify: ntype 0x0005 (COMMBAD)
Communications with UPS UPS@localhost lost

...

At this point, upsd reports an error:

...
Pinging UPS [UPS]
Got PONG from UPS [UPS]
acl_check: localhost: match 1
ACL [localhost] matches, action=1
Connection from 127.0.0.1
acl_check: localhost: match 1
ACL [localhost] matches, action=1
write: [destfd=6] [len=3] [OK
]
acl_check: localhost: match 1
ACL [localhost] matches, action=1
write: [destfd=6] [len=3] [OK
]
acl_check: localhost: match 1
ACL [localhost] matches, action=1
Client monuser@127.0.0.1 logged into UPS [UPS]
write: [destfd=6] [len=3] [OK
]
acl_check: localhost: match 1
ACL [localhost] matches, action=1
write: [destfd=6] [len=22] [ERR VAR-NOT-SUPPORTED
]
...

What variable might upsmon be polling which is not supported by newhidups 
for this UPS? Or how can I find out for myself.

[FTR, hidups doesn't work either, although it used to work with this UPS 
in version 1.2.0.]

Thanks

---
Charlie

On Thu, 26 Jan 2006, Charlie Brady wrote:
> What variable might upsmon be polling which is not supported by newhidups 
> for this UPS? Or how can I find out for myself.
Found it:

...
[pid 20933] write(1, "get_var: UPS@localhost / status\n", 32get_var: 
UPS@localhost / status
) = 32
[pid 20933] write(3, "GET VAR UPS ups.status\n", 23) = 23
[pid 20933] read(3, "E", 1)             = 1
[pid 20933] read(3, "R", 1)             = 1
...

Next puzzle is to find out why "ups.status" is not supported.

--
Charlie