similar to: Simple UpsTray client for Windows

Dear NUT users, New ViB package version 1.3.0 for VMware 5.x has been released. What's new : - Nut upgraded to 2.7.2 - Multiple ups support. You can provide an UPS at NUT_server list in the NutUpsName vmware UserVars. Use space as a separator. NUT client will initiate a shutdown when that last standing UPS goes low batt. All UPS at NUT_server have to use the same user/password. Description

The purpose of this posting is to summarize the FreeBSD installation procedure from the beginning till the very end. 1. Follow the instructions provided in the How-To prepared by Thierry Thomas (http://people.freebsd.org/~thierry/nut_FreeBSD_HowTo.txt). Please note the following: a) if you are using an USB device, as of NUT 2.2 usbhid-ups completely replaces the legacy hidups driver and provides

Hi, I am trying to get NUT 2.7.2 working on my Solaris 11.2 system with a PowerWalker 2000 VI PSW UPS. I have carefully configured the software such that it 'works' using custom values in the ups.conf file: driver = nutdrv_qx port = auto desc = "my UPS" protocol = voltronic-qs subdriver = cypress vendorid = 0665 productid = 5161 The problem I'm experiencing is that after a

On Apr 4, 2015, at 7:19 PM, Richard Flint <richard.flint at gmail.com> wrote: > More extensive debugging by running the driver sudo ./nutdrv_qx -u root -a MY_UPS -DDDDDD indicates the driver works normally then will randomly stop working at stop "send: QS". The debug logs show values successfully retrieved repeatedly until something like: > .... > Quick update... >

On Tue, 13 Oct 2015, Davide Baldini wrote: > Guess I can assume that my OnePower A03-S1001 just doesn't support the > shutdown command. Might this be the case? If the UPS does shut down, then it will have to do so after a delay and not immediately on receiving the shutdown command. Does upsc <ups_name> report anything like ups.delay.shutdown: 30 ups.delay.start: 40

Hello Arno, FreeNAS doesn't come with a compiler and I had to compile with the patch on FreebBSD-9.3 and then copy the produced mge-shut. Unfortunately it didn't work out. For every try I was getting "Connection Refused" and when I tried /usr/local/libexec/nut/mge-shut -D -a <ups_name> I was always getting 'No matching HID UPS found'. I returned back to the

Arjen, All, I need help unwrapping my head from around the problem of getting nut running on the same machine it runs fine with on another drive!! Sound easy -- not here :) I have network-ups-tools 2.4.1-2 on two servers. On one server I had a raid drive fail (which I'm still booting from and running nut on just fine). I bought a second pair of drives to establish a new array in the

Hi, I'm trying to get a sweex ups working with nut on debian sarge. This one: http://www.sweex.com/producten.php?lang=1&%20sectie=&item=59&artikel=95 It's shipped with UPSmart and according to the compatibility list it should work with the genericups upstype=7 driver. But it doesn't. I get: mybox:/etc/nut# /etc/init.d/nut start Starting Network UPS Tools: (upsdrvctl

Hi. I'm from Russia. I try to use NUT with PowerWalker vi 400 se (usb). I use FreeBSD 7.0 (amd64) and megatec_usb driver. Settingup the NUT with FreeBSD installation procedure (Thierry Thomas, from FreeBSD). PowerWalker connect to the computer by usb cable on port usb0 (uhib0). NUT don't starting, and talk to me that supporting device not found. Please, help me. Thank's! With best

Hi, Does anyone have a similar configuration or have used the same model with Ubuntu before with success? Strange my system can't seem to detect the UPS and I can see usbhid 2-1.1:1.0: couldn't find an input interrupt endpoint in dmesg when I plug in the UPS. Hope can share your experience on this.

Hi all, After my last post to this list asking about an UNDI packet driver, I received quite a few responses - one in particular from Ilya Dedinsky who provided me with quite a few useful shims to do this and more. I also had a few requests from people asking me whether I found anything, so I have done up a web page with all the shims on it in case anyone else needs them. The page is at:

On Windows 2008r2, Network UPS tools isn't starting (netstat doesn't show anything on port 3493, and WinNutClient won't connect). I eventually tried running c:\program files (x86)\NUT\bin\nut.exe -N in a command prompt window and it reports the following: -------------------------------------------------------------------------------------------------------------- C:\Program Files

Thank you for the rapid response. I will try and investigate getting answers to some of your points but I'm a little new to Solaris so I'll need some time. Glancing at the configure output, it looks like it built against v0.1.7 of libusb (yes i think that is derived from the one you mention), checking for libusb version via pkg-config... 0.1.7 found checking for libusb cflags... checking

Thanks Dan and Charles - I've found the usb passthrough will be a non-starter (not supported on my host). Dan - is your recommendation to build Nut from source or just the driver? I'm trying to build the whole project but am obviously missing dependencies... I've come across a configure error syntax error near unexpected token `CPPUNIT,' which I've seen in a previous

I changed the driver from blazer_usb to nutdrv_qx, by editing /etc/nut/ups.conf. To apply changes, I did: # service nut-server restart # service nut-client restart Then I've run a second test, this time simpler than the first one described in my previous email; the test only consists in toggling off/on a wall switch which controls power to the UPS. This way, electric ground remains

Hi, I have used the truss command as directed. I have attached both the driver output and the last few sections of truss output leading to the hang. Both outputs end at the CTRL+C i pressed when i was forced to end the processes. Hope this is helpful. Please bear with me if i didn't run it with the right options etc - as I mentioned, I'm a little new to Solaris. Regards, Richard On

Hi, all! Actually I have two questions for a same reason: I want to share my NUT to my LAN, or read UPS from remote device. /**************** firstly *****************/ I downloaded tcp-wrapper, but NUT could not detected it. Previously I successfully configured and make NUT into my embedded system. It worked and UPS is recognized. I downloaded tcp-wrapper (Ver 7.6, most files in the package

On Jan 2, 2015, at 4:27 PM, Mike Raath <raathm at gmail.com> wrote: > Maybe usbpassthrough is something I should look at? I'll do some reading. You may have found this already, but this (plus the followup KB item #1021345) seems to imply that you can bind the USB-to-serial adapter to the NUT VM:

I have an XP Pro box on my LAN, and I'm trying to figure out why nmblookup '*' can't see it. I'm writing a script that finds all the shares on the LAN and mounts them, and it works great except for this one box. On another windows box, when I run "net view", the XP box is listed as I expect. On my linux box, when I run "nmblookup -A 192.168.0.111" it

Hello Arno, Can apply the patch directly or should I recompile nut? Best regards, Panagiotis On 3/4/2015 5:06 ??, Arnaud Quette wrote: > Hello Panagiotis > > 2015-04-03 14:28 GMT+02:00 Panagiotis Kritikakos > <panagiotis.kritikakos at nikitec.gr > <mailto:panagiotis.kritikakos at nikitec.gr>>: > > Hello Arno, > > Question: have you also