similar to: Data stale & Got disconnected by another driver: Device or resource busy

Hi, Here's the message when I try to stop upsdrv daemon (/etc/init.d/upsdrv stop) * Stopping UPS drivers ... Network UPS Tools - UPS driver controller 2.4.3 Can't open /var/lib/nut/usbhid-ups-auto.pid: No such file or directory Here's the message when I try to start upsdrv daemon (/etc/init.d/upsdrv start) * WARNING: upsdrv has already been started. And finally here's

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, 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

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

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

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

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 speech, and figured SNMP would get there eventually since it's UDP. But if you have

Hello! I got my hands on a CyberPower 1500AVRT, and i'm trying to get it connected to my Gentoo machine. I've followed all the basic guides on setting up NUT and UPS' but have had no luck. My current ups.conf is: [cyberpower-gentoo] driver = cyberpower port = /dev/ttyS0 desc = Workstation Upon running /etc/init.d/upsd start or upsdrv start I get: * Starting

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

fellows, You can now commit to the trunk everything that is scheduled for 2.4 For my part, the november month will be mostly dedicated to the following: - commit the USB "improved maintenance" code. I'm about to finish that one, which allows to extract USB info and generate the various USB related files (hotplug, udev and hal). so the end of that bothering era ^_^ - complete &

On Sun, Nov 16, 2008 at 11:08 AM, Arnaud Quette <aquette.dev at gmail.com> wrote: > 2008/11/15 Charles Lepple <clepple at gmail.com>: >> On Fri, Nov 14, 2008 at 5:42 PM, Arnaud Quette <aquette.dev at gmail.com> wrote: >>> fellows, >>> >>> You can now commit to the trunk everything that is scheduled for 2.4 >>> >>> For my part,

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

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 -

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

I have a Gentoo linux (OpenRC) desktop connected to a UPS, the brand is Vultech, but lsusb gives me this: Bus 003 Device 006: ID 0925:1234 Lakeview Research and I found an article about this hardware here, someone had it working with the richcomm_usb driver: http://verahill.blogspot.it/2012/12/kstar-australia-1500-va-ups-on-debian.html So, I installed nut and configured my UPS to work with the

Hello list, I want to virtualize my physical CentOS 4.5 yet. Therefor I download the CentOS 4.5 iso. After mounting the iso on my notebook and make the mounted iso available via nfs I start on my CentOS 5 xen machine following command: virt-install -n myServer --ram=512 -f /virt/myServer.disk -s 150 --nographics -p --location=nfs:nbk:/media/centos This works for CentOS 5 DomUs but CentOS 4.5

[...] > I think this output doesn't help very much. This is very helpful. The problem is not in the connection to the driver, upd->data_ok switches between 0 and 1. Only the driver can change this value by repetitively switching between DATASTALE and DATAOK. There is nothing upsd can do about this, this is a driver problem. This is consistent with the observation that all people

> here the output of "upsd -DDDDD" when starting "upsc apc@localhost > ups.status" (and stopping after 20-30 sec with an ctrl+c) Ah, you have a problem with 'upsc' rather than with 'upscmd' like you stated before. That changes things. > Connection from 127.0.0.1 > acl_check: localhost: match 1 > ACL [localhost] matches, action=1 > write:

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