similar to: upsmon issue: user monuser not found

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everybody, I have a Debian network server doing monitoring for three UPS devices. > MONITOR r3000xr at localhost 1 monuser xxxxxxxxxx master > MONITOR apcups01 at localhost 1 monuser xxxxxxxxx monitor-only > MONITOR apcups02 at localhost 1 monuser xxxxxxxxx monitor-only I want nut to send an email to root for every changes nut

Hi thanks Roger. Well I'm just using Ubuntu Server 16.04 LTS I only ran that command as a few guides say that's how to establish if a daemon is compiled with tcp wrappers: https://www.cyberciti.biz/faq/tcp-wrappers-hosts-allow-deny-tutorial/ I haven't really used TCP wrappers before so I'm not even sure if my hosts.allow entries are correct: upsd : ipaddressofclientgoeshere ups

Hi all, I know there are some howto's about Powerware 5115 and Ubuntu, but I can't still get that thing working. Can someone give some light... 1. Powerware 5115, serial port (ttyS0) 2. Ubuntu 6.06.1 as LTSP-server As reference: http://gentoo-wiki.com/HOWTO_NUT http://keystoneit.wordpress.com/2006/09/25/network-ups-tools-nut-on-ubuntu/ --- a. I try to start driver as root. root at

Hi all, I know there are some howto's about Powerware 5115 and Ubuntu, but I can't still get that thing working. Can someone give some light... 1. Powerware 5115, serial port (ttyS0) 2. Ubuntu 6.06.1 as LTSP-server As reference: http://gentoo-wiki.com/HOWTO_NUT http://keystoneit.wordpress.com/2006/09/25/network-ups-tools-nut-on-ubuntu/ --- a. I try to start driver as root. root at

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

Greetings, I imagine this question must have been answered previously on the list, but I can't search for the answer because the archives are gone. Executive summary: I am trying to install and configure nut 2.0.1 on Fedora Core. I have a SmartUPS Pro plugged into a USB port. Upsmon is logging "UPS myups@localhost is unavailable" to syslog and via wall when it starts up and

Try ALL:ALL in /etc/hosts.allow temporarily. If that still doesn't work, it's likely something else. If it does, only then screw with creating narrow rules . . . - Tim On November 25, 2016 6:37:02 AM CST, Roger Price <roger at rogerprice.org> wrote: >On Fri, 25 Nov 2016, Jonah Naylor wrote: > >> upsd : ipaddressofclientgoeshere > >If it were me I would write >

Hi thanks Roger, I've amended my hosts.allow file to your suggested one - thanks for that. I'm still getting "Connection refused on the client cgi screen as well as in the shell it gives me UPS upsname at ipaddresshere is unavailable... Any ideas what I can try next to debug why it's not working. Also should the "allowfrom = clientIPaddresshere" line be in my monuser

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"

> If you have any more questions regarding this, please use the nut-upsuser > mailinglist instead. Redirected to the appropriate list, sorry. > > Is there a place in the upsmon.conf (or elsewhere) > > file where one may enter something like: > > > > OVERRIDE_BATTERY_CHARGE_LOW 20 > > OVERRIDE_BATTERY.LOW 240 > > > See 'man 8 upsrw'.

Hello, I'm facing problems as I'm installing NUT to monitor a MGE Ellipse ASR600USBS on a FreeBSD 6.1 box. UPS is recognized as : ugen0: MGE UPS SYSTEMS ELLIPSE, rev 1.10/42.41, addr 2 I'm temporarily using root profile (devfs/devd scripts not modified atm). newhidups starts & runs fine (unplugging mains makes newhidups outputs lots of data when started with -DDDD flags)

I meant to send this to the list but evidently only sent it to David. Since sending it I've done a second test which shows what a successful snmpset looks like. First attachment, from the forwarded email, is nutout.txt. Second attachment is snmpout.txt. nomad -------- Forwarded Message -------- Subject: Re: [Nut-upsuser] [EXTERNAL] SNMP shutdown timing out Date: Mon, 4 May 2020 09:28:57

---> On 15/03/2009 8:00 AM, nut-upsuser-request at lists.alioth.debian.org wrote: > Message: 1 > Date: Sat, 14 Mar 2009 21:47:08 +0100 > From: Arjen de Korte <nut+users at de-korte.org> > Subject: Re: [Nut-upsuser] Weird Load and Battery Temp Readings > To: nut-upsuser at lists.alioth.debian.org > Message-ID: <20090314214708.37122w00w79l6u9s at mail.de-korte.org>

Is anyone using snmp-ups with the -k option successfully? This is really starting to look like a bug somewhere in nut, not a config problem. I've just tried the same command from a FBSD box with the same unfortunate result. Mind you, it could be the UPS card, I'm using the same one for both tests. : || nomad at castle nut-2.7.4 [93] ; please drivers/snmp-ups -a nutdev1 -x

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]

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

On Jan 9, 2014, at 4:00 PM, Lonnie Abelbeck wrote: > 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

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

Hello, we have two UPSes - one Galaxy and one from Socomec, both monitored by the NUT server. The NUT server runs the version 2.7.2. We have roughly 3500 clients running upsmon, reading the status of both UPSes. They run mainly the version 2.6.4 and some 2.7.2. We observed the following on both client versions, regardless whether we run upsmon in the daemon or debug mode: Running upsc socomec