Nut upsuser - Sep 2016 - How to get started (Windows)

> On Thu, 8 Sep 2016, Jeff Bowman wrote:
> 
> > (Note: running
> > 'upsc ups at localhost' echoes only a blank line to the
screen, as do
> > both 'upsmon' and 'upsd.')
> 
> Something is wrong here.  Is the daemon upsd running?  On a Unix/Linux
> system, the command ps aux | grep ups gives the report
> 
>   upsd 3196  0.0  0.0  13228   880 ? Ss ao?t30   2:14
/usr/lib/ups/driver/usbhid-ups -a Eaton-66781
>   upsd 3200  0.0  0.0  17560   736 ? Ss ao?t30   0:49 /usr/sbin/upsd -u
upsd
>   root 3203  0.0  0.0  19432   664 ? Ss ao?t30   0:00 /usr/sbin/upsmon
>   upsd 3204  0.0  0.0  19856  1612 ? S  ao?t30   0:41 /usr/sbin/upsmon
> 
> I don't have any Windows boxes, but I guess there is a similar command
on
> Windows.  What does it show?
The equivalent PowerShell command is Get-Process *ups*

Presently it returns this:

    PS C:\Users\Admin> Get-Process *ups*

    Handles  NPM(K)    PM(K)      WS(K) VM(M)   CPU(s)     Id ProcessName
    -------  ------    -----      ----- -----   ------     -- -----------
         57       6      788       3584    25     0.03   3504 usbhid-ups

So no...  it doesn't appear upsd is running.
> Is it possible to ssh into the system which runs NUT, and then run command
> "upsc <myups>"?
FYI RDP is the Windows equivalent to SSH, then a PowerShell prompt. I just did
so and ran this again:

    upsc ups at localhost

Only a blank line echoes to the screen, presumable because the other *usb*
processes aren't running.

Note that when I run upsdrvctl start as indicated on pp21 of the NUT User Manual
(PDF), I get the conflict error I described earlier:

    Can't claim USB device [051d:0003]: libusb0-dll:err [claim_interface]
could not
    claim interface 0, win error: The requested resource is in use.

    Driver failed to start (exit status=1)

Running the .MSI setup on Windows results in a service (daemon) being created,
one that starts and maintains an executable named NUT.exe. I'm not sure what
that process does. The above error occurs only when the service is running:

    PS C:\Users\Admin> Get-Process *nut*

    Handles  NPM(K)    PM(K)      WS(K) VM(M)   CPU(s)     Id ProcessName
    -------  ------    -----      ----- -----   ------     -- -----------
         71       5      692       3376    16     0.00   3840 nut

When I stop the service (NUT.exe) and run upsdrvctl start, the command
immediately echoes this:

    Using subdriver: APC HID 0.95

...and then hangs for 45 seconds before returning to a command prompt. No UPS
hardware information is printed.

With the service stopped and after running upsdrvctl start, PowerShell returns
this:

    PS C:\Users\Admin> Get-Process *ups*

    Handles  NPM(K)    PM(K)      WS(K) VM(M)   CPU(s)     Id ProcessName
    -------  ------    -----      ----- -----   ------     -- -----------
         57       6      788       3584    25     0.03   3504 usbhid-ups

upsd still returns a blank line. I tried adding this to upsd.conf:

    LISTEN 127.0.0.1 3493

But the result is still the same.

Running this again:

    upsc ups at localhost

Also still results in a blank line.

I tried adding this to ups.conf:

    vendorid = 051d

But that didn't help either.

My UPS is an APC Smart-UPS Model C1000, if that helps.

