On 29 December 2025 10:30:02?pm ACDT, nut-upsuser-request at
alioth-lists.debian.net wrote:>Send Nut-upsuser mailing list submissions to
> nut-upsuser at alioth-lists.debian.net
>
>To subscribe or unsubscribe via the World Wide Web, visit
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
>or, via email, send a message with subject or body 'help' to
> nut-upsuser-request at alioth-lists.debian.net
>
>You can reach the person managing the list at
> nut-upsuser-owner at alioth-lists.debian.net
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Nut-upsuser digest..."
>
>
>Today's Topics:
>
> 1. Re: Digitech support (Jim Klimov)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Mon, 29 Dec 2025 12:40:44 +0100
>From: Jim Klimov <jimklimov+nut at gmail.com>
>To: Stephen Davies <sdavies at sdc.com.au>, nut-upsuser Mailing List
> <nut-upsuser at lists.alioth.debian.org>
>Subject: Re: [Nut-upsuser] Digitech support
>Message-ID:
> <CAJYg8vKiS7+DB+ypXLLGFq1J90vAriJ8mNe2QrL6nf+ZDKP+2g at
mail.gmail.com>
>Content-Type: text/plain; charset="utf-8"
>
>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 <sdavies at
sdc.com.au> wrote:
>
>> On 29 December 2025 7:46:01?pm ACDT, Jim Klimov <jimklimov+nut at
gmail.com>
>> 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 <sdavies at
sdc.com.au>
>> 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.
>>
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20251229/dede48d7/attachment-0001.htm>
>
>------------------------------
>
>Subject: Digest Footer
>
>_______________________________________________
>Nut-upsuser mailing list
>Nut-upsuser at alioth-lists.debian.net
>https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
>
>
>------------------------------
>
>End of Nut-upsuser Digest, Vol 246, Issue 11
>********************************************
Selinux is disabled on both boxes. Too much hassle.