I had firewalld enabled. I turned that off. Port 9300 is no longer a problem. Thanks!
On Fri, Apr 28, 2017 at 3:55 PM, Luke Meyer <[email protected]> wrote: > The Elastic Search pods contact port 9300 on other pods, that is, on the > internal pod IP. There should be no need to do anything on the hosts to > enable this. If ES is failing to contact other ES nodes then either there > is a networking problem or the other nodes aren't listening (yet) on the > port. > > On Thu, Apr 27, 2017 at 10:53 PM, Dean Peterson <[email protected]> > wrote: > >> I am trying to start aggregate logging. The elastic search cluster >> requires port 9300 to be open. I am getting Connection refused errors and I >> need to open that port. How do I open port 9300 without messing up the >> existing rules for Openshift. Do I make changes in firewalld or iptables >> directly? I notice iptables is masked. In previous versions it seems like >> firewalld wasn't being used. Now it is. I am not sure what the right way to >> make port 9300 available to aggregate logging is. >> >> _______________________________________________ >> users mailing list >> [email protected] >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> >> >
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
