similar to: What is the purpose of the upsmon setting in upsd.users?

[please use reply-all when responding - the list does not mangle reply-to headers. thanks!] On Jun 22, 2016, at 4:06 AM, Andr? H?nsel wrote: > > On Mittwoch, 22. Juni 2016 09:21 Andr? wrote: > >> Hi list, >> >> (I think) I understand that in upsmon.conf, the MONITOR line ends with >> "master" or "slave". Basically if it's master it will

On Mittwoch, 22. Juni 2016 17:50, Roger Price wrote: On Wed, 22 Jun 2016, Andr? H?nsel wrote: > > Now, what I see is that when the UPS feeding server-1 goes LB, > > server-1 is indeed shut down, but it seems that the UPS is never switched off. > > > > This is a problem because when power is restored after shutdown, but > > before the battery runs out (with no

On Mittwoch, 22. Juni 2016 09:21 Andr? wrote: > Hi list, > > (I think) I understand that in upsmon.conf, the MONITOR line ends with "master" or "slave". Basically if it's master it will wait for slaves to shut down and if it's slave it will signal the master to switch off the UPS after shutdown. > > To be able to monitor a network UPS as a slave, there

I have two hosts. One is the ups-server. It's generator powered and can be assumed to never go down. This is the one that all the UPSs are connected to. It has: - the UPSs configured in upsd.conf - a "upsmon master" user in upsd.users - an empty upsmon.conf The other one is server-1. Its upsmon.conf contains: MONITOR test-apc at ups-server 1 monuser blah slave Now, what I see is

Hi, usually I use rsync with -a but recently I used it without this option and discovered that the same files are synced over and over again (as shown by -v). Of course the rsync algorithm avoids the traffic but the files are all listed. As soon as I use -a for one time those files are not transferred again, even when I remove the -a again. So I suspect, when building the file list, rsync

On Donnerstag, 23. Juni 2016 14:14, Charles Lepple wrote: > The "upsmon slave" setting should not prevent clients from connecting. Can you provide more details about the system? If this is a distributor-provided package, did they link against TCP-wrappers (using /etc/hosts.deny)? It's the Debian (Raspbian) jessie package. Anyway, I'm sorry, I just saw that I had it set to

Using the HOWTO in http://keystoneit.wordpress.com/2006/09/25/network-ups-tools-nut-on-ubuntu/ I installed nut on an Ubuntu Edgy LAMP Server with an Eaton Powerware 5110 attached to it via usb. But nut fails to start properly (see the error message "Starting Network UPS Tools: (upsdrvctl failed) upsd upsmon" below). It then complains about communication with the UPS being lost ("UPS

Hello! I try use NUT on some servers. When i use this package on x64 Windows 2003 servers, upsmon hangs on with error: Faulting application upsmon.exe, version 0.0.0.0, faulting module upsmon.exe, version 0.0.0.0, fault address 0x0000458f. I try use another server, on 32-bit all is ok. Problem only on x64 platform (maybe in libusb)? And no different - upsmon master or slave. C:\Program Files

On Thu, 6 Aug 2020, Todd Benivegna wrote: > ... I grep’d the syslog and here’s the results: Could you also grep for upsd and upsmon in the NAS log? Is this possible? > proton at proton:~$ sudo grep upsmon /var/log/syslog > Aug  6 19:19:09 proton upsmon[1552]: UPS ups at 192.168.1.70 on battery > Aug  6 19:19:14 proton upsmon[1552]: UPS ups at 192.168.1.70 on line

Dear all, I got nut going on one machine as standalone and on another 2 as master/slave and would like to add some checks to nagios to make sure that things are in order. Most of the checks I've seen out there use upsc to check the ups. This is a step forward compared to no monitoring, however as far as I can tell it doesn't really address what I think is a critical point: upsmon is

I have a Dell 500w UPS and it works great with Ubuntu 12.04 LTS and Network UPS tools 2.6.3 via usb. This powers a standalone server for the purposes of clean shutdowns. This was installed using "sudo apt-get install nut" and there are no issues with the Server > nut > ups chain. I am using the usbhid-ups driver and haven't had any issues. I am trying to also add an NAS to the

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

Hello, I wondered how folks monitored slaves. In my case, I am using Nagios and the check_ups plugin. It seems to work fine but being new to nut, I'm seeking confirmation that this is a sane approach. The goal: confirm the slaves have contact with the master. The environment: * FreeBSD 12.1 * nut-2.7.4 installed from package Background: I am replacing an APC 2200 UPS (still in use) with

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

Hi, I'd like to better understand the merits of NUT clients (slaves) properly authenticating with the NUT server (master). NUT allows clients to retrieve UPS status (upsc ups at 10.10.10.1) without authenticating, shutdowns are properly trigger via polling. From testing one apparent benefit of authenticating is the client receives the shutdown event more quickly rather than the polling

[Please use reply-all to keep the discussion on the list, thanks] On Nov 6, 2014, at 10:19 PM, Charles Lepple <clepple at gmail.com> wrote: > On Nov 6, 2014, at 12:48 PM, Steve Read <sd_read at hotmail.com> wrote: > >> I am presently upgrading my servers. The old ones are running Suse 10.1 and I am upgrading to the most recent Debian. > > What version of NUT on

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

Thank you for answer Stuart >?????, 13 ???? 2016, 17:54 +03:00 ?? Stuart Gathman <stuart at gathman.org>: > >On 07/13/2016 10:02 AM, Stuart Gathman wrote: >> On 07/13/2016 04:17 AM, Dmitri Stepanov wrote: >>> I need to shutdown a number of hosts which has not NUT from one which has it. >> Let's make sure you are not missing an obvious point. By

So I finally got a test in after I changed my RPi to the master and everything else (including my Synology) to slaves.  Before I did that though, I timed the shutdown of my Synology since it is the slowest slave to shutdown.  It took 40 seconds to shutdown, so I changed HOSTSYNC in upsmon.conf on the master (“Proton”) to 60.  I then did a test ("sudo upsmon -c fsd”). The slaves shutdown, then

Hey, I have a Compaq T2000 UPS that I use to power my firewall, dmz, and two internal machines and I've just started implementing UPS monitoring to shut the systems down in the event of an outage instead of relying on me, but I've run into a snag. Reading the documentation, it seems the client has to contact the server. The problem is I really don't want to open a port form the