similar to: One little thing not quite correct in my configuration

Dear Charles, thanks for your quick answer and your information! I didn't know there is a difference in the PR-series between old and new. So thanks for this valuable information! usbconfig dump_device_desc shows: ugen0.2: <CyberPower Systems product 0x0601> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (50mA)

Hello, I installed NUT and configured it for 2 MGE UPS's connected via USB. Debian etch NUT package: # dpkg -l nut*|grep ^ii ii nut 2.0.4-3 The core system of the nut - Network UPS Tools ii nut-usb 2.0.4-4 USB Drivers subsystem for the nut - Network UP Separately, with only one UPS defined in ups.conf, each one works fine (I specified specific serial numbers for either, with

On Nov 10, 2017, at 5:31 PM, Christoph Lampl <chris at weeone.de> wrote: > > Dear Charles, > > thanks for your quick answer and your information! I didn't know there is a difference in the PR-series between old and new. So thanks for this valuable information! Just a lucky guess :-) We tend not to know about changes like this until someone reports an issue. > >

I'm using NUT 2.4.1 with openSUSE 11.2, my UPS is an MGE/Eaton Ellipse ASR 1500 USBS. The set-up is as described at http://rogerprice.org/NUT.html. Since NUT uses TCP wrappers, I have the /etc/hosts.allow entry upsd : 10.0.0/24, localhost, LOCAL, 127.0.0.1 : ALLOW When I pull the plug from the wall to test my setup, I get the sequence of KDE notifications and finally a

Hi there First a big thank you to all nut developers. I tried the 2.0.4 as well as the 2.0.5-pre1 versions with my CyberPower OP1000E connected to a serial to USB converter. All I got was the following: # /usr/local/ups/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.5-pre1 Network UPS Tools - CyberPower text protocol UPS driver .05 (2.0.5-pre1) Warning: This is an

Hi, We are having a performance issue with UPSD. OUR ENVIRONMENT -------------------------- We are using a custom script on a SUN V240 server running Solaris 8. The script employs UPSC to interrogate UPSD. UPSD is configured (using upsdrvctl) to talk to two MGE Galaxy 3000 UPS's via the MGE-SNMP ups driver. Our problem is this. When the server runs the backup processes it becomes

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

Hello there. I've just install nut 2.2 from source on my FreeBSD box. I have an MGE AVR 600 UPS on a USB cable. Following the INSTALL instructions, everything works in term of the USB driver detecting the right UPS and upsd loads up and runs without error. However, upsc reports the following error: # upsc mge600 at localhost Error: Connection failure:Can't assign requested address

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]:

Hi friends. Package: nut Version: 2.4.1-1 Depends: libusb, openssl, neon, libgd, net-snmp Status: install user installed Section: admin Architecture: mipsel maintainer: NSLU2 Linux <nslu2-linux at yahoogroups.com> MD5Sum: c8c55a6021fea2b5f194ce4623eb2dfe Size: 1246363 Filename: nut_2.4.1-1_mipsel.ipk Source: http://eu1.networkupstools.org/source/2.4/nut-2.4.1.tar.gz Description: Network UPS

On Jan 24, 2015, at 12:45 AM, Ryan Sizemore <ryan.sizemore at gmail.com> wrote: > Hello, > > I am trying to get nut running on a Windows 2012 R2 server (x64). I am using the MSI release of 2.6.5-3. I am not sure why they are not listed on the main download page, but there are actually three Windows MSI releases after that: http://www.networkupstools.org/package/windows/ I

On Tue, Jan 27, 2015 at 5:53 AM, Charles Lepple <clepple at gmail.com> wrote: > On Jan 24, 2015, at 12:45 AM, Ryan Sizemore <ryan.sizemore at gmail.com> > wrote: > > Hello, > > I am trying to get nut running on a Windows 2012 R2 server (x64). I am > using the MSI release of 2.6.5-3. > > > I am not sure why they are not listed on the main download page,

Trying to configure multiple UPS on one Raspberry Pi 4 (Bullseye). Issue: Whenever more than one is plugged in, one shows as all - as in "upsc x" for all of them shows identical information for one UPS rather distinct for each plugged in. OS: /proc/version = "Linux version 5.10.103-v7l+ (dom at buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU

Hello, No ttyUSB* device under /dev however the new driver has detected the UPS, the nut services are able to start, just "upsc -l ups" sais unknown error and doesn't return any information. Could be due to the driver unable to detect number of battery packs as reported by the nut-driver.service startup? How can I fix that? root at omv:~# systemctl status nut-driver.service●

Cyber Power Systems CP1000PFCLCD = upsc output = attached = Shutdown results = I experienced a genuine power outage shortly after setup. The 1 master system and the 1 slave system both shutdown successfully. The master shutdown before the slave (*not* a bug report; I may not have this configured correctly yet). The UPS was not powered off by the master. I don't know if the UPS

Ok, so I have made some progress that seems to suggest the initial “fix” I stumbled upon isn’t required. I haven’t yet worked backwards to figure out reasons why our customers have had similar complaints or solve the problem on the CentOS VM yet, but that is on the todo list. I am hoping it ends up just being not enabling the service on startup, but I can’t say that explains away all the symptoms

Hello, I am trying to get nut running on a Windows 2012 R2 server (x64). I am using the MSI release of 2.6.5-3. The attached UPS is an APC xs1500 (model bx1500g). The connection is an RJ45 to USB cable. Here is my ups.conf: [xs1500] driver = usbhid-ups port = auto desc = "APC Back-UPS xs1500" The problem I am encountering is upsd crashing with an 'Out of memory' error. I can

On Mar 9, 2024, at 5:16?PM, chribonn at duck.com wrote: > > The posting at https://github.com/networkupstools/nut/issues/432#issuecomment-405371395 references ups.delay.start and suggests setting it to -1. > > upsrw -l pve1 at localhost listed this as modifiable but any attempt at modifying the value failed. I used the override.ups.delay.start = -1 in nut.conf and this is now being

I have an older system which has a simple APC Back-UPS ES 500 connected via USB. I built nut 2.0.2 from source and am attempting to get it to work. I had to manually create the device links and I think it's ok because hidups is recognizing the UPS but any attempts to read data from it fail: [root@server bin]# ./hidups -D -D -D /dev/usb/hid/hiddev0 Network UPS Tools: HID UPS driver 0.13

Dear Chales, Thanks for your quick reply. I have Raspberry with last Kernel [Linux pi1 3.18.6+ #753 PREEMPT Sun Feb 8 14:47:22 GMT 2015 armv6l GNU/Linux] If <upsdrvctl>, <upsd> and <upsmon> are stopped <nutdrv_atcl_usb> Works well without any error as "Device or resource busy". If I run <upsc> command never receive any value from my ups <upsc ups at