similar to: NUT-Server will not start at boot with Cyberpower PR1500

Hi Charles, Thanks for your response. No, I only put 192.168.1.64 as an extra option as I want to allow Slave access from another computer. Otherwise, access will normally only be from localhost. There is only one network interface on this machine. I will try it out with "LISTEN 0.0.0.0 3493" and see what happens. I must confess I usually run without a firewall as I'm only running a

On Saturday 07 March 2020 12:38:07 Paul Newbery wrote: > Hi Charles, > Thanks for your response. No, I only put 192.168.1.64 as an extra > option as I want to allow Slave access from another computer. > Otherwise, access will normally only be from localhost. There is only > one network interface on this machine. I will try it out with "LISTEN > 0.0.0.0 3493" and see

On Mar 6, 2020, at 2:02 PM, Paul Newbery <newberype at hotmail.co.uk> wrote: > > I have since been trying to get them working with the NUT software, which I can do, but I simply cannot get them to start at system start up. It can be seen from the "Syslog Nut Extract" that upsdrvctl successfully loads the driver, but nut-server fails to start and the driver then stops as it

Hi centos 6.3 uses traditional SysV script ( not systemctl) here is the /etc/init.d/ups ( script) assuming it similar to nutshutdown # more /etc/init.d/ups #! /bin/bash # # ups: Starts the Network UPS Tools # # chkconfig: - 26 74 # description: Network UPS Tools is a collection of programs which provide a common \ # interface for monitoring and administering UPS hardware. # processname: upsd #

On Jan 22, 2015, at 9:53 AM, Sebastian Hosche <sebastian.hosche at web.de> wrote: > Hi Charles, > > Thanks so much for your quick and detailed reply! I've added my answers and details inline. Sorry this reply wasn't as quick. > On 22.1.2015 04:46, Charles Lepple wrote: >> On Jan 21, 2015, at 9:15 AM, Sebastian Hosche <sebastian.hosche at web.de> wrote:

Hi Charles, Thanks so much for your quick and detailed reply! I've added my answers and details inline. On 22.1.2015 04:46, Charles Lepple wrote: > On Jan 21, 2015, at 9:15 AM, Sebastian Hosche <sebastian.hosche at web.de> > wrote: > >> First issue: whatever I set as the offdelay, seems to be ignored and >> the UPS just cuts the power about 2sec after receiving

HI in centos: C="/usr/bin/upssched-cmd" here is the output of that file: # more /tmp/NUT.report NUT configuration 2016-05-10 03:02:20 UTC ########### /etc/ups/nut.conf ########### MODE=netserver ########### /etc/ups/ups.conf ########### [cyberpower] #driver = powerpanel #port = auto driver = usbhid-ups port = auto vendorid = 0764 desc = " My main

On Jan 21, 2015, at 9:15 AM, Sebastian Hosche <sebastian.hosche at web.de> wrote: > Hi there, > > I just purchased a CyberPower BR850ELCD and while setting NUT up with the install instructions from the homepage was pretty straightforward, and the UPS was detected by the usbhid-ups driver, I'm having problems getting the UPS to work properly. > > First issue: whatever I

Hi there, I just purchased a CyberPower BR850ELCD and while setting NUT up with the install instructions from the homepage was pretty straightforward, and the UPS was detected by the usbhid-ups driver, I'm having problems getting the UPS to work properly. First issue: whatever I set as the offdelay, seems to be ignored and the UPS just cuts the power about 2sec after receiving the

Since there is apparently no immediate solution to upsstats.cgi not reading the output voltage correctly, I have moved on to trying to use upsset.cgi. To recap the UPS is a CyberPower CyberPower CP1500PFCLCD UPS running on a headless server running Slackware 14.1 with the 3.10.7 kernel. The version of NUT is 2.71 and I am using usbhid-ups for communication with the UPS The problem is that when

Bill S wrote, On 4/15/2014 11:18 AM: > The problem is that when I run upsset.cgi I first get a prompt for > user name and password. I then enter the same username and password > as I established in upsd.users and it seems to accept it. upsset.cgi doesn't check that user/password is valid, it just tries it when doing a command. I just tested it, it is working for me on a remote and

I am having some problems getting NUT to run with my cyberpower avr1200 (brandnew). I have a straight through serial cable, and I am getting this: /usr/local/etc/rc.d/nut.sh start Starting nut. Network UPS Tools - UPS driver controller 2.0.2 Network UPS Tools - CyberPower driver 1.00 (2.0.2) Giving up on hardware detection after 3 tries Unable to get initial hardware info string Driver failed

I am having some problems getting NUT to run with my cyberpower avr1200 (brandnew). I have a straight through serial cable, and I am getting this: /usr/local/etc/rc.d/nut.sh start Starting nut. Network UPS Tools - UPS driver controller 2.0.2 Network UPS Tools - CyberPower driver 1.00 (2.0.2) Giving up on hardware detection after 3 tries Unable to get initial hardware info string Driver failed

Hi I am using centos 6.3, and nut-2.6.5-2.el6.x86_64. could you explain why not sending "a delayed command to the UPS to turn it off" may cause that issue? I saw: ups.delay.shutdown: 20 ups.delay.start: 30 is it something related? thanks min On Sat, May 7, 2016 at 3:44 PM, Roger Price <roger at rogerprice.org> wrote: > On Sat, 7 May 2016, Min Wang wrote: > > Hi

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

Hello, I have a Raspberry Pi model B running Raspbian Stretch. I have installed version 2.7.4-5 of nut from the raspbian repos. I have a CyberPower 1500PFCLCD UPS. When I reboot the Pi, the nut-server service fails to start. root at nut:~# service nut-server status ? nut-server.service - Network UPS Tools - power devices information server Loaded: loaded

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)

Hey guys, :) recently, I installed Cyberpower PR2200ELCDRT2U, however, I have not managed to get this UPS working with FreeNAS 11, yet. According to compatibility list, PR2200 should work fine, when using powerpanel driver: http://networkupstools.org/ddl/Cyber_Power_Systems/ http://networkupstools.org/ddl/Cyber_Power_Systems/PR2200.html However, when trying to establish a connection between

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

I'm a linux newbie and having some trouble with NUT, can anyone assist? I've read the FAQ and various articles online by Peter Sellinger and others thoroughly. OS is ClarkConnect 4.2, which is based on CentOS4/RHEL 4. UPS is an APC SmartUPS 1500 (USB). Correct driver is believed to be usbhid-ups. No RPM for my OS was available past 2.0, so I built from source using NUT 2.2. I think