search for: ups3

...ived from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.12.1.1.2 [ups2-1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.3.3.1.12.1.1.3 [ups2-1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.2.1.1.0 [ups2-1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.2.1.2.0 87.478686 Starting UPS: ups3-1 Network UPS Tools - Generic SNMP UPS driver 0.72 (2.7.2) Detected Smart-UPS 5000 on host ups3-1.[redacted] (mib: apcc 1.2) [ups3-1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.3.1.1.1 [ups3-1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.3.1.1.2 [ups3-1] unh...

...in rack 2 - AP9619" driver = snmp-ups mibs = apcc port = [ups2...] snmp_version = v1 community = [xxx] # snmp_version = v3 # secLevel = authPriv # secName = [xxx] # authPassword = [xxx] # authProtocol = MD5 # privPassword = [xxx] # privProtocol = DES [ups3] desc = "APC Smart-UPS 5000 SNMP in rack 3 - AP9617" driver = snmp-ups mibs = apcc port = [ups3...] snmp_version = v1 community = [xxx] # snmp_version = v3 # secLevel = authPriv # secName = [xxx] # authPassword = [xxx] # authProtocol = MD5 # privP...

I have three APC SmartUPS 5000s. Two of them are AP9617 and one is AP9619. I have a RS-232 connections from my monitor host to all three. All three report status and give information. One of the two AP9617 - ups3-1 - does not shut down when FSD is sent. It did when I first set this system up a year or two ago but it'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 runn...

...s immediately after i plug the power cord... without any kind of delay. After 2 days of testing, frustrated, i tried to setup a new nut server. Different machine, same hardware and same software. This time i used a serial cable and apcsmart driver. Everything just worked! My new ups.conf: [ups3] driver = apcsmart port = /dev/ttyS0 The relevant output of "upsrw ups3 at localhost": [ups.delay.shutdown] Interval to wait after shutdown with delay command (seconds) Type: ENUM Option: "090" SELECTED Option: "180" Option: "270" Option: "36...

...e UPSes the following happens: upssched#1: UPS1 sees the timer daemon is not running, takes the lockfn file and starts to launch a timer daemon. upssched#2: UPS2 sees the timer daemon is not running, and the lockfn is in use, so it deletes the lockfn and goes to sleep for 0.25 seconds. upssched#3: UPS3 UPS1 sees the timer daemon is not running, takes the lockfn file(released by upssched#2, not upssched#1) and starts to launch a timer daemon. Now TIMER-START event will go to two different upssched timer daemons. When power comes back on a little while later all CANCEL-TIMER events are sent to the...

Dear folks, The patch in attachment allows upssched to put actual UPS name into command line even if configuration contains wildcard (*). E.g. AT LOWBATT * EXECUTE "LOWBATT %s" AT ONLINE ups3 EXECUTE "ONLINE %s" where %s is replaced with UPS name before logging and execution. A possible further enhancement could be if regular expressions are also acceptable in place of asterisk. I mean something like this: AT FSD ups1 EXECUTE "shutting down %s" AT FSD *...

...see anything. On the third run I saw messages about "startup timer elapsed" for ups2-1 and then it tried again to launch that one (killing the existing one). It did this multiple times. When trying to systemd I see a bunch of zombie processes that used to be snmp-ups for one of ups2-1 or ups3-1 (depending on the run). I'm trying again with /etc/systemd/system/nut-driver.service.d/nut-driver.conf set to: [Service] TimeoutSec=600 and /etc/ups/ups.conf having maxretry = 10 retrydelay = 15 This time ps shows three apparently happy snmp-ups processes but upsdrvctl start is st...

I'm following advice from Arjen de Korte and Charles Lepple (see http://lists.alioth.debian.org/pipermail/nut-upsuser/2010-January/005829.html). I added a full update on the specifics of my situation: http://lists.alioth.debian.org/pipermail/nut-upsdev/2011-February/005255.html Would appreciate guidance on getting started generating a MIB-to-NUT mapping (tools, etc): OS: CentOS 5.5 NUT

...TEGER: 2 NUT-MIB::deviceIndex.3 = INTEGER: 3 NUT-MIB::deviceIndex.4 = INTEGER: 4 NUT-MIB::deviceIndex.5 = INTEGER: 5 NUT-MIB::deviceIndex.6 = INTEGER: 6 NUT-MIB::deviceName.1 = STRING: ups2 NUT-MIB::deviceName.2 = STRING: xxx NUT-MIB::deviceName.3 = STRING: upsoutlet NUT-MIB::deviceName.4 = STRING: ups3p1 NUT-MIB::deviceName.5 = STRING: ups3p2 NUT-MIB::deviceName.6 = STRING: ups3 NUT-MIB::deviceDesc.1 = STRING: UPS2 10 KVA Lacerda Titan Black tri-mono 10KVA (220v) Serial A08823221 NUT-MIB::deviceDesc.2 = STRING: Fictious NUT-MIB::deviceDesc.3 = STRING: Example outlet NUT-MIB::deviceDesc.4 = STRING...

...TEGER: 2 NUT-MIB::deviceIndex.3 = INTEGER: 3 NUT-MIB::deviceIndex.4 = INTEGER: 4 NUT-MIB::deviceIndex.5 = INTEGER: 5 NUT-MIB::deviceIndex.6 = INTEGER: 6 NUT-MIB::deviceName.1 = STRING: ups2 NUT-MIB::deviceName.2 = STRING: xxx NUT-MIB::deviceName.3 = STRING: upsoutlet NUT-MIB::deviceName.4 = STRING: ups3p1 NUT-MIB::deviceName.5 = STRING: ups3p2 NUT-MIB::deviceName.6 = STRING: ups3 NUT-MIB::deviceDesc.1 = STRING: UPS2 10 KVA Lacerda Titan Black tri-mono 10KVA (220v) Serial A08823221 NUT-MIB::deviceDesc.2 = STRING: Fictious NUT-MIB::deviceDesc.3 = STRING: Example outlet NUT-MIB::deviceDesc.4 = STRING...