search for: minsupply

I changed IP to NAS IP instead of my PC IP and also used NAS login and pass. Didn't work. When I wanted to launch WinNUT with new settings I got: "Fatal error: insufficient power configured!" (same as before) I got this log: Level INFO 10/26/2016 10:46:17 Detected OS as Windows NT Level NOTICE 10/26/2016 10:46:17 Network UPS Tools upsmon 2.0.0.4 Level INFO

This was only the log from the program. I'm sending my upsmon.conf attached (I removed nas ip number, admin login and pass (no spaces in parameters) and also changed back minsupplies to 1), the rest of the settings are the same as I used. Best, Tom 2016-10-26 14:21 GMT+02:00 Charles Lepple <clepple at gmail.com>: > On Oct 26, 2016, at 4:56 AM, Tomasz Przychodzie? wrote: > >

On Dec 7, 2015, at 4:21 PM, Gernot Zander <debian at scorpio.in-berlin.de> wrote: > > Hi, > > am 7 Dez schrieb Marks, Connor: >> Well I just need to monitor the UPS battery for testing and I do about >> 10 UPS's a day. So having to restart my computer every time gets old >> real quick. > > In that case - what about not starting nut-client (upsmon)

On Jan 21, 2014, at 9:24 AM, Rafal Oleszek wrote: > I tried all options: > 1,2 > and in MINSUPPLIES: 1,2,3,4 > still didn't work. My mistake - I gave you the wrong advice before. For MINSUPPLIES, I'm used to either a 1:1 UPS-to-server ratio, or 2:1 where the server can run with either power supply unpowered. I just tried this in upsmon.conf: MONITOR dummy1 1 monuser

On Jan 21, 2014, at 8:05 AM, Rafa? Oleszek wrote: > MONITOR UPS_251 at localhost 2 monmaster password master > MONITOR UPS_252 at localhost 2 monmaster password master I think the "2"s here should be "1". "powervalue is an integer representing the number of power supplies that the UPS feeds *on this system*." So if UPS_251 is connected to one power supply on

On Oct 26, 2016, at 4:56 AM, Tomasz Przychodzie? wrote: > > Level INFO 10/26/2016 10:46:17 Detected OS as Windows NT > Level NOTICE 10/26/2016 10:46:17 Network UPS Tools upsmon 2.0.0.4 > Level INFO 10/26/2016 10:46:17 Config Load: MINSUPPLIES set to 1 > Level INFO 10/26/2016 10:46:17 Config Load: NOTIFYCMD set to "c:\Program

On Jan 21, 2014, at 3:16 AM, Rafa? Oleszek wrote: > I would like to mention that MINSUPPLIES manipulation doesn't work. My nut version is : 2.2.2-4 (RHEL 5) What do your configuration files look like? Setting MINSUPPLIES to 2 should work. You can run upsmon with a debug level of 3 or greater, and it will print the current and minimum "power value", which is what determines

I tried all options: 1,2 and in MINSUPPLIES: 1,2,3,4 still didn't work. UPS_251 and UPS_252 feeds all environment and it's not feed directly one server, but many of them. > On Jan 21, 2014, at 8:05 AM, Rafa? Oleszek wrote: > >> MONITOR UPS_251 at localhost 2 monmaster password master >> MONITOR UPS_252 at localhost 2 monmaster password master > > I think the

> What do your configuration files look like? Setting MINSUPPLIES to 2 should work. You can run upsmon with a debug level of 3 or greater, and it will print the current and minimum "power value", which is what determines when to shut down. > > Also, if you don't want to wait for both UPSes to drain to the low battery state, you can set up a pair of dummy-ups drivers. I'm

> On Jan 21, 2014, at 9:24 AM, Rafal Oleszek wrote: > >> I tried all options: >> 1,2 >> and in MINSUPPLIES: 1,2,3,4 >> still didn't work. > > My mistake - I gave you the wrong advice before. For MINSUPPLIES, I'm used > to either a 1:1 UPS-to-server ratio, or 2:1 where the server can run with > either power supply unpowered. > > I just tried

I've used nut for simple configurations before but now one has grown to a more complex setup and can't seem to find any info online. I would like to have single central nut master monitor a bank of UPSs for a whole rack of servers with redundant PSUs. So UPS A1 ---> Server group A PSU 1 UPS A2 ---> Server group A PSU 2 UPS B1 ---> Server group B PSU 1 UPS B2 ---> Server

On Oct 14, 2014, at 12:12 PM, Michael Stinaff <mstinaff at gmail.com> wrote: > I've used nut for simple configurations before but now one has grown to a more complex setup and can't seem to find any info online. > > I would like to have single central nut master monitor a bank of UPSs for a whole rack of servers with redundant PSUs. > > So > UPS A1 --->

Maybe this will clear up what I was initially thinking. In this diagram all lines on the right of the UPSs are power lines and all lines on the left are serial/usb lines. .---. +--|UPS+-----+--------+--------+---... | | A1| | | | | '---' .---+--. .---+--. .---+--. | |Server| |Server| |Server| | | A1 | | A2 | |

Hi, I have data room with single master nut instance which calling scripts to shutdown environment. I have two Delta UPS reachable from network. Everything works fine but I need to configure nut to shutdown environment when both UPS on battery or low battery. Can you advise me how to do that (is it possible?). THX for any help. -------------- next part -------------- A non-text attachment was

I would like to mention that MINSUPPLIES manipulation doesn't work. My nut version is : 2.2.2-4 (RHEL 5) -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2274 bytes Desc: Kryptograficzna sygnatura S/MIME URL:

Hi, am 7 Dez schrieb Charles Lepple: >> MONITOR dummyups at localhost 1 monmaster masterpass master >> MONITOR testups at localhost 0 monmaster masterpass master >> MINSUPPLIES 1 > To simplify, you could eliminate "dummyups" and use "MINSUPPLIES 0". Maybe there's a bug. To monitor an UPS wich doesn't supply power to a raspi I used: MONITOR

Hi, Another beginner question. I spend hours trying to find the solution for how to configure winnut properly but I' struggling to make it work. I want my QNAP NAS TS-231 to work as a master and send signal to the PC to shut it down during power outage. I configured QNAP properly (like this: http://geekbeat.tv/qnap-adding-external-devices-qnap), but I don't know what to do next. I work

Hello, and welcome to the NUT community! :) On one hand, it would generally help to read up the documentation about NUT architecture, seeing as it is a crucial part of your systems' uptime and data integrity. On another hand, for this particular use-case: it is quite possible to set up monitoring-only systems which only inform you if some *other* NUT data server has had interesting

Well I just need to monitor the UPS battery for testing and I do about 10 UPS's a day. So having to restart my computer every time gets old real quick. -----Original Message----- From: Rob Crittenden [mailto:rcrit at greyoak.com] Sent: Monday, December 07, 2015 11:49 AM To: Marks, Connor; nut-upsdev at lists.alioth.debian.org Subject: Re: [Nut-upsdev] Stopping Machine powering off On

Yes both UPS units are on different power supplies. MINSUPPLIES is set to 1. Afaik NUT waits for OB and LB before shutting down the system. Is there a way to change this behavior to only wait for OB? Then I would use FINALDELAY in case the power outage doesn't last long. I already tried to change the battery.runtime.low setting over the webinterface of the CS121 (snmp is readonly) but with