This is starting to get sticky, isn't it?
> Given that a perfect data set is mission critical for you, I would
recommend
> having a test rig where you can check that you can handle wall power return
> at every phase of NUT action.
My plan is to plug the server into a separate power source not controlled by the
UPS, and then run my tests. If everything is configured correctly, the server
will start its shutdown when I pull the plug on the UPS. But at first I'm
only going to have it do something simple, like write some text out to a file or
sign out of the current user session. Something non-destructive.
> > Sounds good. Next up: how to then send the 'delayed shutdown'
command
> > to the UPS hardware itself? Does the driver automatically handle that?
> 
> The command upsdrvctl shutdown does this.  See man upsdrvctl.
Got it, thanks. Will do. RTFM.
> "Shortly after" means using timers. If you want to preserve the
battery
> charge, but not use timers, you need to use a combination of OB and LB and
> set your LB level high using a command such as
> 
>   upsrw -s battery.charge.low=60 -u upsmaster -p sekret my-ups
My timers/loops/etc will be in the logic of the shutdown program I'll
eventually write for this (probably a small .NET Console app). All I need NUT to
do is detect the power outage and fire the NOTIFYFLAG ONBATT EXEC event, which
in turn will run my program. Once control is handed off, I can do anything I
want from there. (Start a loop to re-check power status, send emails, shut down
the NAS, make log entries, etc.)

But first I have to get it working  :-)
> Roger
Thanks again,
Jeff Bowman
Fairbanks, Alaska

On Sun, 11 Sep 2016, Jeff Bowman wrote:
> But first I have to get it working  :-)
Have you seen 
https://grafenthal.de/wiki/index.php/Installation_Network_UPS_Tools_%28NUT%29_unter_Windows_Server_2012_USB
which shows a working NUT configuration under Windows Server 2012. It's in 
german, but the configuration files are readable.

Roger

> Have you seen
>
https://grafenthal.de/wiki/index.php/Installation_Network_UPS_Tools_%28NUT%29_unter_Windows_Server_2012_USB
> which shows a working NUT configuration under Windows Server 2012. It's
in
> german, but the configuration files are readable.
Thank you for finding that and sending the link. I still can't get NUT to
start listening, though, even with those details.

One difference I did notice...  he's got a libusb.dll file on his system,
where I don't:

https://grafenthal.de/wiki/index.php/Datei:Nut_win_usb_(13).png

I'm looking around, but I'm not finding a place to get that file.
Everything seems to refer/point to libusb0.dll instead.

I also tried reinstalling libUSB using Zadig, but that didn't help either.

I'm at a loss. Do you know where I can find that libusb.dll for Windows?
Their website seems to be down at the moment, so we can't look there.
> Roger
Thanks again,
Jeff Bowman
Fairbanks, Alaska

On Sep 11, 2016, at 3:37 PM, Jeff Bowman <jeff.bowman at intexx.com>
wrote:
> 
>    Using subdriver: APC HID 0.95
> 
> ...and then hangs for 45 seconds before returning to a command prompt. No
UPS hardware information is printed.
It can take about that long to read the descriptors. The non-Windows NUT drivers
will print that message, then return to the command line when they go into the
background (seems similar to your case, if I understand that you ran the
PowerShell process list command after that 45-second wait).

Speaking of which, what version of NUT is this? Given the exact version string,
those without Windows systems can at least look at the source code. I know there
are some differences in the logging, but I don't recall the specifics.

Here's the NUT stack:

UPS <-> Driver (usbhid-ups) <-> Server (upsd) <-> Clients
(upsmon, upsc)

I think you have that first link working (assuming usbhid-ups is still running).
If the server is not running, you can try starting it manually with one or more
"-D" flags to see what is going wrong.

On the other hand, if the driver is only running for that 45 second interval,
you can also run the driver manually with "-D". ("upsdrvctl
start" is primarily a shortcut for systems that stash the drivers out of
$PATH, and also to start multiple drivers in sequence.)

> On Sep 11, 2016, at 3:37 PM, Jeff Bowman <jeff.bowman at intexx.com>
wrote:
> >
> >    Using subdriver: APC HID 0.95
> >
> > ...and then hangs for 45 seconds before returning to a command prompt.
No
> UPS hardware information is printed.
> 
> It can take about that long to read the descriptors. The non-Windows NUT
> drivers will print that message, then return to the command line when they
go
> into the background (seems similar to your case, if I understand that you
ran
> the PowerShell process list command after that 45-second wait).
Yes, that's correct--I ran the PowerShell command after the wait. When I run
it after issuing 'upsdrvctl stop' no processes are listed (as expected).
> Speaking of which, what version of NUT is this?
NUT 2.6.5
> I think you have that first link working (assuming usbhid-ups is still
> running). If the server is not running, you can try starting it manually
with
> one or more "-D" flags to see what is going wrong.
Not much here:

