search for: mythus

...he logic behind the IPv6 code, but the first line indicates a problem binding to the IPv6 localhost address. The "LISTEN 127.0.0.1 3493" line in upsd.conf is sufficient for local control and monitoring, and you can remove "LISTEN ::1 3493". OK, did that restarted services and: mythuser at amethi:/etc/nut$ upscmd -l CyberUPS1 Instant commands supported on UPS [CyberUPS1]: beeper.disable - Disable the UPS beeper beeper.enable - Enable the UPS beeper beeper.mute - Temporarily mute the UPS beeper beeper.off - Obsolete (use beeper.disable or beeper.mute) beeper.on - Obsolete (use b...

...(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?...

...battery.charge.low > * battery.runtime.low > > You can adjust these with the "upsrw" command, but I don't think we have verified whether the settings are stored in non-volatile memory on this particular UPS. > >> I had problem initially starting: >> >> mythuser at amethi:/etc/nut$ sudo upsdrvctl start >> Network UPS Tools - UPS driver controller 2.7.2 >> Network UPS Tools - Generic HID driver 0.38 (2.7.2) >> USB communication driver 0.32 >> Can't claim USB device [0764:0501]: could not detach kernel driver from interface 0: O...

...first line indicates a problem binding to the IPv6 localhost >> address. The "LISTEN 127.0.0.1 3493" line in upsd.conf is sufficient >> for local control and monitoring, and you can remove "LISTEN ::1 3493". > > OK, did that restarted services and: > > mythuser at amethi:/etc/nut$ upscmd -l CyberUPS1 > Instant commands supported on UPS [CyberUPS1]: > > beeper.disable - Disable the UPS beeper > beeper.enable - Enable the UPS beeper > beeper.mute - Temporarily mute the UPS beeper > beeper.off - Obsolete (use beeper.disable or beeper.mute...

On 12/10/2016 07:42 AM, Charles Lepple wrote: >> On Dec 9, 2016, at 10:40 PM, Jack McGee wrote: >> >> ? nut-server.service - LSB: Network UPS Tools initscript >> Loaded: loaded (/etc/init.d/nut-server; bad; vendor preset: enabled) >> Active: active (running) since Fri 2016-12-09 13:48:34 CST; 7h ago >> Docs: man:systemd-sysv-generator(8) >>

...nal: Broadcast message from nut at amethi (somewhere) (Fri Dec 2 12:33:03 2016): UPS CyberUPS1 at localhost is unavailable I am still unclear on where to set when nut shutdowns system. I see nut-client and nut server are automatically starting from SystemD. I had problem initially starting: * *mythuser at amethi:/etc/nut$ sudo upsdrvctl start Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - Generic HID driver 0.38 (2.7.2) USB communication driver 0.32 Can't claim USB device [0764:0501]: could not detach kernel driver from interface 0: Operation not permitted Driver faile...

...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:...

...; > I had a similar issue I think when Ubuntu moved to SystemD with Mythtv > not waiting to start until network was up and then erroring. I will > see if I can recall what I did to fix that and apply it to NUT and see > if that fixes it. Restart of nut-server after boot, fixes it: mythuser at amethi:~$ sudo systemctl status nut-server.service [sudo] password for mythuser: ? nut-server.service - LSB: Network UPS Tools initscript Loaded: loaded (/etc/init.d/nut-server; bad; vendor preset: enabled) Active: active (running) since Sat 2016-12-10 08:35:17 CST; 17s ago Docs:...

On 12/03/2016 09:36 AM, Charles Lepple wrote: >> On Dec 3, 2016, at 9:44 AM, Jack McGee <jack at greendesk.net> wrote: >> >> But doesn't this still indicate an error: >> >> mythuser at amethi:/etc/nut$ upscmd -l CyberPower1 >> Error: Connection failure: Connection refused > Correct - "upsc", "upscmd" and "upsrw" need to connect to "upsd", and "upsd" talks to the driver. Looks like you got the driver working before, s...

...hing similar. ps auxww|grep [/]nut nut 19724 0.0 0.0 27932 516 ? Ss 08:41 0:00 /lib/nut/usbhid-ups -a CyberUPS1 root 20308 0.0 0.0 37844 2632 ? Ss 08:41 0:00 /lib/nut/upsmon nut 20309 0.0 0.0 45632 4884 ? S 08:41 0:00 /lib/nut/upsmon mythuser at amethi:/etc/nut$ grep upsd /var/log/syslog Dec 3 08:38:16 amethi nut-server[18216]: No upsd found running; none killed. Dec 3 08:38:16 amethi upsd[18234]: not listening on ::1 port 3493 Dec 3 08:38:16 amethi upsd[18234]: listening on 127.0.0.1 port 3493 Dec 3 08:38:16 amethi upsd[18234]: n...

..._Systems/CP1500PFCLCD.html * battery.charge.low * battery.runtime.low You can adjust these with the "upsrw" command, but I don't think we have verified whether the settings are stored in non-volatile memory on this particular UPS. > I had problem initially starting: > > mythuser at amethi:/etc/nut$ sudo upsdrvctl start > Network UPS Tools - UPS driver controller 2.7.2 > Network UPS Tools - Generic HID driver 0.38 (2.7.2) > USB communication driver 0.32 > Can't claim USB device [0764:0501]: could not detach kernel driver from interface 0: Operation not...

> On Dec 3, 2016, at 9:44 AM, Jack McGee <jack at greendesk.net> wrote: > > But doesn't this still indicate an error: > > mythuser at amethi:/etc/nut$ upscmd -l CyberPower1 > Error: Connection failure: Connection refused Correct - "upsc", "upscmd" and "upsrw" need to connect to "upsd", and "upsd" talks to the driver. Looks like you got the driver working before, so that c...

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 Faile...