[Nut-upsuser] Timer doesn't appear to start
Roger Price
roger at rogerprice.org
Tue Jan 28 09:14:42 GMT 2020
On Mon, 27 Jan 2020, Greg Treantos wrote:
> root at nutpi:/etc/nut# ps -elf | grep -E '[n]ut|ups[dms]'
> 4 S avahi 246 1 0 80 0 - 1472 poll_s Jan26 ? 00:00:31 avahi-daemon: running [nutpi.local]
> 1 S nut 451 1 0 80 0 - 678 poll_s Jan26 ? 00:03:41 /lib/nut/upscode2 -a deltec-PRA1500
> 1 S nut 454 1 0 80 0 - 1173 poll_s Jan26 ? 00:00:28 /lib/nut/upsd
> 1 S root 460 1 0 80 0 - 1136 pipe_w Jan26 ? 00:00:00 /lib/nut/upsmon
> 5 S nutmon 461 460 0 80 0 - 1714 hrtime Jan26 ? 00:00:10 /lib/nut/upsmon
The last line shows that the instance of upsmon which should call upssched is
running as nutmon. Good.
> [root at donner nut]# grep ^[^#] upsmon.conf
> RUN_AS_USER nutmon
> MONITOR deltec-PRA1500 at localhost 1 nutmon ******** master
> MINSUPPLIES 1
> SHUTDOWNCMD "/sbin/shutdown -h +0"
> NOTIFYCMD /sbin/upssched
The last line shows that upsmon expects upssched to be in /sbin.
> pi at nutpi:~ $ sudo ls -alt /home/nutmon
> total 32
> -rw------- 1 nutmon nutmon 172 Jan 26 12:32 .bash_history
> drwxrwx--- 2 nutmon nutmon 4096 Jan 26 12:32 upssched
But this shows that upssched is located in directory /home/nutmon. Is this the
problem?
What NOTIFYFLAG declarations with the EXEC option do you have in upsmon.conf ?
If the declarations
NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC
NOTIFYFLAG LOWBATT SYSLOG+WALL+EXEC
are missing, that could also be a problem.
Roger
More information about the Nut-upsuser
mailing list