similar to: NUT behaviour when master system fails

Hi, In Debian lenny I used the following in upsd.conf: ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACL webinterface 192.168.0.2/32 ACL slave 192.168.50.22/32 ACCEPT localhost ACCEPT webinterface ACCEPT slave REJECT all and in upsd.users: [monmaster] password = secret0 allowfrom = localhost upsmon master [monslave] password = secret1 allowfrom =

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

Short description: when upsmon starts it logs this to /var/log/messages: Jul 11 12:35:55 sorcerer upsmon[23902]: Startup successful Jul 11 12:35:55 sorcerer upsmon[23902]: user monuser not found Near as I can tell upsd is running properly. Long description: Centos 5 system (x86_64), built nut 2.2.2 from stable source with ./configure --with-usb --with-user=nut --with-group-nut make

Hi ups-dev ! I bring you some news about my work : it works ^_^ you can now try out the new configuration formalism. I modified upsd, the drivers and upsmon to use the new formalism and the new parser (via the libupsconfig library) The SVN link : svn co svn://svn.debian.org/nut/branches/JD-NewConf How to use it : To test it, I propose that you execute the following commands : Go to the

Dear list, Can't make upssched notify me on event occured. OS: Debian, 2.6.26-1-amd64 Nut: 2.4.3-1.1squeeze1 UPS: Ippon Smart Winner 3000 connected via COM On event ( plug out the cord from UPS ) upsmon detect's status change to OB and gives WALL and syslog notify, but no script starting. In syslog no errors and no upssched process occured, just upsmon. There're no PIPE and LOCK

Hello all, I'm having problems with what I'm told should be a straightforward issue. The message in /var/log/daemon is: <quote> Feb 13 10:37:57 lupin upsmon[31324]: Master privileges unavailable on UPS [lupin1500AVR@localhost]

Here are the results from the output of upsc under different conditions from my Debian Test system with NUT 2.7.2 : Normal: ups.status: OL No wall power: ups.status: OB Runtime calibration (started from AP9630 web interface): ups.status: OB CAL So at this stage there is a difference! I then connected to my QNAP and set the UPS settings on the web interface to "Shutdown server if power

Hi... I'm almost to the point of pulling hair! I was recently given a SOLA-330 UPS However, it didn't come with the comms cable so I'm having some trouble trying to find a pin-out for this UPS and secondly exactly what driver to use with NUT ?? I've got the users manual for a SOLA-325 (from website) and this has a pin-out for this model but clearly it's not the same for

Hi, I'm using debian sarge on my server and connected a MGE-ups ellipse via the serial port. I searched the internet for the answer, but can't find it. My config files: <upsd.users> [admin] password = pwd allowfrom = 127.0.0.1/32 actions = set instcmds = all [upsmon] password = pwd allowfrom = 127.0.0.1/32 10.0.0.224/32 upsmon master [upsslave] password

Hi, this is my first nut installation, i see lot of connection failure and when i tried the configuration removing the power chord from the ups i expected tha machine will power itslef down but this has not happened. I'm using nut 2.2.2-2 from debian lenny, ups is a mustek powermust 2000 with usb cable. All config files are root:nut and 640, i've had to add nut user to nut group

I got a bunch of configfiles that look like this: mgmt-dev:/etc/nut# grep -v 'niets' * ups.conf:[ups] ups.conf:driver=newhidups ups.conf:port=auto upsd.conf:ACL all 0.0.0.0/0 upsd.conf:ACL localhost 127.0.0.1/32 upsd.conf:ACL remote 192.168.110.0/24 upsd.conf:ACCEPT remote upsd.conf:ACCEPT localhost upsd.conf:REJECT all upsd.users:[monuser] upsd.users:password = mypass upsd.users:allowfrom

Was /etc/nut/upssched-cmd automatically installed? I don't have it on my raspberry pi. :-( On 2019-04-03 1:54 p.m., Mike wrote: > I figured this out and it is working now.  This fix seems strange to me > and is possibly a bug.  I'm sharing in case it might help others. > > I had to uncomment all of the NOTIFYFLAG statements whether I was > changing them or not. 

Hi All, I have an mge pulsar esv 14+ rackmount UPS connected via straight through serial cable to a USB to serial adaptor (My motherboard does not have a native RS232 port). I am running Ubuntu Server 9.04 x64, and nut 2.4.1-2ubuntu4 installed via APT. I am getting the error: Poll UPS [ups1 at localhost] failed - Driver not connected My conf files: (ups.conf) [ups1] driver=mge-utalk

Hallo group, I am running openSUSE 10.3 with nut-2.2.0-20 installed. I have configured it as mentioned in /usr/share/doc/packages/nut/README.SUSE. on starting nut using "rcupsd start" i get following: # Starting NUT UPS monitor done Broadcast Message from root at pane (somewhere) at 22:27 ... Communications with UPS myups at localhost

Hi all, I've just upgraded my debian box from etch to lenny, and am now having Nut problems. I have read through the UPGRADING text (which helped fixed my first ups driver related problem), but have now hit another problem, which seems quite common, but non of the responses I've found on Google apply, so I'm coming to you for help. On issuing a "/etc/init.d/nut start"

Hello! I am running Slackware Linux 10.2 with kernel bareacpi.i 2.4.31. My UPS is inform GUARD series line interactive UPS This is all the info I could extract from my UPS's documentation. I downloaded and installed the NUT Slcakware package nut-1.4.1-i486-1JKv. The hostname of my system is "marto", the domain name is "mydomain". Apart from the "root", I have

Hi all I have a simple setup: Ubuntu 9.04 server APC Back-UPS ES-700 connected with USB nut installed from packages (apt-get install nut). I guess that makes it version 2.4.1 ? The problem: When issuing: upsmon -c fsd I get a messages that the server will halt, and it does. But it won't restart again. I have set the BIOS to always power on, and this works fine when if I just cut the

Hy list, first of all - yes I have read the docs, but obvious I must have missed something. The user/password setting in upsd.users seems to be ignored and I can monitor the ups with some arbitrary password. The following setup is working: Server A has nut installed and has the following config: upsd.conf: ACL localnets 192.168.101.0/255.255.255.0 ACL localhost 127.0.0.1/32 ACL all

Hello! I am running Slackware Linux 10.2 with kernel bareacpi.i 2.4.31. My UPS is inform GUARD series line interactive UPS This is all the info I could extract from my UPS's documentation. I downloaded and installed the NUT Slcakware package nut-1.4.1-i486-1JKv. The hostname of my system is "marto", the domain name is "mydomain". Apart from the "root", I have one

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)