similar to: Passwords not verified in upsmon?

Everything runs fine for several hours, then communication is lost and nut doesn't reestablish communication on its own. Running sudo upsdrvctl stop then sudo upsdrvctl start reestablishes communication. OS Version: Linux piaware 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux Nut Version: 2.7.2-4 Nut Installation Method: apt Device: CyberPower PR1500LCD Uses ? ? Generic

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

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 =

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

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

those mails list are from last century but i give it a try ! created : https://github.com/networkupstools/nut/issues/563 Hello all, Trying to run an EATON 850pro via USB on a Debian Stretch Stable. I have letsencrypt certificate installed and working. When trying to manage the EATON device, i got: upsmon Can not initialize SSL context When 850pro is connected via USB, i can: lsusb Bus 009

An update - I ran a test by unplugging my UPS and letting it run down. The system shut down as it should. However, the /etc/killpower file was not created, and the UPS did not shut off power as it should from the shutdown scripts. This may be because the command to kill the output of the UPS isn't available, or that by not being able to log in as master prevents this. The permissions on the

I'm trying to execute some commands on my ups, but I keep getting ERR ACCESS-DENIED upscmd -l sinus Instant commands supported on UPS [sinus]: beeper.toggle - Toggle the UPS beeper load.off - Turn off the load immediately load.on - Turn on the load immediately shutdown.return - Turn off the load and return when power is back shutdown.stayoff - Turn off the load and remain off shutdown.stop -

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 all, We have recently bought an APC UPS and are in the process of setting up the NUT software to make use of it. We are experiencing a problem with the behaviour of the slave systems when the master system goes off line. Although the failure of our master system will (hopefully) be a rare event, and we hope not to experience too many power outages, it is possible (if unlikely) that both

I'm getting a lot of entries like this in my log: Apr 16 10:10:18 postamt dovecot: auth(default): shadow(doxxxris,141.42.206.38): CRYPT(wrongpassword) != '$1$qSe71xxx$09MoMqNyll.wPLCdSaFuA0', try MD5-CRYPT scheme instead It seems that changing the password via SquirrelMail (poppasswd) breaks the authentication scheme somewhat. Users cannot log in anymore. -- Ralf Hildebrandt

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 just upgraded my nut 2.2.1 setup to 2.4.1. The "upsdrvctl shutdown" command now works using a APC Backup-UPS CS350 via USB. Great! The removed ACL/allowfrom functionality can be replaced by tcp_wrappers. Unfortunately there isn't much documentation about the migration. First you have to compile nut with "--with-wrap". I have a special "nutadmin"

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

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

Dears, I have centos 5.5 with kernel 2.6.18 UPS: Mustek PowerMust 2000VA USB I trying to setup monitoring for this ups, I connect ups with server via COM port and USB. But here is the problem (with megatec_usb): [root at optimus ups]# /sbin/upsdrvctl start Network UPS Tools - UPS driver controller 2.2.0- Network UPS Tools 2.2.0- - Megatec protocol driver 1.5.4 [megatec_usb] Carlos

And sorry, I forgot to put log from messages, I always got this: Oct 30 21:06:25 optimus kernel: usb 5-1: usbfs: process 9808 (megatec_usb) did not claim interface 0 before use From: nut-tracker-bounces+vladimir=micovic.com at lists.alioth.debian.org [mailto:nut-tracker-bounces+vladimir=micovic.com at lists.alioth.debian.org] On Behalf Of Vladimir Micovic Sent: Saturday, October 30, 2010 8:00

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

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)

Hello world! Please, help me :-) I have a APC RS-800 usb and it don't shutdown. I try every things but nothing: don't shutdown. Uhmmmm My actual situation: tux:/home/effem# uname -a Linux tux 2.6.26-1-686 #1 SMP Wed Aug 20 12:56:41 UTC 2008 i686 GNU/Linux tux:/home/effem# wajig policy nut nut: Installato: 2.2.2-6 Candidato: 2.2.2-6 Tabella versione: 2.2.2-7 0 -20