similar to: Stopping dummy ups from broadcasting messages

Now that upsstats.cgi works, I've noticed that dummy-ups changes state every 5 minutes between OL and OB (probably when the 300 second timer expires). The UPS state stays online. Also "online" and "onbatt" are broadcast to the console probably via WALL. (The state changes don't seem to be form the ups as upsshed-cmd doesn't run). Upssched-cmd does run when the UPS

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

On Fri, 16 Feb 2024, Dan Grostick via Nut-upsuser wrote: > Is there any way to stop dummy ups from continuously broadcasting status? > (onbatt)? I want to keep the broadcasts from the ups itself. Could you show us your entry in ups.conf for the dummy ups ? If you have an entry "port = file" in that section of ups.conf, could you show us the contents of "file" ?

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

thank you all for your input. Roger, I'm a nut noob and only marginally understand the implementation (from your other email), but I really like the idea of a heartbeat and design wise it makes a lot of sense. I'll see if I can implement it some time soon. thank you, Spike On Sat, Apr 1, 2017 at 1:54 PM Roger Price <roger at rogerprice.org> wrote: > On Sat, 1 Apr 2017, Stuart

On Mon, 6 May 2019, Gareth Davies wrote: > Just another thing I wanted to mention... once I've resolved the > aforementioned issues, would it be possible for the system to run without any > maintenance or checking up on it? What I mean is, once I've plugged it into my > grandmother's house, I'd like to leave it running and forget about it > basically - in the

On Fri, 29 Mar 2024, Dan Grostick wrote: > It is consistently happening 14-15 minutes after starting. Please see attached > upssched-cmd and upssched.conf. I don't have a upssched.cmd. The binary > upssched is used. After the heartbeat failure, is upsd still running? Does the command "upsc -L" report the UPS's? If you use systemd, what does the command

I have written up a collection of NUT configurations. The chapters are 1. Introduction 2. Simple server with no local users 3. Server with multiple power supplies 4. Workstation with local users 5. Workstations share a UPS 6. Workstation with heartbeat 7. Workstation with timed shutdown 8. Workstation with additional equipment 65 pages A5 format. A PDF reader could place two

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

I've not been able to connect to my ups using NUT 2.7.4 or NUT 2.8.0. 2.7.4 was installed as a package, 2.8.O was compiled from source. I've messed with permissons, everything is root:root and has the approprate read/execute permissons. I've tried two differnt UPS(es) APC & CyperPower. I'm running PI OS (Raspbian) on a Raspberry Pi3 model B. The port 3493 is open (UFW). I can

NUT 2.8.01 When I pull the USB cable from the UPS, I get two notifications of the nocomm-timer expired. The first notification is in the proper sequence, the second notification occurs after 'commok' occurs. Seems somehow that upssched-cmd is getting a second nocomm-timer expired delayed. Dan -------------- next part -------------- An HTML attachment was scrubbed... URL:

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 edit any of the existing NUT > documentation before creating a new document. We chose AsciiDoc in part >

This note describes a heartbeat technique for validating the integrity of a NUT installation. Introduction ------------ A NUT configuration may run for months with little or no output to a system administrator to assure that the combined processes are running correctly. The technique described in this note verifies that the ups driver, upsd, upsmon, upssched and upssched-cmd components are

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 tried your suggestions on another Proxmox environment with the following ups.conf: # Wait 10 seconds for the driver to finish starting. maxstartdelay = 10 # Try 3 times to start the driver, before giving up. maxretry = 3 # Wait 5 seconds between attempts to start the driver. retrydelay = 5 # Poll the ups every 5 seconds pollinterval = 5 [pve1] # Cyber Power Systems, Inc driver =

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,

Now back to computers - so re-checked some bits. The existing https://networkupstools.org/documentation.html page offers currently the https://github.com/networkupstools/ConfigExamples/releases/latest/ URL as "NUT Configuration Examples <https://github.com/networkupstools/ConfigExamples/releases/latest> book maintained by Roger Price" This in turn redirects to a particular newest

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,

It is consistently happening 14-15 minutes after starting. Please see attached upssched-cmd and upssched.conf. I don't have a upssched.cmd. The binary upssched is used. Dan ________________________________ From: Nut-upsuser <nut-upsuser-bounces+danpower2023=outlook.com at alioth-lists.debian.net> on behalf of Roger Price via Nut-upsuser <nut-upsuser at alioth-lists.debian.net>