search for: service3493

...and it listens on this port for the shut-down command. 2) Is this correct? On the slave if I run the following: steve at MyDesktop:~$ nmap -p 3493 192.168.0.6 Starting Nmap 6.40 ( http://nmap.org ) at 2014-11-09 15:42 ESTNmap scan report for 192.168.0.6Host is up (0.00013s latency).PORT STATE SERVICE3493/tcp closed nut Nmap done: 1 IP address (1 host up) scanned in 11.06 seconds Which tells me this port is configured for nut but it is closed? I have rebooting and starting and stopping the service using: sudo service ups-monitor stop sudo service ups-monitor startBut it remains closed. 3) Assuming...

...aster (via upsd) listens on port 3493, and the slave connects to that port. On the slave if I run the following: steve at MyDesktop:~$ nmap -p 3493 192.168.0.6 Starting Nmap 6.40 ( http://nmap.org ) at 2014-11-09 15:42 ESTNmap scan report for 192.168.0.6Host is up (0.00013s latency).PORT STATE SERVICE3493/tcp closed nut Nmap done: 1 IP address (1 host up) scanned in 11.06 seconds Which tells me this port is configured for nut but it is closed? As mentioned above, that is expected. But if you run it against the master (192.168.0.7, if I understand correctly) from the slave, you should see that it is...

On Nov 8, 2014, at 1:52 PM, Steve Read <sd_read at hotmail.com> wrote: > I have made changes but it is still the same. That is when the server gets the lowbat/noAC signal it does shut down as expected but the slave does not. > > Perhaps it makes sense for me to list the present settings: > > On the Master: > > nut.conf > MODE=netserver > >

On Nov 9, 2014, at 3:48 PM, Steve Read <sd_read at hotmail.com> wrote: > I would like to verify my understanding keeping in mind I have a one master and one slave computer. > > When the master gets the low batt/noAC signal it initiates a broadcast packet(s) on port 3493. > > 1) Is this correct? No, the slave computer's upsmon process connects to the master (via TCP, so