[Nut-upsuser] Eco Eclipse 1600 connects via USB put does not put out any data:

Stefan Schumacher stefanschumacheratwork at gmail.com
Fri Jul 5 14:39:41 BST 2024


Hi Greg

Yes, Debian's Nut is old. Even Sid has only 2.8.1. I will build the
current release (2.82) and see if this brings any improvement. If not
I will have to compile the git master also, also I am cautious about
building bleeding edge software when it has the potential to suddenly
shut down my main server. I will report back after building 2.8.2

Yours
Stefan

Am Fr., 5. Juli 2024 um 15:12 Uhr schrieb Greg Troxel via Nut-upsuser
<nut-upsuser at alioth-lists.debian.net>:
>
> Stefan Schumacher via Nut-upsuser <nut-upsuser at alioth-lists.debian.net>
> writes:
>
> > I am using: Debian Bookworm 12.6 with these packages, which were
> > installed from the official Debian Repository.
> > ii  nut                             2.8.0-7
> >   all          network UPS tools - metapackage
> > ii  nut-client                      2.8.0-7
> >   amd64        network UPS tools - clients
> > ii  nut-server                      2.8.0-7
> >   amd64        network UPS tools - core system
>
>
> Your mail is mangled.  Lines longer than 72 characters which are
> logs/config/output etc. should not be wrapped.
>
> But, I can tell that Debian has old nut.  My system has 2.8.2.  And
> there are changes in git master since then.   I'm not the maintainer,
> but for projects where I have a maintainer role, I expect the first
> step is updating to the latest release if not from git.
>
> > root at mars:/usr/lib/nut# ./usbhid-ups -DD -a Eaton
> > Network UPS Tools - Generic HID driver 0.47 (2.8.0)
> > USB communication driver (libusb 1.0) 0.43
> >    0.000000     [D1] debug level is '2'
> >    0.001566     [D2] Initializing an USB-connected UPS with library
> > libusb-1.0.26 (API: 0x1000109) (NUT subdriver name='USB communication
> > driver (libusb 1.0)' >
> >    0.001575     [D1] upsdrv_initups (non-SHUT)...
> >    0.004892     [D2] Checking device 1 of 7 (1D6B/0003)
> >    0.004908     [D1] Failed to open device (1D6B/0003), skipping:
> > Access denied (insufficient permissions)
> >    0.004911     [D2] Checking device 2 of 7 (0BDA/5452)
> >    0.004917     [D1] Failed to open device (0BDA/5452), skipping:
> > Access denied (insufficient permissions)
> >    0.004921     [D2] Checking device 3 of 7 (1D6B/0002)
> >    0.004926     [D1] Failed to open device (1D6B/0002), skipping:
> > Access denied (insufficient permissions)
> >    0.004929     [D2] Checking device 4 of 7 (1D6B/0003)
> >    0.004937     [D1] Failed to open device (1D6B/0003), skipping:
> > Access denied (insufficient permissions)
> >    0.004941     [D2] Checking device 5 of 7 (0463/FFFF)
> >    0.463157     [D2] - VendorID: 0463
> >    0.463198     [D2] - ProductID: ffff
> >    0.463215     [D2] - Manufacturer: EATON
> >    0.463231     [D2] - Product: Ellipse ECO
> >    0.463249     [D2] - Serial Number: 000000000
> >    0.463268     [D2] - Bus: 001
> >    0.463287     [D2] - Device: unknown
> >    0.463314     [D2] - Device release number: 0100
> >    0.463332     [D2] Trying to match device
> >    0.463350     [D2] match_function_subdriver (non-SHUT mode):
> > matching a device...
> >    0.463603     [D2] Device matches
> >    0.463624     [D2] Reading first configuration descriptor
> >    0.463662     [D2] failed to claim USB device: Resource busy
> >    0.463689     [D2] Kernel driver already detached
> >    0.463714     [D2] failed to claim USB device: Resource busy
> >    0.463740     [D2] Kernel driver already detached
> >    0.463764     [D2] failed to claim USB device: Resource busy
> >    0.463787     [D2] Kernel driver already detached
> >    0.463809     [D2] failed to claim USB device: Resource busy
> >    0.463831     [D2] Kernel driver already detached
> >    0.463854     Can't claim USB device [0463:ffff]@0/0: Entity not found
>
> It's really hard to say from this.   I would think there is a way to
> tell usbhid-ups the device name and have it just try that.    Could be a
> debian issue, could be something wrong with nut.   My advice would be to
> build git master and debug from there, with gdb and ktrace (however you
> spell ktrace on debian, perhaps it is strace).
>
>
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser



More information about the Nut-upsuser mailing list