similar to: UPS not Shutting Down

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 =

Thank Charles. I've bookmarked this and will try to experiment a bit. On Mon, 3 Jun 2024, 04:33 Charles Lepple via Nut-upsuser, < nut-upsuser_at_alioth-lists.debian.net_chribonn at duck.com> wrote: > On Jun 2, 2024, at 12:14?PM, Roger Price wrote: > > > >> Is the comment about offdelay (in red) correct / can this line be > eliminated?. > > > > My

Hello, I am a new user of NUT and trying to wrap my ahead around a couple of things. I installed NUT 2.7.4-13 from package on RasPi 4, running Raspbian Linux 11 (bullseye). I have Cyberpower SL700U connected to it. For testing I set battery.charge.low to 90, so I wouldn't have to wait a long time. See all relevant config below. First of all, what seems to happen is that UPS gets to the low

2018-02-28 21:11 GMT+01:00 Jairo Rotava <jairo.rotava at gmail.com>: > Hello, > > I think that on this file nutdrv_qx_megatec.c the definition for > shutdown.stayoff may be wrong. In the file the definition is "S%sR0000\r"m > while on the megatec protocol description ( > http://networkupstools.org/protocols/megatec.html) the command is just > "S%s\r".

Angel Tsankov wrote, On 12/6/2013 12:31 PM: > Hello, Ren?. > >> You can change the parameter >> ups.delay.start into your UPS to set the "Interval to wait before >> (re)starting the load (seconds)" >> >> use upsset to change the value. > > So far, the ups.delay.start parameter in my MGE Protection Center 675 > has always been equal to the

Hello there. Have been experimenting with an APC Smart-UPS 1500 RM and would like to share the results of my research. I hope this could be of help to people having this kind of units. I would also like to give something back to the NUT community. :) Here are the details of the unit in question (a 1500 VA rack mountable one): Model: Smart-UPS 1500 RM Firmware revision: 617.3.I USB firmware

Welcome, Acctualy, I'm try to poweroff my ESXi (6.7). Virtual machine with Ubuntu and redirected USB port with APC Back UPS CS 650, have nut-server and send info to ESXi. When battery is low, ESXi poweroff gracefully all VM and same ESX go down. This work fine and don't have any problem. But important to me, is set to more offdelay on UPS than the default 60 sec. (cut off power socket

Hi Roger, Hi all,   > Does upsmon.conf specify a shutdown on LB? I think so. You mean SHUTDOWNCMD? The relevant parts of my upsmon.conf (notifications removed): MONITOR ups at localhost 1 upsmaster secret master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" POLLFREQ 5 POLLFREQALERT 2 HOSTSYNC 15 DEADTIME 40 POWERDOWNFLAG /etc/killpower RBWARNTIME 43200 NOCOMMWARNTIME 1800

On Tue, Oct 2, 2018 at 3:59 PM Charles Lepple <clepple at gmail.com> wrote: > > On Sep 27, 2018, at 6:59 PM, Gabriel <jarod125 at gmail.com> wrote: > > > > Hi, > > > > I'm struggling with a peculiar issue with my UPS. After a power > > outage, the devices powered by it properly shut down via nut. > > Eventually, the UPS also goes down.

Dear All, I am running Slackware64-14.1(Linux marto 3.10.17 #1 SMP Fri Feb 14 16:39:21 CST 2014 x86_64 Intel(R) Pentium(R) CPU G3250 @ 3.20GHz GenuineIntel GNU/Linux) with kernel 3.10.17 and nut package nut-2.6.5-x86_64-1_SBo, buit from source using the build script http://slackbuilds.org/repository/14.1/system/nut/ In the README.Slackware it is suggested that the commands for killing the

Hi, I try to install the newhidups driver for a MGE Pulsar M2200 connected to a USB port under Linux Red Hat 4 Upd 4. I have compiled and installed the usb driver (make usb && make install-usb). I followed the instructions in /nut-2.0.5/scripts/hotplug-ng/README abour the /etc/udev/rules.d/025_nut-usbups.rules. The ups is recognized by the kernel: Mar 12 14:52:03 serveur1 kernel: usb

Hi, I try to install the newhidups driver for a MGE Pulsar M2200 connected to a USB port under Linux Red Hat 4 Upd 4. I have compiled and installed the usb driver (make usb && make install-usb). I followed the instructions in /nut-2.0.5/scripts/hotplug-ng/README abour the /etc/udev/rules.d/025_nut-usbups.rules. The ups is recognized by the kernel: Mar 12 14:52:03 serveur1 kernel: usb

On 12/06/2013 10:57 PM, Kris Jordan wrote: > [...] > (*) Some UPS's do provide extra options to determine when they will > restore power to load. That would be a nice feature. Anyway, it is a strange thing that I can set the waiting time for power to be restored if main power comes back before offdelay has elapsed, but the UPS ignores this setting if main power comes back after

Angel Tsankov wrote, On 12/24/2013 1:22 AM: > On 12/06/2013 10:57 PM, Kris Jordan wrote: > > [...] >> (*) Some UPS's do provide extra options to determine when they will >> restore power to load. > > That would be a nice feature. > > Anyway, it is a strange thing that I can set the waiting time for > power to be restored if main power comes back before

The serial number looks completely different, but the firmware seems to be the same. Pasting upsc output: battery.charge: 80 battery.charge.low: 10 battery.charge.warning: 50 battery.date: 2013/12/04 battery.mfr.date: 2013/12/04 battery.runtime: 1781 battery.runtime.low: 120 battery.temperature: 29.2 battery.type: PbAc battery.voltage: 13.5 battery.voltage.nominal: 12.0 device.mfr: American Power

Hi, thanks for your reply. >> The Unit is new, the battery drains because it went down to about 15 >> percent before NUT shuts it down. >> >> Yes, I can here a "clac". The problem is not the shutdown procedure, >> it works quite good. After the Unit reaches 20 percent the NUT-Server >> on the pi shuts down the system and the ups is turned off as

Hi Charles, > Sigh, I wish the vendors wouldn't change operation without changing identifiers. > > Do you have any recommendations on how the driver should decide whether it is an old 0x0004 or new 0x0004 device? No-no, there is no an old 0x0004 or new 0x0004 device, I guess that we have to handle general case for all 0d9f:0x0004 devices. From PCM_USB_LIST_device2014.pdf attached

Set with upsrw: ups.delay.shutdown=60 is the same as offdelay = 30. This time was done correctly by UPS. Set with upsrw: ups.delay.start=90 is the same as ondelay = 40. The UPS shut down and reset and forget about the settings. If I use the program in Win 10 settings in the program from Eaton are stable!? Jan. > -----Original Message----- > From: Nut-upsuser

Hello, looking for replacements for some older Powerware equipment I found the MGE Pulsar Extreme 1000C and I'm currently testing one with nut-2.0.3 on a self-brewn i386-linux. Upto now everything seems to work fine - except I can't get the power outlets switching on again after mains returns. As this works with Personal Solution-Pac 2 on W2k I thought that there might be a way to

On Jan 21, 2015, at 9:15 AM, Sebastian Hosche <sebastian.hosche at web.de> wrote: > Hi there, > > I just purchased a CyberPower BR850ELCD and while setting NUT up with the install instructions from the homepage was pretty straightforward, and the UPS was detected by the usbhid-ups driver, I'm having problems getting the UPS to work properly. > > First issue: whatever I