<div dir="ltr"><div>Actually just today I had a PR <a href="https://github.com/networkupstools/nut/pull/2678">https://github.com/networkupstools/nut/pull/2678</a> to replace those numeric codes in messages with slightly more meaningful text.</div><div><br></div><div>There is indeed little immediate practical impact (as in, nothing gets broken), but rather a moderate strategic one:</div><div><br></div><div>* if you run NUT in a systemd distro (eventually maybe SMF or other such frameworks), where notifications are possible and useful to e.g. report that a driver's service has started only after it completes the first data walk of a device, these messages help you see you are missing out on that (either NUT built without support for the framework, or running not under its wing - intentionally during testing or not). In your case this goal was reached - detected that the package was not built sufficiently feature-full :)<br><br>*
if you run NUT in a distro without such framework, or do not plan to use one for whatever reasons even if available, your init-script (or even systemd unit) may be missing out on `export NUT_QUIET_INIT_UPSNOTIFY=true` to hush those messages.<br></div><div><br></div><div>More details in <a href="https://github.com/networkupstools/nut/issues/1590">https://github.com/networkupstools/nut/issues/1590</a>, <a href="https://github.com/networkupstools/nut/pull/1777">https://github.com/networkupstools/nut/pull/1777</a> and <a href="https://github.com/networkupstools/nut/pull/2136">https://github.com/networkupstools/nut/pull/2136</a></div><div><br></div><div>Jim</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Nov 16, 2024 at 12:30 AM Orion Poplawski via Nut-upsuser <<a href="mailto:nut-upsuser@alioth-lists.debian.net">nut-upsuser@alioth-lists.debian.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 11/15/24 15:57, Orion Poplawski wrote:<br>
> This is on EL9 with 2.8.2:<br>
> <br>
> nut-monitor[150988]: upsnotify: failed to notify about state 2: no<br>
> notification tech defined, will not spam more about it<br>
> <br>
> I have no idea what this really means. I think it has something to do about<br>
> systemd startup notification, but I'm not really sure. Can someone enlighten me?<br>
> <br>
> Is this something that anyone should care about?<br>
> <br>
<br>
So, it appears to be because the nut package is being built without<br>
systemd-devel and its notification support. If I build nut with that, I now get:<br>
<br>
nut-monitor[153720]: upsnotify: logged the systemd watchdog situation once,<br>
will not spam more about it<br>
<br>
which I will assume to be completely informational and not anything that<br>
anyone should care about. Right?<br>
<br>
-- <br>
Orion Poplawski<br>
he/him/his - surely the least important thing about me<br>
Manager of IT Systems 720-772-5637<br>
NWRA, Boulder Office FAX: 303-415-9702<br>
3380 Mitchell Lane <a href="mailto:orion@nwra.com" target="_blank">orion@nwra.com</a><br>
Boulder, CO 80301 <a href="https://www.nwra.com/" rel="noreferrer" target="_blank">https://www.nwra.com/</a><br>
_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@alioth-lists.debian.net" target="_blank">Nut-upsuser@alioth-lists.debian.net</a><br>
<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
</blockquote></div>