Cluster Status is Red
Re: Cluster Status is Red
Are you able to get a profile from the machines?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: Cluster Status is Red
Sorry here are the profiles from each server.
https://gohcl-my.sharepoint.com/:f:/p/s ... g?e=qRAXsl
https://gohcl-my.sharepoint.com/:f:/p/s ... g?e=qRAXsl
Re: Cluster Status is Red
Things look better in that the status is green now but it's showing odd output for
It's showing the IP address for both cl-p-nagioslog01 and cl-p-nagioslog02. If you try to ping these addresses from the NLS machines' command line, do you get this IP? Has the /usr/local/nagioslogserver/elasticsearch/config/elasticsearch.yml been modified outside the default settings?
Code: Select all
curl 'localhost:9200/_cat/nodes?v'As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: Cluster Status is Red
Those ip address are the Nagios Log servers. I have not touch any files other then what was asked of me in here.
setup@cl-p-nagioslog01:~$ ping cl-p-nagioslog01
PING cl-p-nagioslog01.hcl.internal (127.0.1.1) 56(84) bytes of data.
64 bytes from cl-p-nagioslog01.hcl.internal (127.0.1.1): icmp_seq=1 ttl=64 time=0.013 ms
64 bytes from cl-p-nagioslog01.hcl.internal (127.0.1.1): icmp_seq=2 ttl=64 time=0.030 ms
^C
--- cl-p-nagioslog01.hcl.internal ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1030ms
rtt min/avg/max/mdev = 0.013/0.021/0.030/0.009 ms
setup@cl-p-nagioslog01:~$ ping cl-p-nagioslog02
PING cl-p-nagioslog02.hcl.internal (10.10.10.23) 56(84) bytes of data.
64 bytes from cl-p-nagioslog02.hcl.internal (10.10.10.23): icmp_seq=1 ttl=64 time=0.261 ms
64 bytes from cl-p-nagioslog02.hcl.internal (10.10.10.23): icmp_seq=2 ttl=64 time=0.365 ms
setup@cl-p-nagioslog01:~$ ping cl-p-nagioslog01
PING cl-p-nagioslog01.hcl.internal (127.0.1.1) 56(84) bytes of data.
64 bytes from cl-p-nagioslog01.hcl.internal (127.0.1.1): icmp_seq=1 ttl=64 time=0.013 ms
64 bytes from cl-p-nagioslog01.hcl.internal (127.0.1.1): icmp_seq=2 ttl=64 time=0.030 ms
^C
--- cl-p-nagioslog01.hcl.internal ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1030ms
rtt min/avg/max/mdev = 0.013/0.021/0.030/0.009 ms
setup@cl-p-nagioslog01:~$ ping cl-p-nagioslog02
PING cl-p-nagioslog02.hcl.internal (10.10.10.23) 56(84) bytes of data.
64 bytes from cl-p-nagioslog02.hcl.internal (10.10.10.23): icmp_seq=1 ttl=64 time=0.261 ms
64 bytes from cl-p-nagioslog02.hcl.internal (10.10.10.23): icmp_seq=2 ttl=64 time=0.365 ms
Re: Cluster Status is Red
Are these the values in /usr/local/nagioslogserver/var/cluster_host?
cluster_host on 10.10.10.21 should contain:
and cluster_host on 10.10.10.23 should contain:
cluster_host on 10.10.10.21 should contain:
Code: Select all
localhost
10.10.10.23Code: Select all
localhost
10.10.10.21As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: Cluster Status is Red
I changed it so it was exactly how you showed but after rebooting both servers i still cant login. When I say I cant login its to the web interface not the server via ssh.
Re: Cluster Status is Red
Is it waiting for elasticsearch again or not accepting credentials or something else? Some fresh profiles may have some new info now that the cluster_host files have been updated.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: Cluster Status is Red
no this is saying invalid username or password. I dont get the waiting on elastic search just cant login to see anything lol
Re: Cluster Status is Red
I see a ticket has been opened so we'll lock this up and work through that to avoid duplicating efforts.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.