Nut upsdev - Jan 2014 - Problems with blazer_usb. Driver will not shut down my UPS

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi there!

I don't know if you are able to help me. Have tried almost everything
at this point..

I recently switched from a BlueWalker(Powerwalker?) PW UPS VI2000 LCD
2000VA offline UPS to a BlueWalker(Powerwalker?) PW UPS VFI 1500 LCD
1500VA Online UPS.

Seems like the driver is accepting both, however, the shutdown command
wont work. And this is what I get when i run upsdrvctl shutdown
<ups-name>:

Network UPS Tools - UPS driver controller 2.6.3
Network UPS Tools - Megatec/Q1 protocol USB driver 0.04 (2.6.3)
Initiating UPS shutdown
instcmd: command [shutdown.stop] failed
instcmd: command [shutdown.stop] failed
instcmd: command [shutdown.stop] failed
Shutdown failed!
Driver failed to start (exit status=1)

On my old UPS the whole shutdown process works like a charm with both
Server and UPS shutdown. Now i am stuck with UPS running "forever"..

Here is my output from upsc powerwalker:
battery.voltage: 40.86
battery.voltage.nominal: 36.0
beeper.status: disabled
device.mfr:
device.model: HV 1K5
device.type: ups
driver.name: blazer_usb
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.version: 2.6.3
driver.version.internal: 0.04
input.current.nominal: 6.0
input.frequency: 50.0
input.frequency.nominal: 50
input.voltage: 230.3
input.voltage.fault: 230.3
input.voltage.nominal: 230
output.voltage: 230.1
ups.delay.shutdown: 30
ups.delay.start: 180
ups.firmware: 00001911
ups.load: 8
ups.mfr:
ups.model: HV 1K5
ups.productid: 5161
ups.status: OL
ups.temperature: 19.0
ups.type: online
ups.vendorid: 0665

Since the driver seems to be working very well on my other UPS and
guess this could be a driver issue. System running is Linux
3.5.0-23-generic #35~precise1-Ubuntu SMP x86_64 x86_64 x86_64 and all
programs are installed from Ubuntu's repository

Have spent many hours now trying to solve this.. I really hope you can
give me some advice here.

Many thanks and regards
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJSxxjeAAoJEM18BAAVtKX3w1kH/2In2hLqV+TRk2aDv5MhOjG8
IkMI+zYErsitbjyE+vap+G3xVKhr8PuHQmqCzpHvHy2V7y1E/G1LPw+glCphI+Do
MaDY5r1/MRU4HRMqQTXaUg2KCoBV0IjyBs3XDerZnt70rveIP15yjCDZ3njda6pc
ltMb93bCTaOSUz/ABt/BelXniZ5Vtcztr+Z24tY/2l32Pk6VBknyhqnhfakq6dYy
tMgUhDWpG6p3bPYZ3uCAxkP5J/McT2yShM5SkkCFrZf8OvVSYBmLpimAC76tNyNK
gnt2FWwvyTj1S5d20hH844ibqZRnzNyNgENqt9yFbKKARpYLjR12dkuFmvR5PLY=Xx7e
-----END PGP SIGNATURE-----

2014/1/3 Eirik Skorstad <eskorsta at hotmail.com>:
> Hi there!
>
Hi
> Seems like the driver is accepting both, however, the shutdown command
> wont work. And this is what I get when i run upsdrvctl shutdown
> <ups-name>:
>
> Network UPS Tools - UPS driver controller 2.6.3
> Network UPS Tools - Megatec/Q1 protocol USB driver 0.04 (2.6.3)
> Initiating UPS shutdown
> instcmd: command [shutdown.stop] failed
> instcmd: command [shutdown.stop] failed
> instcmd: command [shutdown.stop] failed
> Shutdown failed!
> Driver failed to start (exit status=1)
Assuming shutdown.return works when issued via upscmd (does it work?),
the problem seems to be that your UPS doesn't accept a shutdown.stop
when there's no shutdown pending (or, maybe, the UPS doesn't support
it at all), therefore the shutdown sequence cannot continue and issue
the shutdown.return command.
That problem has been addressed in commit:

https://github.com/networkupstools/nut/commit/d079be2e4aab3c1999d99e87d70de5ee24309a31

It should be available in 2.7.1

(Keep the list CCed)

2014/1/4 Eirik Skorstad <eskorsta at hotmail.com>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>> Assuming shutdown.return works when issued via upscmd (does it
>> work?), the problem seems to be that your UPS doesn't accept a
>> shutdown.stop when there's no shutdown pending (or, maybe, the UPS
>> doesn't support it at all), therefore the shutdown sequence cannot
>> continue and issue the shutdown.return command. That problem has
>> been addressed in commit:
>>
>>
https://github.com/networkupstools/nut/commit/d079be2e4aab3c1999d99e87d70de5ee24309a31
>>
>>  It should be available in 2.7.1
>
>
> Thanks for the answer. When i run upscmd -u user -p pass <ups-name>
> shutdown.return it returns back "OK", but in the syslog
there's
> another story:
>
> upsd[2783]: Instant command: nutmon at 127.0.0.1 did shutdown.return on
> powerwalker
> blazer_usb[2781]: instcmd: command [shutdown.return] failed
>
Apart from what the logs say, has the command some effects on the UPS?
Can you please launch the driver with debug level = 3 and send the
logs of when you execute the command shutdown.return via upscmd?

