Nut upsuser - Aug 2011 - mustek powermust 1060 - upsmon wodoo and crappy messages

Dear all,

I have installed nut-2.6.1 (compiled from source) on CentOS release  
4.9 (Final).

[root at mail bin]# ./upsdrvctl -u root start
Network UPS Tools - UPS driver controller 2.0.5
Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.6.1)
Supported UPS detected with mustek protocol
Vendor information unavailable
Battery runtime will not be calculated (runtimecal not set)
[root at mail bin]#

First question:

If battery runtime info is NOT AVAILABLE, how will be possible for  
upsmon to do a clean shutdown of the system before running out all  
energy from batteries?

Second question, and very important:
Why after starting upsmon, I am receiving al all consoles from few  
seconds to few seconds, the following crappy message (snip from memory):

Broadcat mesage, Lost connection with ups mustek1060 ...
after few seconds
Connection with ups mustek1060 established

And in system log appear:
Aug 18 13:04:56 mail upsd[790]: Data for UPS [mustek1060] is stale -  
check driver
Aug 18 13:05:02 mail blazer_usb[699]: Communications with UPS re-established

Aug 18 17:11:39 mail upsd[790]: Data for UPS [mustek1060] is stale -  
check driver
Aug 18 17:11:44 mail blazer_usb[699]: Communications with UPS re-established
Aug 18 17:11:44 mail upsd[790]: UPS [mustek1060] data is no longer stale
Aug 18 17:11:53 mail blazer_usb[699]: Communications with UPS lost:  
status read failed!
Aug 18 17:11:54 mail blazer_usb[699]: Communications with UPS re-established
Aug 18 17:12:03 mail blazer_usb[699]: Communications with UPS lost:  
status read failed!
Aug 18 17:12:04 mail blazer_usb[699]: Communications with UPS re-established
Aug 18 17:12:13 mail blazer_usb[699]: Communications with UPS lost:  
status read failed!
Aug 18 17:12:14 mail blazer_usb[699]: Communications with UPS re-established
Aug 18 17:12:23 mail blazer_usb[699]: Communications with UPS lost:  
status read failed!
Aug 18 17:12:25 mail blazer_usb[699]: Communications with UPS re-established
Aug 18 17:12:33 mail blazer_usb[699]: Communications with UPS lost:  
status read failed!
Aug 18 17:12:35 mail upsd[790]: Data for UPS [mustek1060] is stale -  
check driver
Aug 18 17:12:40 mail blazer_usb[699]: Communications with UPS re-established
Aug 18 17:12:40 mail upsd[790]: UPS [mustek1060] data is no longer stale


Any ideas how to fix it and what is causing these problems?

Below, it comes upsd and upsmon messages when it has been started up:
[root at mail sbin]# ./upsd -4 -u root
Network UPS Tools upsd 2.6.1
listening on 127.0.0.1 port 3493
Connected to UPS [mustek1060]: blazer_usb-mustek1060
[root at mail sbin]#

[root at mail bin]# ./upsc -L 127.0.0.1 or ./upsc -L
mustek1060: Mustek PowerMust 1060, 600W, 1000 VA
[root at mail bin]#

[root at mail bin]# ./upsc mustek1060 at 127.0.0.1
battery.voltage: 26.90
beeper.status: enabled
device.type: ups
driver.name: blazer_usb
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.version: 2.6.1
driver.version.internal: 0.03
input.frequency: 50.1
input.voltage: 227.7
input.voltage.fault: 227.7
output.voltage: 227.7
ups.delay.shutdown: 30
ups.delay.start: 180
ups.load: 0
ups.productid: 5161
ups.status: OL
ups.type: offline / line interactive
ups.vendorid: 0665
[root at mail bin]#

[root at mail ~]# /usr/local/nut/sbin/upsmon
Network UPS Tools upsmon 2.6.1
UPS: mustek1060 at 192.168.13.1 (master) (power value 1)
Using power down flag file /etc/killpower
[root at mail ~]#

Regards,
Alx


-------------------------------------------------
This message sent via VFEmail.net
http://www.vfemail.net
$14.95 Lifetime accounts!  15GB disk!  No bandwidth quotas!

On Aug 19, 2011, at 5:03 AM, linux at vfemail.net wrote:
> If battery runtime info is NOT AVAILABLE, how will be possible for  
> upsmon to do a clean shutdown of the system before running out all  
> energy from batteries?
The UPS signals a binary "low battery" state separate from any of the
other statistics. (Hence the term "optional" in the section of the man
page describing runtime.)

Quoting "Charles Lepple" <clepple at gmail.com>:
> On Aug 19, 2011, at 5:03 AM, linux at vfemail.net wrote:
>
>> If battery runtime info is NOT AVAILABLE, how will be possible for  
>> upsmon to do a clean shutdown of the system before running out all  
>> energy from batteries?
>
> The UPS signals a binary "low battery" state separate from any of
> the other statistics. (Hence the term "optional" in the section
of
> the man page describing runtime.)
Hello and thanks for reply, but still unclear for me your answer.

What to understand? Nut will be able to do a clean shutdown even if it  
cannot read/estimate runtime? Does it mean that everything is ok with  
this ups?

Regards,
Alx


-------------------------------------------------
This message sent via VFEmail.net
http://www.vfemail.net
$14.95 Lifetime accounts!  15GB disk!  No bandwidth quotas!