---------------
C:\Users\Admin>upsdrvctl -DD start
Network UPS Tools - UPS driver controller Windows-v2.6.5-5-7-g72f380c
   0.000000
If you're not a NUT core developer, chances are that you're told to
enable debugging
to see why a driver isn't working for you. We're sorry for the
confusion, but this is
the 'upsdrvctl' wrapper, not the driver you're interested in.

Below you'll find one or more lines starting with 'exec:' followed
by an absolute
path to the driver binary and some command line option. This is what the driver
starts and you need to copy and paste that line and append the debug flags to
that
line (less the 'exec:' prefix).

   0.080003     Starting UPS: ups
   0.080003     exec:  C:\Program Files (x86)\NUT\bin/usbhid-ups.exe -a ups
Network UPS Tools - Generic HID driver 0.38 (Windows-v2.6.5-5-7-g72f380c)
USB communication driver 0.32
interrupt pipe disabled (add 'pollonly' flag to 'ups.conf' to
get rid of this message)
Using subdriver: APC HID 0.95
---------------
> On the other hand, if the driver is only running for that 45 second
interval,
> you can also run the driver manually with "-D". ("upsdrvctl
start" is
> primarily a shortcut for systems that stash the drivers out of $PATH, and
> also to start multiple drivers in sequence.)
This looks better. Could it be related to the missing libusb.dll?

---------------
C:\Users\Admin>usbhid-ups.exe -a ups -D
Network UPS Tools - Generic HID driver 0.38 (Windows-v2.6.5-5-7-g72f380c)
USB communication driver 0.32

   0.000000	debug level is '1'
   0.000000	upsdrv_initups...
   0.015634	interrupt pipe disabled (add 'pollonly' flag to
'ups.conf' to get rid of this message)
   0.076421	Using subdriver: APC HID 0.95
   0.076421	Path: UPS.PowerSummary.iProduct, Type: Feature, ReportID: 0x01,
Offset: 0, Size: 8, Value: 2
   0.076421	Path: UPS.PowerSummary.iSerialNumber, Type: Feature, ReportID: 0x02,
Offset: 0, Size: 8, Value: 3
   0.076421	Path: UPS.PowerSummary.iManufacturer, Type: Feature, ReportID: 0x03,
Offset: 0, Size: 8, Value: 1
   0.076421	Path: UPS.PowerSummary.iOEMInformation, Type: Feature, ReportID:
0x04, Offset: 0, Size: 8, Value: 1
   0.076421	Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature, ReportID:
0x05, Offset: 0, Size: 8, Value: 4
   0.076421	Path: UPS.PowerSummary.Rechargeable, Type: Feature, ReportID: 0x06,
Offset: 0, Size: 8, Value: 1
   0.076421	Path: UPS.PowerSummary.CapacityMode, Type: Feature, ReportID: 0x06,
Offset: 8, Size: 8, Value: 2
   0.076421	Path: UPS.PowerSummary.DesignCapacity, Type: Feature, ReportID:
0x0e, Offset: 0, Size: 8, Value: 100
   0.076421	Path: UPS.PowerSummary.FullChargeCapacity, Type: Feature, ReportID:
0x0e, Offset: 8, Size: 8, Value: 100
   0.076421	Path: UPS.PowerSummary.RemainingCapacity, Type: Input, ReportID:
0x0c, Offset: 0, Size: 8, Value: 100
   0.076421	Path: UPS.PowerSummary.RemainingCapacity, Type: Feature, ReportID:
0x0c, Offset: 0, Size: 8, Value: 100
   0.076421	Path: UPS.PowerSummary.CapacityGranularity1, Type: Feature,
ReportID: 0x10, Offset: 0, Size: 8, Value: 1
   0.076421	Path: UPS.PowerSummary.CapacityGranularity2, Type: Feature,
ReportID: 0x10, Offset: 8, Size: 8, Value: 1
   0.076421	Path: UPS.PowerSummary.WarningCapacityLimit, Type: Feature,
ReportID: 0x0f, Offset: 0, Size: 8, Value: 50
   0.076421	Path: UPS.PowerSummary.RemainingCapacityLimit, Type: Feature,
ReportID: 0x11, Offset: 0, Size: 8, Value: 10
   0.076421	Path: UPS.PowerSummary.ManufacturerDate, Type: Feature, ReportID:
