Page 1 of 2
system status
Posted: Mon Jul 16, 2018 1:25 pm
by HASupport
Hello Support,
There was a strange behavior of system status in NLS
my Elastic search Database and Logtash collector are behaving strangely
I have restarted both, but status is same
Please have a look of the screen shot
Re: system status
Posted: Mon Jul 16, 2018 3:02 pm
by tmcdonald
9 times out of 10 this is going to be related to memory. What is the RAM installed vs used on this system?
Re: system status
Posted: Mon Jul 16, 2018 3:20 pm
by HASupport
There are four instances please see the screen shot accordingly
RAM = 32GB/instance (32 GB * 4)
Re: system status
Posted: Mon Jul 16, 2018 3:49 pm
by cdienger
1 out of 10 times it will be a DNS problem - make sure that your client(the machine running the browser accessing NLS) can resolve the hostname(vhal1nls001.healthcare.huarahi.health.govt...) and that the NLS machines can do both a forward and reverse lookup for all hostnames and IPs listed:
nslookup vhal1nls001.healthcare.huarahi.health.govt...
nslookup 10.17.31.50
Re: system status
Posted: Mon Jul 16, 2018 4:47 pm
by HASupport
so you are saying it may be a DNS issue?
Re: system status
Posted: Mon Jul 16, 2018 8:48 pm
by HASupport
Hi Support
I have rebooted nagios log server, still the status is the same
kindly support
Re: system status
Posted: Tue Jul 17, 2018 11:32 am
by cdienger
Have you verified the DNS? Can your client resolve the hostname to an IP?
Re: system status
Posted: Tue Jul 17, 2018 1:15 pm
by HASupport
nslookup 10.17.31.50
-bash: nslookup: command not found
nslookup vhal1nls001
-bash: nslookup: command not found
Re: system status
Posted: Tue Jul 17, 2018 1:45 pm
by HASupport
may be nslookup install is not available,
as a cluster,
it is pinging all the four instances
Re: system status
Posted: Tue Jul 17, 2018 3:12 pm
by cdienger
To install nslookup:
yum -y install bind-utils
Also try running nslookup on your client machine(the machine where the browser is running).