search for: ups01

...ent.conf (code=exited, status=0/SUCCESS) Main PID: 831 (upsmon) Tasks: 2 (limit: 512) CGroup: /system.slice/nut-monitor.service ??831 /usr/sbin/upsmon -F -DD ??902 /usr/sbin/upsmon -F -DD Sep 16 18:51:35 client upsmon[831]: 450.063107 Trying to connect to UPS [ups01 at ups.server.lan:3493] Sep 16 18:51:35 client upsmon[831]: 450.063321 UPS [ups01 at ups.server.lan:3493]: connect failed: No such host Sep 16 18:51:40 client upsmon[831]: 455.063402 Trying to connect to UPS [ups01 at ups.server.lan:3493] Sep 16 18:51:40 client upsmon[831]: 455.063...

I'm attempting to get a HP R1500 G2 UPS working with Solaris 10 connected via USB. Thanks to Arnaud's patch to drivers/tripplite-hid.c found at http://lists.alioth.debian.org/pipermail/nut-upsuser/2010-February/005887.html things mostly work. upsc ups01 shows a couple of things that don't look quite right. [....] battery.temperature: -234.1 [....] ups.alarm: No battery installed! But the real problem I'm having right now is it does not want to turn off the UPS. --------< ups.conf >-------- [ups01] driver = usbhid-ups port = auto des...

Hi. I'm looking for a way to configure an Eaton Powerware 5125 under Debian Squeeze (amd64) with USB port. Can someone help me? Find attached bellow my settings: # cat /etc/nut/ups.conf ... [ups01] driver = bcmxcp_usb port = /dev/bus/usb/002/003 desc = "Powerware 5125" # ls -la /dev/bus/usb/002/003 crw-rw-r-- 1 root nut 189, 130 Nov 21 11:45 /dev/bus/usb/002/003 # /lib/nut/bcmxcp_usb -DDDDDDDD -a ups01 Network UPS Tools - BCMXCP UPS driver 0.23 (2.4.3) USB communication subdriv...

...ay rely on > > whole chain from vendor firmware implem to chips, hubs, OS drivers, > > powersaving and whatnot. And everyone cuts corners. > > > > Running the drivers in debug mode can expose the events and state > > changes: stop their services, run `usbhid-ups -a vdn-ups01 -DDDDDD`, > > watch console as you pull the plug and put it back. > > > > Also current NUT (master certainly, 2.8.0 release maybe) should try > > harder to reconnect upon problems. Possibly an upgrade would address > > your ling-term stability issues. > > > &g...

...this auto correct once name resolution is working properly regardless? upsmon on the Raspbian NUT server works fine and is attached > to localhost:3493. > > If I use an ip instead of a DNS name this config works correctly on boot. Do commands on the client such as: echo "GET VAR ups01 battery.charge" | netcat ups.server.lan 3493 echo "GET VAR ups01 battery.charge" | netcat 11.22.33.44 3493 reproduce the problem? If so, the problem may be with the DNS rather than NUT. What does command dig ups.server.lan on the client report? Roger

...t; > > > Binary package hint: nut > > > > I was using nut with the megatec_usb driver for years without problems. > > Now I upgraded my server to 10.04 and the driver stopped to work with > > nut_2.4.3-1ubuntu3.1. Here is the ups.conf I am using > > > > [ups01] > > driver = megatec_usb > > port = auto > > vendorid = 0665 > > productid = 5161 > > mfr = "Powerwalker" > > model = "Line Interactive VI 1400" > > serial = "73712C00008&quot...

...it > does not allow a value smaller than 6, the blazer_usb refused to work > (it was 1 in megatec). > > Thanks a lot to Arnaud for the quick reply! > thanks goes to Arjen de Korte, a NUT senior lieutenant, who worte the blazer drivers. > Here is my new ups.conf now: > > [ups01] > driver = blazer_usb > port = auto > vendorid = 0665 > productid = 5161 > # after shutdown, wait 5 minutes after return of power > ondelay = 5 > # wait 1 minute after power-off command before cutting power >...

...in after power returned (waiting the defined delay). I also attached the blazer_usb output in case this is needed. If there are other testes required to improve the driver I am happy to do this (maybe read out the remaining battery capacity?). This is the output of upsc: root at xen-base:~# upsc ups01 battery.voltage: 25.70 battery.voltage.nominal: 24.0 beeper.status: enabled device.type: ups driver.name: blazer_usb driver.parameter.offdelay: 60 driver.parameter.ondelay: 5 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.productid: 5161 driver.parameter.vendorid: 066...

...as long as they work reliably or at all, which may rely on whole chain from vendor firmware implem to chips, hubs, OS drivers, powersaving and whatnot. And everyone cuts corners. Running the drivers in debug mode can expose the events and state changes: stop their services, run `usbhid-ups -a vdn-ups01 -DDDDDD`, watch console as you pull the plug and put it back. Also current NUT (master certainly, 2.8.0 release maybe) should try harder to reconnect upon problems. Possibly an upgrade would address your ling-term stability issues. Jim PS: returning discussion to mailing list :) On Tue, Jan 3...