similar to: NOTIFYCMD not running

Displaying 20 results from an estimated 1000 matches similar to: "NOTIFYCMD not running"

2020 Feb 11
1
NOTIFYCMD not running
> 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
2020 Feb 11
1
NOTIFYCMD not running
>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
2020 Feb 11
1
NOTIFYCMD not running
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
2020 Oct 28
0
GT710 and Nouveau on ARM/ARM64
On Wed, Oct 28, 2020 at 10:20 AM Dave Stevenson <dave.stevenson at raspberrypi.com> wrote: > > Hi Ilia > > Thanks for taking the time to reply. > > On Wed, 28 Oct 2020 at 14:10, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > > > > The most common issue on arm is that the pci memory window is too narrow to allocate all the BARs. Can you see if there are
2020 Nov 03
0
GT710 and Nouveau on ARM/ARM64
On Tue, Nov 3, 2020 at 1:08 PM Dave Stevenson <dave.stevenson at raspberrypi.com> wrote: > > Hi Ilia > Thanks again for the reply. > > On Wed, 28 Oct 2020 at 14:59, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > > > > On Wed, Oct 28, 2020 at 10:20 AM Dave Stevenson > > <dave.stevenson at raspberrypi.com> wrote: > > > > > > Hi
2020 Nov 03
2
GT710 and Nouveau on ARM/ARM64
Hi Ilia Thanks again for the reply. On Wed, 28 Oct 2020 at 14:59, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > > On Wed, Oct 28, 2020 at 10:20 AM Dave Stevenson > <dave.stevenson at raspberrypi.com> wrote: > > > > Hi Ilia > > > > Thanks for taking the time to reply. > > > > On Wed, 28 Oct 2020 at 14:10, Ilia Mirkin <imirkin at
2020 Oct 28
2
GT710 and Nouveau on ARM/ARM64
Hi Ilia Thanks for taking the time to reply. On Wed, 28 Oct 2020 at 14:10, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > > The most common issue on arm is that the pci memory window is too narrow to allocate all the BARs. Can you see if there are messages in the kernel to that effect? All the BAR allocations seem to succeed except for the IO one. AIUI I/O is deprecated, but is it
2020 Feb 12
1
NOTIFYCMD not running
Philippe Andersson I think tried to respond on this thread but all I see is your corporate email signature? I did some more troubleshooting tonight. TL;DR at the end. First, confirmed that NOTIFYCMD is in fact firing. So I changed it to: NOTIFYCMD logger "NOTIFYCMD FIRED!" followed by: sudo service nut-client restart and that message does show up in /var/log/messages when I pull the
2023 Jun 10
1
Fopen upsmon.pid - no such file or directory - Nut 2.8.0 built from source
I've built NUT 2.8.0 from source. When the nut-monitor runs: fopen upsmon.pid fails. I'm running as root, upsmon has root:root permissions as well as the other daemons and .conf files. I've tried configuring with and without --prefixpath --prefixaltpath. Is there something I am missing? Please see attached. Dan -------------- next part -------------- An HTML attachment was
2019 Dec 11
1
[EXTERNAL] Re: Tripp Lite SMART1500LCD repeatedly disconnecting and reconnecting
Thought I'd follow up in case someone else runs into this issue. In the end what worked for me was tweaking the udev rules. I have had no USB disconnects or stale data warnings so far. I only used one rule for my UPS: # /etc/udev/rules.d/62-nut-usbups.rules SUBSYSTEM!="usb", GOTO="nut-usbups_rules_end" # TrippLite # e.g. TrippLite SMART1500LCD - usbhid-ups
2011 Sep 02
2
NUT 2.6.1+ Windows 2008 R2 - NOTIFYCMD not being called
Hi All, I'm using a recent post 2.6.1 build provided by Fred (executables have modified date of 9th August) I have configured upsmon.conf with :- NOTIFYCMD C:\NUT\etc\NotifyCmd.bat and :- NOTIFYFLAG ONLINE SYSLOG+EXEC NOTIFYFLAG ONBATT SYSLOG+EXEC NOTIFYFLAG LOWBATT SYSLOG+EXEC NOTIFYFLAG FSD SYSLOG+EXEC NOTIFYFLAG COMMOK SYSLOG+EXEC NOTIFYFLAG COMMBAD SYSLOG+EXEC
2007 Jan 17
1
NOTIFYCMD not running
I have the nut package installed and running - everything perfect (or so I thought). My syslog shows everything looks great, and pulling the UPS plug for a few seconds triggers a WALL event, but not my notifycmd (which should write a test message to syslog). Can someone offer insight/ideas as to why my NOTIFYCMD is not running? Thanks, Michelle ----------------------- Extract from messages
2012 Apr 11
1
NOTIFYCMD doesn't work from Windows service
Hello dear all, I try to use NUT for windows (not WinNUT), and stuck with launching NOTIFYCMD. On any event marked as SYSLOG+WALL+EXEC syslog entry appears, popup window appears, but NOTIFYCMD script doesn't run. If I run upsmon.exe in cmd (i. e. not as a service) everything works fine. Here is my upsmon.conf: MONITOR central at 10.35.0.180 1 user password slave MINSUPPLIES 1 SHUTDOWNCMD
2006 Jul 11
2
notifycmd problem
hello, i've got a problem with the notifycmd here is a part of my upsmon.conf : NOTIFYCMD /usr/local/ups/bin/nut_notify NOTIFYMSG ONLINE "UPS %s is getting line power" NOTIFYMSG ONBATT "UPS %s is on battery" NOTIFYMSG REPLBATT "The UPS %s battery is bad and needs to be replaced" NOTIFYMSG LOWBATT "UPS %s is being shutdown by the master" NOTIFYMSG FSD
2015 Sep 21
1
problem with NOTIFYCMD
After some testing, I notice that my NOTIFYCMD script seems to work if I call it as user 'john' (that's me) but if I call it as 'root' it does not work. So is there a permissions issue ? I have permission on the file set to 755. I see there is a variable in upsmon.conf called RUN_AS_USER. I do not have this defined. Does this variable need to be defined ? I presume that if
2015 Sep 22
2
NOTIFYCMD shell script problem driving me NUTS
Either I am missing something or I am really STUPID. 1. I have added a user, named nutmon, to the nut group. 2. In upsmon.conf I have set RUN_AS_USER nutmon . 3. I have NOTIFYCMD /etc/nut/notifyme.sh and it is set as 755, so should be executable by everyone. 4. I have the NOTIFYFLAG set as SYSLOG+WALL+EXEC, so the shell should execute. This is the shell script : #!/bin/bash # # NUT NOTIFYCMD
2020 Oct 28
2
GT710 and Nouveau on ARM/ARM64
Hi Seeing as we (Raspberry Pi) have just launched the Compute Module 4 with an exposed PCIe x1 lane, people are asking about adding graphics cards. Seeing as you are the people who have the knowledge with regard to NVidia and nouveau, what are your immediate thoughts of nouveau working on ARM/ARM64? Is there a chance of this working? I'm no PCIe expert, although I can call on some expertise
2010 Mar 23
0
[asterisk-ss7]Chan_ss7 issue
Dear all, Do you have come acrross with this issue. My ss7 link get fluctuating. It use chan_ss7 version 1.0.95-beta. I have 8 E1s running on a DL380 server with Digium E1 cards ( 4 port cards). This enable to have calls from sip to ss7 and vice versa. However ss7 links are not stable. linkset siuc, link l1, schannel 1, sls 0, NOT_ALIGNED, rx: 1, tx: 2/4, sentseq/lastack: 127/127, total
1998 Jan 16
0
mtp2R.pl
I received some large data sets in Minitab Portable Worksheet (.mtp) format and wanted to read them into R. Here is a _first cut_ at a perl script that transforms .mtp files into something that can be read by R. Comments, bug-fixes, enhancements and extensions are welcome. #!/usr/bin/perl # Convert a Minitab Portable Worksheet to an R (or S-PLUS) list structure # $Id: mtp2R.pl,v 1.1 1998/01/16
2017 Apr 26
0
APC Back-UPS XS1300 battery behaviour on test shutdown
Hi there, Seeing an odd behaviour when running upsmon -c fsd to test my Raspberry Pi (running Jesse Lite) setup as a upsmon master, attached via USB to an APC Back-UPS XS1300. The Raspberry Pi is plugged into the Master outlet on the APC. The UPS clicks onto battery (and the fan spins up) for a few minutes, then resets, then repeats again, while finally remaining on AC power afterwards. The