0x09, Offset: 0, Size: 16, Value: 18094
   0.076421	Path: UPS.PowerSummary.RunTimeToEmpty, Type: Input, ReportID: 0x0d,
Offset: 0, Size: 16, Value: 4320
   0.076421	Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature, ReportID:
0x0d, Offset: 0, Size: 16, Value: 4320
   0.076421	Path: UPS.PowerSummary.DelayBeforeShutdown, Type: Feature, ReportID:
0x12, Offset: 0, Size: 16, Value: -1
   0.076421	Path: UPS.PowerSummary.DelayBeforeReboot, Type: Feature, ReportID:
0x13, Offset: 0, Size: 24, Value: -1
   0.076421	Path: UPS.PowerSummary.RemainingTimeLimit, Type: Input, ReportID:
0x08, Offset: 0, Size: 16, Value: 120
   0.076421	Path: UPS.PowerSummary.RemainingTimeLimit, Type: Feature, ReportID:
0x08, Offset: 0, Size: 16, Value: 120
   0.076421	Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x0a,
Offset: 0, Size: 16, Value: 24
   0.076421	Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x0b,
Offset: 0, Size: 16, Value: 27
   0.076421	Path: UPS.PowerSummary.AudibleAlarmControl, Type: Input, ReportID:
0x14, Offset: 0, Size: 8, Value: 1
   0.076421	Path: UPS.PowerSummary.AudibleAlarmControl, Type: Feature, ReportID:
0x14, Offset: 0, Size: 8, Value: 1
   0.076421	Path: UPS.PowerSummary.PresentStatus.Charging, Type: Input,
ReportID: 0x07, Offset: 0, Size: 1, Value: 0
   0.076421	Path: UPS.PowerSummary.PresentStatus.Charging, Type: Feature,
ReportID: 0x07, Offset: 0, Size: 1, Value: 0
   0.076421	Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Input,
ReportID: 0x07, Offset: 1, Size: 1, Value: 0
   0.076421	Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Feature,
ReportID: 0x07, Offset: 1, Size: 1, Value: 0
   0.076421	Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input,
ReportID: 0x07, Offset: 2, Size: 1, Value: 1
   0.076421	Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature,
ReportID: 0x07, Offset: 2, Size: 1, Value: 1
   0.076421	Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: Input,
ReportID: 0x07, Offset: 3, Size: 1, Value: 1
   0.076421	Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: Feature,
ReportID: 0x07, Offset: 3, Size: 1, Value: 1
   0.076421	Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit,
Type: Input, ReportID: 0x07, Offset: 4, Size: 1, Value: 0
   0.076421	Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit,
Type: Feature, ReportID: 0x07, Offset: 4, Size: 1, Value: 0
   0.076421	Path: UPS.PowerSummary.PresentStatus.ShutdownRequested, Type: Input,
ReportID: 0x07, Offset: 5, Size: 1, Value: 0
   0.076421	Path: UPS.PowerSummary.PresentStatus.ShutdownRequested, Type:
Feature, ReportID: 0x07, Offset: 5, Size: 1, Value: 0
   0.076421	Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Input,
ReportID: 0x07, Offset: 6, Size: 1, Value: 0
   0.076421	Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type:
Feature, ReportID: 0x07, Offset: 6, Size: 1, Value: 0
   0.076421	Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired,
Type: Input, ReportID: 0x07, Offset: 7, Size: 1, Value: 0
   0.076421	Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired,
Type: Feature, ReportID: 0x07, Offset: 7, Size: 1, Value: 0
   0.076421	Path: UPS.PowerSummary.PresentStatus.CommunicationLost, Type: Input,
ReportID: 0x07, Offset: 8, Size: 1, Value: 0
   0.076421	Path: UPS.PowerSummary.PresentStatus.CommunicationLost, Type:
Feature, ReportID: 0x07, Offset: 8, Size: 1, Value: 0
   0.076421	Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Input,
ReportID: 0x07, Offset: 9, Size: 1, Value: 0
   0.076421	Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Feature,
ReportID: 0x07, Offset: 9, Size: 1, Value: 0
   0.076421	Path: UPS.PowerSummary.PresentStatus.Overload, Type: Input,
