marceloNYC
asked on
Nagios critical error 800 days old
Hello Experts,
I started here in April and I m trying to clean house.
We use Nagios religously.
There are this errors that I want to clean up. This one I am not sure where to begin:
commsrv1
Debian GNU/Linux
Internal DNS
Notifications for this service have been disabled
CRITICAL 2015-07-31 09:36:41 890d 16h 6m 48s 4/4 DNS CRITICAL - 0.023 seconds response time (No ANSWER SECTION found)
If you could give me an idea where to begin please.
Thank you!
Screenshot-from-2015-07-31-09-50-12.png
I started here in April and I m trying to clean house.
We use Nagios religously.
There are this errors that I want to clean up. This one I am not sure where to begin:
commsrv1
Debian GNU/Linux
Internal DNS
Notifications for this service have been disabled
CRITICAL 2015-07-31 09:36:41 890d 16h 6m 48s 4/4 DNS CRITICAL - 0.023 seconds response time (No ANSWER SECTION found)
If you could give me an idea where to begin please.
Thank you!
Screenshot-from-2015-07-31-09-50-12.png
i would look at the command being used
i'm guessing it is using check_dig
look at the command line; possible it was not setup correctly
i'm guessing it is using check_dig
look at the command line; possible it was not setup correctly
ASKER
Aha! I found this fellow in services conf file
# check that ssh services are running
define service {
hostgroup_name internal-dns-servers
service_description Internal DNS
check_command check_dig!coxxx-server.cor p.ok7-elev en.com
use generic-service
}
define service {
hostgroup_name store-internal-dns-servers
service_description Internal DNS
check_command check_dig!coxxx-server.cor p.ok7-elev en.com
normal_check_interval 10
max_check_attempts 10
use generic-service
}
# check that ssh services are running
define service {
hostgroup_name internal-dns-servers
service_description Internal DNS
check_command check_dig!coxxx-server.cor
use generic-service
}
define service {
hostgroup_name store-internal-dns-servers
service_description Internal DNS
check_command check_dig!coxxx-server.cor
normal_check_interval 10
max_check_attempts 10
use generic-service
}
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Digging... need a few
look at the command using check_dig and see what parameters are being used
ASKER
Okay,
For sure the solution is in the two config files .
My problem now is finding out what server should go where.
There 3 to choose from.
The one that is in the command check_dig! does seem to be doing anything now yet it does respond to a ping.
Asking around to get the right idea.
For sure the solution is in the two config files .
My problem now is finding out what server should go where.
There 3 to choose from.
The one that is in the command check_dig! does seem to be doing anything now yet it does respond to a ping.
Asking around to get the right idea.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I am stuck figuring out what name DNS server to put there ( I found 4). That is a beside the issue that you helped me with
Thank you!
Thank you!
Check the services inside /etc/nagios3/conf.d/ until you find the culprit.
HTH,
Dan