Nut upsuser - Feb 2010 - NUT with Cyber Power 700 AVR

I recently purchased a Cyber Power 700 AVR UPS. I installed it just fine
and wanted to install NUT to monitor the unit. 

I searched the mailing
list and found a similar post. However, the distro used in that post was
different and the unit was slightly different (900 AVR). 

My server is
running Debian Lenny. The Cyber Power UPS is connect to one of the serial
ports using the cable that came with the unit. This is the first time I
have used serial ports on the server. There are two on the back. Despite
trying them both, I have yet to succeed in my installation. 

The ups.conf
file contains: 

[server] 

 driver = cyberpower 

 port = /dev/ttyS0 


desc = "Server" 

When I run the following command, I get: 

server:#
upsdrvctl start 

Network UPS Tools - UPS driver controller 2.2.2 

Network
UPS Tools - CyberPower driver 1.00 (2.2.2) 

Giving up on hardware
detection after 3 tries 

Unable to get initial hardware info string


Driver failed to start (exit status=1)  I did add the user "nut" to
the
"dialout" group. Below are permissions on the serial devices:  
server:# ls
-l /dev | grep ttyS crw-rw---- 1 root dialout 4, 64 2010-02-22 22:52 ttyS0
crw-rw---- 1 root dialout 4, 65 2010-02-22 23:01 ttyS1 crw-rw---- 1 root
dialout 4, 66 2010-02-22 21:47 ttyS2 crw-rw---- 1 root dialout 4, 67
2010-02-22 21:47 ttyS3   Any idea what is causing my error?  Thanks, Tom  
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20100222/5b35355b/attachment.htm>

Citeren Thomas Jensen <tom.jensen op digitaltoolbox-inc.com>:
> server:#
> upsdrvctl start
>
> Network UPS Tools - UPS driver controller 2.2.2
>
> Network
> UPS Tools - CyberPower driver 1.00 (2.2.2)
Try running the powerpanel driver. The cyberpower driver is no longer  
maintained and has no provisions for debugging the communication with  
the UPS.

[server]
     driver = powerpanel
     port = /dev/ttyS0
     desc = "Server"

If this fails to detect the UPS, try running the *driver* in debug mode:

     /path/to/powerpanel -DDD -a server

The first 10 seconds worth of output might give a clue why it isn't  
working. After that you should kill it with Ctrl-C (otherwise it will  
keep spitting out debug information forever).

If this works, you'll probably want to upgrade to nut-2.4.1 (or  
better) since there have been some changes in the interpretation of  
the readings from the UPS since nut-2.2.2 was released almost two  
years ago.

Best regards, Arjen
-- 
Please keep list traffic on the list

My previous post was a follow-up to this discussion in February:


http://lists.alioth.debian.org/pipermail/nut-upsuser/2010-February/005924.html