Hm, the mention of Rocky 9 vs 10 brings to mind another recent discussion: https://github.com/networkupstools/nut/issues/3230
TL;DR: maybe SELinux is the problem, so things that are reasonably expected to talk and work with the POSIX permission model are blocked by that. While improvements (PRs) are desirable to solve this out of the box, check if `setenforce 0` just solves the issue (at least we would know if that is the culprit or not). Jim On Mon, Dec 29, 2025 at 11:46 AM Stephen Davies <[email protected]> wrote: > On 29 December 2025 7:46:01 pm ACDT, Jim Klimov <[email protected]> > wrote: > >Thanks for the update. > > > >That looks like a normal Megatec dialog, at least on the receive side. > Send > >does not look like Q (at least not its basic queries), maybe need to > >compare with different https://networkupstools.org/ups-protocols.html for > >what that could be. > > > >Does that debug log start from the start-up of UPSmart, so it also > >discovers the device there? Or is it in the middle of that life-time? > > > >Jim > > > > > >On Mon, Dec 29, 2025 at 7:43 AM Stephen Davies <[email protected]> > wrote: > > > >> Had a break today and moved the UPS to my Rocky 9 laptop. > >> Wireshark can see USB connections but I couldn't work out how to get > >> something meaningful so I tried UPSmart and it did work. > >> I restarted UPSmart with debug logging turned on then plugged in the > UPS. > >> Attached is the resulting log. > >> Hope it helps work out what is going on. > >> > >> Cheers, > >> Stephen > >> > >> On 28/12/25 14:54, Stephen Davies wrote: > >> > Yes. It can. > >> > > >> > I'm busy for the next week but will try more ASAP. > >> > > >> > Have a great 2026. > >> > > >> > Stephen > >> > > I unplugged the UPS, started UPSmart in debug log mode then plugged in the > UPS so it should show the whole process. >
_______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
