Glad it worked out!
> I have not made ANY changes to hosts.conf in my server.
So was this in the end a wrong assumption on your side, or was some error
in the file shipped by packaging (or even NUT upstream sources)?
Jim
On Wed, Oct 11, 2023 at 5:25 AM S K wrote:
> Can close the thread! Had
Can close the thread! Had a typo in hosts.conf
On Tuesday, October 10, 2023 at 10:07:12 PM EDT, S K via Nut-upsuser
wrote:
sudo tcpdump --interface=eth0 -n host 192.168.0.20 and port 3493tcpdump:
verbose output suppressed, use -v[v]... for full protocol decodelistening on
eth0,
sudo tcpdump --interface=eth0 -n host 192.168.0.20 and port 3493tcpdump:
verbose output suppressed, use -v[v]... for full protocol decodelistening on
eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes21:55:26.538305
IP 192.168.0.29.36942 > 192.168.0.20.3493: Flags [P.], seq
Well... one troubleshooting idea is to use a sniffer (ngrep, tcpdump, etc.)
to see the dialogue between the web server and upsd data server (
192.168.0.20:3493), to check if anything looks fishy there. Maybe some
firewalls, SELinux after an update, etc. tempered up and there is no
network chatter
Hey the NUT sever (http://192.168.0.29/) was working fine and the URL
http://192.168.0.29/cgi-bin/nut/upsstats.cgi did show me all the UPS slaves -
but all of a sudden one particular slave is not showing up.The one that is
not showing up IP is 192.168.0.20 and the following command in NUT
