Thank you for the insight.
Further investigation revealed that upssched-cmd wasn't running due to a typo
in the file. Found an error code in Syslog.
Case closed.
Dan
From: Nut-upsuser
on
behalf of Matus UHLAR - fantomas via Nut-upsuser
Sent: Monday, February
On 19.02.24 14:48, Dan Grostick via Nut-upsuser wrote:
Msmtp is not sending messages when invoked from upssched-cmd.
I can manually invoke it from the command line.
where is its config file?
There is a 's' instead of an 'x' in the ls -l. Might this be some sort of
permission problem?
Msmtp is not sending messages when invoked from upssched-cmd. I can manually
invoke it from the command line. There is a 's' instead of an 'x' in the ls
-l. Might this be some sort of permission problem?
upsmon.conf has run user as root.
Dan
___
Hello, and thanks for the detailed report.
Regarding /var/run/nut - I think `systemd-tmpfiles --create` should have
taken care of this. Can you check if your tarball "package" actually
shipped a /usr/lib/tmpfiles.d/nut-common-tmpfiles.conf file, and does it
list (/var)/run/nut among the items
