search for: monmaster

...> In that case - what about not starting nut-client (upsmon) at all? upsc > (to see the output of the ups) requires nut-server only. > > Or, if you really want upsmon: > - Set up a dummy ups _and_ the ups to be tested. > - in upsmon.conf set > MONITOR dummyups at localhost 1 monmaster masterpass master > MONITOR testups at localhost 0 monmaster masterpass master > and > MINSUPPLIES 1 > > That way the dummy ups will "power your computer" and the testups will > supply 0 power so its power outage gets ignored. To simplify, you could eliminate "du...

Hi all, i've a problem with only a command in all suite: upsrw. root at ProLiant:/etc/nut# upsrw -u monmaster -p p455w0rd -s ups.delay.shutdown=180 ups Unexpected response from upsd: ERR ACCESS-DENIED root at ProLiant:/etc/nut# upsc and upsmon work greatly. This is in my /etc/host.allow: upsd : localhost, LOCAL, 127.0.0.1, [::1] : ALLOW What miss ? Thank you!

...sswords obliterated. # Network UPS Tools: example ups.conf user nutmon [lupin1500AVR] driver = cyberpower port = /dev/tty01 # Network UPS Tools: example upsd configuration file ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACCEPT localhost REJECT all # Network UPS Tools: Example upsd.users [monmaster] password = * allowfrom = localhost actions = SET instcmds = ALL # Network UPS Tools: example upsmon configuration RUN_AS_USER nutmon MONITOR lupin1500AVR@localhost 1 monmaster * master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /usr/local/ups/bin/notifyme POLLFRE...

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

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: MO...

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

...y build the dummy-ups driver. > Thank you for your reply. I tested configuration on live environment and on dummy-ups. I also built the newest NUT version, tested on dummy-ups and it didn't work with my config. My config files: upsmon.conf: RUN_AS_USER root MONITOR UPS_251 at localhost 2 monmaster password master MONITOR UPS_252 at localhost 2 monmaster password master MINSUPPLIES 2 SHUTDOWNCMD "/etc/ups/test" NOTIFYCMD /usr/sbin/upssched POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 30 POWERDOWNFLAG /etc/killpower NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC NOTIFYFLAG ONBATT...

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

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 /usr/sbin/upssched the early shutdown script use "upsmon -c fsd" to set FSD to master ups. but whe...

Thanks for suggetions and keep me indumb about making of Debian packages:D I will try this package "nut_2.2.0-2_i386.deb" One little questionm, shoud I use newmge-shut driver? - my ups is quite old - more then 3 years, connected through serial cable. >> PS: Arjen de Korte suspected something was wrong around my "heater" load, >> for now I have used two 150W lamps

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

...very time gets old > real quick. In that case - what about not starting nut-client (upsmon) at all? upsc (to see the output of the ups) requires nut-server only. Or, if you really want upsmon: - Set up a dummy ups _and_ the ups to be tested. - in upsmon.conf set MONITOR dummyups at localhost 1 monmaster masterpass master MONITOR testups at localhost 0 monmaster masterpass master and MINSUPPLIES 1 That way the dummy ups will "power your computer" and the testups will supply 0 power so its power outage gets ignored. CU, Gernot

...h=110 ups.conf: default.battery.voltage.low=86.7 ups.conf: offdelay=300 ups.conf: ondelay=6 ------------- upsd.conf:LISTEN 127.0.0.1 3493 upsd.conf:LISTEN 192.168.7.105 3493 ----------- upsd.users:[root] upsd.users:password=**password** upsd.users:actions=set upsd.users:instcmds=all upsd.users:[monmaster] upsd.users:password=***password* upsd.users:upsmon master upsd.users:[monslave] upsd.users:password=**password** upsd.users:upsmon slave upsd.users:[piebnsrv] upsd.users:password=**password** upsd.users:upsmon slave ------------ upsmon.conf: MONITOR ippon at localhost 1 monmaster bggjy master MI...

