similar to: Upsdrv failed to start

I can't seem to get NUT to connect to my new PowerWare (Eaton) 5115. (Linux 2.6.34.1 x86_64, Gentoo) # /etc/init.d/upsdrv start * Caching service dependencies ... [ ok ] * Starting UPS drivers ... Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - BCMXCP UPS driver 0.23 (2.4.3) USB communication subdriver 0.18

Hi, I'm trying to setup my Mustek 600 with USB (no serial ports on my computer) on Gentoo. The configuration I use is: [Mustek] driver = megatec_usb port = auto desc = "Power Mustek 600 USB" The NUT I use on my x86_64 machine is: sys-power/nut-2.4.3-r2 USE="bash-completion ssl usb xml -cgi -hal -snmp" When I start upsdrv I get: weasel ~ # /etc/init.d/upsdrv start

This issue has been occurring for years on my setup. OS: Gentoo most recent kernel: 4.1.12 UPS: Eaton Powerware 9130 rackmount 2000kVA, connected via USB The upsdrv service dies and must be restarted several times a day. Zero output to dmesg or any other log other than failed reattempts reporting no such file or directory errors. "/lib64/nut/usbhid-ups -DDD -q -a powerware" exited 1

First, a little history; nut has been working on this system for about two years. It was a Fedora Core 2 (3?) system that I wiped and installed SUSE 10.1 on so I'm fairly confident of the hardware. I thought I'd saved the nut configuration details before I did the reinstall, but can't find them. (D'oh!) The UPS is an APC BackUPS Pro 420. The cable is a clone of the APC

On 2014-02-16 16:36, Elliot Dierksen wrote: > On 2/5/2014 8:24 AM, Charles Lepple wrote: >> On Feb 4, 2014, at 10:48 PM, Elliot Dierksen wrote: >> >>> NUT will complain endlessly about communication errors and never >>> establish SNMP communication with my APC UPS >> Hmm, at first glance, I read the "complain endlessly" part as a figure >> of

Hi Charles, thank you for your answer. This was indeed the core of the problem. I have amended the configuration files. It means now the communication works as required. Alas I now have another problem. Just for the record here is the configuration after the changes. The configuration is as follows. #nut.conf MODE=standalone #ups.conf [eaton] driver = usbhid-ups port = auto

Hi, I have a small home-use UPS for my home server from powerwalker (http://powerwalker.com/de/index.php?option=com_content&task=blogcategory&id=63&Itemid=106 sorry I only found a german version). It has a USB and a serial connector. lsusb lists it as "06da:0003 Phoenixtec Power Co., Ltd", in /proc/bus/usb/devices it sais "Manufacturer=OMRON" and

I have a 64 bit Gentoo, with a Liebert UPS. The last NUT working version was sys-power/nut-2.4.1-r1 (I also tried sys-power/nut-2.4.3-r2 but downgraded, don't remember the reason). Anyway with the upgrade to sys-power/nut-2.6.0 I started to see this error message when I try to start upsdrv: [root at aemaeth:/etc/nut]$ /etc/init.d/upsdrv start * Starting UPS drivers ... Network UPS Tools -

Good afternoon. I try to put nut on gentoo. Has executed installation by a standard command emerge nut. All has passed successfully. I use UPS POWERCOM BNT-1500AP. It is connected to serial port 1, i.e. for my system it/dev/tts/0. In/etc/nut/ups.conf [powercom] driver = powercom port = /dev/tts/0 desc = "PowerCom BNT-1500AP on IP-PBX" modelname = "BNT-1500AP" linevoltage = 230

I just installed NUT on a new Linux (Gentoo) system. Most things work, (notification after 10 seconds on battery, notification and system shutdown after 100 seconds on battery.) However I can't seem to get the UPS (an Eaton 5SC1500) to turn itself off after the Gentoo system shutdown. This is the shutdown command I am using in /etc/nut/upsmon.conf: SHUTDOWNCMD "/usr/sbin/upsdrvctl

Hello I'm back with another problem I made a lot of tests with my ups MGE I worked on my script upssched-cmd and i stopped several times my ups etc etc .... Suddenly my UPS wasn't be detected by my server I tried restore my system I tried modify files without success my UPS isn't detected by my serveur When I enter this command lsusb I have had no more this bus001 device 002 : ID

Hi, I'm running the latest stable nut (2.4.3). It doesn't appear to provide support for the Tripp Lite SmartOnline SU1000XLA. [sups] driver = usbhid-ups port = auto vendorid = 09ae productid = 4004 4337# 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:

Hi all, As requested by upsdrvctl, I'm reporting on my results connecting a Tripp Lite UPS (G1010USB). This server is running on Ubuntu Lucid, nut version is 2.4.3-1ubuntu3.1. With ups.conf: [ups] driver = usbhid-ups port = auto Results: # 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

Hey all, I am trying to use NUT for a Tripplite Smart1200 LCD on a fresh copy of Debian 6.0.2.1. I installed NUT version 2.4.3 and I have pored through pages and pages of other posts, but for the life of me I can not get it to recognize the Tripplite. I know its an 09ae:2009 device and I've tried to add a rule in /lib/udev/rules.d/52-nut-usbups.rules as according to some posts, but to no

This really isn’t what you want. You should use a normal shutdown command on Gentoo: SHUTDOWNCMD "/sbin/shutdown -h +0” When you emerged the NUT package, you should have seen this message: * Please note that NUT now runs under the 'nut' user. * NUT is in the uucp group for access to RS-232 UPS. * However if you use a USB UPS you may need to look at the udev or * hotplug

Greetings. I have a Tripp-Lite AVR-900U that I am trying to get work with NUT. (I rather naively bought the thing assuming that since NUT worked with the AVR-750U, that the same would be so of this model.) Here's what I've got so far: # 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 This

Hi, I'm trying to install NUT on Ubuntu. All is good until I try to start the driver, then I get this error: $ sudo 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 This APC device (051d:0003) is not (or perhaps not yet) supported by usbhid-ups. Please make sure you have an up-to-date version of

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

Hi, I am running nut with megatec driver accessing ttyS0 as user nut on "standard" kernel (gentoo-sources). It works fine. However, I just built a hardened kernel on a new gentoo machine and have no experience with it. NUT (upsdrv) is failing because it says it doesn't have permission to access ttyS0 even though nut is within the appropriate group. I can add user = root in ups.conf

Good day all and sorry my English. I have some problem when updating NUT. I have server with 4 UPS connected. When I starting upsdrv and upsd and after sometime (1-2 minutes) I can't get data from ups's # upsc apc at localhost battery.type Error: Data stale and errors in /var/log/{syslog,debug,daemon.log} usbhid-ups[2385]: Got disconnected by another driver: Device or resource busy OS: