Hi,
On 13.01.2014 15:10, torsten.amsh...@gad.de wrote:
Hi,
we just installed icinga2. It runs smooth with more than 3k hosts and
24k services to check.
Which hardware/specs are you using?
Now I tried to set up a second icinga2 server to build a cluster.
Please share your configuration with the reader.
Some issues later (most of them just because of missing docs)
Care to elaborate? Please open tickets if you think that some doc bits
are missing.
I got stuck with an error about the address family.
Can you post the exact error message please?
I found this line in components/cluster/clusterlistener.cpp:
(AddListener-Method)
server->Bind(service, AF_INET6);
Why is icinga2 forcing IPv6?
It does not force IPv6. IPv4 connects are still handled and mapped
through the AF_INET6 address family. For example If I'm using
192.168.1.101 and 192.168.1.102 as cluster nodes to bind my interface
on, they still speak IPv4 with each other.
It would be interesting which 'bind_host' you are using. If it's a fqdn,
does it resolve to an ipv6 address? Any cluster messages on the logs
where the peer is connecting to?
We have disabled IPv6 on all of our Servers.
Any specific reason for that? And how did you disable it? I'd guess that
the interface is still up for the kernel to bind a port via ipv6.
What does a local tcpdump tell for the cluster bind_{host,port} address?
I'm using 0.0.6 installed on SLES 11 with RPMs.
Either way, some configs & logs would probably help identify the problem
at first sight.
Regards,
Michael
--
DI (FH) Michael Friedrich
mail: michael.friedr...@gmail.com
twitter: https://twitter.com/dnsmichi
jabber: dnsmi...@jabber.ccc.de
irc: irc.freenode.net/icinga dnsmichi
icinga open source monitoring
position: lead core developer
url: https://www.icinga.org
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
