search for: myups3

Which OS is that? With Linux+systemd, I'd expect systemd to start the drivers (hence blocking the port) and keep logs in the systemd journal (if your packaging includes nut-driver-enumerator, you may see them with `journalctl -lu nut-driver at myups3`; for older systems just `journalctl -lu nut-driver`), and on others init-scripts added by packaging should do the same to start drivers when booted, and /var/log/syslog or /var/log/messages or some such to hold the messages. >From "2.8.0" in the log I assume it is packaged (and thank...

...matching a > device... > > >0.288406[D3] match_function_regex: matching a device... > > >0.288509[D2] match_function_regex: failed match of Device: (null) > > >0.288563[D2] Device does not match - skipping > > The UPS has been defined in ups.conf as: > > [myups3] > > driver : usbhid-ups > > port = auto > > vendorid = 0463 > > productid = ffff > > desc = "5S" > > bus = 002 > > device = 014 > > pollonly > I have only: [ups02] driver=usbhid-ups port=auto serial = [redacted] -- Dan Langille dan at...

On Thursday, March 9th, 2023 at 8:34 AM, Dan Langille via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> wrote: >> The UPS has been defined in ups.conf as: >> >> [myups3] >> >> driver : usbhid-ups >> >> port = auto >> >> vendorid = 0463 >> >> productid = ffff >> >> desc = "5S" >> >> bus = 002 >> >> device = 014 >> >> pollonly > > I have only: > > [u...

..._subdriver (non-SHUT mode): matching a device... > 0.288406 [D3] match_function_regex: matching a device... > 0.288509 [D2] match_function_regex: failed match of Device: (null) > 0.288563 [D2] Device does not match - skipping The UPS has been defined in ups.conf as: [myups3] ?????? driver : usbhid-ups ?????? port = auto ?????? vendorid = 0463 ?????? productid = ffff ?????? desc = "5S" ?????? bus = 002 ?????? device = 014 ?????? pollonly Here is the lsusb trace. GNU nano 7.2 lsusb.trc2...

...ubject: Re: [Nut-upsuser] Question on EATON UPS Which OS is that? With Linux+systemd, I'd expect systemd to start the drivers (hence blocking the port) and keep logs in the systemd journal (if your packaging includes nut-driver-enumerator, you may see them with `journalctl -lu nut-driver at myups3`; for older systems just `journalctl -lu nut-driver`), and on others init-scripts added by packaging should do the same to start drivers when booted, and /var/log/syslog or /var/log/messages or some such to hold the messages. >From "2.8.0" in the log I assume it is packaged (and th...

...9 ? : nut-upsuser Mailing List <nut-upsuser at lists.alioth.debian.org> Objet : Re: [Nut-upsuser] Question on EATON UPS On Thursday, March 9th, 2023 at 8:34 AM, Dan Langille via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> wrote: The UPS has been defined in ups.conf as: [myups3] driver : usbhid-ups port = auto vendorid = 0463 productid = ffff desc = "5S" bus = 002 device = 014 pollonly I have only: [ups02] driver=usbhid-ups port=auto serial = [redacted] I have an Eaton 5P750 connected via USB and agree, a less specific entry in ups.conf works fin...

....alioth.debian.org> > *Objet : *Re: [Nut-upsuser] Question on EATON UPS > > > > On Thursday, March 9th, 2023 at 8:34 AM, Dan Langille via Nut-upsuser < > nut-upsuser at alioth-lists.debian.net> wrote: > > > > The UPS has been defined in ups.conf as: > > [myups3] > > driver : usbhid-ups > > port = auto > > vendorid = 0463 > > productid = ffff > > desc = "5S" > > bus = 002 > > device = 014 > > pollonly > > I have only: > > [ups02] > driver=usbhid-ups > port=auto > > serial = [...

....alioth.debian.org> > *Objet : *Re: [Nut-upsuser] Question on EATON UPS > > > > On Thursday, March 9th, 2023 at 8:34 AM, Dan Langille via Nut-upsuser < > nut-upsuser at alioth-lists.debian.net> wrote: > > > > The UPS has been defined in ups.conf as: > > [myups3] > > driver : usbhid-ups > > port = auto > > vendorid = 0463 > > productid = ffff > > desc = "5S" > > bus = 002 > > device = 014 > > pollonly > > I have only: > > [ups02] > driver=usbhid-ups > port=auto > > serial = [...

...d I?m not getting the same error message which is probably due to the server working in the background still locking the device I think the daemon starts but gets into an infinite loop and doesn?t finish and hand back control. Here are the updated traces I got by restarting : sudo ./usbhid-ups -a myups3 -DDD>& tracefile Please apologies for the extra length of the traces as most of them are probably irrelevant (I had to cut the main file into multiple chunks): I have zipped the trace as requested. Thanks Laurent De : Nut-upsuser <nut-upsuser-bounces+laurenttaieb=free.fr at ali...

...ut-upsuser] Question on EATON UPS >> >> >> >> On Thursday, March 9th, 2023 at 8:34 AM, Dan Langille via Nut-upsuser < >> nut-upsuser at alioth-lists.debian.net> wrote: >> >> >> >> The UPS has been defined in ups.conf as: >> >> [myups3] >> >> driver : usbhid-ups >> >> port = auto >> >> vendorid = 0463 >> >> productid = ffff >> >> desc = "5S" >> >> bus = 002 >> >> device = 014 >> >> pollonly >> >> I have only: >...