search for: ups1

...itself (I think; there have been some changes to that code over the years) and it will show the whole command line. > > Another option (which papers over the problem, but may help in the near term) is to see if this is just a startup issue. You can specify one UPS with "upsdrvctl start ups1", and then see if the other drivers still start if you wait until the first driver has completed its SNMPv3 handshake. You can automate this a bit with the "maxretry" and "retrydelay" options in ups.conf: http://networkupstools.org/docs/man/ups.conf.html > ------------...

...to use SNMPv3 then on startup upsdrvctl complains about "unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.7.1.1.3" and fails to start. My current [redacted] ups.conf follows. The only differences between the values are on the port and desc lines (ignoring #, of course). [ups1] desc = "APC Smart-UPS 5000 SNMP in rack 1 - AP9617" driver = snmp-ups mibs = apcc port = [ups1...] # snmp_version = v1 # community = [xxx] snmp_version = v3 secLevel = authPriv secName = [xxx] authPassword = [xxx] authProtocol = MD5 privPassw...

Hi, I have had a long standing problem with NUT talking to 110V MGE UPSs on FreeBSD, I was recently investigating again and noticed that upsd seems overly noisy, eg.. May 5 03:50:36 egbert upsd[96662]: UPS [ups1] data is no longer stale May 5 03:50:36 egbert upsd[96662]: Data for UPS [ups1] is stale - check driver May 5 03:50:36 egbert upsd[96662]: UPS [ups1] data is no longer stale May 5 03:50:36 egbert upsd[96662]: Data for UPS [ups1] is stale - check driver May 5 03:50:39 egbert upsd[96662]: UPS [up...

Hi All, I have an mge pulsar esv 14+ rackmount UPS connected via straight through serial cable to a USB to serial adaptor (My motherboard does not have a native RS232 port). I am running Ubuntu Server 9.04 x64, and nut 2.4.1-2ubuntu4 installed via APT. I am getting the error: Poll UPS [ups1 at localhost] failed - Driver not connected My conf files: (ups.conf) [ups1] driver=mge-utalk port=/dev/ttyUSB0 (upsd.conf) ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACCEPT localhost REJECT all (upsd.users) [monuser] allowfrom = localhost password = pass upsmon mast...

(Note that I mentioned this *was* previously working with an older version of Nut). [irs2-ups1] driver = snmp-ups port = irs2-ups1.sum.naoj.org mibs = auto community = private irs2-ups1.sum.naoj.org responds to pings. On Tue, Oct 8, 2013 at 3:55 PM, Tim Rice <tim at multitalents.net> wrote: > On Tue, 8 Oct 2013, Philip Tait wrote: > > > Here is the upsc...

Hello, I've got a setup with NUT, where we've got two UPSes, ups1 and ups2. UPS1 supports our servers, while UPS2 supports our desktop boxes. We monitor both of them via USB on a box now called "upsmon". The interesting point comes here. We monitor both UPSes on the upsmon box, but if UPS2 fails, which supports our desktop boxes, NUT shouldn't init...

...ng shut_get_report(id: 06, len: 1800) shut_wait_ack(): ACK received entering shut_get_report(id: 06, len: 1800) shut_wait_ack(): ACK received entering upsdrv_updateinfo() entering shut_get_report(id: 0f, len: 1800) And upsd.. write: [destfd=7] [len=15] [ERR DATA-STALE] sstate_dead: driver for UPS [ups1] says data is stale Broadcast Message from radar at negrocreek.dnsalias.net (no tty) at 7:57 UTC... Communications with UPS ups1 at localhost lost sstate_dead: driver for UPS [ups1] says data is stale UPS [ups1] data is no longer stale acl_check: localhost: match 1 ACL [localhost] matche...

...1 MGE UPS SYSTEMS' and '1 EATON'). Strangely, vendor is '0x0463 MGE UPS Systems' for both. They're also on the same bus ('Bus 003 Device 063' and 'Bus 003 Device 064') Since there is no flag for manufacturer, I had to go with serial. This is my new ups.conf: [ups1] driver = usbhid-ups port = /dev/usb/hiddev0 serial=000000000 [ups2] driver = usbhid-ups port = /dev/usb/hiddev1 serial=1HCG4700J When I run upsdrvctl start ups1, it starts /lib/nut/usbhid-ups -a ups1 but no -x flag. Starting usbhid-ups manually with the -...

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 ap9630 card here just fine. H...

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() 0.000341 SNMP UPS driver : entering nut_snmp_init(snmp-ups) 0.056112 SNMP UPS driver : entering load_mib2nut(auto) 0.05612...

Hello I'm having a bit of a trouble to set up a Back-UPS on a production box. We're using the newhidups driver for this module here, in the office, and I'd like to monitor the one, out in our server farm. The situation is the following: # /lib/nut/newhidups -u root -DD -a ups1 2> ups1.out Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) this one worked flawlessly, while as a user, it cannot access the UPS: # /lib/nut/newhidups -u nut -DD -a ups1 Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) debug level is '2&...

...ind that it connects with the in the device folder as hiddev0 and if I connect a second device it connects under hiddev1. I attempted to use your software with the driver=usbhid-ups and port=auto, but when I try to discover it it can't be found. Then when I run the command /sbin/usbhid-ups -a ups1 -D where ups1 described the driver and port combination, I get the following output: This Tripp Lite device (09ae/3014) is not (yet) supported by usbhid-ups. Please make sure you have an up-to-date version of NUT. If this does not fix the problem, try to tun the driver with the '-x productid=3...

Hi, I've got a question about managing two UPSes under NUT. I have two similar model APC usb-connected UPSes to work with, but don't know how to manage them simultaneously from under Windows. Long story short, my ups.conf looks like this: --- ups.conf --- [ups1] driver= usbhid-ups port= auto serial=AS1054340323 [ups2] driver= usbhid-ups port= auto serial=AS1026662626 --- ups.conf --- I tried all the combinations with vendorid, productid, vendor, product as in the manual for usbhid-ups and libusb's test --- TestLibUsb --- - Manufacturer :...

Hello, We have two APC Back-UPS RS 1500 USB stuff, and i've got a bit of a problem with it and NUT. The usbdevs output: addr 2: Back-UPS RS 1500 FW:8.g8 .I USB FW:g8, American Power Conversion addr 3: Back-UPS RS 1500 FW:8.g8 .I USB FW:g8, American Power Conversion (UPS1 and UPS2) I've configured our NUT system to monitor the UPSes, and it went very fine till the time had arrived for a test. UPS unpower (-> ONBAT), and test what NUT does to the boxes connected to it. After I've unplugged the power cable of UPS1, nut started not to notice that on its cg...

...ompat page. When I start up the nut daemon, I get the following output: # /usr/local/etc/rc.d/nut start Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools - Multi-MIBS SNMP UPS driver 0.41 (2.0.5) Warning: This is an experimental driver. Some features may not function correctly. [ups1] nut_snmp_get: .1.3.6.1.2.1.33.1.1.2.0: Error in packet: (noSuchName) There is no such variable name in this MIB. ietf MIB wasn't found on ups1 Driver failed to start (exit status=1) Do any of you know if it is possible to use the 66102 card with the snmp driver at all, or do I have to buy...

Hi, I didn't found an answer for my question in NUT documentation/FAQ or this mailing list archive so I?m posting it here. I want to start a timer only if both of my UPSes remain on battery. Not just one, both. My UPSes are: - ups1@host-a - ups2@host-b Is it possible to use something like this in upssched.conf? AT ONBATT ups1.* && ups2.* START-TIMER onbattwarn 180 Thanks, Dumitru

...sh FreeBSD 6.x system). It sees the UPS but I can't actually query it for data, in the usbhid-ups debug output I see.. 30.840512 HIDGetEvents: failed to buffer report: Result too large 30.840600 Got -34 HID objects... 30.840681 Quick update... upsc gives.. downie:~>upsc ups1 at localhost ups.status: WAIT downie:~>upsc ups1 at localhost Error: Data stale I have attached the output from the following sudo /usr/local/sbin/upsd -D -D -D sudo /usr/local/libexec/nut/usbhid-ups -D -D -D -a ups1 Any ideas? The libusb support in 6.x is pretty crappy so maybe it's that...

...ew variable, named 'device.parent', so that > every device can reference its parent. > > I propose to add a new entry in docs/nut-names.txt, with the following > content: > > | device.parent | Reference to the parent node in the PowerChain (NUT host > format) | ups1 at localhost > > A new chapter will be created in the user manual, to describe the usage of > this feature. > > Note that there will be a separate mail to discuss implementation details. > I've been thinking a bit more on PowerChain design and implementation. it appeared tha...

...tifier: /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut Dec 10 21:40:21 nas6 notifier: nut_upsmon not running? (check /var/db/nut/upsmon.pid). Dec 10 21:40:21 nas6 notifier: Starting nut_upsmon. Dec 10 21:40:21 nas6 notifier: kill: No such process Dec 10 21:40:21 nas6 notifier: UPS: UPS1 (master) (power value 1) Dec 10 21:40:21 nas6 upsmon[39737]: UPS [UPS1]: connect failed: Connection failure: Connection refused Dec 10 21:40:21 nas6 upsmon[39737]: Communications with UPS UPS1 lost Dec 10 21:40:21 nas6 notifier: nut_upslog not running? (check /var/db/nut/upslog.pid). Dec 10 21:40:2...

...t's stopped doing so since then. Resetting the management interface does not change anything. This is all that shows up in /var/log/messages on the host that is connected to the UPSs and running the full NUT suite: Dec 25 08:00:26 [redacted] upsd[9800]: Client upsmon@[redacted] set FSD on UPS [ups1-1] Dec 25 08:00:26 [redacted] upsd: Client upsmon@[redacted] set FSD on UPS [ups1-1] Dec 25 08:00:26 [redacted] upsd: Client upsmon@[redacted] set FSD on UPS [ups2-1] Dec 25 08:00:26 [redacted] upsd: Client upsmon@[redacted] set FSD on UPS [ups3-1] Dec 25 08:00:26 [redacted] upsd[9800]: Client upsm...