Hello, I've got a setup with NUT, where we've got two UPSes, ups1 and ups2. UPS1 supports our servers, while UPS2 supports our desktop boxes. We monitor both of them via USB on a box now called "upsmon". The interesting point comes here. We monitor both UPSes on the upsmon box, but if UPS2 fails, which supports our desktop boxes, NUT shouldn't initiate a shutdown in

...1 #NUT logs 1. Feb 22 19:48:43 microserver upsd[2586]: listening on 127.0.0.1 port 3493 2. Feb 22 19:48:43 microserver upsd[2586]: Connected to UPS [ups]: blazer_usb-ups 3. Feb 22 19:48:43 microserver upsd[2596]: Startup successful 4. Feb 22 19:48:43 microserver upsd[2596]: User monmaster at 127.0.0.1 logged into UPS [ups] 5. Feb 22 19:48:43 microserver upsmon[2608]: Startup successful 6. Feb 22 19:48:48 microserver upsmon[2610]: UPS ups at localhost: forced shutdown in progress 7. Feb 22 19:48:48 microserver upsd[2596]: Client monmaster at 127.0.0.1 set FSD on UPS...

upsmon.conf using NOTIFCMD and NOTIFYFLG is working well, it is calling my script "notify" on requested events (ONBATTERY,LOWBATTERY and ONLINE). Command #upsmon -c fsd -u monmaster myups at localhost gracefully shutdown my box and after several seconds switch off the ups's load. Two problems: - notify script is called and executed as user "nut" (as it used to be defined in nut package for Debian 4.0 Etch). To execute forced shutdown it must be root!...

...ups rqt 161 rq 1 len 8 ret -71 Oct 13 12:57:12 echo upsmon[5060]: UPS smart750@localhost on battery Oct 13 12:57:12 echo upsmon[5060]: UPS smart750@localhost battery is low Oct 13 12:57:12 echo upsmon[5060]: UPS smart750@localhost battery needs to be replaced Oct 13 12:57:12 echo upsd[5056]: Client monmaster@127.0.0.1 set FSD on UPS [smart750] Oct 13 12:57:12 echo upsmon[5060]: Executing automatic power-fail shutdown Oct 13 12:57:12 echo upsmon[5060]: Auto logout and shutdown proceeding Oct 13 12:57:17 echo upsd[5056]: Host 127.0.0.1 disconnected (read failure) Oct 13 12:57:17 echo shutdown[14003]: shu...

...27.0.0.1/32 ACL nutMaster xx.xx.xx.xx1/32 ACL nutSlave1 xx.xx.xx.xx7/32 ACL nutSlave2 xx.xx.xx.xx3/32 ACCEPT localhost nutMaster nutSlave1 nutSlave2 REJECT all upsd.users ---------- $ grep -v "#" upsd.users [upsadmin] password = **** allowfrom = nutMaster actions = SET instcmds = ALL [monmaster] password = **** allowfrom = nutMaster upsmon master [monslave-nutSlave1] password = **** allowfrom = nutSlave1 upsmon slave [monslave-nutSlave2] password = **** allowfrom = nutSlave2 upsmon slave upsmon.conf ----------- $ grep -v "#" upsmon.conf MONITOR apcups at nutMaster.domain.uk...

Hi, I've got two MGE Ellipse 1500 UPS connected via usb to an ubuntu jaunty system with nut and libupsclient1 2.4.1-2ubuntu4. As soon as I start the driver for the second one, they start fighting each other and I get no data. I found an older post to this list that said: If you want to monitor multiple UPSes through usbhid-ups, you *must* make sure that each one can be uniquely identified

...# but you still want to monitor. Use this when you want to hear about # changes for a given UPS without shutting down when it goes critical, # unless <powervalue> is 0. # # <username> and <password> must match an entry in that system's # upsd.users. If your username is "monmaster" and your password is # "blah", the upsd.users would look like this: # # [monmaster] # password = blah # allowfrom = (whatever applies to this host) # upsmon master (or slave) # # "master" means this system will shutdow...