> On Dec 3, 2016, at 12:31 PM, Jack McGee <jack at greendesk.net> wrote: >> so this is progress. Thanks! Anything else to check to know it is working as it should?http://networkupstools.org/docs/user-manual.chunked/ar01s06.html#Testing_shutdowns The "FSD" test is more for the NUT logic, which isn't too complicated with only one UPS and one server. If you want to pull power to the UPS, you probably want to interrupt just the hot line, with something like a circuit breaker or power strip switch. If you don't mind sending the full output of "upsc" and "upsrw", we can update the DDL page (it only has "upsc" output for an older version of NUT). This UPS provides some sort of serial number (doesn't match the label) in the device.model (and mirrored at ups.model) variables, so if you want to mask off a few digits from the end, that's fine. (CyberPower seems to have swapped the model name and serial number strings in the USB descriptor.)>> >> My next step will be to point NUT client on another machine to this one. They are both plugged into this UPS.You will need to adjust upsd.conf for this. If you only have one network interface, you can change "LISTEN 127.0.0.1 3493" to "LISTEN 0.0.0.0 3493". Otherwise, you can use the IP address of the *server* to bind to just that network interface (to help prevent outside systems from accessing NUT). More complicated access control situations (only allow a few hosts from a subnet, for instance) can be handled with TCP-wrappers (/etc/hosts.allow and /etc/hosts.deny) or with kernel firewall rules.> > Maybe still a problem: > > mythuser at amethi:/etc/nut$ sudo upsc CyberUPS1 at localhost ups.status > [sudo] password for mythuser: > Init SSL without certificate database > OL > > But if I read this > https://askubuntu.com/questions/468632/nut-ups-and-ssl-certificates#565740 > correctly, it is just a warning? > But shouldn't I see a status?"Init SSL without certificate database" is a warning. The status is "OL" on the next line. (That was the reason for the "2>/dev/null" in an earlier post.) If you just run "upsc CyberUPS1", then it prints the variable names and values, but if you add a variable name like "ups.status" to the command line, it doesn't print the name as well. (The latter option is to avoid having to carve up the results with awk, as was done in the askubuntu.com post.)
On 12/03/2016 11:46 AM, Charles Lepple wrote:> > If you don't mind sending the full output of "upsc" and "upsrw", we can update the DDL page (it only has "upsc" output for an older version of NUT). This UPS provides some sort of serial number (doesn't match the label) in the device.model (and mirrored at ups.model) variables, so if you want to mask off a few digits from the end, that's fine. (CyberPower seems to have swapped the model name and serial number strings in the USB descriptor.)mythuser at amethi:/etc/nut$ upsc CyberUPS1 at 192.168.0.105 Init SSL without certificate database battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 3840 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 24.0 battery.voltage.nominal: 24 device.mfr: CPS device.model: CP1500PFCLCD device.serial: 000000000000 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.synchronous: no driver.parameter.vendorid: 0764 driver.version: 2.7.4.1 driver.version.data: CyberPower HID 0.4 driver.version.internal: 0.42 driver.version.usb: libusb-1.0 (API: 0x1000104) input.transfer.high: 139 input.transfer.low: 88 input.voltage: 126.0 input.voltage.nominal: 120 output.voltage: 142.0 ups.beeper.status: enabled ups.delay.shutdown: 20 ups.delay.start: 30 ups.load: 13 ups.mfr: CPS ups.model: CP1500PFCLCD ups.productid: 0501 ups.realpower.nominal: 900 ups.serial: 000000000000 ups.status: OL ups.test.result: No test initiated ups.timer.shutdown: -60 ups.timer.start: -60 ups.vendorid: 0764 mythuser at amethi:/etc/nut$ upsrw CyberUPS1 at 192.168.0.105 [battery.charge.low] Remaining battery level when UPS switches to LB (percent) Type: STRING Maximum length: 10 Value: 10 [battery.runtime.low] Remaining battery runtime when UPS switches to LB (seconds) Type: STRING Maximum length: 10 Value: 300 [input.transfer.high] High voltage transfer point (V) Type: STRING Maximum length: 10 Value: 139 [input.transfer.low] Low voltage transfer point (V) Type: STRING Maximum length: 10 Value: 88 [ups.delay.shutdown] Interval to wait after shutdown with delay command (seconds) Type: STRING Maximum length: 10 Value: 20 [ups.delay.start] Interval to wait before (re)starting the load (seconds) Type: STRING Maximum length: 10 Value: 30
I rebooted machine and nut cannot connect to the UPS. mythuser at amethi:/etc$ sudo /lib/nut/usbhid-ups -DD -a CyberUPS1 Network UPS Tools - Generic HID driver 0.42 (2.7.4.1) USB communication driver (libusb 1.0) 0.02 0.000000 debug level is '2' 0.000499 upsdrv_initups... 0.005722 Checking device (8087/8000) 0.005753 Failed to open device, skipping. (Access denied (insufficient permissions)) 0.005764 Checking device (1D6B/0002) 0.005775 Failed to open device, skipping. (Access denied (insufficient permissions)) 0.005781 Checking device (8087/8008) 0.005790 Failed to open device, skipping. (Access denied (insufficient permissions)) 0.005798 Checking device (1D6B/0002) 0.005807 Failed to open device, skipping. (Access denied (insufficient permissions)) 0.005811 Checking device (1D6B/0003) 0.005821 Failed to open device, skipping. (Access denied (insufficient permissions)) 0.005827 Checking device (10C4/EA60) 0.005834 Failed to open device, skipping. (Access denied (insufficient permissions)) 0.005841 Checking device (0764/0501) 0.006592 - VendorID: 0764 0.006603 - ProductID: 0501 0.006606 - Manufacturer: CPS 0.006608 - Product: CP1500PFCLCD 0.006611 - Serial Number: 000000000000 0.006614 - Bus: 003 0.006616 - Device release number: 0001 0.006620 Trying to match device 0.006644 Device matches 0.006648 Reading first configuration descriptor 0.006655 auto detached kernel driver from USB device 0.006663 failed to claim USB device: Resource busy 0.006668 Kernel driver already detached 0.006673 failed to claim USB device: Resource busy 0.006677 Kernel driver already detached 0.006683 failed to claim USB device: Resource busy 0.006688 Kernel driver already detached 0.006692 failed to claim USB device: Resource busy 0.006697 Kernel driver already detached 0.006702 Can't claim USB device [0764:0501]: Entity not found