2012/2/27 Thomas Maisl exp-122...@maisl.com:
Hello,
schrieb Arnaud Quette, Am 16.02.2012 18:48:
Can you please counter check, and report back upsc/upsrw/upscmd
upsc:
# upsc YQ450
battery.voltage: 13.40
beeper.status: disabled
device.type: ups
driver.name: blazer_usb
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.productid: 0002
driver.parameter.protocol: zinto
driver.parameter.subdriver: cypress
driver.parameter.vendorid: 06da
driver.version: 2.6.3
driver.version.internal: 0.04
input.frequency: 50.0
input.voltage: 232.0
input.voltage.fault: 1.0
this seems not normal!
output.voltage: 232.0
ups.delay.shutdown: 30
ups.delay.start: 180
ups.load: 0
ups.productid: 0002
ups.status: OL BYPASS
ups.temperature: 25.0
ups.type: offline / line interactive
ups.vendorid: 06da
# upsrw -u xxx -p xxx -s ups.delay.start YQ450
Enter new value for ups.delay.start: 90
Unexpected response from upsd: ERR ACCESS-DENIED
# upsrw -u xxx -p xxx -s ups.delay.shutdown YQ450
Enter new value for ups.delay.shutdown: 90
Unexpected response from upsd: ERR ACCESS-DENIED
# upscmd -u xxx -p xxx YQ450 shutdown.return 1
Unexpected response from upsd: ERR ACCESS-DENIED
the user and password used for upsrw and upscmd are the ones defined
in upsd.users.
here, upsd is telling us that you've used wrong ones (generally system
ones, such as root...).
output, along with the shutdown test:
http://www.networkupstools.org/docs/user-manual.chunked/ar01s06.html#Shutdown_design
while doing shutdown
# upslog -s yq450 -i 2 -l -
Network UPS Tools upslog 2.6.3
logging status of yq450 to - (2s intervals)
20120227 091805 NA 0.0 0 [OB] 25.0 0.0
20120227 091807 NA 0.0 0 [OB] 25.0 0.0
20120227 091809 NA 0.0 0 [OB] 25.0 0.0
20120227 091811 NA 0.0 0 [OB] 25.0 0.0
20120227 091957 NA NA NA [FSD WAIT] NA 0.0
20120227 091959 NA 0.0 0 [FSD OB] 25.0 0.0
20120227 092001 NA 0.0 0 [FSD OB LB] 25.0 0.0
20120227 092003 NA 0.0 0 [FSD OB LB] 25.0 0.0
so, no battery voltage is displayed
battery.voltage is not part of the default upslog string:
%TIME @Y@m@d @H@M@S% %VAR battery.charge% %VAR input.voltage% %VAR
ups.load% [%VAR ups.status%] %VAR ups.temperature% %VAR
input.frequency%
the above shows that OB+LB has triggered FSD.
so upsmon.conf-SHUTDOWNCMD has been executed.
parallel
/lib/nut/blazer_usb -a YQ450 -D
23.832061 read: (000.0 001.0 230.0 000 00.0 12.5 25.0 10001000
25.472224 send: Q1
25.816057 read: (000.0 001.0 230.0 000 00.0 12.5 25.0 11001000
25.816249 send_to_all: SETINFO ups.status OB LB
27.473243 send: Q1
27.832053 read: (000.0 001.0 230.0 000 00.0 12.5 25.0 11001000
29.476227 send: Q1
29.848055 read: (000.0 001.0 230.0 000 00.0 12.5 25.0 11001000
31.478227 send: Q1
31.832056 read: (000.0 001.0 230.0 000 00.0 12.5 25.0 11001000
32.070549 send_to_one: PONG
Temperature is always 25.0°C
When cutting off power to the UPS, power to the outlets isn't switched off
despite the low battery warning (at least 15 minutes after cutting power)
Do I have a faulty UPS?2
it depends on what you mean with cutting off power to the UPS...
if you refer to upscmd -u xxx -p xxx YQ450 shutdown.return, it has failed.
if you mean following the above FSD, it's indeed not normal.
I would need the driver output when going FSD (or using upscmd...
shutdown.return)
remember to not power your PC with the UPS while testing this!
note that you may also contact the manufacturer support to get some
help on their possible variation of the protocol.
cheers,
Arno
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
