similar to: My NUT experience

Hi Sergey, 2011/7/15 Sergey Talchuk <tals1975 at gmail.com> > Hi Arnaud, > > both configurations are ok :). Please find the file attached. > logic since the 2nd is automatically guessed from the first using USB Vendor and Product ID ;-) can you please send in upsc, upscmd and upsrw output. and also report the shutdown testing as described here:

Hi, recently I observed that during a power outage, my NUT setup doesn't shutdown properly. Indeed it never reaches the LowBattery state to notify and initiate shutdown on clients. Reviewing my setup and logs I think I'm facing multiple problems and I'm unable to point to real root cause. First, let me focus on my scenario and current setup: In normal status (ONLINE, fully charged)

Le samedi 12 septembre 2009 ? 01:59 -0300, Vitor Choi Feitosa a ?crit : > Hi Arnaud, Hi Vitor, > I found your email on the contact page and since you seem to work for > Eaton and is involved in the NUT community I think you're the right > person to contact. > > I've got an Eaton NV 1000H and just installed it here. Before NUT > configuration I've checked the HCL

The UPS is connected to the following environment: OS: Debian GNU/Linux 9.6 (stretch) NUT version: 2.7.4-5 Device output from lsusb: 0463:ffff MGE UPS Systems UPS Model name: MGE EllipseMAX 1500 URLs: http://powerquality.eaton.com/Products-services/Backup-Power-UPS/Ellipse-MAX-eol.aspx?cx=97&GUID=7BB6CD53-9F6D-4D62-B326-1099F137BF8D http://powerquality.eaton.com/68558.aspx?cx=97 The problem

> If there is no message to NUT, I would consider opening a trouble > ticket with Eaton. It is possible that there is a known issue and/or > a firmware upgrade. What kind of message to NUT? In the log (syslog) there is no other message registered. In nut.log only this appears: > Dec 1 08:10:54 openmediavault upsd[5284]: Data for UPS [ellipsemax] > is stale - check driver >

Hello, I'm experiencing a strange early shutdown behavior with the following system: * */OS/*: Slackware Linux 14.2 x86_64 * */NUT/*: 2.7.4 (from my own package <https://sotirov-bg.net/slackpack/pack.cgi?id=4083>) * */UPS/*: MGE Ellipse PRO 1600 <powerquality.eaton.com/Products-services/Backup-Power-UPS/Ellipse-PRO.aspx> (bought in September 2017) */Problem

Hello, I am currently building a new server using debian amd64. Therefore I need to use my UPS EATON Evolution 1550 on it, using usbhid-ups driver. I installed nut with apt (version 2.4.3-1.1squeeze1) on debian 2.6.32-5 amd64. I can currently use nut with the drivers, upsc and upsmon: my UPS is detected and works. Actually everything works except upssched: I can shut down the server using

?Hello, There is a new intermediate Windows binaries release available at : http://www.networkupstools.org/package/windows/NUT-Installer-2.6.5-3.msi This fixes a regression about stopping the NUT service. Feedback is highly appreciated. Regards, Fred -- Eaton Opensource Team - http://opensource.eaton.com ----------------------------- -----------------------------

Here is the previous email that I sent directly to Charles Lepple. ?I am now sending to the correct email with cc to Charles. ---------------- I am looking at, and trying to understand the rest of the conf files. ?But first want to askabout something from this message:[CODE]root at debian:/home/john# upsdrvctl startNetwork UPS Tools - UPS driver controller 2.7.2Network UPS Tools - Megatec/Q1

hello, I installed with NUT UPS MGE Pulsar Evolution 2200 all orders of arrest, interrogation etc etc ... UPS work well However, I have a problem with the order in NOTIFYCMD upsmon.conf that not run ... I created a script that generates a simply log I indicated in upsmon.conf NOTIFYCMD / home / nut / alert_ups.sh below my upsmon.conf RUN_AS_USER nut MONITOR pulsar at localhost 1 admin1

Hello, I'm using Archlinux x86_64 with linux-nouveau kernel (based on linux-mainline (that is linux-3.6)). I've installed nut-2.6.5. I first tried to use new systemctl .service scripts, but they are problematic. So I start and stop nut from /etc/rc.c script. This way, it "woks". Here are my config files : nut.conf : MODE=netserver ups.conf : [ellipse] driver = usbhid-ups

?Hello, There is a new intermediate Windows binaries release available at : http://www.networkupstools.org/package/windows/NUT-Installer-2.6.5-2.msi This fixes three regressions: - upssched was not working - Event logging was not working (unless for NUT service binary itself) - usbhid-ups was not working with Back-UPS ES ups. Feedback is highly appreciated. Regards, Fred -- Eaton

Hello all, There is a new Windows package of NUT. It now contains nut-scanner binary. Note that there is a known issue with libupsclient.dll with nut-scanner. The scan of NUT servers using nut-scanner will not work for now. You can find it at : http://www.networkupstools.org/source/2.6/NUT-Installer-2.6.3-1.msi Please send feedback to the list. Regards, Fred -- Team Open Source Eaton -

Hi, I have been running nut successfully for a long time with my Debian 11 server. I upgraded my server to Debian 12 today, which upgraded nut also from 2.7.4-13 to 2.8.0-7. I noticed that after upgrade there was a upssched process running and taking 100% cpu time. I checked if there were any changes to configuration file formats with nut upgrade and only differences I noticed were a terminology

Hello, I set up a FreeBSD 8.2 system with nut 2.6.1 and a Powerware 5115 connected by RS-232. I expected this setup to shut down before running out of battery power, but I either missed some important configuration or something else went wrong: The syslog says: Jan 9 05:03:42 b1 upsmon[67752]: UPS upsb1 at localhost on battery Jan 9 05:04:42 b1 upsmon[67752]: UPS upsb1 at localhost on line

An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20120104/34be491b/attachment.html>

Hello. I've tried to configure Windows (complete port, Beta): Windows MSI installer 2.6.0-1 with my Powerware 5115 connected via USB port but have no luck. Here is my config files: *nut.conf:* MODE = netserver *ups.conf:* [PW5115] driver = bcmxcp_usb port = notUsed desc = "PowerWare 5115" *upsd.conf:* LISTEN 192.168.1.12 3493 *upsd.users:* [monuser]

I'm trying to use a Nas4Free storage system. This same hardware worked fine on Freenas 0.7.2. O/S: Nas4Free 9.0.0.1.148 which comes with nut 2.6.4. UPS is an APC Back UPS RS 800. USB interface. Driver : usbhid-ups Port: auto my NAS is communicating with the UPS, but in testing power failures, I'm not getting the shutdown to be handled properly. When I pull the AC plug on the UPS,

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

Hello NUT Team! I am testing the early shutdowns in NUT 2.6.5-1 package for Windows (Windows 7 x64). My configuration files: upsmon.conf RUN_AS_USER upsmon MONITOR upsa at 192.168.10.200 1 upsmon pass master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD "upssched.exe" POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG