similar to: APC SmartUPS 1500 (USB) does not report OL/OB state

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

Hi Philip, I've updated NUT to 2.7.3 and finally found the root cause for the unexpected shutdown: It is recommended to increase pollinterval to 10 seconds in ups.conf for usbhid-ups driver due to a known issue: http://www.networkupstools.org/docs/man/usbhid-ups.html Default DEADTIME=15 in upsmon.conf was triggering shutdown. Increasing the value to 30 seconds resolved the issue. Now when

Sergey, I?m no expert on this but I have been reading the driver code, trying to sort out bigger problems with the OpenUPS driver! I can make 2 observations that I can?t check out myself : ?beeper.disable? was previously ?beeper off? - and ?beeper.enable? was ?beeper.on?. Not sure if it?s worth trying the old versions? If your UPS doesn?t wait for LB, could this be because there is another

Hi! Have a similar issue with one of our customers having HP R12000/3 UPS with AF430A card. Upsmon shows the UPS as Online, on Battery and Battery discharging at the same time: [root at smrsrvslv06 lib64]# upsc hpups at localhost ambient.temperature: 19.0 ambient.temperature.high: 0.00 ambient.temperature.low: 0.00 battery.charge: 94.00 battery.current: 0.00 battery.runtime: 4620.00

Hi all, I have problem with UPS from PowerWalker model VFI 2000 RT LCD over USB (didn't try serial yet). UPS should work via HID driver but ups.status is not rendered properly. Specification of UPS says USB HID compatible. HID driver is the only one which talks with UPS as i try a few from /lib/nut. I use driver usbhid-ups (which communicate with ups), but subdriver resolving is

Linux NUT 2.7.1 Eaton 5PX usbhid-ups It would appear that interrupts are not actually working on my 5PX using the usbhid-ups driver. I will be trying the serial mge-shut driver next. It just seemed like it was working before because of the default pollinterval of 2 seconds. The status update comes in during the pollinterval no matter what I have pollfreq set to. And I can set pollonly and

Hi, Can't get newhidups (2.0.5) or usbhid-ups (SVN trunk) to work 2.0.5 hidups seems to work, but I was hoping for more information... like temperature, etc. Tried newhidups and usbhid-ups, but they don't seem to detect my UPS... should I switch back to serial? Will I get more information? (trying not to move back to apcupsd, since i have a mixed environment) Here is some debug

I'm trying to setup a server controlling 8 ups, 6 APC Smartups 1500 and two 1000. Because of the number of ups, i connected them using usb cables. I'm using Debian Etch AMD64 and nut 2.2.0 from testing (already tried 2.0 from stable, but had problems reading the ups serials and all the following problems of 2.2). This is my ups.conf: [ups2] driver = usbhid-ups port =

Using nut v2.2.2, and the APC serial cable. I have a client who's APC SMART-UPS 1500 (circa 2000) is always reporting LB. The batteries were old so they were replaced two weeks ago with brand new batteries. UPS still reported low batteries... I ran a calibration and a test on the unit (using the nut upscmd utility) During those tests, the battery charge on the unit goes to zero and slowly

Further information on this issue, attn. Arnaud Quette: Here is the result of a test I made a few days ago. I've pulled the input plug on the UPS and watched the 3 critical OIDs through a MIB browser: - 1.3.6.1.4.1.232.165.3.4.5.0 goes from 3 (OL) to 5 (OB) (as expected => good) - 1.3.6.1.4.1.232.165.3.7.3.0 stays at 1 (OB) (=> seems meaningless) - 1.3.6.1.4.1.232.165.3.7.4.0

Linux-2.4.28 libusb-0.1.8 nut-2.6.5 [+most recent drivers from GIT] - from tarball EATON 3S700DIN [mfr.date 09/28/14] ---------------------------------- ISSUES: I) Too many kernel logs: --- In /var/log/kernel.log usbdevfs: usb_submit_urb returned -28 In /var/log/daemon.log: usbhid-ups[744]: libusb_get_interrupt: No error usbhid-ups[744]: libusb_get_interrupt: error submitting URB: No space left

Additional question: I noticed on the HP Website that the latest version of "CPQPOWER.MIB" (1.76, dated Sept. 19, 2013) was more recent than the related file (./drivers/compaq-mib.c) in the NUT driver. Is the MIB structure as implemented on the management card perhaps no longer in line with the NUT driver ? The latest MIB file can be downloaded from the following URL:

I have a SmartUPS 750 (SUA750) which has the temperature and humidity SmartSlot card installed. When NUT 2.2 communicates with this UPS over /dev/ttyS0 using apcsmart, using the APC Smart cable connected to the SUA750 serial port, and this ups.conf: [su700] driver=apcsmart port = /dev/ttyS0 I can see the ambient temperature and humidity data with "upsc su700 at

We recently had to replace an old APC SmartUPS 3000 with a newer 3000VA (the 2U one). It has both serial and USB in the back (with an RJ-45 on the end of the serial cable). I can't get the apcsmart driver to connect. I figured it should work the exact same as the old UPS, with /dev/ttyS0 as the port (I'm using the same port on the server that the last one was plugged into). I even

Hello, Yes, "pollonly" is a driver option for certain devices (and relevant to just some drivers). Disconnects are probably relevant, at least to loss of connection (and staying that way, with less agressive retries in NUT v2.7.4 and before). There is a logged issue that "pollonly" mode might have trouble detecting a disconnection/staleness, I'm not sure there's merit

On Tue, 8 Oct 2013, Philip Tait wrote: > Here is the upsc output: > > # /usr/local/ups/bin/snmp-ups -DD -a irs2-ups1 > Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) > 0.000000 debug level is '2' > 0.000327 SNMP UPS driver : entering upsdrv_initups() [snip] > 4.457750 No supported device detected I'm using a APC smart ups with a

Bonjour, Je fais suite au message que vous avez post? en 2015 : http://lists.alioth.debian.org/pipermail/nut-upsuser/2015-February/009568.html J'ai le m?me probl?me et ne trouve pas la solution. Comment vous en ?tes-vous sorti ? D'avance, merci pour votre aide. -- Cordialement Herv? BASTET Nouveau num?ro non surtax? 01 69 42 87 94 Ce message est prot?g? par les r?gles relatives au

OS: CentOS 7 NUT Version: 2.7 Installed NUT through: yum install nut UPS: APC smart UPS srt3000 with NMC I am trying to set up NUT with snmp for my apc ups. Heres the config; [ups6]                 Driver = snmp-ups                 Port: ups6.domain.name (also tried 192.168.24.9)                 Snmp_version = v3                 secLevel = authPriv                 secName = ups6

Hello One our customer has two Linux HP-branded servers powered from "clasic" APC Smart-UPS 2200 RM 2U (p/n SUA2200RMI2U). It is connected to first server via RS232c port with APC-branded cable. We have installed NUT 2.6.4 with apcsmart driver. This setup works fine for months. Two weeks ago all the hardware powered from the UPS started to switch off occasionally while on line