similar to: Possibility to set NUT drivers to "monitor only"?

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

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

Hello and welcome, Can you please point to any online "PiNUT" docs, if that is a project name? I did not find anything that looked specific to the key word. In any case, the "primary" role of upsmon applies to any UPS that it is connected to and can directly manage, so in case of a power outage it tells everyone else (secondaries) to shut down first, and then runs the UPS

I have a PiNUT setup. It is physically connected (USB) and monitoring 3 UPS units (UPSA, UPSB, and UPSC). The PiNUT is powered by USPA. UPSA powers other equipment with clients installed. Other equipment will be clients of UPSB and UPSC. I am confused about how to correctly configure the PiNUT settings. I have searched for howto notes but they seem to have conflicting information. Should

Well it is the season for storms and power outages here in the US PNW. I noticed that today when the power went out, NUT mostly did what I hoped/wanted. But it did not actually turn off the UPS at all. The UPS kept beeping and I had to turn it off manually. I thought that NUT would handle this. But perhaps it cannot for my unit? Or perhaps I have things improperly configured? Any suggestions?

Here is the previous email that I sent directly to Charles Lepple. ?I am now sending to the correct email with cc to Charles. ---------------- I am looking at, and trying to understand the rest of the conf files. ?But first want to askabout something from this message:[CODE]root at debian:/home/john# upsdrvctl startNetwork UPS Tools - UPS driver controller 2.7.2Network UPS Tools - Megatec/Q1

Hello. I've tried to configure Windows (complete port, Beta): Windows MSI installer 2.6.0-1 with my Powerware 5115 connected via USB port but have no luck. Here is my config files: *nut.conf:* MODE = netserver *ups.conf:* [PW5115] driver = bcmxcp_usb port = notUsed desc = "PowerWare 5115" *upsd.conf:* LISTEN 192.168.1.12 3493 *upsd.users:* [monuser]

I just did a fresh installation of Debian Jessie on one of my servers, but NUT won't configure and install. When I try to install, I get the following: Setting up nut-client (2.7.2-1+b2) ... Job for nut-monitor.service failed. See 'systemctl status nut-monitor.service' and 'journalctl -xn' for details. invoke-rc.d: initscript nut-client, action "start" failed.

Dear all, I am using the Microsoft Windows XP SP3 and would like to use the Windows MSI installer 2.6.1-1 I tried to configure NUT manually, but until now failed. If possible I would like to use the PowerWalker Line-Interactive VI 1400 device which should work with blazer_usb Does anyone have possibility to provide me the correct configuration for the files (ups.conf, upsd.{users,conf} and

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

hello, I installed with NUT UPS MGE Pulsar Evolution 2200 all orders of arrest, interrogation etc etc ... UPS work well However, I have a problem with the order in NOTIFYCMD upsmon.conf that not run ... I created a script that generates a simply log I indicated in upsmon.conf NOTIFYCMD / home / nut / alert_ups.sh below my upsmon.conf RUN_AS_USER nut MONITOR pulsar at localhost 1 admin1

Hi Leslie, 2014-09-29 17:14 GMT+02:00 Leslie Rhorer <lrhorer at mygrande.net>: > > I just did a fresh installation of Debian Jessie on one of my > servers, but NUT won't configure and install. When I try to install, I get > the following: > > Setting up nut-client (2.7.2-1+b2) ... > Job for nut-monitor.service failed. See 'systemctl status >

hi: my testing server has two power supply and attach to two ups. one of the ups is connect to the server with usb. my upsmon.conf like below: # for two ups MONITOR ftups at localhost 1 monmaster nutmaster master MONITOR ftups at 10.1.1.2 1 monslave nutslave slave MINSUPPLIES 1 # for early shutdown NOTIFYFLAG ONBATT EXEC+WALL+SYSLOG NOTIFYFLAG ONLINE EXEC+WALL+SYSLOG NOTIFYCMD

I have only RS-232 on the box (meanwhile, it was manufactured on march of 2011) Here is my configs: nut.conf: * * MODE = netserver ups.conf: * * [KIN1500] driver = powercom port = notUsed desc = "Powercom KING PRO KIN-1500AP RM" upsd.conf: * * LISTEN 192.168.1.2 3493 upsd.users: * * [monuser] password = xxxxxxxx upsmon master

Hi Charles, Are there any logs generated by the WinNUT client? I'm trying to configure it for the first time and I cannot make it to work. Here are my settings: Nut.conf MODE=netclient Upsmon.conf MONITOR ups at pfsense 1 <username> <password> slave MINSUPPLIES 1 SHUTDOWNCMD "C:\\WINDOWS\\system32\\shutdown.exe -s -t 0" POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME

An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20120104/34be491b/attachment.html>

I am having some problems getting NUT to run with my cyberpower avr1200 (brandnew). I have a straight through serial cable, and I am getting this: /usr/local/etc/rc.d/nut.sh start Starting nut. Network UPS Tools - UPS driver controller 2.0.2 Network UPS Tools - CyberPower driver 1.00 (2.0.2) Giving up on hardware detection after 3 tries Unable to get initial hardware info string Driver failed

I am having some problems getting NUT to run with my cyberpower avr1200 (brandnew). I have a straight through serial cable, and I am getting this: /usr/local/etc/rc.d/nut.sh start Starting nut. Network UPS Tools - UPS driver controller 2.0.2 Network UPS Tools - CyberPower driver 1.00 (2.0.2) Giving up on hardware detection after 3 tries Unable to get initial hardware info string Driver failed

Ok, I installed the ups, and installed nut, and /proc/bus/usb/devices says this T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=06da ProdID=0002 Rev= 0.01 S: Manufacturer=POWERWARE S: Product=Powerware UPS C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 20mA I: If#= 0 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=00