similar to: Fwd: RE: Can't make Smart-UPS 1500 shutdown over serial

Hi folks, Today I installed nut on my Dell Poweredge 1800 server running Ubuntu 8.04 Server, with an APC Smart-UPS 1500 connected to it with the black APC cable. I used apt to install nut, upsd -v gives me "Network UPS Tools upsd 2.2.1-" I then copied and configured the config files. Most of the setup seems OK; I get console messages for line power fail / good, and I can do instant

Hello ! I'm totally new with Linux, just migrating from NetWare. Our brand new server runs SuSE Linux Enterprise Server 11 Service Pack 1 SLED11 ships with NUT 2.2.2-69.11 I'm trying to setup NUT to communicate with our UPS over the USB cable. First, I've tried with a "standard" ups.conf. Error message : device is (or not yet) supported. Second attempt, including productid

I'm setting up a cluster with multiple ups's using nut 2.2. The ups's are Belkin 1500 (ID 050d:0751) which don't appear to report a serial number. Is there any other way I can setup ups.conf with multiple of these ups over usb on Linux? If I just setup the vendor and product id's, every definition in ups.conf appears to match the first one, and therefore all of them but

Hi there... nut 2.4.3 kicks an error at me when I try to talk to my UPS. machine is linux 2.4.21-32.ELsmp with libusb-0.1.8-3 package update. # /usr/local/ups/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 Using subdriver: APC HID 0.95 libusb_get_interrupt: error submitting URB: Invalid

On Dec 8, 2013, at 10:41 PM, Christian wrote: > test.battery.start.deep - Start a deep battery test > test.battery.start.quick - Start a quick battery test Ideally, you would want to do a deep test with a dummy load, like a lamp, so as not to put your server in danger of getting cut off again. You can probably do the test.battery.start.quick test with the server still plugged into the UPS,

Charles, the unit has two redundant power supplies, with only one hooked up to the UPS. So I should be able to do a deep test with the machine itself, right? I have tried it, but it aborts at some point... For the quick test, it discharges the battery a bit, then recharges, but once it is back to 100%, upsc still gives me: ups.test.result: No test initiated Is that expected? Best, Christian

I've got it ! Actually, it was obvious. A question of rights on the USB port. As soon as the process has the right rights (?) on the port, it runs smoothly. Sorry for the useless post... Regards, Pierre Boullier ----- Original Message ----- From: Pierre Boullier To: nut-upsuser at lists.alioth.debian.org Sent: Friday, November 12, 2010 3:18 PM Subject: usbhid-ups and APC Smart-UPS 1500

Charles, thanks for your detailed answer. >> Occasionally, i get these in daemon.log: Dec 4 03:11:54 afs1 >> usbhid-ups[21973]: libusb_get_interrupt: could not claim interface >> 0: Device or resource busy > > This isn't great, but I don't think it's related. > > It is normal to get a "could not claim interface 0" error once after >

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

On Dec 7, 2013, at 2:38 PM, Christian wrote: > 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

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]:

I don't reply to messages send to me in private. Best regards, Arjen -- Please keep list traffic on the list -------------- next part -------------- An embedded message was scrubbed... From: Rudolf Cejka <cejkar op fit.vutbr.cz> Subject: NUT and removed allowfrom/ACCEPT/REJECT support Date: Mon, 14 Sep 2009 19:23:17 +0200 Size: 3148 URL:

Whenever I try to use the newhidups driver with my new UPS I get the following message: #/lib/nut/newhidups -DDD -a SmartUps1500 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) debug level is '3' [...skip unrelevant device...] Checking device (051D/0002) (001/005) - VendorID: 051d - ProductID: 0002 - Manufacturer: American Power Conversion - Product: Smart-UPS 1500 FW:601.3.I USB

To people with APC, CyberPower, Belkin and TrippLite UPS'es and using the 'usbhid-ups' driver. There are some concerns that the usbhid-ups driver is not acting as it is supposed to do. Could you run the following command (as root and with the mains plugged) and check if the UPS powers back on automatically? upsmon -c fsd I think we should *not* release nut-2.2.1 if we're not

Hello there. Have been experimenting with an APC Smart-UPS 1500 RM and would like to share the results of my research. I hope this could be of help to people having this kind of units. I would also like to give something back to the NUT community. :) Here are the details of the unit in question (a 1500 VA rack mountable one): Model: Smart-UPS 1500 RM Firmware revision: 617.3.I USB firmware

I did a test shutdown on a nut controlled UPS and it all went as expected except that when it got to: /usr/local/ups/bin/upsdrvctl shutdown Nothing happened. So the halt script went on and shut down the system. I waited a while but the UPS never turned itself off. Am I doing something wrong, or does this UPS not support this function? Thank you, David Mathog mathog at caltech.edu Manager,

Hi Folks, I just bought two APC UPSes, an EX 1300 and an ES 550 for two different sites and installed NUT for the first time on two machines (one Centos 4.1, the other Ubuntu 7.04). So far I'm well impressed -- excellent work by the dev team! The EX 1300 is working beautifully with NUT on the Centos box, but I'm having a bit of a problem with the ES 550: even while loaded, the ups.load

Hi everyone, I just want to know about driver support over new APC smart models. My company recently bought a Smart-Ups RT model: SURT3000XLI and a I cannot do to make work it with last version of nut software. Maybe this model it doesn?t supported yet and I want to know if so. The diference with others models like matrix or backup ones is the famous Smart Cable: 940-1525A (utp - db9). I

Hi everyone, I just want to know about driver support over new APC smart models. My company recently bought a Smart-Ups RT model: SURT3000XLI and a I cannot do to make work it with last version of nut software. Maybe this model it doesn?t supported yet and I want to know if so. The diference with others models like matrix or backup ones is the famous Smart Cable: 940-1525A (utp - db9). I