search for: ups0

...Could I be missing some dependency, external application, which upsmon uses as a timer? (A side issue is that it's not using the correct variable when passing to upssched-cmd, but uses the notify text itself, "ONBATT", this can be seen in the last line from, messages, $1 is "UPS ups0 at localhost on line power", but this is not important for me, but may be used to explain why the timer is not working) ONBATT Dec 2 18:48:56 storage01 upsmon[3603]: ONBATT Dec 2 18:48:56 storage01 wall[4371]: wall: user root broadcasted 1 lines (8 chars) Dec 2 18:48:56 storage01 upssched...

...al, googled much, read most NUT manuals, read up to 'queequeg', asked on APC forums, etc. The most distressing problem is the UPS stays OB after removing and reapplying utility power. When power is removed, the UPS goes OB and upsmon detects the power failure no problem, reporting 's0-ups0 at localhost is on battery'. But when power is restored, there is no clicking of contactors, no switch back to OL, and no detection by upsmon that power is restored. The UPS can be manually put back OL with 'upscmd load.on'. I would expect the UPS go back OL automatically, though; am...

...UT manuals, read up to > 'queequeg', asked on APC forums, etc. > > The most distressing problem is the UPS stays OB after removing and > reapplying utility power. When power is removed, the UPS goes OB and > upsmon detects the power failure no problem, reporting > 's0-ups0 at localhost is on battery'. But when power is restored, there is > no clicking of contactors, no switch back to OL, and no detection by > upsmon that power is restored. The UPS can be manually put back OL with > 'upscmd load.on'. I would expect the UPS go back OL automatica...

...ne is 2.6.3-1ubuntu2. Both of them are installed from the repositories. I tried adding "pollinterval=20" to ups.conf, "MAXAGE25" to upsd.conf and "DEADTIME25" to upsmon.conf but I still get stale errors in syslog and null information about all the stats. #ups.conf [ups0] driver = mge-utalk port = /dev/ttyS0 pollinterval = 20 The logs are in the attached file. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20130418/59ae715a/attachment.html> -------------- next...

...s Jordan wrote: > John Morris wrote, On 9/21/2013 11:28 AM: >> The most distressing problem is the UPS stays OB after removing and >> reapplying utility power. When power is removed, the UPS goes OB and >> upsmon detects the power failure no problem, reporting >> 's0-ups0 at localhost is on battery'. But when power is restored, there is >> no clicking of contactors, no switch back to OL, and no detection by >> upsmon that power is restored. The UPS can be manually put back OL with >> 'upscmd load.on'. I would expect the UPS go back O...

...ars correct, as the input stays steady, and the output shows ~5V. For the above, the Powercom upsmon software appears to special-case those ~5/15V results, and on the next update, report it as 0V. I have no idea how to even special-case the screwy input/output-swapping behavior... ./powercom -a ups0 -DDD Network UPS Tools - PowerCom protocol UPS driver 0.12 (2.4.1-2308) 0.000000 debug level is '3' 0.001406 Flow control disable 0.150003 Detected: BNT-other-500AP , 120V 0.153986 Values of arguments: 0.154001 manufacturer : 'PowerCom'...

...f it is disconnected just for a second, or even worse, when I got low tension. So, mail notifications are well configured, I guess... I think the problem is in upssched. I'm new to this, so it could be a stupid thing that I'm missing... My configurations files are like this: *ups.conf:* [ups0] driver = mge-shut port = /dev/ttyS0 #It's serial, not USB *upsmon.conf:* # NOTIFYCMD <command> NOTIFYCMD /usr/local/ups/bin/notifyme # POWERDOWNFLAG - Flag file for forcing UPS shutdown on the master system POWERDOWNFLAG /etc/killpower # Th...

Hello! I've ran into this annoying issue when setting up a new server. I have an APC SmartUPS hooked up on a USB-serial converter on /dev/ttyUSB0. This works nicely, until: hub 3-0:1.0: port 1 disabled by hub (EMI?), re-enabling... pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0 usb 3-1: pl2303 converter now attached to ttyUSB1 apcsmart gets into an infinite loop of this:

...ce 003: ID 09ae:3024 Tripp Lite AVR900U Contents of /etc/ups/ups.conf: > [tripplite] > driver =  usbhid-ups > port = auto Contents of /etc/udev/rules.d/50-ups.rules: > SUBSYSTEM=="usb", ATTR{idVendor}=="09ae", ATTR{idProduct}=="3024", SYMLINK+="ups0", GROUP="nut" Post-configuration, I rebooted then ran upsdrvctl and received the following output: > $ upsdrvctl start > Network UPS Tools - UPS driver controller 2.7.4 > Network UPS Tools - Generic HID driver 0.41 (2.7.4) > USB communication driv...

...t; repositories. > > I tried adding "pollinterval=20" to ups.conf, "MAXAGE25" to > upsd.conf and "DEADTIME25" to upsmon.conf but I still get stale > errors in syslog and null information about all the stats. > > #ups.conf > [ups0] > driver = mge-utalk > port = /dev/ttyS0 > pollinterval = 20 > > The logs are in the attached file. > > > mge-utalk was fixed in the development branch, but was not yet released. > You can download from github either the tree or just the patch: > https...

...1) It's most likely a problem with permissions for accessing the device. You can fix that by specifying an udev rule that sets the correct group: /etc/udev/rules.d/50-ups.rules SUBSYSTEM=="usb", ATTR{idVendor}=="XXXX", ATTR{idProduct}=="YYYY", SYMLINK+="ups0", GROUP="nut" Where idVendor and idProduct are the device manufacturer and product ID. You can see these either in the error output [XXXX:YYYY] or by using lsusb. After this is done, reload and retrigger udev rules by issuing this command: # udevadm control --reload-rules &&...

I am forwarding the below message. Does anybody on this list know anything about this problem? Petr - perhaps you should switch from the "hidups" to the "newhidups" driver. I believe it supported the APC Back UPS even in NUT 2.0.2, and it certainly does so in the Development version that you can get from CVS (see the NUT download page). Also, could you post the output of

.... I downloaded NUT 2.0.3 and built it from source using ./configure --prefix /usr/local --with-statepath=/var/run/nut/ \ --with-pidpath=/var/run/nut/ --sysconfdir=/etc/nut --with-user=nut With NUT installed and the UPS plugged in to a USB port on the machine: kaylee# cat /etc/nut/ups.conf [ups0] driver = tripplite_usb port = auto product = "TRIPP LITE UPS" productid = 2005 serial = "692195 A" kaylee# tripplite_usb -a ups0 -DDDDD -u root Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.6 (2.0.3) Warning: This is an experimental driver. Some feature...

...rial (using mge-shut) ----------------------- battery.charge: 100 battery.charge.low: 20 battery.runtime: 5400 device.mfr: MGE UPS SYSTEMS device.model: Pulsar Evolution 3000 device.serial: AF3E39202 device.type: ups driver.name: mge-shut driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ups0 driver.version: 2.6.2 driver.version.internal: 0.69 input.frequency: 50 input.voltage: 240 outlet.1.autoswitch.charge.low: 0 outlet.1.delay.shutdown: -1 outlet.1.delay.start: -1 outlet.1.desc: PowerShare Outlet 1 outlet.1.id: 1 outlet.1.switch: 1 outlet.1.switchable: 1 outlet.2.autoswitch.charge.lo...