search for: apcups

...t then not exactly apples > to apples to now. > Well that's interesting. The attached script output shows the two commands I used. The first command, nut-scanner, showed no traffic at all, probably not surprising given the error: : || lvd at chscc-pc-052 ~ [1121] ; please tcpdump host apcups and port snmp tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eno1, link-type EN10MB (Ethernet), capture size 262144 bytes ^C 0 packets captured 4 packets received by filter 0 packets dropped by kernel But the second command, snmp-ups, showed unencrypted tr...

...>> > > Well that's interesting. > > The attached script output shows the two commands I used. > > The first command, nut-scanner, showed no traffic at all, probably not > surprising given the error: > > : || lvd at chscc-pc-052 ~ [1121] ; please tcpdump host apcups and port snmp > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > listening on eno1, link-type EN10MB (Ethernet), capture size 262144 bytes > ^C > 0 packets captured > 4 packets received by filter > 0 packets dropped by kernel > > > But the se...

...ects type ?int?, but argument 4 has type ?long unsigned int? Also libusb-devel was the 64 bit version. The ups is an APC Back-UPS RS 1500 attached by one of APC's odd RJ45 to USB cables. upsmon has an issue, but upsc doesn't, it shows the status of the UPS fine: % /usr/local/ups/bin/upsc apcups at localhost battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 etc. Here are my config files - presumably something is bogus but I do not see what: ups.conf: [apcups] driver = usbhid-ups port = auto desc = "APC Back-UPS RS 1500 on 12334567890"...

...ystem. I think this is one of these situations. I've installed NUT on my Mac OS X 10.5 server, using the macports build. The machine is a dual processor G4 tower, connected to an APC UPS via USB. usbhid-ups seems to be working, see output below. However, when I run /opt/local/bin/upsc apcups at localhost All I get is an error message: Error: Data stale When I run upslog, it seems to clearly not be finding the data that usbhid-ups is getting: $ sudo /opt/local/bin/upslog -s apcups -l- Network UPS Tools upslog 2.2.2 logging status of apcups to - (30s intervals) 20081016 103242 NA NA...

...sword43LongerWord Privacy Passphrase: NutScan at Password43LongerWord Authentication protocol: MD5 (only option other than none) Privacy Protocol: DES (only option other than none) In access control I've enabled user nut. However, when I try to use nut-scanner on it: $ nut-scanner -S -s apcups --secLevel authPriv --secName nut --authProtocol MD5 --authPassword NutScan at Password43LongerWord --privProtocol DES --privPassword NutScan at Password43LongerWord Scanning SNMP bus. Error: unknown authtypeError generating Ku from authentication pass phrase snmpwalk gives a different error: $ sn...

...t is going on and what we are doing wrong. By running a slave upsmon process with a debugging flag set it can be seen that the 15 minute delay occurs as a result of the upsmon's poll of the master's upsd process. Once the master has gone off line, the slave upsmon reports: polling ups: apcups at nutMaster.domain.uk get_var: apcups at nutMaster.domain.uk / status and then 'hangs'. A 15 minute delay follows before the polling process returns that the master's upsd process is not reachable. A brief examination of the NUT source code indicates that a system "write"...

Just a hunch about your snmpwalk, what happens if you format like this? snmpwalk -l authpriv -v 3 -u user -a MD5 -x DES -A authpassphrase -X privpassphrase {host address} so snmpwalk -l authpriv -v 3 -u nut -a MD5 -x DES -A NutScan at Password43LongerWord -X NutScan at Password43LongerWord apcups Thank you, David Zomaya Tripp Lite ________________________________ From: Nut-upsuser <nut-upsuser-bounces+david_zomaya=tripplite.com at alioth-lists.debian.net> on behalf of Lee Damon <nomad at ee.washington.edu> Sent: Tuesday, April 28, 2020 3:28 PM To: nut-upsuser Mailing List...

...ted the values that may be changed, but it would not change them. When I try it asks for a username/password. I tried root, nut (the user "built into" nut), and the single user entry in upsd.users. In all cases this happened: % /usr/local/ups/bin/upsrw -s battery.charge.low=25 -u root apcups at localhost Password: Unexpected response from upsd: ERR ACCESS-DENIED This is nut 2.2.2 built from source. Possibly relevant, the password for the upsd.users account is 23 characters long. Too long for the software maybe??? It works ok with upsmon though. Thanks, David Mathog mathog at ca...

...transfer.low: 103 input.transfer.reason: selfTest input.voltage: 120.90 input.voltage.maximum: 122.20 input.voltage.minimum: 120.20 output.current: 0.00 output.frequency: 60.00 output.voltage: 120.90 output.voltage.nominal: 115 ups.delay.shutdown: 20 ups.delay.start: 0 ups.firmware: 70.11.D ups.id: apcups ups.load: 14.00 ups.mfr: APC ups.mfr.date: 07/28/98 ups.model: SMART-UPS 1400 ups.serial: WS9831004667 ups.status: OL ups.temperature: 24.70 ups.test.date: 04/29/2020 ups.test.result: Ok I can use snmpset to halt the UPS. snmpset -v 3 -a MD5 -A NutScan at Password43LongerWord -l authPriv -u nut...

