search for: g72f380c

...(Wonderful thing, that WayBack Machine.) I decided on the latest x86 version available there, openssl-1.0.2h-i386-win32.zip. I extracted the two files, LIBEAY32.dll and SSLEAY32.dll, to .\NUT\bin and tried upsd again. Success! C:\Users\Admin>upsd Network UPS Tools upsd Windows-v2.6.5-5-7-g72f380c listening on 127.0.0.1 port 3493 Connected to UPS [ups]: usbhid-ups-ups ...and this: C:\Users\Admin>upsmon Network UPS Tools upsmon Windows-v2.6.5-5-7-g72f380c UPS: ups at localhost (master) (power value 1) Using power down flag file C:\killpower ...and this: C:\Users\Admin>...

...sbhid-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...

...driver = usbhid-ups port = auto # vendorid = 051D desc = "UPS-0031" When I try to run UPSDRVCTL this is what I get: C:\Program Files (x86)\NUT\bin>upsdrvctl -D start Network UPS Tools - UPS driver controller Windows-v2.6.5-5-7-g72f380c 0.000000 Starting UPS: UPS-0031 Network UPS Tools - Generic HID driver 0.38 (Windows-v2.6.5-5-7-g72f380c) USB communication driver 0.32 Can't claim USB device [051d:0002]: libusb0-dll:err [claim_interface] could not claim interface 0, win error: The requested resource is in use. 0.08...

...---------------------------------------------------------------------------------------- C:\Program Files (x86)\NUT\bin>nut.exe -N Running in non-service mode EventLog : Starting EventLog : Starting drivers EventLog : Starting upsd Network UPS Tools - UPS driver controller Windows-v2.6.5-5-7-g72f380c Can't start C:\Program Files (x86)\NUT\bin/(null).exe: No such file or directory [The system cannot find the file specified. ] EventLog : Starting upsmon ------------------------------------------------------------------------------------------------------------------ I installed it with NUT...

...t; So this all represents significant progress. But we're not out of the woods yet. > > When I run 'upsdrvctl start' I still get the 45-second hang and then only this: > > C:\Users\Admin>upsdrvctl start > Network UPS Tools - UPS driver controller Windows-v2.6.5-5-7-g72f380c > 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 > > It doesn't display the...

...2012 R2 NUT-Version: Windows-v2.6.5-6 UPS: APC SC 1500VA Driver: apcsmart upsdrvctl.exe start outputs this errors: ---------------------------------------------------------------------------------------------------------------- Network UPS Tools - APC Smart protocol driver 3.1 (Windows-v2.6.5-5-7-g72f380c) APC command table version 3.1 w32_serial_open (COM4) setting initial state on COM4 000000A8 = w32_serial_open (COM4) Warning: no locking method is available: No error [Der Vorgang wurde erfolgreich beendet. ] vmin_ 0, vtime_ 0 action 0 vtime 0, vmin 1 ReadTotalTimeoutConstant -2, ReadIntervalTime...

...sponse: APPCRASH Response: Not available Cab ID: 0 P1: snmp-ups.exe P2: 0.0.0.0 P3: 5317277b P4: libnetsnmp-30.dll P5: 0.0.0.0 P6: 4f9128b9 P7: c0000005 P8: 000053e1 P9: P10: C:\Program Files (x86)\NUT\bin>snmp-ups.exe -a ups Network UPS Tools - Generic SNMP UPS driver 0.70 (Windows-v2.6.5-5-7-g72f380c) No matching MIB found for sysOID '.1.3.6.1.4.1.8072.3.2.10'! Please report it to NUT developers, with an 'upsc' output for your device. Going back to the classic MIB detection method. => Same error and entry in eventlog Any idea how to fix this and get the things work? Greeti...

> 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

Hello. I have problem with connecting to APC SC1000 using NUT port for windows 2.6.5-6. Last working version is NUT 2.6.1-1. With the same config files it works well. c:\NUT\bin>apcsmart.exe -a SC1000 Network UPS Tools - APC Smart protocol driver 3.1 (Windows-v2.6.5-5-7-g72f380c) APC command table version 3.1 w32_serial_open (COM3) setting initial state on COM3 0000007C = w32_serial_open (COM3) Warning: no locking method is available: No error [+?????? ??????? ?????????. ] vmin_ 0, vtime_ 0 action 0 vtime 0, vmin 1 ReadTotalTimeoutConstant -2, ReadIntervalTimeout -1, Re...

...1 os build 10586.29 nut 2.6.5-6 windows binary package device ups: poweron vs 950 when I do testing shutdown it does not shutdown. Thank's. driver debug output: C:\Program Files (x86)\NUT\bin>blazer_usb -DD -a myups Network UPS Tools - Megatec/Q1 protocol USB driver 0.10 (Windows-v2.6.5-5-7-g72f380c) 0.000000 debug level is '2' 0.000000 Checking device (0665/5161) (bus-0/\\.\libusb0-0001--0x0665-0x5161) 0.000000 - VendorID: 0665 0.000000 - ProductID: 5161 0.000000 - Manufacturer: unknown 0.000000 - Product: USB to Serial 0.000000 - Seria...

...This looks better. Could it be related to the missing libusb.dll? > Agreed that it looks better, but it wouldn't get that far if it didn't have the proper libusb files. > C:\Users\Admin>usbhid-ups.exe -a ups -D > Network UPS Tools - Generic HID driver 0.38 (Windows-v2.6.5-5-7-g72f380c) The last part is what tells us exactly where to look. Incidentally, that means there was another release (v2.6.5-6...) after the version you have. The version string looks like a mess, but it's the "Windows" branch, based on the main NUT v2.6.5 codebase, 5th release (but the 7th Git...