> 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
>
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
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 wrote:
>On Fri, 25 Nov 2016, Jonah Naylor wrote:
>
>>
Hi,
When on the same LAN it just worked without anything in the hosts.allow
file. It's difficult for me to now put the slave back on the same lan as
the master due to the way the production servers are being used... Causing
downtime etc...
I do have another spare server though which I could put
On Fri, 25 Nov 2016, Jonah Naylor wrote:
I'm still getting "Connection refused on the client cgi screen as well
as in the shell it gives me UPS upsname@ipaddresshere is unavailable...
You reported that access works correctly from elsewhere on the master
subnetwork. Does access from the
Hi thanks Roger,
I've amended my hosts.allow file to your suggested one - thanks for that.
I'm still getting "Connection refused on the client cgi screen as well as
in the shell it gives me UPS upsname@ipaddresshere is unavailable...
Any ideas what I can try next to debug why it's not working.
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@localhost\
-s '%s@%h accepted access to %d from %c'\
sysadmin@somedomain) &
Hi thanks Roger. Well I'm just using Ubuntu Server 16.04 LTS
I only ran that command as a few guides say that's how to establish if a
daemon is compiled with tcp wrappers:
https://www.cyberciti.biz/faq/tcp-wrappers-hosts-allow-deny-tutorial/
I haven't really used TCP wrappers before so I'm not
On Fri, 25 Nov 2016, Jonah Naylor wrote:
I don't think nut is built with TCP wrappers support, although the
package is listed as depending on libwrap...
Why would you have such a dependency if nut didn't use TCP Wrappers?
I ran this command: ldd /sbin/upsd | grep libwrap.so and it has
Hi thanks for helping.
I don't think nut is built with TCP wrappers support, although the package
is listed as depending on libwrap...
I ran this command: ldd /sbin/upsd | grep libwrap.so
and it has returned no output.
Does this mean I have to compile from source or is there a way to add the
On Thu, 24 Nov 2016, Jonah Naylor wrote:
I installed Nut via apt-get, not from source (which I'd rather stick
with if possible just for ease of security updates etc) - so I'm not too
sure if TCP wrappers are there or available...
This could be the problem, am I still able to add the wrappers
On Nov 24, 2016, at 10:58 AM, Jonah Naylor wrote:
>
> Is there something I should be doing other than adding "allowfrom =
> ipaddressofslave" to the upsd.users file on the master?
Which version of NUT are you using?
Reference for the current version:
Hi thanks for the reply.
The servers can ping each other...
The router log doesn't show anything and I am the admin for the servers.
The machines firewalls allow each other's ips etc.
Part of the issue is possibly that I just don't know if I've set up NUT
correctly for this arrangement? Like I
On Thu, 24 Nov 2016, Jonah Naylor wrote:
Hi can anyone please help.
Although I have two servers in the same cabinet/room and sharing the same UPS -
they're on different networks.
I've tried everything I can find online, but whatever I do I can't get the
slave nut client to connect to the
Hi can anyone please help.
Although I have two servers in the same cabinet/room and sharing the same
UPS - they're on different networks.
I've tried everything I can find online, but whatever I do I can't get the
slave nut client to connect to the master.
When testing then on the same LAN, they
15 matches
Mail list logo