...t: 0 ups.firmware: 70.11.D ups.id<https://urldefense.proofpoint.com/v2/url?u=http-3A__ups.id&d=DwMFaQ&c=f9s1WCuF-N6cmD_YaZ7gBg&r=lhr3k4au5dVQgHY_iS-v_t9g8PHVkn8Px_wyaupZGfQ&m=VdKSS_Vk98WT0ADZ-mQe_3zCfrLacAAuMS7JSj5wn1w&s=Cv5z1Xm7dspkGCX9gosuUR3R9b6cDZLJnumKkJ4s1Ms&e=>: apcups ups.load: 14.00 ups.mfr: APC ups.mfr.date: 07/28/98 ups.model: SMART-UPS 1400 ups.serial: WS9831004667 ups.status: OL ups.temperature: 24.70 ups.test.date: 04/29/2020 ups.test.result: Ok I can use snmpset to halt the UPS. snmpset -v 3 -a MD5 -A NutScan at Password43LongerWord -l authPriv -u nut...

...ps and it is fine. 2. upsrw battery.date works fine for both UPS. and the modified result shows immediately. no need to restart the driver. (I still need to restart the driver to get correct battery.date.maintenance. but I think that's not very important. there's not even that attribute at apcupsd.) 3. test.battery.stop works fine at SRT3000XL. but it is not working at SMT2200RM2U (same experience as the driver author). I think it is not important. BTW, at program "apctest" from apcupsd, the function "test.battery.start" is called "self test", and the physical...

...ps and it is fine. 2. upsrw battery.date works fine for both UPS. and the modified result shows immediately. no need to restart the driver. (I still need to restart the driver to get correct battery.date.maintenance. but I think that's not very important. there's not even that attribute at apcupsd.) 3. test.battery.stop works fine at SRT3000XL. but it is not working at SMT2200RM2U (same experience as the driver author). I think it is not important. BTW, at program "apctest" from apcupsd, the function "test.battery.start" is called "self test", and the physical...

...modbus may be needed for USB support >> (detailed in the earlier PR), but Serial and TCP may already be well served >> by a distro near you! >> >> Hi: >> I got a new APC SRT3000XL and tested the new driver "apc_modbus". >> the ups works fine with nut+apcupsd. the new driver "apc_modbus" has >> result below: >> >> 1. upsrw can write the variable "battery.date". but the new value >> will only show after restarting apc_modbus. and in my case the written >> data will shift one day. eg the command "u...

...modbus may be needed for USB support >> (detailed in the earlier PR), but Serial and TCP may already be well served >> by a distro near you! >> >> Hi: >> I got a new APC SRT3000XL and tested the new driver "apc_modbus". >> the ups works fine with nut+apcupsd. the new driver "apc_modbus" has >> result below: >> >> 1. upsrw can write the variable "battery.date". but the new value >> will only show after restarting apc_modbus. and in my case the written >> data will shift one day. eg the command "u...

...2. upsrw battery.date works fine for both UPS. and the modified result > shows immediately. no need to restart the driver. (I still need to > restart the driver to get correct battery.date.maintenance. but I > think that's not very important. there's not even that attribute at > apcupsd.) > > 3. test.battery.stop works fine at SRT3000XL. but it is not working at > SMT2200RM2U (same experience as the driver author). I think it is not > important. BTW, at program "apctest" from apcupsd, the function > "test.battery.start" is called "self test...

...2. upsrw battery.date works fine for both UPS. and the modified result > shows immediately. no need to restart the driver. (I still need to > restart the driver to get correct battery.date.maintenance. but I > think that's not very important. there's not even that attribute at > apcupsd.) > > 3. test.battery.stop works fine at SRT3000XL. but it is not working at > SMT2200RM2U (same experience as the driver author). I think it is not > important. BTW, at program "apctest" from apcupsd, the function > "test.battery.start" is called "self test...

...e, a custom build of libmodbus may be needed for USB support > (detailed in the earlier PR), but Serial and TCP may already be well served > by a distro near you! > > Hi: > I got a new APC SRT3000XL and tested the new driver "apc_modbus". > the ups works fine with nut+apcupsd. the new driver "apc_modbus" has > result below: > > 1. upsrw can write the variable "battery.date". but the new value > will only show after restarting apc_modbus. and in my case the written > data will shift one day. eg the command "upsrw -s > battery...

...e, a custom build of libmodbus may be needed for USB support > (detailed in the earlier PR), but Serial and TCP may already be well served > by a distro near you! > > Hi: > I got a new APC SRT3000XL and tested the new driver "apc_modbus". > the ups works fine with nut+apcupsd. the new driver "apc_modbus" has > result below: > > 1. upsrw can write the variable "battery.date". but the new value > will only show after restarting apc_modbus. and in my case the written > data will shift one day. eg the command "upsrw -s > battery...