search for: claim_interfac

...ut itself down, thereby allowing the server enough time to safely > > shut itself down as well? > > Yes. Very good, thank you. > The command is "upsdrvctl shutdown". That's what I thought, but I get this: 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) I don't know why it thinks I'm trying to start the driver. > The 300 seconds start when the effect of "upsdrvctl shutdown" reaches the UPS > hardware....

...n source fashion, I hacked at it till it worked. Couple things in this pull request: 1. Scale values for some of the SMART1500LCD parameters. 2. With my hardware and kernel, usbhid-ups wouldn't run more than 10 minutes before exiting with a fatal error. This seems to be related to holding usb_claim_interface() the entire life of the program. I've refactored claim_interface/release_interface calls to be around only when work is being done. Now usbhid-ups has run for 24+ hours without issue. 3. The very nature of USB in a home means that sometimes the driver will lose communications with the UPS (a...

...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.087000 Driver failed to start (exit status=1) If the problem is that interface 0 is in use is there a way to direct the NUT driver to claim a different interface? Is that even the right question to ask? I'...

...caused error: "GenerateConsoleCtrlEvent error : 87". Issuing usbhid-ups -a ups1 or usbhid-ups -a ups2 works, but 1. exclusively - I can see only one UPS at a time (trying to run second ups while the first is running gives: "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) 2. randomly - This means that no matter what I put into ups.conf NUT will pick anything that responds first. which eventually is useless. Thus my question is whether it is an error of usblib or NUT's usbhid-ups and...

...intermediate level of understanding; thus it's still quite a bit over my head. Your patience and slow explanations are appreciated. I presently have four issues: 1. CLI error: I get an error when running 'upsdrvctl start': "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." 2. Event log errors: As noted the service starts fine, but I'm getting these two errors on service stop--"Error stopping upsd (2)" and "Error stopping upsmon (2)." 3. I don't understand wha...

...ed at it till it worked. Couple things in this pull request: > > 1. Scale values for some of the SMART1500LCD parameters. Thanks! > 2. With my hardware and kernel, usbhid-ups wouldn't run more than 10 minutes before exiting with a fatal error. This seems to be related to holding usb_claim_interface() the entire life of the program. I've refactored claim_interface/release_interface calls to be around only when work is being done. Now usbhid-ups has run for 24+ hours without issue. Given how long we have been running with code that claims the interface at driver startup, I am a wary about...

I'm facing a looming deadline for getting this working, so I'm hoping someone experienced can weigh in on this. I'm getting errors in the Event Log when stopping the service: 1. Error stopping upsd (2) 2. Error stopping upsmon (2) Is there a detailed log somewhere? How can I track this down and find out what they mean? Or does someone know? Also, these three commands result in

On Oct 5, 2016, at 10:59 PM, Jeff Bowman wrote: > >> The command is "upsdrvctl shutdown". > > That's what I thought, but I get this: > > 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) > > I don't know why it thinks I'm trying to start the driver. > The "upsdrvctl shutdown" command is designed to be run late in the shutd...

...safely >>> shut itself down as well? >> >> Yes. > > Very good, thank you. > > > >> The command is "upsdrvctl shutdown". > > That's what I thought, but I get this: > > 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) > [snip] I have found the shutdown delay to be quite elusive within the NUT realm. I have asked for the kind folk of this mailing list to post those UPS's...

Thank you VERY much, Roger, for your detailed explanations. I'm going to choose to heed your warning. > On Thu, 8 Sep 2016, Jeff Bowman wrote: > > > 1. CLI error: I get an error when running ?upsdrvctl start?: ?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.? The solution to this was easy: the conflict occurred because the service was running. Apparently NUT.exe on Windows runs all of the preparatory commands, one of which is 'upsdrvctl start.' > > 2. Event...

...here tend to assume at least an > intermediate level of understanding; thus it?s still quite a bit over my head. Your patience and slow explanations are appreciated. > > 1. CLI error: I get an error when running ?upsdrvctl start?: ?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.? > > 2. Event log errors: As noted the service starts fine, but I?m getting these two errors on service stop--?Error stopping upsd (2)? and ?Error stopping > upsmon (2).? > > 3. I don?t understand what...

I'm trying to better understand OffDelay and OnDelay: http://networkupstools.org/docs/man/usbhid-ups.html#_extra_arguments My server requires ~3? minutes to shut itself down. Considering this I'm comfortable setting OffDelay to 300 (five minutes). How does this work in conjunction with the UPS hardware? Does NUT immediately send a command to the UPS to wait for 300 seconds and then shut

...ly 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 d...