search for: sagebrushnetworks

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 was wondering what you guys do about UPS shutdown on Windows systems? Apcupsd has the same issue, so I'm assuming it is the same with NUT. Windows just makes it hard/impossible to do. Do you find draining the batteries down so much cause issues for longevity? Regarding my Eaton 5110, I found that automatic driver setup works just fine on Windows XP but not at all on Windows 7 x64 (I

Test machine: Windows 7 Pro x64, NUT 2.6.5-3 UPS model: Tripp-Lite Internet Office UPS (INTERNET525U) I needed a UPS and I had this old, but lightly used Tripp-Lite in storage. On the compatibility list I see a (?similar?) INTERNETOFFICE700 using the tripplite_usb driver. But the driver is not liking this particular model that I have. I'll be receiving a 3S550 soon, so I'm not

Dmitri Stepanov wrote on 7/14/2016 5:18 AM: > All the hosts are installed together in one rack and have fed from one > UPS (only I am remote from the system :) and I haven't ability to > connect to it. Some of hosts haven't NUT for a number of reasons. I > don't need to inform not-NUT hosts about any UPS events, heartbeat, > etc... but only shutdown all the hosts

Kris Jordan <nut.kj <at> sagebrushnetworks.com> writes: > > Marcelo Roccasalva wrote, On 3/1/2013 12:10 PM: > > On Thu, Feb 28, 2013 at 6:17 PM, Marcelo Roccasalva <roccas <at> gmail.com> wrote: > >> On Tue, Feb 26, 2013 at 10:56 PM, Charles Lepple <clepple <at> gmail.com> wrote: > >...

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

Windows 7 Pro x64 Eaton 3S550 (brand new, battery mfg 8/15/2012) NUT 2.6.5-3 ups.status: OL CHRG CHRG was present even though it has been plugged in a few days turned on and battery.charge was 100%. Log includes me running upsc and removing power long enough to see that battery.charge will decrease. This UPS doesn't have controlled outlets despite what the upsc output says. ---

Nut for Windows 2.6.3-3 + Eaton/PW 5110 (103004256-5591). I had to manually install libusb driver and I'm using bcmxcp_usb. upsd.exe is reporting to me "Out of memory". It will run, but once anything connects to the daemon, it dies with that message. I don't have much experience with NUT yet so I'm not sure what the next course of action is. I do have NUT for Windows

I fixed a couple issues in the RedHat init script provided in the scripts directory. There are some other things about it that could use updating, but first I checked out the one included with the RPM (https://admin.fedoraproject.org/pkgdb/acls/name/nut). That one looks pretty good, maybe it should replace the included scripts if permission is given by mhlavink? -------------- next part

Roger Price wrote, On 12/4/2013 12:35 PM: > I would like nut to become more loquacious, and to log a much more > complete report of its activity. At present nut reports that its > components have started operation but does not automatically log their > activity when UPS's switch between OB and OL. I believe that this > under-reporting of important facts is too minimalist -

Angel Tsankov wrote, On 12/6/2013 12:31 PM: > Hello, Ren?. > >> You can change the parameter >> ups.delay.start into your UPS to set the "Interval to wait before >> (re)starting the load (seconds)" >> >> use upsset to change the value. > > So far, the ups.delay.start parameter in my MGE Protection Center 675 > has always been equal to the

Angel Tsankov wrote, On 12/25/2013 12:16 AM: > > What did you mean by "load.on.delay"? > upscmd -l <ups> load.on.delay - Turn on the load with a delay (seconds) ---- ups.timer.shutdown: 0 ups.timer.start: 0 are my upsc values. I'll have to pay more attention to those next time I test.

Windows 7 Pro x64, NUT 2.6.5-4 (interim release) Product: Back-UPS RS 1200 FW:8.g3 .D USB FW:g3 Setting UPS values can be confusing. For example, battery.charge.low and battery.runtime.low. Using upsrw, the values will be retained after restarting the OS, but not if the UPS is turned off/restarted. In the driver log (below), it looks like the values are obtained from the UPS, but if I set

Windows Server 2000 R2 Standard edition x64 I found a bunch of message.exe processes running on this system (181 of them in total). The UPS was going on-battery a lot! There is no attached screen and I don't see any message boxes when I RDP. Do I just set NOTIFYCMD to something nonsensical to stop it from running message.exe? It would be nice if the Windows defaults were shown in the

So based on the compatibility page, I might be okay with the 5P. The page specifically mentions the 5PX. Anyone using this UPS? When looking at Eaton UPS's I excluded any of the older ones that use the BCM driver since that driver provides little functionality as I've learned with the 5110. There's also the Evo, but I would prefer to have one with ABM. I'm open to other

Windows 7 x64 NUT 2.6.5-4 Eaton 5PX1500RT Using explore did not yield any additional output. This UPS is on the compatibility list, so hopefully not a big deal. I double-checked that the 3S still works with the same USB cable. I'll check mge-shut over serial next. Regards. -------------- next part -------------- Network UPS Tools - Generic HID driver 0.37 (2.6.5-3780M) USB communication

Windows 7 Pro x64 SP1 NUT 2.6.5-4 upsd is crashing when stopped and I think it has only started with the latest version. Nothing shows up in 5'D upsd output, the normal output just quits. Windows 7 event log output below. It's also crashing on XP, though I do have one XP system where it doesn't crash. One difference on WinXP is the upsd process gets stuck running and doesn't

Windows 7 Pro x64 NUT 2.6.5-4 upsmon, when there is a problem, spams the event log every 5 seconds. Poll interval is 5 seconds also. I have witnessed the below messages filling up the event log. upsmon - UPS [ups at localhost]: connect failed: Connection failure: Unknown error. upsmon - Poll UPS [ups at localhost] failed - Data stale. I've already reported earlier how I've been

The Windows driver installer isn't always successful, actually most of the time it fails. I thought it was due to differences between Windows XP and 7 or different UPS models. But I'm noticing that it might be a bit more random than that. What does seem to always work is running wdi-simple.exe from the others folder manually. When having it run from the NUT installer, it will extract

NUT 2.6.5-4 Eaton 3S550 Windows 7 Pro x64 usbhid-ups is crashing if it is started without debugging. This UPS worked fine on my test system with the same OS, but since moving it to the system where it will be used, it's refusing to function with NUT. Looks like it is working with the Windows built-in drivers though. Thanks. -------------- next part -------------- A non-text attachment was