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
system status
system status
Last edited by swolf on Wed Jul 18, 2018 4:18 pm, edited 1 time in total.
Reason: Removed attachment as requested in ticket
Reason: Removed attachment as requested in ticket
Re: system status
9 times out of 10 this is going to be related to memory. What is the RAM installed vs used on this system?
Former Nagios employee
Re: system status
There are four instances please see the screen shot accordingly
RAM = 32GB/instance (32 GB * 4)
RAM = 32GB/instance (32 GB * 4)
Last edited by swolf on Wed Jul 18, 2018 4:18 pm, edited 1 time in total.
Reason: Removed attachment as requested in ticket
Reason: Removed attachment as requested in ticket
Re: system status
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
nslookup vhal1nls001.healthcare.huarahi.health.govt...
nslookup 10.17.31.50
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: system status
so you are saying it may be a DNS issue?
Re: system status
Hi Support
I have rebooted nagios log server, still the status is the same
kindly support
I have rebooted nagios log server, still the status is the same
kindly support
Last edited by swolf on Wed Jul 18, 2018 4:17 pm, edited 1 time in total.
Reason: Removed attachment as requested in ticket
Reason: Removed attachment as requested in ticket
Re: system status
Have you verified the DNS? Can your client resolve the hostname to an IP?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: system status
nslookup 10.17.31.50
-bash: nslookup: command not found
nslookup vhal1nls001
-bash: nslookup: command not found
-bash: nslookup: command not found
nslookup vhal1nls001
-bash: nslookup: command not found
Re: system status
may be nslookup install is not available,
as a cluster,
it is pinging all the four instances
as a cluster,
it is pinging all the four instances
Re: system status
To install nslookup:
yum -y install bind-utils
Also try running nslookup on your client machine(the machine where the browser is running).
yum -y install bind-utils
Also try running nslookup on your client machine(the machine where the browser is running).
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.