similar to: UPS connection established, lost, established, etc.

Hello! I try use NUT on some servers. When i use this package on x64 Windows 2003 servers, upsmon hangs on with error: Faulting application upsmon.exe, version 0.0.0.0, faulting module upsmon.exe, version 0.0.0.0, fault address 0x0000458f. I try use another server, on 32-bit all is ok. Problem only on x64 platform (maybe in libusb)? And no different - upsmon master or slave. C:\Program Files

Hello, I use the following in my ups.conf: # USB: [apc] driver = usbhid-ups port = auto desc = "APC 1500VA" pollfreq = 5 On my new motherboard (an Intel DP55KG), every once and awhile I get this: Broadcast Message from nut at box.com (somewhere) at 17:48 ... Communications with UPS apc at localhost lost Broadcast Message from nut at box.com

I've googled and RTFM'ed, but still can't solve this one. I hope you folks can. This affects my entire computer cluster, but let's start simple: I've got a computer running NUT; OS is Scientific Linux 5.5; kernel 2.6.18-274.12.1.el5xen. It connects to an APC SMART-UPS via an APC SmartCard using the snmp-ups driver. It generally works: upsmon will detect if the battery is low

>> I am running NUT on a Synology NAS with attached a USB APC UPS. > > Do you have upsd and upsmon running as daemons on the Synology DSM? > Yes I have them both running on the Synology DSM: root 7236 1 0 Jun01 ? 00:00:16 /usr/sbin/upsd root 7741 1 0 Jun01 ? 00:00:00 /usr/sbin/upsmon root 7744 7741 0 Jun01 ? 00:00:12

Hello, I'm using driver newhidups with APC Back-UPS CS 500. Most things works fine except the following: After I disconnect the UPS the upsd write "Data for UPS [apc] is stale - check driver" in /var/log/messages. In the same second it tells "UPS [apc] data is no longer stale". This repeats all the time the ups is disconnected: Jan 25 14:45:03 degpn026w226 kernel: usb

Hi, the following UPS isnt supported by the driver "usbhid-ups". Manufacturer: APC Model: Back-UPS 950 (https://www.apc.com/shop/de/de/products/APC-BACK-UPS-950VA-230V-AVR-Schuko- Sockets/P-BX950U-GR) Config: [USV] driver = usbhid-ups port = auto desc = "USV" . MODE=standalone Terminal: root at debian-jessie-final:~# sudo upsd -u root

Hello, I am running NUT on a Synology NAS with attached a USB APC UPS. I am trying to connect and shutdown a Mac OS X system. I have installed the NUT software and it looks like there is connection with the master but when battery gets low the Mac is not shutdown. I don't know if I have to configure upssched.conf and where? On the slave (Mac) ? It will be great to know before I will start

I got around to unplugging my UPS and I found it doesn't last nearly as long as estimated. Is the "upsmon[1446]: UPS desktop_ups at localhost battery is low" logged when "battery.runtime:" = "battery.runtime.low: 120"? Does any make better batteries that don't go down faster when they get old? battery.charge: 100 battery.charge.low: 10

Hi debian jessie, nut 2.7.2-4 APC Smart-UPS 1500 connected through USB, running nut driver usbhid-ups This UPS powers my switches, internet connection and my monitor server that monitors this and my other UPSes + runs smokeping and nagios. But recently a powerloss seemed to have shutdown my monitor PC immediately, so it did not shut down the other servers cleanly. Power seem to be lost

On Sunday 08 December 2019 21:48:03 Charles Lepple wrote: > On Dec 7, 2019, at 7:01 PM, Gene Heskett <gheskett at shentel.net> wrote: > > What driver do I now put in /etc/nut/ups.conf? hid-generic doesn't > > seem to want to talk to it, and the original name _(usbhid-ups) > > doesn't work from new mobo. Oh wait, I can't spell. But that didn't > >

Dear list, I have an APC Smart-UPS 1500 hooked up via the USB port. Recently, when we had a power outage, the only entry in the logs was: Dec 3 14:43:43 afs1 upsmon[3035]: UPS apc at localhost on battery and then the machine seems to have run until the battery was empty. It only notices the "battery low" after I turn the system back on: Dec 3 16:01:39 afs1 usbhid-ups[21973]:

Well, after our first real extended power outage, I found out that even though the UPS 1000 RM is recognized okay, it does not work properly. It never seems to see any change in UPS status. It looks very similar to the other issue I reported with the APC CyberFort 350. I never was able to get to the bottom of the CyberFort issue, but I'll bet it's the same issue as we have with the

Hi list, UPS is a Smart-UPS 3000 RM (SU3000RM3U, ups.firmware 92.11.D, ups.mfr.date 12/14/99) with brand-new batteries. NUT is 2.6.5 running on SL6 (RHEL6 clone) from EPEL packages. 'upsc' output pasted at bottom. I'm not very familiar with UPSs in general or this model in particular, and it's doing things I don't expect. I have done my homework, and read UPS user manual,

APC Smart-UPS X 1500 Restart Issue. Hi All, I have installed nut-2.4.3. I have manually modified the files apc-hid.c and udev-rules to support 5G APC UPS. I took sample code from the 2.5 development tree. Shutdown process is working very well -- upsmon creates the file /etc/killpower - shutdown script checks for the file and issues /sbin/upsdrvctl shutdown - UPS cuts the power off. All

APC Smart-UPS X 1500 Restart Issue. Hi All, I have installed nut-2.4.3. I have manually modified the files apc-hid.c and udev-rules to support 5G APC UPS. I took sample code from the 2.5 development tree. Shutdown process is working very well -- upsmon creates the file /etc/killpower - shutdown script checks for the file and issues /sbin/upsdrvctl shutdown - UPS cuts the power off. All

Hello all NUT users and developers! Have some questions about nut suite: 1. Does upscmd provide only device-specific commands? Or commands like shutdown.stayoff are general and good for all ups models? When i see output of 'upscmd -l' - is this general commands that supported by given device or this is unique commands of this device? For example, i have APC SmartUPS-750 and it shows me

OS name and version, MASTER SYSTEM has three APC smart UPS 3000 UPS connected via USB debian 8 "jessie" Linux pdxvhtst01 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux SLAVE SYSTEMS monitoring MASTER via IP debian 8 "jessie" Linux geaaetst01

I'm using nut 2.0.2 from Fedora Core 4 and had some trouble getting my APC Back-UPS 500 working. I ended up having to rebuild the RPM myself after making some code changes. I had to increase the upsd synchronization timeout from 5 to 15 seconds. It seems like 10 is the sweet spot but allowing a few extra seconds doesn't seem to hurt anything. At 5 the UPS would timeout 5 out of 6

Hi, I cant get it working. Here is my terminal output: root at debian-jessie-final:~# lsusb -d 051d:0002 Bus 001 Device 010: ID 051d:0002 American Power Conversion Uninterruptible Power Supply root at debian-jessie-final:~# ls -l /dev/bus/usb/001/010 crw-rw-r-- 1 root nut 189, 9 Mai 6 15:35 /dev/bus/usb/001/010 root at debian-jessie-final:~# sudo upsdrvctl start Network UPS Tools - UPS driver

Hello, I encountered a problem with my APC Smart-UPS 750, connected via USB, using newhidups. Without any reason, nut/upsmon shut down my PC: >>> Oct 13 12:57:08 echo kernel: usb 2-9.1.1: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 161 rq 1 len 8 ret -71 Oct 13 12:57:12 echo upsmon[5060]: UPS smart750@localhost on battery Oct 13 12:57:12 echo upsmon[5060]: UPS smart750@localhost