Try ALL:ALL in /etc/hosts.allow temporarily. If that still doesn't work, it's likely something else. If it does, only then screw with creating narrow rules . . . - Tim On November 25, 2016 6:37:02 AM CST, Roger Price <roger at rogerprice.org> wrote:>On Fri, 25 Nov 2016, Jonah Naylor wrote: > >> upsd : ipaddressofclientgoeshere > >If it were me I would write > > upsd : ipaddressofclient :\ > spawn (/bin/mail -r hosts.allow at localhost\ > -s '%s@%h accepted access to %d from %c'\ > sysadmin at somedomain) & : ALLOW > > upsd : ALL :\ > spawn (/bin/mail -r hosts.allow at localhost\ > -s '%s@%h refused access to %d from %c'\ > sysadmin at somedomain) & : DENY > >so I get a trace of what happens, at least during testing. > >> ups : monuser at 127.0.0.1/32 monuser at masterstaticIP >monuser at slavestaticIP > >I'm not sure what you are trying to do here. In any case, the >daemon_list should specify upsd, not ups. See man 5 hosts_access. > >Rogr > >_______________________________________________ >Nut-upsuser mailing list >Nut-upsuser at lists.alioth.debian.org >http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser-- Sent from my Android device with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20161125/e32b6ba8/attachment.html>
Hi thanks for all the help with this. I may have now resolved this and got things working... All I've ended up doing is making the slave the master and the master the slave! They now connect! What is strange though is that one machine is Ubuntu and one is Debian - with Debian as the Master things work no problem, without needing anything in hosts.allow at all. And Ubuntu is quite happy as the slave and shows the connection etc. The other way round as you know from my previous posts and Debian as the slave just won't connect to the Ubuntu box... So this may just be an Ubuntu issue with 14.04LTS. But I'm happy as it doesn't matter to me which is master or slave, so this will be fine without us having to get to the bottom of the problem. The only other thing I wanted to check with everyone is just that all the slaves will powerdown when the battery is low by default. Do I need to set up any settings, or if there are no lines in a config file will this just happen and the defaults are fr this to happen anyway? Thanks once again for all the help and suggestions. Much appreciated. On 25 November 2016 at 16:32, Tim Dawson <tadawson at tpcsvc.com> wrote:> Try ALL:ALL in /etc/hosts.allow temporarily. If that still doesn't work, > it's likely something else. If it does, only then screw with creating > narrow rules . . . > > - Tim > > On November 25, 2016 6:37:02 AM CST, Roger Price <roger at rogerprice.org> > wrote: >> >> On Fri, 25 Nov 2016, Jonah Naylor wrote: >> >> upsd : ipaddressofclientgoeshere >>> >> >> If it were me I would write >> >> upsd : ipaddressofclient :\ >> spawn (/bin/mail -r hosts.allow at localhost\ >> -s '%s@%h accepted access to %d from %c'\ >> sysadmin at somedomain) & : ALLOW >> >> upsd : ALL :\ >> spawn (/bin/mail -r hosts.allow at localhost\ >> -s '%s@%h refused access to %d from %c'\ >> sysadmin at somedomain) & : DENY >> >> so I get a trace of what happens, at least during testing. >> >> ups : monuser at 127.0.0.1/32 monuser at masterstaticIP >>> monuser at slavestaticIP >>> >> >> I'm not sure what you are trying to do here. In any case, the >> daemon_list should specify upsd, not ups. See man 5 hosts_access. >> >> Rogr >> >> ------------------------------ >> >> Nut-upsuser mailing list >> Nut-upsuser at lists.alioth.debian.org >> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser >> >> > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20161126/349077d0/attachment.html>
Charles Lepple
2016-Nov-27 16:17 UTC
[Nut-upsuser] Can't get NUT slave to connect to master
> On Nov 26, 2016, at 1:48 PM, Jonah Naylor wrote: > > The only other thing I wanted to check with everyone is just that all the slaves will powerdown when the battery is low by default. Do I need to set up any settings, or if there are no lines in a config file will this just happen and the defaults are fr this to happen anyway?I can't keep track of the default configuration files for all of the different versions of Linux, but I can recommend reading this section of the NUT user manual: http://networkupstools.org/docs/user-manual.chunked/ar01s06.html#UPS_shutdown -- - Charles Lepple https://ghz.cc/charles/