search for: cyberups1

...ing) since Fri 2016-12-09 13:48:34 CST; 7h ago >> Docs: man:systemd-sysv-generator(8) >> Process: 1886 ExecStart=/etc/init.d/nut-server start (code=exited, status=0/SUCCESS) >> CGroup: /system.slice/nut-server.service >> ??2082 /lib/nut/usbhid-ups -a CyberUPS1 >> >> Dec 09 13:48:33 amethi systemd[1]: Starting LSB: Network UPS Tools initscript... >> Dec 09 13:48:33 amethi nut-server[1886]: * Starting NUT - power devices information server and drivers >> Dec 09 13:48:34 amethi usbhid-ups[2082]: Startup successful >> Dec 09 13...

...path of least resistance would be to listen on 0.0.0.0 and use > a firewall rule to limit connections to that subnet. > > > sorry, after reboot I started seeing this error in terminal: > > Broadcast message from nut at amethi (somewhere) (Sat Dec 10 08:05:01 2016): > > UPS CyberUPS1 at localhost is unavailable > > > 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...

...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 beeper.enable) load.off - Turn off the load...

...ccessing 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? &...

...na [ 1.792323] usbcore: registered new interface driver usbhid [ 1.792324] usbhid: USB HID core driver [ 1.796791] hid-generic 0003:0764:0501.0001: hiddev0,hidraw0: USB HID v1.10 Device [CPS CP1500PFCLCD] on usb-0000:00:14.0-5/input0 journalctl: Dec 09 21:28:49 amethi upsmon[2359]: UPS [CyberUPS1 at localhost]: connect failed: Connection failure: Connection refused Now, I found out that if I do service nut-server stop service nut-server start It works. But this is how it is before those commands: ? nut-server.service - LSB: Network UPS Tools initscript Loaded: loaded (/etc/init...

...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 beeper.en...

...ou still get "Connection refused", it might be a firewall issue. If not, check syslog for any messages from upsd saying that it couldn't bind to a port, or something 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. D...

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

...Synaptic, >> Network UPS Tools upsd 2.7.2 >> >> I am getting these messages in the terminal: >> 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. > The basic configuration is that upsmon will shut down the system (running SHUTDOWNCMD in /etc/nut/upsmon.conf) when the UPS signals that its battery is low. > > Your UPS probably i...

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

This is new install on Ubuntu 16.04, using packages from Synaptic, *Network UPS Tools upsd 2.7.2 I am getting these messages in the terminal: 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....

...ng packages from Synaptic, > Network UPS Tools upsd 2.7.2 > > I am getting these messages in the terminal: > 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. The basic configuration is that upsmon will shut down the system (running SHUTDOWNCMD in /etc/nut/upsmon.conf) when the UPS signals that its battery is low. Your UPS probably indicates this curre...

...Active: active (running) since Fri 2016-12-09 13:48:34 CST; 7h ago > Docs: man:systemd-sysv-generator(8) > Process: 1886 ExecStart=/etc/init.d/nut-server start (code=exited, status=0/SUCCESS) > CGroup: /system.slice/nut-server.service > ??2082 /lib/nut/usbhid-ups -a CyberUPS1 > > Dec 09 13:48:33 amethi systemd[1]: Starting LSB: Network UPS Tools initscript... > Dec 09 13:48:33 amethi nut-server[1886]: * Starting NUT - power devices information server and drivers > Dec 09 13:48:34 amethi usbhid-ups[2082]: Startup successful > Dec 09 13:48:34 amethi upsd[...

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