I saw your new UPS is shipped with ViewPower (developed by Voltronic
Power, mainly for their UPSes), so, if it's manufactured by Voltronic
Power maybe it's using their new protocol 'QGS' (mapped as
'voltronic'
in the new driver nutdrv_qx - available in 2.7.1) or one of their
other ones.
Maybe the command itself is accepted by the UPS, but since it may use
'(ACK'/'(NAK' replies instead of the 'ACK'/'echoing
back' of Q1 units
the driver sees the '(ACK' as a failure.
This problem has been addressed in blazer in 2.7.1:

https://github.com/networkupstools/nut/commit/031f43d17a129872bd8d5372d580bb497cafbe26
> When I run test.battery.start.quick it starts with the quick test, so
> something is definitely working.
>
> I really can't believe that a online UPS lacks this function while my
> cheep line-interactive got it.. Maybe I will have to write a mail to
> BlueWalker GmBh to see if they can answer med about the shutdown
> function.
>
> Is it possible to upgrade to 2.7.1 from apt or do I have to compile it
> from source?
I'm not using ubuntu.. however, here's some .deb:

https://launchpad.net/ubuntu/trusty/+source/nut/2.7.1-1ubuntu1
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJSx1XUAAoJEM18BAAVtKX3KIYH/isnMuJM8DhvDVNIWuFzjg/O
> 5R74VzabCWmF+zGp7EhexwWIRciJKF96C801RkueQTHtzb9IzGugXUnUBQkCRhJz
> p+vjMokWNHXl3Rb7ygaPIcVvMp17iSiKW4PotoO9wQvru6d4IIlx6XeXjY7CkOnF
> +YXGQdYmSLVn35+VdyhcNMarQRgPaEozQUX65PmllCapMX0TGWsDNdfTvNVQFw+N
> SaSoiQtCmtI+4aBEgvspyCQo3cRElDYPukdIcdW/ywdm2JzxPkQy+AVN/4ySAeVD
> tOsoYy0ef1ZGM2z3SX9VeT4ETDzS44ZrBiEUXIR3MIj6ejOZd1c/cSG+8rkjm2A> =0aqD
> -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


>> Apart from what the logs say, has the command some effects on the
>> UPS? Can you please launch the driver with debug level = 3 and
>> send the logs of when you execute the command shutdown.return via
>> upscmd?
>> I saw your new UPS is shipped with ViewPower (developed by
>> Voltronic Power, mainly for their UPSes), so, if it's
>> manufactured by Voltronic Power maybe it's using their new
>> protocol 'QGS' (mapped as 'voltronic' in the new driver
nutdrv_qx
>> - available in 2.7.1) or one of their other ones. Maybe the
>> command itself is accepted by the UPS, but since it may use 
>> '(ACK'/'(NAK' replies instead of the
'ACK'/'echoing back' of Q1
>> units the driver sees the '(ACK' as a failure. This problem has
>> been addressed in blazer in 2.7.1:
> 
>>
https://github.com/networkupstools/nut/commit/031f43d17a129872bd8d5372d580bb497cafbe26

>>
>> 
I'm not using ubuntu.. however, here's some
.deb:
> 
>> https://launchpad.net/ubuntu/trusty/+source/nut/2.7.1-1ubuntu1

Well, I started with an upgrade to 2.7.1 and that seems to fix the
problem by it self :) Here is the files i had to download and install
in same order:

dh-systemd_1.13_all.deb
init-system-helpers_1.13_all.deb
libupsclient-dev_2.7.1-1ubuntu1_amd64.deb
libupsclient3_2.7.1-1ubuntu1_amd64.deb
nut-client_2.7.1-1ubuntu1_amd64.deb
nut-server_2.7.1-1ubuntu1_amd64.deb


Ran upscmd shutdown.return followed by a shutdown.stop and the UPS
responded as it should. Did a upsmon -c fsd and the server and UPS
responded according to my settings. Still have to do a long batteri
test though, however I am pretty sure this solved the problem.

Maybe it's time for Ubuntu to update their sources..

Many thanks for your help :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJSx+ZEAAoJEM18BAAVtKX3kxQH/iaMKNKP5i6qyfQdAXnwHuVl
wy4Q1Ya67sxxZizBaqrMY+dKa0LHWmEEPtx6SXm43V6R9bgjj9zJp4f94Z9DwN8q
1f8q+8gcd//zrTwIDEtYvLk5mRDcNCxtnlrJFxXAEJaSFTGd0rIizBiZ8RsJHoFN
e/0vsg8rj3xV7tfY84PbxaAGp7f3+EkVGIlk0GSGtom2X4mzHTZCiZWOysO/7Wy+
NQ6hUTGwMAhiM5EcG+Y6dkdsRrb6PO6I1tr9N4q8YQVX9IijzHdKnMy+4SWQf8+N
0L0JrL1wFTBiKwyXtj7gLpseFcpZaf7Jz/byKoU+sXqAUcM4snhcAbJgtXfaZ8c=yLv1
-----END PGP SIGNATURE-----