[Nut-upsuser] Timer doesn't appear to start
Greg Treantos
gtreanto at gmail.com
Tue Jan 28 21:54:47 GMT 2020
The time and upssched-cmd are now working.
Here are the issues I had:
1) Did not define NOTIFYCMD in upsmon.conf Added NOTIFYCMD /sbin/upssched
2) Added +EXEC to NOTIFYMSG rules I am using
3) Change ownership of upssched.conf to my nut user nutmom. I had added
nutmon to the group nut but it didn't work.
Thanks again for all your guidance
On Tue, Jan 28, 2020 at 7:00 AM <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: Timer doesn't appear to start (Roger Price)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 28 Jan 2020 10:14:42 +0100 (CET)
> From: Roger Price <roger at rogerprice.org>
> To: nut-upsuser Mailing List <nut-upsuser at lists.alioth.debian.org>
> Subject: Re: [Nut-upsuser] Timer doesn't appear to start
> Message-ID: <alpine.LSU.2.20.2001280959120.5507 at titan>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
> 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
>
> ------------------------------
>
> 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 175, Issue 35
> ********************************************
>
--
Greg
http://www.linkedin.com/in/gregtreantos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200128/cf0b01fe/attachment.html>
More information about the Nut-upsuser
mailing list