similar to: ACL problem

Hi, I have the above UPS connected to a FreeBSD 6.2 box and it shows 'data stale' very frequently (every few minutes). I have tried the usual trick of setting maxage, poll interval, etc etc but to no avail. When I wind up logging I see (on mge-shut) entering shut_get_report(id: 0d, len: 1800) shut_wait_ack(): ACK received entering shut_get_report(id: 16, len: 1800) shut_wait_ack():

Hi there, I'm trying to track down a problem with said combination. Broadcast message from nut (Thu Jan 26 13:22:06 2006): Communications with UPS UPS@localhost lost Broadcast message from nut (Thu Jan 26 13:22:11 2006): UPS UPS@localhost is unavailable "newhidups -DDD hiddev0" seems happy enough, as does "upsd -DDD -f" - at least until I start upsmon. Then I

I get the following errors constantly in my messages log: Sep 21 11:53:37 cgydc002 upsd[22659]: Connection from 127.0.0.1 Sep 21 11:53:37 cgydc002 upsd[22659]: Host 127.0.0.1 disconnected (read failure) Sep 21 11:53:37 cgydc002 upsd[22659]: Connection from 127.0.0.1 Sep 21 11:53:37 cgydc002 upsd[22659]: Host 127.0.0.1 disconnected (read failure) Sep 21 11:53:37 cgydc002 upsd[22659]: Connection

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

O.S. Ubuntu 10.10, Maverick Meerkat 32 bit. NUT 2.4.3-1ubuntu5, package installed Belkin F6C1500-TW-RK I am having trouble starting uspd whenever I add a client from my lan to uspd.conf: LISTEN 127.0.0.1 3493 LISTEN 192.168.36.106 3493 naknight at nak-server:~$ sudo upsd -DDDD Network UPS Tools upsd 2.4.3 0.000000 listen_add: added 127.0.0.1:3493 0.000093 listen_add:

Hi R users, I am new to R and am trying to merge data frames in the following way. Suppose I have n data frames each with two fields. Field 1 is common among data frames but may have different entries. Field 2 is different. Data frame 1: Src Target1 1 aaa 1 bbb 1 ccc 2 aaa 3 ddd Data frame 2: Src Target2 2 aaaa 3 dddd 4 bbbb 4

Hello, I'm using NUT to manage a MGE Ellipse ASR UPS, with the newhidups driver. It works fine, except that after a few hours, I get a few errors from the kernel and the driver dies. Here's the output from the syslog: Apr 26 02:00:41 ezquiel kernel: usb 1-1: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 128 rq 6 len 255 ret -110 Apr 26 02:00:43 ezquiel last message repeated 2 times

Hi, I am unable to get my UPS working with NUT. Information: lsb_release -a: Distributor ID: Raspbian Description: Raspbian GNU/Linux 8.0 (jessie) Release: 8.0 Codename: jessie apt-cache policy nut-server: nut-server: Installed: 2.7.2-4 Candidate: 2.7.2-4 Version table: *** 2.7.2-4 0 500 http://mirrordirector.raspbian.org/raspbian/ jessie/main armhf Packages

Can someone give me a push in the right direction with this? I'm trying to get an upsonic IRT1000 to work on ubuntu 14.04lts using the usb connection. The most likely drivers (blazer_usb and usbhid-ups) don't seem to recognize it or I've got the configuration parameters wrong. I've got no idea what driver it actually wants though there's an old thread that seems to have got

My UPS is a Eaton Ellipse 1000S (But its identified as MGE Ellipse 0463:ffff). I have been using the usb interface with the usbhid-ups driver, but I found that sometimes (too much times) the driver doesn't respond and NUT doesn't receive changes nor notifications from the UPS. The kernel lose the connections with USB device, in the kernel logs appears: Dec 30 11:24:12 rei kernel:

Hello everybody, After succeeded in "tuning" nut-2.0.0's hidups and 2.0.3's newhidups on customized Linux kernels, we are now facing a new challenge : trying to install nut-2.0.5 on a RedHat ES4 which is based on a 2.6.9 kernel. I picked up the 2.0.5 source package and follow the INSTALL doc until step 6. So far so good. RH ES4 is managed by udev, therefore I presume we

Hi, I've seen a few emails in the archives about problems polling MGE UPSs via USB under FreeBSD, but unfortunately I didn't find a solution in them that works for me. A few details about my setup.. The UPS is a MGE Nova AVR 600 connected via USB to a FreeBSD 6.2 box. I have tried both the nut port (2.0.5) and the svn trunk but have had no success yet. I am running nut as root to

Hi, I've seen a few emails in the archives about problems polling MGE UPSs via USB under FreeBSD, but unfortunately I didn't find a solution in them that works for me. A few details about my setup.. The UPS is a MGE Nova AVR 600 connected via USB to a FreeBSD 6.2 box. I have tried both the nut port (2.0.5) and the svn trunk but have had no success yet. I am running nut as root to

Hello, Got this UPS (connected via USB). I've checked on the nut website, driver is usbhid-ups When I "upsdrvctl start", it says : Network UPS Tools - UPS driver controller 2.6.5-Unversioned directory Network UPS Tools - Generic HID driver 0.37 (2.6.5-Unversioned directory) USB communication driver 0.31 No matching HID UPS found Driver failed to start (exit status=1) Here is

Hi BACKGROUND INFO:I have a new Eaton 5E 1100i USB UPS which their website claims is supported on Linux. They don't provide software for it for Linux, only for Windows.Referring links: https://www.eaton.com/za/en-gb/catalog/backup-power-ups-surge-it-power-distribution/Eaton_5E_UPS.html https://www.eaton.com/za/en-gb/skuPage.5E1100IUSB.specifications.html It was manufactured in May 2020

Great, thanks Arjen! Now we need an autoconf test to set HAVE_IPV6 automatically. I will look into what functionality needs to be tested; the test can be refined as problems arise later. -- Peter Arjen de Korte wrote: > > Author: adkorte-guest > Date: Sat Jan 6 19:39:08 2007 > New Revision: 710 > > Modified: > trunk/ChangeLog > trunk/clients/upsc.c >

Hi everybody, I installed and configured Nut 2.4.3 on Debian Squeeze, using package. It monitors an MGE Pulsar 1500 UPS in standalone mode. Here are parts of upsmon.conf : SHUTDOWNCMD "/bin/bash /root/extinction.sh >> /var/log/ups/ups.log 2>>&1" NOTIFYCMD "/bin/bash /usr/sbin/alerte.sh" [...] NOTIFYFLAG ONBATT SYSLOG+EXEC At startup, driver, upsd and upsmon

On Nov 12, 2014, at 2:49 AM, Klint Gore <kgore4 at une.edu.au> wrote: > Can someone give me a push in the right direction with this? I?m trying to get an upsonic IRT1000 to work on ubuntu 14.04lts using the usb connection. The most likely drivers (blazer_usb and usbhid-ups) don?t seem to recognize it or I?ve got the configuration parameters wrong. I?ve got no idea what driver it

Hi Thanks Gabor for your suggestion. I am posting the code that worked for me. dataframe1 = data.frame(cbind(Src = c(1,1,1,2,3), Target1 = c('aaa','bbb','ccc','aaa','ddd'))); #must be data frame dataframe2 = data.frame(cbind(Src = c(2,3,4,4,4), Target2 = c('aaaa','dddd','bbbb','eeee','ffff'))); dataframe3 =

Hello, I have trouble connecting to an Eaton 5PX UPS via the usbhid-ups driver. It is supposed to be fully working according to the compatibility list (support level 5). OS: A fresh Debian stable install. Then changed the apt source to unstable and did "aptitute update" and "aptitude install nut". Nothing else. I did that, because the "unstable" package is a more