Need Help with Windows NUT Server install #2598
Comments
jimklimov
added
question
Windows
USB
impacts-release-2.7.3-or-older
|
Hello, the 2.6.5 baseline is very old (Aug 2012, so ~12 years now), although unfortunately it is what the MSI installer was made from and now the community knowledge about that arcane magic got a bit lost. I am not certain which exact commits went into that package file, but The NUT for Windows effort was revived a couple of years back, so there are builds of current codebase being built by Appveyor CI, with downloadable archives (no installer yet) as detailed at https://github.com/networkupstools/nut/wiki/NUT-for-Windows You may still need a few tricks about getting libusb based drivers seen, as commented there. With your existing installation, please see if a |
|
Thanks for your help! do you happen to know if there will be an installer soonish (before I try to force this to work?), I can survive for the short term if its "coming soon". Also riello_ups.exe doesn't exist in the install. |
|
Unfortunately, probably not "soonish" -- needs some time from a determined developer to make it all come together on the platform, maybe with same or a different packaging technology. I had some interest about portable code base to get that it buildable and testable on the platform, and eventually merged, but struggled to find time for the finishing touches like the packager or certain known-missing equivalent code blocks. |
Sorry, I fat-fingered - |
|
Hmm, so not sure how I should proceed... |
|
Re-check if that driver is at all present in the old package you have; then we might try to somehow get it running and at least check if it sees your UPS. Otherwise forgo the package and try to use the archived installation prepared by CI farm, per wiki. |
|
I can confirm there is no file that starts with 'rie' in the 'NUT' folder structure, where is the archived installation located please? (sorry I feel like i'm missing something here)... Thanks |
|
Per https://github.com/networkupstools/nut/wiki/NUT-for-Windows
I've updated it with a screenshot to help navigate now. |
|
Hiya,
Yeah, I think I'm going to look at other options for this like hosting NUT
on a Lite Linux system.
Thanks for your help though!
…On Thu, 22 Aug 2024 at 09:30, Jim Klimov ***@***.***> wrote:
Per https://github.com/networkupstools/nut/wiki/NUT-for-Windows
Current NUT for Windows archives from CI are available at
https://ci.appveyor.com/project/nut-travis/nut/build/artifacts - note
this is a rolling URL for a "latest" build that may include PR checks; for
a somewhat-stable codebase (PR merges to "master" branch) one needs to open
the "History" tab (NOT "Current build") and find the newest AppVeyor build
link from a green-ticked commit at
https://github.com/networkupstools/nut/commits/master history. In
AppVeyor Web UI, a master-branch build would have a small gray comment with
only "master" branch name and a commit ID, without another branch name and
commit as is done for pull request builds (they also have a gray title to
that effect).
I've updated it with a screenshot to help navigate now.
—
Reply to this email directly, view it on GitHub
<#2598 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BKVAGHZ7LYWZRQRZTDLUW63ZSWORTAVCNFSM6AAAAABM2AWX4CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBUGA4DGNJVHA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
The information in this email may be privileged or confidential and is
solely for the use of the intended recipient(s). If you receive this email
in error, please notify the sender and delete the email in its entirety
from your system immediately. In such circumstances, you must not make use
of the email or its contents.
Views expressed by the sender do not
necessarily reflect the views of TCF Group or its subsidiaries.
|
|
At the moment that may be more flexible and functional :) But if you do try Windows builds - would be great to hear how it went in real life :) |
|
I'd love to hear once the install is on a Microsoft install package :-) |
|
I was able to install the NUT server on a Windows 7 machine successfully. I believe the instructions would be similar for Windows 10 with minor variations. I used the this build: NUT-for-Windows-x86_64-SNAPSHOT-2.8.2.2096-master. In order to run the server I had to learn about libusb-win32 driver and all that comes with the installation using zadig-2.9.exe. In the end the driver from CyperPower (CP1500PFCLCD) was replaced with the libusb-win32 driver. It was a painful learning curve to figure out how to hijack the existing UPS USB Driver using libusb-win32. Before installing NUT, I have never heard of libusb-win32 or the zadig-2.9.exe that is used replace the driver from CyperPower (CP1500PFCLCD) with the libusb-win32 driver.
The only remaining mystery that I cannot figure out is whether upsdrvctl is supposed to self-terminate after it has started the usbhid-ups.exe process or whether it is supposed to hang around (doing what?). It states that it will exit but the console window hangs around. I can minimize it to the taskbar but it would be nice to have it go away if it is finished starting usbhid-ups.exe in another process space that it appears to be doing. This is what the console shows after executing upsdrvctl in a console. Network UPS Tools upsdrvctl - UPS driver controller 2.8.2.986.9-995-g943ed3c06 (development iteration after 2.8.2) I am starting it via the Task Scheduler but you could likely just drag a shortcut to a batch file into the Startup folder to accomplish the same thing. Note that Task Scheduler under Windows 7 has issues with starting batch processes that I can cover in a write-up. The Windows netclient is a breeze to set up on Windows 10 having set up Linux and MacOS NUT packages in the past. It took only a few minutes and it was up and running. Windows 7 is not so nice and several issues prevent a successful installation. I spent a good part of a day debugging it. As for an installer, really the only thing that is needed is to create the C:\Program Files\NUT folder and copy the files to it. After that, it should update the system PATH (add - C:\Program Files\NUT\bin and C:\Program Files\NUT\sbin). I may do an installation write-up for how to use the Windows NUT package for Windows 7 and Windows 10. If I decide to do so, where could I post it? Can I add to your Wiki page? |
|
I should have added this comment. If you launch upsdrvctl from a .cmd file (Windows batch file) and close the console from which upsdrvctl is executing (and reportedly 'finished'), you will get an error message and the usbhid-ups.exe has crashed. My guess is that the usbhid-ups.exe is spawned as a child process of upsdrvctl.exe (or of the .cmd) rather than opening a new process environment. I have also tested launching upsdrvctl.exe directly from Task Scheduler with the same result. Before closing the console (or taskeng window):
After the close:
|
|
Sounds great, thanks for the report. A Wiki page (maybe a new one linked from the one you mentioned) would be also great! :) While at it, can you please check the |
Hi Everyone,
So the issue I have is when I install NUT-Installer-2.6.5-6.exe as admin I get the error message:-
NUT UPS driver installer.
Searching for known UPS...
No known UPS device found.
Try installing libUSB manually.
Hit enter to continue
I get the same error is I manually run wdi-simple.exe
The system is Windows 11 Pro with 23H2 and Intel(R) Core(TM) i7-10700KF CPU with 16.0 GB Memory (Mainboard is Gigabyte H410M H V2).
The UPS is a Riello Sentinel Dual 4kVA SDU 4000 and is connected via USB (this all works fine in the PowerShield software they suggest using). I've looked into this and tried to 'install' libUSB but this seems to be a a folder with "files" in it but no exe file to 'install' from looking at the NUT site it suggests that SDU 4000 is compatible using the [riello_usb] driver https://networkupstools.org/docs/man/riello_usb.html)
I'm not sure exactly what I need to do to get the NUT install to use the riello_usb and get the software to see the UPS.
Thank you so much if you can help and i'm sorry if this seems an obvious question.
The text was updated successfully, but these errors were encountered: