similar to: [Announcement] Python3 scripts to replace upsmon, upssched, upssched-cmd

On Sat, 28 Jan 2023, John Fowler wrote: > We are getting "Init SSL without certificate database? in response to all requests. > > pi at cyva:~ $ upsc ups at cyva > Init SSL without certificate database > battery.charge: 100 If you don't like the warning, then a command such as upsc ups at cyva 2>/dev/null will hide it. Otherwise the simplest, and possibly the safest,

Hello, Also note that NUT project does not currently issue packages, and I have a hard time guessing what distro might ship a "driver.version: DSM7-1-1-42930-workplus-version2-repack-42930-220712". Ask them what NUT version (release or snapshot) they use, and if they would consider shipping a newer one? Sometime recently (after 2.8.0 release) an option was added to quiesce this

Hi, I cant seem to get my upssched to get called by upsmon. Upsmon -c fsd just shuts down without the message I set or the one in upssched-cmd /etc/ups/upsmon.conf: MONITOR ups6 at localhost 1 <user> <pass> master MONITOR ups8 at localhost 1 <user> <pass> master SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /usr/sbin/upssched NOTIFYMSG

Hi, we're trying to do something that's perhaps unorthodox, but seemingly should work; but not for me. We've got a Powerware 9315, that we are serially attaching one machine to. We have several classes of systems that we want to have shut down at different times. I've been doing my config testing by attaching the master machine to a Powerware 9120, and yanking the power

Hi All, I was wondering what people are doing to shutdown their equipment based on the temperature NUT grabs from a UPS? It doesn't appear that upsmon(8) has an appropriate notify event for temperature levels. For the time being, it looks like I'll write a simple perl wrapper around upsc to get ups.temperature, but would love to use something natively from NUT, if possible. Also,

> > > > MONITOR dummy at artu 1 user pass master >> SHUTDOWNCMD "/sbin/shutdown -h +0" >> NOTIFYCMD /usr/local/bin/upssched-script >> > > Hi, As far as I can see, what you are getting in syslog corresponds > correctly to what you have specified. You have specified that upsmon is to > call upssched-script _directly_. This means that the argument

Where syslog output ends up is an OS specific question and depends upon the configuration of the system logger in use. On most systems the logging information will be found in /var/log. On most Linux systems, the default system log is /var/log/messages. Denny > On Sep 20, 2018, at 13:30, Ito-Cole, Kaeny (Student) <Kaeny.Ito-Cole.stu at gtri.gatech.edu> wrote: > > First

Ah yes sorry I forgot to specify I am on CentOS 7 and the newest NUT for that is 2.7.2 On 9/21/18, 9:04 AM, "Denny Page" <denny at cococafe.com> wrote: Where syslog output ends up is an OS specific question and depends upon the configuration of the system logger in use. On most systems the logging information will be found in /var/log. On most Linux systems, the

Dear list, Can't make upssched notify me on event occured. OS: Debian, 2.6.26-1-amd64 Nut: 2.4.3-1.1squeeze1 UPS: Ippon Smart Winner 3000 connected via COM On event ( plug out the cord from UPS ) upsmon detect's status change to OB and gives WALL and syslog notify, but no script starting. In syslog no errors and no upssched process occured, just upsmon. There're no PIPE and LOCK

On Mon, 3 Jul 2017, Andrea de Lutti wrote: > MONITOR dummy at artu 1 user pass master > SHUTDOWNCMD "/sbin/shutdown -h +0" > NOTIFYCMD /usr/local/bin/upssched-script Hi, As far as I can see, what you are getting in syslog corresponds correctly to what you have specified. You have specified that upsmon is to call upssched-script _directly_. This means that the argument to

Hi, I have been running nut successfully for a long time with my Debian 11 server. I upgraded my server to Debian 12 today, which upgraded nut also from 2.7.4-13 to 2.8.0-7. I noticed that after upgrade there was a upssched process running and taking 100% cpu time. I checked if there were any changes to configuration file formats with nut upgrade and only differences I noticed were a terminology

Hi, I ran the strace command while upssched was 100% CPU hungry. This is what I got: 1686633611.702798 read(7, "", 1) = 0 <0.000004> 1686633611.702816 read(7, "", 1) = 0 <0.000004> 1686633611.702834 pselect6(11, [7 10], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [7], left {tv_sec=0, tv_nsec=999998800}) <0.000006> 1686633611.702862 read(7,

Hi, I ran the strace command while upssched was 100% CPU hungry. This is what I got: 1686633611.702798 read(7, "", 1) = 0 <0.000004> 1686633611.702816 read(7, "", 1) = 0 <0.000004> 1686633611.702834 pselect6(11, [7 10], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [7], left {tv_sec=0, tv_nsec=999998800}) <0.000006> 1686633611.702862 read(7,

Hi Roger, On 5/16/23 17:00, Roger Price wrote: > Hello Carsten, That's what I did but for a much simpler setup. I live in > an area with a lot of lightning, and my shutdown criteria is to be able > to shut down repeatedly during an electrical storm.? The NOTIFY and > CMDSCRIPT and the upssched-cmd logic are written up in detail in chapter > 7 of

*** solved *** Using http://rogerprice.org/NUT/ConfigExamples.A5.pdf and upsrw, my BSD shutdown at low power of 80% Bye

Hi! I'm trying to setup a small mobile server rack with key switch to power on/off the whole system. Used USP is an APC Smart-UPS 1500 SMT1500RMI2U with extra AP9613 IO card [1] to get the key switch "connected" to the UPS. The IO card has several inputs which can trigger actions like power on and "gracefully" shutdown. On key switch OFF this SMT ups model changes ups

On June 21, 2017 11:03:00 AM GMT+02:00, Roger Price <roger at rogerprice.org> wrote: >On Tue, 13 Jun 2017, Charles Lepple wrote: > >> On Jun 9, 2017, at 10:16 AM, Roger Price wrote: >>> To address this, I propose a "NUT configuration for Noobs" which is >>> called "Configuration Examples". > >> I am also curious whether you tried to

On 5/16/23 14:09, Carsten Aulbert wrote: > Hi Roger, > > On 5/16/23 17:00, Roger Price wrote: >> Hello Carsten, That's what I did but for a much simpler setup. I live >> in an area with a lot of lightning, and my shutdown criteria is to be >> able to shut down repeatedly during an electrical storm.? The NOTIFY >> and CMDSCRIPT and the upssched-cmd logic are

Hi, I've stumbled over a race condition in upssched when using 3 or more UPSes in combination with START-TIMER/CANCEL-TIMER. I have a solution that works but is ugly, so I'm going to describe the bug here in the hope somebody can come up with a better solution. The problem is in upssched.c:629 check_parent() (see https://github.com/networkupstools/nut/blob/master/clients/upssched.c ).

Hi, The exec is returning 126 - "Command invoked cannot execute. A permission or command not executable problem.". Are you sure that the script is executable by the user running NUT? Do you have SELinux enabled? Regards, Neil. On 27/04/15 20:55, James Hammond wrote: > Hi Roger, > > I get: > > Apr 27 20:50:05 unifi upsmon[1022]: UPS ups on battery > Apr 27