"failed to claim USB device: Permission denied" error #2266
Labels
impacts-release-2.7.4
Issues reported against NUT release 2.7.4 (maybe vanilla or with minor packaging tweaks)
impacts-release-2.8.1
Issues reported against NUT release 2.8.1 (maybe vanilla or with minor packaging tweaks)
macOS
Qx protocol driver
Driver based on Megatec Q<number> such as new nutdrv_qx, or obsoleted blazer and some others
USB
Comments
|
So I got a little smarter and found out there's a macosx-ups driver, so I tried that one in the homebrew install. It initially complained about the runtimecal and chargetime parameters in the config (since it doesn't support them). I commented those out, but the macosx-ups driver just doesn't even see the UPS. So nutdrv_qx can see and ID the UPS, but can't connect to it, and macosx-ups could probably connect to it, but can't see or ID it. |
|
The Mac does "see" the UPS, but has no ability to control it; i.e. the standard UPS controls don't appear in System Settings. So it doesn't appear to be a cable issue.
|
jimklimov
added
USB
macOS
Qx protocol driver
|
I believe In the "real" driver logs, I am concerned by Per your log for 2.8.1 it was Also not sure if some What can help at least temporarily is to add |
|
CC @clepple : just in case, got any more ideas to add here? :) |
|
Added user=root to the config, that seems to have helped. Now seeing if I can get upsmon working. |
|
@jimklimov no idea, sorry. I don't think there is an equivalent of In general, I don't really know what else to do with random libusb errors on macOS, especially when sending stuff works one minute, yields some data, and stops working seconds later. libusb-0.1 had a |
|
A QX driver's I/O error for In any case, to try this code (merged not long ago) you'd need a build of NUT from git master branch, see https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests - note you don't have to actually install the custom build over existing NUT just for dev/testing. You can later install over that if the result is good :) |
|
I followed the instructions at the link provided, using the same config flags as the default homebrew install. The result looks pretty similar. From what the driver is spitting out, is this going to cause upsd and upsmon to fail as well? When I fire up everything, neither one is happy, and I want to be sure it's not just a stupid configuration mistake. |
|
Let's make sure I'm doing this right. The script I'm using to start the custom build (and executing via sudo) is: The upsd startup either never completes or doesn't go to background, because upsmon never starts. The output I'm seeing from this is: |
|
Every now and then I see this: |
|
And hang on, but it looks like upsmon is talking too (finally started it separately): |
|
Oddly enough, if I try to start nutdrv_qx using upsdrvctl, it fails, but if I start it directly, it works. At any rate, I have a working setup at this point. The trick seems to be installing the latest build per Jim's link above, but using the same config options as homebrew uses (see https://formulae.brew.sh/formula/nut). Many, many thanks to @jimklimov and @clepple for the assist. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Note: this UPS was previously connected & working with NUT on an RPi using nutdrv_qx, and I set up the same config on macOS 14.2.1. I tried NUT 2.7.4 via MacPorts and NUT 2.8.1 via Homebrew.
The driver obviously sees the device, as does macOS System Profiler, and although macOS has no built-in capability for this particular UPS, for some reason the kernel isn't releasing it.
NUT 2.8.1 via Homebrew has the same issue.
The text was updated successfully, but these errors were encountered: