similar to: Configuration Examples

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 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 >

On Fri, 16 Feb 2024, Dan Grostick wrote: > [heartbeat] > driver=dummy-ups > port=heartbeat.conf > mode=dummy-once > desc= "Heart beat verfication of NUT" I would be interesting to see the file heartbeat.conf and the NOTIFYFLAG declarations in upsmon.conf . See also chapter 6.3 "Configuration file upsmon.conf for workstation with heartbeat" in

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

Most of the questions asked in the nut-user mailing list seem to me to be either erudite technical discussion of new and exotic UPS units, or n00b questions of the style "I have this old UPS so I installed NUT but it didn't work". NUT is thoroughly documented with man pages and User Manual, but from my own experience it is not easy for Joe N00b to know what a working setup

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 =

On Tue, 30 Jul 2024, Harlan Stenn via Nut-upsuser wrote: > I've got a client who lives in an area where there are now frequent power > outages that last for several hours at a time. I live in an area with frequent power outages, so I use a nut configuration [1] which shuts down the system using a timer rather than waiting for LB status. Important: It requires a UPS unit capable of

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,

On Jun 9, 2017, at 10:16 AM, Roger Price wrote: > > Most of the questions asked in the nut-user mailing list seem to me to be either erudite technical discussion of new and exotic UPS units, or n00b questions of the style "I have this old UPS so I installed NUT but it didn't work". > > NUT is thoroughly documented with man pages and User Manual, but from my own

Thanks for the response, Roger. On 7/31/2024 12:19 AM, Roger Price wrote: > On Tue, 30 Jul 2024, Harlan Stenn via Nut-upsuser wrote: > >> I've got a client who lives in an area where there are now frequent >> power outages that last for several hours at a time. > > I live in an area with frequent power outages, so I use a nut > configuration [1] which shuts down

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

Allow me to suggest a couple more sample configs: 1) Server as UPS controller with clients that are also on UPS, considering shutdown sequencing and 2) Multi power supply server with multiple UPS (with or without clients). - Tim On June 13, 2017 10:01:54 PM CDT, Charles Lepple <clepple at gmail.com> wrote: >On Jun 9, 2017, at 10:16 AM, Roger Price wrote: >> >> Most of the

My thought of #2 require none of that . . . I have a server with two supplies, and two UPS units. One supply is on each UPS, and clients are distributed otherwise to balance. The main thing is to ensure that it is documented accurately how to config so that the server only shuts down when the *second* unit hits low battery . . . I found the info on this topic almost nonexistent at present . . .

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

On Sun, 16 Jul 2017, Mike Schaffner wrote: > I have 2 APC UPS systems, one is connected to my ESXi host and the other > to my FreeNAS.?? The battery for the FreeNAS will run out before the > battery for the ESXi, so I need ESXi to shutdown first.?? If I wait > until BatteryLow on ESXI, it will be too late as FreeNAS will have > already shutdown.?? How can I change the

On Thu, 3 May 2018, Daniel Hilst Selli wrote: > I was reading the user manual but something is little gray to me. Does the > master instruct the UPS to shutdown after it? I wrote up my own notes on how this works - you will find it in chapter 5.4 of http://rogerprice.org/NUT/ConfigExamples.A5.pdf > I'm asking because I'm still testing stuff here and I don't want my UPS to

My bad. I'll check it out. On Sun, 2 Jun 2024 at 08:14, Roger Price < roger_at_rogerprice.org_chribonn at duck.com> wrote: > On Sat, 1 Jun 2024, Alan via Nut-upsuser wrote: > > > root at proxmox-01:~# cat nano /etc/nut/ups.conf > > If you send us hundreds of lines of comments it makes your post difficult > to > understand. Could you trim out the comments with

> > > > 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

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 Thu, 1 Feb 2018, Lee Damon wrote: > I've "fixed" this problem by modifying the nutshutdown script: > #!/bin/sh > # stop nut driver to free up access to the device > /sbin/systemctl stop nut-driver > # make sure it has time to die > sleep 2 > # check to see if we need to actually shutdown the UPS then do it > /usr/sbin/upsmon -K >/dev/null