similar to: Unable to get variable list - Receive timeout

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

Sounds great! By `connection error` it looks like the `upsc` client had nowhere to go. Is `upsd` started (and does it `LISTEN` on locahost or asterisk per `upsd.conf`)? Jim On Sat, Oct 26, 2024, 08:13 William R. Elliot <bill at wreassoc.com> wrote: > Hello again. > > I now have large chunks of the new driver working in the foreground and > wanted to see what upsc reports

Hello Charles, Thank you so much for your help. Just run upsc and it is possible that input.transfer.low is the one because we used power regulator to bring down the power around 84v and then the ups sent the power loss message to PC. Do you think some others may take effect for the low voltage? Just have the upsc result attached. Then I retried input.transfer.low, default.input.transfer.low,

Gabor: note, these HCL reports go to the nut-upsdev list. Begin forwarded message: > From: Gabor Tjong A Hung > Subject: Re: Network UPS Tools - Compatibility List > Date: September 3, 2013 2:18:31 PM EDT > > Sorry, > I just noticed the "If your device isn?t listed" part: > > [HCL] Forza FX-1500LCD supported by blazer_usb > > > [root at freenas] ~#

First off, my apologies for bringing back this thread from the dead (September 2005, http://lists.alioth.debian.org/pipermail/nut-upsdev/2005-September/000150.html), however my problem seems relevant enough that I wondered what happened to this thread as it seems to have died after the message I quote below. Despite the fact that I am having trouble getting my Sweex 1000VA UPS (USB) to work, and

First off, my apologies for bringing back this thread from the dead (September 2005, http://lists.alioth.debian.org/pipermail/nut-upsdev/2005-September/000150.html), however my problem seems relevant enough that I wondered what happened to this thread as it seems to have died after the message I quote below. Despite the fact that I am having trouble getting my Sweex 1000VA UPS (USB) to work, and

Hey Charles, Latest update. Looks like in ups.conf I setup default.input.transfer.low = 84. After I took that line out, restart upsdrvctl, upsmon, and upsd, the command of sudo upsrw -s input.transfer.low=70 -u * -p * ups return OK. Still need to verify if it works by using voltage regulator and will keep you updated. Thank you for your help Regards Shen On Thu, Jun 5, 2014 at 8:54 AM,

Hi, just through setting up nut-2.0.2 I ran into a shutdown problem. As I have already spend some time on it and don't know any further, I like to ask for advice. Situation: Powerware 9125 serially connected using /dev/cua0 nut compiled and installed fine system shall - broadcast a message and shut down if ups on battery for 30+ s - wait 120 s - broadcast another message - give system 120

Manufacturer: Aviem Power RT 1000-3000VA Description: Rack/Tower Intelligent Online LCD UPS. connected with serial cable. #upsc battery.voltage: 24.96 battery.voltage.low: 21.5 battery.voltage.nominal: 24.0 beeper.status: enabled device.mfr: device.model: device.type: ups driver.name: blazer_ser driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyUSB1 driver.version: 2.6.3

Does anyone on this list have a CyberFort 350? It's a European model, and should be equivalent to the US BackUPS ES 350 model. What I'm seeing is upsd reporting stale data. While the battery is running down, upsc doesn't see the battery % changing, so I'm assuming the driver isn't collecting data at that point. Unfortunately, the system/UPS is not here (I'm in the

On Mon, 15 May 2017, Dinow Hsieh wrote: > ==> I have tried this command "upsdrvctl shutdown" as below results (However the UPS still sustain the power) > > ??? Network UPS Tools - UPS driver controller 2.7.1 > ??? Network UPS Tools - Generic HID driver 0.38 (2.7.1) > ??? USB communication driver 0.32 > ??? Using subdriver : PowerCOM HID 0.4 > ??? Initiating UPS

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

Good Day Roger Price AA. Hi, Normally one would expect the UPS to disconnect it's power outlets after the default ups.delay.shutdown = 20 seconds. ==> I got it. I tried to command "upsdrvctl shutdown" on both line-mode and battery-mode ==> But ups do not disconnect its outlets power ----------------------------------------------------------------------------------- BB.

All of this work is being done on the system that has the UPS - I'm not trying to do any network monitoring yet. The symptom is that when I try to use 'upsc' I get the failure message "Error: server disconnected" on the console, and this line in /var/log/daemon.log: <date/name> upsd[4899]: Rejecting TCP connection from 127.0.0.1 My current suspicion is I don't

Hello Charles, Thank you so much for your reply. Yes. 40v was too low. In windows, those range started from 76v, 85v, and 96v. Just tried upsrw command to modify input.transfer.low and input.transfer.boost.low. There were some error messages returned. Tried another one battery.charge.low and it returns ok. $ sudo upsrw -s input.transfer.low=70 -u * -p * ups Unexpected response from upsd: ERR

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

I have an APC 9210 PDU in my rack. It's connected to the network and is configurable by web access. I'd like to control it in combination with my ups. Unfortunately I cannot get NUT to recognise this PDU. Here's my ups.conf section: [apc] driver = snmp-ups port = 192.168.10.21 mibs = auto community = public snmp_version = v1 running upsdrvctl gives this: $ sudo

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 Jun 4, 2014, at 6:38 PM, Shen Chuan wrote: > $ sudo upsrw -s battery.charge.low=70 -u * -p * ups > OK Not sure this does what you originally asked, though. Does upsc show any settings related to sensitivity? -- Charles Lepple clepple at gmail

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