On 10.11.24 23:18, Jim Klimov wrote:
Maybe...ish - I haven't seen those for a while, but had few outages either.
Can you check if the updated (root) user profile or default profile(s)
under /etc mention `mesg n` or similar means of limiting broadcasts?
In your manual `wall` executions, do you see them in the same terminal that
sent the message, or on all terminals (GUI, SSH sessions)? As root or as
any user (as recipient and as sender)?
I have "mesg y" by default.
manual "wall" did send the message to multiple terminal sessions, just as
upsmon from older Debian versions.
I suspect systemd may also be guilty of that, since it tende to mess up much
- I don't run selinux nor apparmor on that machine
(but I may check again)
seems that there's no way of debugging that, the highest debug level used is
4. I can compile upsmon locally to debug more.
On Sun, Nov 10, 2024 at 9:17 PM Matus UHLAR - fantomas via Nut-upsuser <
[email protected]> wrote:
I have noticed that (apparensly) since Debian 12 upgrade the WALL
commands for upsmon.conf don's seem to work.
To test I have configured upsmon-dummy.conf to debug this:
NOTIFYCMD /usr/sbin/upssched
NOTIFYFLAG ONBATT SYSLOG+EXEC+WALL
NOTIFYFLAG ONLINE SYSLOG+EXEC+WALL
the /usr/sbin/upssched gets called:
/lib/nut/upsmon -D -D -D -D -f /etc/nut/upsmon-dummy.conf
and I can see the command being executed:
15.006263 [D2] do_notify: ntype 0x0001 (ONBATT)
15.006273 UPS dummy@localhost on battery
15.006598 [D3] Current power value: 1
15.006637 [D3] Minimum power value: 1
Executing command: onbattwarn
Nov 10 20:29:05 xxx upssched[22030]: Executing command: onbattwarn
Nov 10 20:29:05 xxx upssched-cmd[22033]: The UPS is off-line
35.008150 [D2] do_notify: ntype 0x0000 (ONLINE)
35.008186 UPS dummy@localhost on line power
35.008511 [D3] Current power value: 1
35.008574 [D3] Minimum power value: 1
Executing command: ups-back-on-power
Nov 10 20:29:25 xxx upssched[22065]: Executing command: ups-back-on-power
Nov 10 20:29:25 xxx upssched-cmd[22068]: The UPS is on-line
however the WALL flag does not work.
executing "wall" command manually does work.
Did anyone notice behaviour change?
As I mentioned, I have Debian 12, nut 2.8.0. On Debian 10/11 with nut
2.7.4 wall worked.
--
Matus UHLAR - fantomas, [email protected] ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
We are but packets in the Internet of life (userfriendly.org)
_______________________________________________
Nut-upsuser mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
