Shade Alabsa
2014-Mar-25 23:39 UTC
[Nut-upsuser] Configuring APC Smart-UPS 2200 on two computers
I have a dual controller box similar to this - http://www.supermicro.com/products/system/3U/6037/SSG-6037B-DE2R16L.cfm On one controller I have Nut configured and working as a server. On the other side I'm trying to configure Nut as a slave to query the other side and for some reason it's not working. I'm getting this error: "Error: Connection failure: Connection refused" I'm running with the following set up OS - CentOS 6.4 Nut - 2.6.5-2el6.x86_64 http://dl.fedoraproject.org/pub/epel/6/x86_64/repoview/nut.html Nut client - nut-client-2.6.5-2.el6.x86_64 http://dl.fedoraproject.org/pub/epel/6/x86_64/repoview/nut-client.html UPS - APC Smart-ups 2200 I installed both nut packages via RPM's taken from the links above. I have a pastebin link below with all the configurations. I only added in the lines that weren't commented out. Also if there is only a config file listed for 192.168.123.1 but not one listed for 192.168.123.3 it is because 192.168.123.3 has the exact config file. I also do not have iptables or selinux running. I also have this same exact set up running on Fedora 11 and nut package 2-4.1-12.fc11.x86_64 so I'm not sure what the difference is. 192.168.123.1 is the master and is the controller directly connected to the UPS 192.168.123.3 is the slave and is the controller that I want to poll 192.168.123.1 for information. http://pastebin.com/dGgKEBDH I feel like it's a stupid configuration issue that I've missed so hopefully somebody can point it out for me. Thanks! Shade -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140325/6d3c4f2d/attachment.html>
Charles Lepple
2014-Mar-26 00:30 UTC
[Nut-upsuser] Configuring APC Smart-UPS 2200 on two computers
On Mar 25, 2014, at 7:39 PM, Shade Alabsa wrote:> 192.168.123.1 is the master and is the controller directly connected to the UPS > 192.168.123.3 is the slave and is the controller that I want to poll 192.168.123.1 for information....> ############################################################################## > upsd.conf on 192.168.123.1 > ############################################################################## > > LISTEN 127.0.0.1 3493You probably want to add "LISTEN 192.168.123.1 3493" after that (or replace with "LISTEN 0.0.0.0 3493" to listen on all interfaces). Especially in the latter case, I would recommend firewall rules as an additional line of defense. -- Charles Lepple clepple at gmail