>I just went through the same issue. Take a look at my thread.
>Double check that upsmon.conf:NOTIFYCMD /sbin/upssched is not still
commented.
Thanks for the response, can you link to it? I'm not finding it in the
search. I'm not using /sbin/upssched, I have NOTIFYCMD set up as:
NOTIFYCMD /home/pi/Documents/scripts/ups-log.py
and it's not commented out.
On Tue, Feb 11, 2020 at 4:59 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: NOTIFYCMD not running (Greg Treantos)
> 2. Re: NOTIFYCMD not running (Max Pierson-Liénard)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 11 Feb 2020 07:45:54 -0500
> From: Greg Treantos <gtreanto at gmail.com>
> To: nut-upsuser at alioth-lists.debian.net
> Subject: Re: [Nut-upsuser] NOTIFYCMD not running
> Message-ID:
> <CAGuknmh-RRH> cVQeDUhwESPnoHZ8nvyQpOSz_9Q1pGqkZD_t3g at
mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> I just went through the same issue. Take a look at my thread.
>
> Double check that upsmon.conf:NOTIFYCMD /sbin/upssched is not still
> commented.
>
> On Tue, Feb 11, 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. NOTIFYCMD not running (Max Pierson-Liénard)
> > 2. Re: NOTIFYCMD not running (Roger Price)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Tue, 11 Feb 2020 02:11:45 -0800
> > From: Max Pierson-Liénard <maxpierson at gmail.com>
> > To: nut-upsuser at alioth-lists.debian.net
> > Subject: [Nut-upsuser] NOTIFYCMD not running
> > Message-ID:
> > <
> > CAK31S7ZNLsCkZbTtPW6hMMDyXRc9S34Prgmi0qcDnd34nzjmjQ at
mail.gmail.com>
> > Content-Type: text/plain; charset="utf-8"
> >
> > Hi, I'm setting up NUT on a raspberry pi 4, following the guide
here:
> > https://melgrubb.com/2016/12/11/rphs-v2-ups/
> > OS version: Raspian Buster
> > NUT version: 2.7.4.8
> > Installed via: apt package install
> > Device: Legrand Keor Multiplug connected via USB
> >
> > The problem I am experiencing is that *NOTIFYCMD* never runs. I can
> > connect to the device via *upsc*, and I receive WALL messages when I
> > connect and disconnect the power. I have the following in
*upsmon.conf*:
> >
> > *MONITOR ROUTERUPS at localhost 1 upsmon <mypassword> master*
> > *NOTIFYCMD /home/pi/Documents/scripts/ups-log.py*
> >
> >
> >
> >
> >
> >
> > *NOTIFYFLAG ONLINE SYSLOG+WALL+EXECNOTIFYFLAG ONBATT
> > SYSLOG+WALL+EXECNOTIFYFLAG LOWBATT SYSLOG+WALL+EXECNOTIFYFLAG FSD
> > SYSLOG+WALL+EXECNOTIFYFLAG SHUTDOWN SYSLOG+WALL+EXECNOTIFYFLAG
> > REPLBATT SYSLOG+WALL+EXECNOTIFYFLAG NOPARENT SYSLOG+WALL*
> >
> > I am able to run that command,
> > */home/pi/Documents/scripts/ups-log.py "some text"*
> > without any issues, and it doesn't require root privileges. The
owner is
> > nut and the permissions are 755:
> > -rwxr-xr-x 1 nut nut 2927 Feb 9 22:26 ups-log.py
> >
> > Contents of my /etc/nut/ folder:
> >
> >
> >
> >
> >
> >
> > *-rw-r----- 1 nut nut 1544 Feb 3 07:40 nut.conf-rw-r----- 1 nut nut
> 5588
> > Feb 3 07:38 ups.conf-rw-r----- 1 nut nut 4578 Jun 1 2018
> > upsd.conf-rw-r----- 1 nut nut 2283 Feb 3 13:27 upsd.users-rw-r-----
1
> nut
> > nut 15434 Feb 10 23:22 upsmon.conf-rw-r----- 1 nut nut 15308 Feb 3
15:45
> > upsmon.conf.save-rw-r----- 1 nut nut 3887 Jun 1 2018 upssched.conf*
> >
> > Contents of my syslog via tail:
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > *Feb 11 11:59:52 raspberrypi kernel: [ 6355.200755] usb 1-1.4: New USB
> > device strings: Mfr=1, Product=2, SerialNumber=0Feb 11 11:59:52
> raspberrypi
> > kernel: [ 6355.200768] usb 1-1.4: Product: USB to SerialFeb 11
11:59:52
> > raspberrypi kernel: [ 6355.200780] usb 1-1.4: Manufacturer: INNO
TECHFeb
> 11
> > 11:59:52 raspberrypi kernel: [ 6355.214192] hid-generic
> > 0003:0665:5161.0002: hiddev96,hidraw0: USB HID v1.00 Device [INNO TECH
> USB
> > to Serial] on usb-0000:01:00.0-1.4/input0Feb 11 11:59:52 raspberrypi
> > mtp-probe: checking bus 1, device 5:
> >
> >
>
"/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4"Feb
> > 11 11:59:52 raspberrypi mtp-probe: bus: 1, device: 5 was not an MTP
> > deviceFeb 11 11:59:52 raspberrypi mtp-probe: checking bus 1, device 5:
> >
> >
>
"/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4"Feb
> > 11 11:59:52 raspberrypi mtp-probe: bus: 1, device: 5 was not an MTP
> > deviceFeb 11 11:59:57 raspberrypi upsmon[14209]: UPS ROUTERUPS at
localhost
> > on
> > batteryFeb 11 12:00:22 raspberrypi upsmon[14209]: UPS ROUTERUPS at
localhost
> > on line power*
> >
> > That's as much information as I can think of, it seems like it has
to be
> a
> > permissions thing but it's not spitting out any kind of error that
would
> > help troubleshoot.
> >
> > Thank you for the time!
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL: <
> >
>
http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200211/7be8c874/attachment-0001.html
> > >
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Tue, 11 Feb 2020 12:55:52 +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] NOTIFYCMD not running
> > Message-ID: <alpine.LSU.2.20.2002111252310.5507 at titan>
> > Content-Type: text/plain; charset="utf-8";
Format="flowed"
> >
> > On Tue, 11 Feb 2020, Max Pierson-Liénard wrote:
> >
> > > The problem I am experiencing is that NOTIFYCMD never runs. I
can
> > connect to
> > > the device via upsc, and I receive WALL messages when I connect
and
> > disconnect
> > > the power. I have the following in upsmon.conf:
> > >
> > > MONITOR ROUTERUPS at localhost 1 upsmon <mypassword> master
> > > NOTIFYCMD /home/pi/Documents/scripts/ups-log.py
> > > NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC
> > > NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC
> > > ...
> > > I am able to run that command,
> > > /home/pi/Documents/scripts/ups-log.py "some text"
> > > without any issues, and it doesn't require root privileges.
The owner
> > is nut
> > > and the permissions are 755:
> >
> > When you run that command, does "some text" appear in the
system log?
> >
> > 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 176, Issue 3
> > *******************************************
> >
>
>
> --
> Greg
>
> http://www.linkedin.com/in/gregtreantos
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
>
http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200211/9abcfb24/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Tue, 11 Feb 2020 04:58:38 -0800
> From: Max Pierson-Liénard <maxpierson at gmail.com>
> To: nut-upsuser at alioth-lists.debian.net
> Subject: Re: [Nut-upsuser] NOTIFYCMD not running
> Message-ID:
> <CAK31S7ak4Ce3hzsM5OxuOapU+w-25i7G> LczFKL+ZgRvPmtWLA at
mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> > When you run that command, does "some text" appear in the
system log?
> When I run Documents/scripts/ups-log.py manually I do see the expected text
> echo'ed to the command line. It actually appends to a Google Sheet,
not
> the internal log files.
>
> When I would expect to see it triggered by NOTIFYCMD, I don't see any
text
> printed and nothing shows up at the google sheets. If the permission was
> being denied, would that be logged somewhere?
>
>
>
> On Tue, Feb 11, 2020 at 4: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. NOTIFYCMD not running (Max Pierson-Liénard)
> > 2. Re: NOTIFYCMD not running (Roger Price)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Tue, 11 Feb 2020 02:11:45 -0800
> > From: Max Pierson-Liénard <maxpierson at gmail.com>
> > To: nut-upsuser at alioth-lists.debian.net
> > Subject: [Nut-upsuser] NOTIFYCMD not running
> > Message-ID:
> > <
> > CAK31S7ZNLsCkZbTtPW6hMMDyXRc9S34Prgmi0qcDnd34nzjmjQ at
mail.gmail.com>
> > Content-Type: text/plain; charset="utf-8"
> >
> > Hi, I'm setting up NUT on a raspberry pi 4, following the guide
here:
> > https://melgrubb.com/2016/12/11/rphs-v2-ups/
> > OS version: Raspian Buster
> > NUT version: 2.7.4.8
> > Installed via: apt package install
> > Device: Legrand Keor Multiplug connected via USB
> >
> > The problem I am experiencing is that *NOTIFYCMD* never runs. I can
> > connect to the device via *upsc*, and I receive WALL messages when I
> > connect and disconnect the power. I have the following in
*upsmon.conf*:
> >
> > *MONITOR ROUTERUPS at localhost 1 upsmon <mypassword> master*
> > *NOTIFYCMD /home/pi/Documents/scripts/ups-log.py*
> >
> >
> >
> >
> >
> >
> > *NOTIFYFLAG ONLINE SYSLOG+WALL+EXECNOTIFYFLAG ONBATT
> > SYSLOG+WALL+EXECNOTIFYFLAG LOWBATT SYSLOG+WALL+EXECNOTIFYFLAG FSD
> > SYSLOG+WALL+EXECNOTIFYFLAG SHUTDOWN SYSLOG+WALL+EXECNOTIFYFLAG
> > REPLBATT SYSLOG+WALL+EXECNOTIFYFLAG NOPARENT SYSLOG+WALL*
> >
> > I am able to run that command,
> > */home/pi/Documents/scripts/ups-log.py "some text"*
> > without any issues, and it doesn't require root privileges. The
owner is
> > nut and the permissions are 755:
> > -rwxr-xr-x 1 nut nut 2927 Feb 9 22:26 ups-log.py
> >
> > Contents of my /etc/nut/ folder:
> >
> >
> >
> >
> >
> >
> > *-rw-r----- 1 nut nut 1544 Feb 3 07:40 nut.conf-rw-r----- 1 nut nut
> 5588
> > Feb 3 07:38 ups.conf-rw-r----- 1 nut nut 4578 Jun 1 2018
> > upsd.conf-rw-r----- 1 nut nut 2283 Feb 3 13:27 upsd.users-rw-r-----
1
> nut
> > nut 15434 Feb 10 23:22 upsmon.conf-rw-r----- 1 nut nut 15308 Feb 3
15:45
> > upsmon.conf.save-rw-r----- 1 nut nut 3887 Jun 1 2018 upssched.conf*
> >
> > Contents of my syslog via tail:
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > *Feb 11 11:59:52 raspberrypi kernel: [ 6355.200755] usb 1-1.4: New USB
> > device strings: Mfr=1, Product=2, SerialNumber=0Feb 11 11:59:52
> raspberrypi
> > kernel: [ 6355.200768] usb 1-1.4: Product: USB to SerialFeb 11
11:59:52
> > raspberrypi kernel: [ 6355.200780] usb 1-1.4: Manufacturer: INNO
TECHFeb
> 11
> > 11:59:52 raspberrypi kernel: [ 6355.214192] hid-generic
> > 0003:0665:5161.0002: hiddev96,hidraw0: USB HID v1.00 Device [INNO TECH
> USB
> > to Serial] on usb-0000:01:00.0-1.4/input0Feb 11 11:59:52 raspberrypi
> > mtp-probe: checking bus 1, device 5:
> >
> >
>
"/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4"Feb
> > 11 11:59:52 raspberrypi mtp-probe: bus: 1, device: 5 was not an MTP
> > deviceFeb 11 11:59:52 raspberrypi mtp-probe: checking bus 1, device 5:
> >
> >
>
"/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4"Feb
> > 11 11:59:52 raspberrypi mtp-probe: bus: 1, device: 5 was not an MTP
> > deviceFeb 11 11:59:57 raspberrypi upsmon[14209]: UPS ROUTERUPS at
localhost
> > on
> > batteryFeb 11 12:00:22 raspberrypi upsmon[14209]: UPS ROUTERUPS at
localhost
> > on line power*
> >
> > That's as much information as I can think of, it seems like it has
to be
> a
> > permissions thing but it's not spitting out any kind of error that
would
> > help troubleshoot.
> >
> > Thank you for the time!
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL: <
> >
>
http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200211/7be8c874/attachment-0001.html
> > >
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Tue, 11 Feb 2020 12:55:52 +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] NOTIFYCMD not running
> > Message-ID: <alpine.LSU.2.20.2002111252310.5507 at titan>
> > Content-Type: text/plain; charset="utf-8";
Format="flowed"
> >
> > On Tue, 11 Feb 2020, Max Pierson-Liénard wrote:
> >
> > > The problem I am experiencing is that NOTIFYCMD never runs. I
can
> > connect to
> > > the device via upsc, and I receive WALL messages when I connect
and
> > disconnect
> > > the power. I have the following in upsmon.conf:
> > >
> > > MONITOR ROUTERUPS at localhost 1 upsmon <mypassword> master
> > > NOTIFYCMD /home/pi/Documents/scripts/ups-log.py
> > > NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC
> > > NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC
> > > ...
> > > I am able to run that command,
> > > /home/pi/Documents/scripts/ups-log.py "some text"
> > > without any issues, and it doesn't require root privileges.
The owner
> > is nut
> > > and the permissions are 755:
> >
> > When you run that command, does "some text" appear in the
system log?
> >
> > 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 176, Issue 3
> > *******************************************
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
>
http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200211/8e8eec80/attachment.html
> >
>
> ------------------------------
>
> 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 176, Issue 4
> *******************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200211/70d95235/attachment-0001.html>