Nut upsuser - Dec 2013 - (newb) Installing on windows w/Eaton 5110.

I like to think of myself as reasonably intelligent when it comes to
systems (MS in Comp Sci, albeit a few hundred moons ago), but I seem to
be missing something when it comes to installing NUT on a 64 bit windows
XP system.

I downloaded and attempted it install but the installer said I needed
to install libusb manually.  So I went and grabbed that, unpacked the
ZIP file and ran the x86/install-filter and re-ran the installation.

Running nut-scanner finds the UPS but
-------------
Cannot load NUT library (libupsclient) : The specified module could not
be found .. NUT search disabled.
Scanning USB bus.
No start IP, skipping SNMP
Scanning XML/HTTP bus.
[nutdev1]
        driver = "bcmxcp_usb"
        port = "auto"
        vendorid = "0592"
        productid = "0002"
        product = "Powerware UPS"
        bus = "bus-0"

This application has requested the Runtime to terminate it in an
unusual way. Please contact the application's support team for more
information.

This application has requested the Runtime to terminate it in an
unusual way. Please contact the application's support team for more
information.
------------

upsdrvctl stop and start don't complain...

------------
C:\Program Files (x86)\NUT\bin>upsdrvctl stop
Network UPS Tools - UPS driver controller 2.6.5-3723:3731M

C:\Program Files (x86)\NUT\bin>upsdrvctl start
Network UPS Tools - UPS driver controller 2.6.5-3723:3731M

C:\Program Files (x86)\NUT\bin>Network UPS Tools - BCMXCP UPS driver
0.26 (2.6.5 -3723:3731M)
USB communication subdriver 0.21
-------------

But many other commands complain...

-------------
C:\Program Files (x86)\NUT\bin>upsc nutdev1
Error: Connection failure: Unknown error
-------------

which makes me think I probably missed a step...  Any hints would be
most appreciated.

For what it's worth, the 'system' is a host with several 'vmware
player' VMs running on it. The eventual goal would be to have the host
running as a nut server and have each of the VMs running a nut client
so they can shut themselves down gracefully in the event of a longer
power outage.

Thanks again,
Bruce

-- 
+-------------------+---------------------------------------------------+
Bruce Bowler        | You can't hold a man down without staying down
1.207.315.2567 x503 | with him. 
bbowler at bigelow.org | - Booker T. Washington 
+-------------------+---------------------------------------------------+

On Dec 17, 2013, at 12:45 PM, Bruce Bowler wrote:
> upsdrvctl stop and start don't complain...
> 
> ------------
> C:\Program Files (x86)\NUT\bin>upsdrvctl stop
> Network UPS Tools - UPS driver controller 2.6.5-3723:3731M
> 
> C:\Program Files (x86)\NUT\bin>upsdrvctl start
> Network UPS Tools - UPS driver controller 2.6.5-3723:3731M
> 
> C:\Program Files (x86)\NUT\bin>Network UPS Tools - BCMXCP UPS driver
> 0.26 (2.6.5 -3723:3731M)
> USB communication subdriver 0.21
> -------------
I'm not sure how this works on the Windows port, but you also need upsd
running.

This diagram shows how the pieces go together:

http://www.networkupstools.org/docs/developer-guide.chunked/ar01s02.html#_the_layering
> But many other commands complain...
> 
> -------------
> C:\Program Files (x86)\NUT\bin>upsc nutdev1
> Error: Connection failure: Unknown error
> -------------
upsdrvctl seems to have successfully started the bcmxcp_usb driver, but for upsc
to get data from the driver, it needs to go through upsd. If you have a TCP port
listening on 3493, then upsd is running.
> For what it's worth, the 'system' is a host with several
'vmware
> player' VMs running on it. The eventual goal would be to have the host
> running as a nut server and have each of the VMs running a nut client
> so they can shut themselves down gracefully in the event of a longer
> power outage.

Makes sense. Depending on how long a shutdown/startup cycle takes, it could be
useful to suspend the VMs.

-- 
Charles Lepple
clepple at gmail

On Thu, 19 Dec 2013 08:51:04 -0500
Charles Lepple <clepple at gmail.com> wrote:
> On Dec 17, 2013, at 12:45 PM, Bruce Bowler wrote:
> 
> > upsdrvctl stop and start don't complain...
> > 
> > ------------
> > C:\Program Files (x86)\NUT\bin>upsdrvctl stop
> > Network UPS Tools - UPS driver controller 2.6.5-3723:3731M
> > 
> > C:\Program Files (x86)\NUT\bin>upsdrvctl start
> > Network UPS Tools - UPS driver controller 2.6.5-3723:3731M
> > 
> > C:\Program Files (x86)\NUT\bin>Network UPS Tools - BCMXCP UPS
driver
> > 0.26 (2.6.5 -3723:3731M)
> > USB communication subdriver 0.21
> > -------------
> 
> I'm not sure how this works on the Windows port, but you also need
> upsd running.
> 
> This diagram shows how the pieces go together:
> 
>
http://www.networkupstools.org/docs/developer-guide.chunked/ar01s02.html#_the_layering
> 
> > But many other commands complain...
> > 
> > -------------
> > C:\Program Files (x86)\NUT\bin>upsc nutdev1
> > Error: Connection failure: Unknown error
> > -------------
> 
> upsdrvctl seems to have successfully started the bcmxcp_usb driver,
> but for upsc to get data from the driver, it needs to go through
> upsd. If you have a TCP port listening on 3493, then upsd is running.
> 
> > For what it's worth, the 'system' is a host with several
'vmware
> > player' VMs running on it. The eventual goal would be to have the
> > host running as a nut server and have each of the VMs running a nut
> > client so they can shut themselves down gracefully in the event of
> > a longer power outage.
> 
> 
> Makes sense. Depending on how long a shutdown/startup cycle takes, it
> could be useful to suspend the VMs.
> 
Thanks for the pointers.  I'll poke around a bit about upsd and see
what turns up.  

Bruce

-- 
+-------------------+---------------------------------------------------+
Bruce Bowler        | Idealism is what precedes experience;cynicism is
1.207.315.2567 x503 | what follows. 
bbowler at bigelow.org | - David T. Wolf 
+-------------------+---------------------------------------------------+