similar to: upsdrvctl doesn't seem to start with init.d

In /var/log/syslog Dec 23 13:04:50 ************** upsmon[2010]: Poll UPS [rack1ups at localhost] failed - Write error: Broken pipe After this, there is no longer a upsd daemon running. Error messages follow: Dec 23 13:04:50 ************** upsmon[2010]: Communications with UPS rack1ups at localhost lost ... Dec 23 13:04:55 ************** upsmon[2010]: UPS [rack1ups at localhost]: connect

We recently had to replace an old APC SmartUPS 3000 with a newer 3000VA (the 2U one). It has both serial and USB in the back (with an RJ-45 on the end of the serial cable). I can't get the apcsmart driver to connect. I figured it should work the exact same as the old UPS, with /dev/ttyS0 as the port (I'm using the same port on the server that the last one was plugged into). I even

I have a new APC Smart-UPS SUA2200RM2U. I've had no success with the manufacturer's PowerChute software and smart signaling, so I have decided to try NUT. The smartups driver can't make contact through the serial port. Since this is rack-mounted, it comes with a 940-1524 serial cable. As far as I can tell, this is supposed to work with smart signaling. Here's my ups.conf:

Hi everyone, I just want to know about driver support over new APC smart models. My company recently bought a Smart-Ups RT model: SURT3000XLI and a I cannot do to make work it with last version of nut software. Maybe this model it doesn?t supported yet and I want to know if so. The diference with others models like matrix or backup ones is the famous Smart Cable: 940-1525A (utp - db9). I

Hi everyone, I just want to know about driver support over new APC smart models. My company recently bought a Smart-Ups RT model: SURT3000XLI and a I cannot do to make work it with last version of nut software. Maybe this model it doesn?t supported yet and I want to know if so. The diference with others models like matrix or backup ones is the famous Smart Cable: 940-1525A (utp - db9). I

I did a test shutdown on a nut controlled UPS and it all went as expected except that when it got to: /usr/local/ups/bin/upsdrvctl shutdown Nothing happened. So the halt script went on and shut down the system. I waited a while but the UPS never turned itself off. Am I doing something wrong, or does this UPS not support this function? Thank you, David Mathog mathog at caltech.edu Manager,

All, I have built and installed nut from git on Archlinux. It uses the usbhid driver. Beginning a couple of years ago, nut begin failing to run on Archlinux without 'tweaking' or 'fudging' the install. There are two primary problems: (1) upsdrvctl cannot be launched normally i.e. (/usr/sbin/upsdrvctl start) without failing to connect: Dec 14 02:24:39 phoinix systemd[1]:

On 12/14/2013 12:37 PM, David C. Rankin wrote: > I will test with the new ubs dev permission and report back. Thank you for your > help Charles. Charles, Setting uid:gid to root:nut on /dev/bus/usb/004/002 seemed to be the issue. The question now become how to automate this process so that the user isn't required to manually hunt down the usb dev and change gid to the nut gid? So

On Dec 14, 2013, at 4:19 AM, David C. Rankin wrote: > lsusb shows: > > Bus 004 Device 002: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS I am guessing that 'ls -l /dev/bus/usb/004/002' shows that the device node is not owned by the NUT gid? > Why doesn't > "upsdrvctl start" allow nut to find the UPS when it can find it without a > problem with

On 12/14/2013 07:20 AM, Charles Lepple wrote: > On Dec 14, 2013, at 4:19 AM, David C. Rankin wrote: > >> lsusb shows: >> >> Bus 004 Device 002: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS > > > I am guessing that 'ls -l /dev/bus/usb/004/002' shows that the device node is > not owned by the NUT gid? > crw-rw-r-- 1 root root 189, 385 Dec

Hi all, I just got myself 2 APC Back-UPS CS 350 I downloaded the stable nut tar.gz installed it. This is not the first time i install and configure nut so i used the same configuration as on my other server as i always did. Then i made the 2 required modification. I changed these 2 thing: driver = apcsmart port = /dev/hiddev0 # ls -al /dev/hiddev0 crw------- 1 nut nut 180, 96

Listmates, After wrangling with the voltage value on the CyberPower 1000AVRLCD and now having 2 of them working, I though it would be a simple matter to move my APC BP650 from apcupsd to nut so that all 3 servers would be monitored on the same web interface. The APC is attached to an older box running openSuSE 11.0 with nut-2.2.2-66.1. (nut-classic). The APC BP650 uses a serial connection

Hello all, Rebooted my server by mistake (don't ask...) - everything was working OK before the reboot, but after the reboot, NUT stopped working - so had a look and I found I couldn't track the exact problem - I'm quite stumped as there's nothing indicating that there's a problem, but it just doesn't work... In a nutshell.... destiny:/usr/local/ups/bin# ./upsdrvctl

Hello all, Rebooted my server by mistake (don't ask...) - everything was working OK before the reboot, but after the reboot, NUT stopped working - so had a look and I found I couldn't track the exact problem - I'm quite stumped as there's nothing indicating that there's a problem, but it just doesn't work... In a nutshell.... destiny:/usr/local/ups/bin# ./upsdrvctl

Hi, I installed apcupsd through pfsense and noticed some discrepancy with the NUT package. I'm not sure if this is a bug regarding the BATTDATE (apcupsd) and battery.date (NUT) but BATTDATE shows the correct date of 2016/05/11. While NUT shows the battery.date as 2001/09/25 which doesn't make sense. Any ideas? Pfsense 2.4.3-RELEASE-p1 (amd64) NUT 2.7.4_6 NUT installed through

Hello, I'm trying to setup a UPS configuration whereas I have one physical UPS but two UPS entities loaded by the system used by different network slaves. In my ups.conf configuration I have ... [ups] driver = apcsmart port = /dev/ttyS0 desc = "APC UPS" [qnapups] driver = dummy-ups port = ups at localhost desc = "APC UPS for

I have installed nut 2.0 Var/log/messages: Aug 14 16:37:26 server kernel: hiddev96: USB HID v1.10 Device [American Power Conversion Back-UPS BF500 FW:814.s3.I USB FW:s3] on usb-0000:00:1d.0-1 Aug 14 16:37:26 server kernel: hub 5-0:1.0: USB hub found Aug 14 16:37:26 server kernel: hub 5-0:1.0: 2 ports detected My ups.conf : [APC350] driver = apcsmart port = /dev/usb/hidddev96 desc =

I have been running a Smart-UPS RT 3000 VA using nut successfully over the 940-0095B cable for a couple of years. I have just received a second unit, but it is slightly different in 3 ways that I have found so far. 1. It's a Smart-UPS RT 3000 XL 2. The 940-0095B cable now uses an RJ45 connector at the UPS end. 3. It now requires a baud rate of 9600 instead of the 2400 used previously.

Hi all - I'm new to both UPS setup and SNMP on linux - so I'd appreciate any help I can get....I'm stuck! I'm running fedora core 5, and have installed net-snmp and nut. I'm trying to get my network connected UPS to this linux machine. My /etc/ups/ups.conf looks like this: [upsnetwork] driver = snmp-ups port = 172.31.254.7 community = public desc="Network

> On Aug 13, 2018, at 06:17, Charles Lepple <clepple at gmail.com> wrote: > > On Aug 12, 2018, at 11:03 PM, Kevin Mychal M. Ong <kevindd992002 at yahoo.com> wrote: >> >> Hi, >> >> I installed apcupsd through pfsense and noticed some discrepancy with the NUT package. I'm not sure if this is a bug regarding the BATTDATE (apcupsd) and battery.date