search for: leppleclepple

Displaying 5 results from an estimated 5 matches for "leppleclepple".

2014 Nov 10
0
Master Works, Slave Does Not
...PS sdrups at 192.168.0.7 established Once that connection is up, you can run "sudo upsmon -c fsd" on the master to simulate a power failure (to avoid running down the batteries too much). Note that this will shut down the master system, too. Details are in the upsmon man page. -- Charles Leppleclepple at gmail -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20141110/34098cbe/attachment.html>
2014 Nov 10
0
Master Works, Slave Does Not
...d be open how do I fix this? You mentioned that you have a "LISTEN 0.0.0.0" line in upsd.conf on the master - has upsd been restarted since that change was made? Other than that, you should be set. Do things match the "netstat" output I mentioned in a previous email? -- Charles Leppleclepple at gmail -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20141109/ac8d997f/attachment-0001.html>
2014 Nov 08
1
Master Works, Slave Does Not
On Nov 8, 2014, at 10:34 AM, Steve Read <sd_read at hotmail.com> wrote: > Thank you Charles, I am hoping fiddle with that sometime today or tomorrow. > > But I have another question, when you ask me to modify various files I am confused as to weather you mean on the server, client or both? > > So in your statement: > > "Instead, you want to listen on the
2014 Nov 09
2
Master Works, Slave Does Not
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
2014 Nov 10
3
Master Works, Slave Does Not
On Nov 9, 2014, at 7:56 PM, Steve Read <sd_read at hotmail.com> wrote: > Boy, I guess I got that one wrong. > > When I run nmap on the master it does say that port 3493 is open which is expected. > > So then what you are telling me means the ports are open. > In other words I don't have a firewall issue. I know this sounds incredibly pedantic, but if you run nmap