Nut upsuser - Feb 2022 - NUT Client Not Working, Server OK

Roger,

I ran both:

*upsc 1LRES850 at 196.168.1.235 <1LRES850 at 196.168.1.235>*
*upsc 2UCES750 at 192.168.1.236 <2UCES750 at 192.168.1.236>*

from the server's terminal - which is 192.168.1.235.  In both cases the
outcome was:

*Error: Connection failure: No route to host.*

Which is interesting as I can successfully ping both from .235.

If it makes any difference, when I run* sudo systemctl status nut-server*
from 235 [the server] it will show:
*upsd [506]: Connected to UPS [1LRES850] usbhid-ups-1*

Bill
-- 
Fredericksburg, VA
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20220213/e152de94/attachment.htm>

On Sun, 13 Feb 2022, William Cole via Nut-upsuser wrote:
> I ran both:
> 
> upsc 1LRES850 at 196.168.1.235
> upsc 2UCES750 at 192.168.1.236
> 
> from the server's terminal - which is 192.168.1.235.? In both cases the
outcome was:
> 
> Error: Connection failure: No route to host.
What does "upsc 1LRES850" do?  What is the output from "ifconfig
-a" for the
local network interface?
> Which is interesting as I can successfully ping both from .235.
ping uses the ICMP protocol's mandatory ECHO_REQUEST datagram to elicit an
ICMP
ECHO_RESPONSE from a host.  This is not the same TCP/IP protocol used by 
commands such as upsc.
> If it makes any difference, when I run sudo systemctl status nut-server
from 235 [the server] it will show:
> upsd [506]: Connected to UPS [1LRES850] usbhid-ups-1
Surprising, I would expect to see

    upsd [506]: Connected to UPS [1LRES850] usbhid-ups-1LRES850

What happens on .235 if you type "upsc 1" ?

Roger