On 12/10/2016 08:37 AM, Jack McGee wrote:
On 12/10/2016 08:10 AM, Jack McGee wrote:
e, the 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
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
> 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:
On 12/08/2016 09:38 PM, Charles Lepple wrote:
On Dec 8, 2016, at 7:56 PM, Jack McGee wrote:
I rebooted machine and nut cannot connect to the UPS.
Any messages from the kernel regarding USB HID drivers? (Check dmesg and/or
journalctl.)
dmesg:
[1.658554] usb 3-5: new
On Dec 8, 2016, at 7:56 PM, Jack McGee wrote:
>
> I rebooted machine and nut cannot connect to the UPS.
Any messages from the kernel regarding USB HID drivers? (Check dmesg and/or
journalctl.)
___
Nut-upsuser mailing list
I rebooted machine and nut cannot connect to the UPS.
mythuser@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.00debug level is '2'
0.000499upsdrv_initups...
0.005722
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
> On Dec 3, 2016, at 12:31 PM, Jack McGee 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,
Looks like you did - "OL" is shorthand for "On Line"
- Tim
On December 3, 2016 11:31:46 AM CST, Jack McGee wrote:
>On 12/03/2016 10:55 AM, Jack McGee wrote:
>> On 12/03/2016 10:35 AM, Charles Lepple wrote:
>>> On Dec 3, 2016, at 11:16 AM, Jack McGee
On 12/03/2016 10:55 AM, Jack McGee wrote:
On 12/03/2016 10:35 AM, Charles Lepple wrote:
On Dec 3, 2016, at 11:16 AM, Jack McGee wrote:
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
On 12/03/2016 10:35 AM, Charles Lepple wrote:
On Dec 3, 2016, at 11:16 AM, Jack McGee wrote:
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]: no
On Dec 3, 2016, at 11:16 AM, Jack McGee wrote:
>
> 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]: no listening interface available
I can't say I
> On Dec 3, 2016, at 11:01 AM, Jack McGee wrote:
>
> I did restart those services, no change.
>
$ ps auxww|grep [/]nut
root 13074 0.0 0.0 37844 2628 ?Ss 08:42 0:00 /lib/nut/upsmon
nut 13076 0.0 0.0 45632 5148 ?S08:42 0:00
On 12/03/2016 09:36 AM, Charles Lepple wrote:
On Dec 3, 2016, at 9:44 AM, Jack McGee wrote:
But doesn't this still indicate an error:
mythuser@amethi:/etc/nut$ upscmd -l CyberPower1
Error: Connection failure: Connection refused
Correct - "upsc", "upscmd" and "upsrw" need
> On Dec 3, 2016, at 9:44 AM, Jack McGee wrote:
>
> But doesn't this still indicate an error:
>
> mythuser@amethi:/etc/nut$ upscmd -l CyberPower1
> Error: Connection failure: Connection refused
Correct - "upsc", "upscmd" and "upsrw" need to connect to "upsd", and "upsd"
On 12/03/2016 08:44 AM, Jack McGee wrote:
On 12/03/2016 08:03 AM, Charles Lepple wrote:
On Dec 2, 2016, at 10:23 PM, Jack McGee wrote:
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
On 12/03/2016 08:03 AM, Charles Lepple wrote:
On Dec 2, 2016, at 10:23 PM, Jack McGee wrote:
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@amethi
On Dec 2, 2016, at 10:23 PM, Jack McGee wrote:
>
> 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@amethi (somewhere) (Fri Dec 2 12:33:03 2016):
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@amethi (somewhere) (Fri Dec 2 12:33:03 2016):
UPS CyberUPS1@localhost is unavailable
I am still unclear on where to set when
19 matches
Mail list logo