ReportID: 0x07, Offset: 10, Size: 1, Value: 0
   0.076421	Path: UPS.PowerSummary.PresentStatus.Overload, Type: Feature,
ReportID: 0x07, Offset: 10, Size: 1, Value: 0
   0.076421	Path: UPS.PowerSummary.PresentStatus.VoltageNotRegulated, Type:
Input, ReportID: 0x07, Offset: 11, Size: 1, Value: 0
   0.076421	Path: UPS.PowerSummary.PresentStatus.VoltageNotRegulated, Type:
Feature, ReportID: 0x07, Offset: 11, Size: 1, Value: 0
   0.076421	Path: UPS.PowerSummary.PresentStatus.ff860080, Type: Input,
ReportID: 0x07, Offset: 12, Size: 1, Value: 0
   0.076421	Path: UPS.PowerSummary.PresentStatus.ff860080, Type: Feature,
ReportID: 0x07, Offset: 12, Size: 1, Value: 0
   0.076421	libusb_get_report: libusb0-dll:err [control_msg] sending control
message failed, win error: A device attached to the system is not functioning.



   0.076421	Can't retrieve Report 89: Input/output error [A device attached
to the system is not functioning. ]
   0.076421	Path: UPS.ff8600fd, Type: Input, ReportID: 0x89, Offset: 0, Size: 8
   0.076421	libusb_get_report: libusb0-dll:err [control_msg] sending control
message failed, win error: A device attached to the system is not functioning.



   0.076421	Can't retrieve Report 90: Input/output error [A device attached
to the system is not functioning. ]
   0.076421	Path: UPS.ff8600fc, Type: Output, ReportID: 0x90, Offset: 0, Size: 8
   0.076421	Path: UPS.ff8600f1, Type: Feature, ReportID: 0x96, Offset: 0, Size:
8, Value: 0
   0.076421	Path: UPS.ff8600f7, Type: Feature, ReportID: 0x8d, Offset: 0, Size:
8, Value: 0
   0.076421	Path: UPS.ff8600f6, Type: Feature, ReportID: 0x8e, Offset: 0, Size:
8, Value: 0
   0.076421	Path: UPS.ff8600f3, Type: Feature, ReportID: 0x93, Offset: 0, Size:
8, Value: 1
   0.076421	Path: UPS.ff8600f2, Type: Feature, ReportID: 0x94, Offset: 0, Size:
8, Value: 1
   0.076421	Path: UPS.ff8600f4, Type: Feature, ReportID: 0x92, Offset: 0, Size:
8, Value: 3
   0.076421	Detected a UPS: American Power Conversion /Smart-UPS C 1000 FW:UPS
10.0 / ID=1005
   0.076421	upsdrv_initinfo...
   0.076421	upsdrv_updateinfo...
   0.076421	Not using interrupt pipe...
   0.076421	Quick update...
   0.076421	upsdrv_updateinfo...
   0.076421	Not using interrupt pipe...
   0.076421	Quick update...
   2.080525	upsdrv_updateinfo...
   2.080525	Not using interrupt pipe...
   2.080525	Quick update...
   4.084411	upsdrv_updateinfo...
   4.084411	Not using interrupt pipe...
   4.084411	Quick update...
   6.085311	upsdrv_updateinfo...
   6.085311	Not using interrupt pipe...
   6.085311	Quick update...
   8.085513	upsdrv_updateinfo...
   8.085513	Not using interrupt pipe...
   8.085513	Quick update...
  10.085726	upsdrv_updateinfo...
  10.085726	Not using interrupt pipe...
  10.085726	Quick update...
  12.085875	upsdrv_updateinfo...
  12.085875	Not using interrupt pipe...
  12.085875	Quick update...
  14.099848	upsdrv_updateinfo...
  14.099848	Not using interrupt pipe...
  14.099848	Quick update...
  16.104959	upsdrv_updateinfo...
  16.104959	Not using interrupt pipe...
  16.104959	Quick update...
  18.113727	upsdrv_updateinfo...
  18.113727	Not using interrupt pipe...
  18.113727	Quick update...
  20.113867	upsdrv_updateinfo...
  20.113867	Not using interrupt pipe...
  20.113867	Quick update...
  20.858772	upsdrv_cleanup...
^C
---------------