False alarm I fixed my own issue.
So what happened was another user removed an entry from /etc/icinga/servers/blank.cloud9ortho.com.cfg, but they did not remove the associated hostgroups_icinga.cfg config for DNS checks. This apparently cause it to not work.
Search found 20 matches
- Tue Jun 18, 2019 8:06 am
- Forum: Open Source Nagios Projects
- Topic: Certain Hostgroups not working after Upgrade
- Replies: 2
- Views: 1061
- Tue Jun 18, 2019 7:51 am
- Forum: Open Source Nagios Projects
- Topic: Certain Hostgroups not working after Upgrade
- Replies: 2
- Views: 1061
Certain Hostgroups not working after Upgrade
All, We recently upgraded our system which we ran Nagios3 on from Debian 7.11 to Debian 9.9. I know that Nagios3 is not supported in Debian 9, so I have to use Icinga instead. But Icinga is a drop in replacement of Nagios3. I have gone through this a couple time with different Monitoring servers we ...
- Wed Apr 24, 2019 2:14 pm
- Forum: Open Source Nagios Projects
- Topic: "Couldn't match /usr/bin/mailq output" after Debian Upgrade
- Replies: 10
- Views: 4395
Re: "Couldn't match /usr/bin/mailq output" after Debian Upgr
I updated the nrpe_local.cfg file and modified the Mailq check to the following: command[check_mailq]=/usr/lib/nagios/plugins/check_mailq -w 2 -c 5 -M exim I then restarted Nagios-nrpe-server. After that restart the check on our monitoring server is now OK. It is no longer showing the Unknown error....
- Wed Apr 24, 2019 2:06 pm
- Forum: Open Source Nagios Projects
- Topic: "Couldn't match /usr/bin/mailq output" after Debian Upgrade
- Replies: 10
- Views: 4395
Re: "Couldn't match /usr/bin/mailq output" after Debian Upgr
Hello,
Thank you for the reply.
When I enter the following command:
/usr/lib/nagios/plugins# ./check_mailq -w 10 -c 20 -M exim
I get the following output:
OK: exim mailq (0) is below threshold (10/20)|unsent=0;10;20;0
So it appears to give actual data using that command.
Thank you for the reply.
When I enter the following command:
/usr/lib/nagios/plugins# ./check_mailq -w 10 -c 20 -M exim
I get the following output:
OK: exim mailq (0) is below threshold (10/20)|unsent=0;10;20;0
So it appears to give actual data using that command.
- Wed Apr 24, 2019 12:03 pm
- Forum: Open Source Nagios Projects
- Topic: "Couldn't match /usr/bin/mailq output" after Debian Upgrade
- Replies: 10
- Views: 4395
Re: "Couldn't match /usr/bin/mailq output" after Debian Upgr
Hello,
Below is an output of ls -l on /usr/bin/mailq:
-rwsr-xr-x 1 mail root 18584 Jul 31 2016 /usr/bin/mailq
Is Exim -bp a command?
Thanks
Below is an output of ls -l on /usr/bin/mailq:
-rwsr-xr-x 1 mail root 18584 Jul 31 2016 /usr/bin/mailq
Is Exim -bp a command?
Thanks
- Wed Apr 24, 2019 7:28 am
- Forum: Open Source Nagios Projects
- Topic: "Couldn't match /usr/bin/mailq output" after Debian Upgrade
- Replies: 10
- Views: 4395
Re: "Couldn't match /usr/bin/mailq output" after Debian Upgr
Hello,
Thank you for the reply. I logged into the server that I updated (not the monitoring server), and ran the command locally.
root:/usr/lib/nagios/plugins# ./check_nrpe -H 127.0.0.1 -t 30 -c check_mailq
Couldn't match /usr/bin/mailq output
I ran the command logged in as root.
Thanks
Thank you for the reply. I logged into the server that I updated (not the monitoring server), and ran the command locally.
root:/usr/lib/nagios/plugins# ./check_nrpe -H 127.0.0.1 -t 30 -c check_mailq
Couldn't match /usr/bin/mailq output
I ran the command logged in as root.
Thanks
- Mon Apr 22, 2019 3:54 pm
- Forum: Open Source Nagios Projects
- Topic: "Couldn't match /usr/bin/mailq output" after Debian Upgrade
- Replies: 10
- Views: 4395
Re: "Couldn't match /usr/bin/mailq output" after Debian Upgr
Hello,
Thank you for the reply. The command that is attempting to run is the following:
/usr/lib/nagios/plugins/check_nrpe -H <hostname> -t 30 -c check_mailq
I do not believe I can SSH into the server as Nagios user, but is there any way to run the command as the Nagios user?
Thanks
Thank you for the reply. The command that is attempting to run is the following:
/usr/lib/nagios/plugins/check_nrpe -H <hostname> -t 30 -c check_mailq
I do not believe I can SSH into the server as Nagios user, but is there any way to run the command as the Nagios user?
Thanks
- Mon Apr 22, 2019 8:49 am
- Forum: Open Source Nagios Projects
- Topic: "Couldn't match /usr/bin/mailq output" after Debian Upgrade
- Replies: 10
- Views: 4395
"Couldn't match /usr/bin/mailq output" after Debian Upgrade
Hello All, I recently upgraded one of our Debian systems from Debian 7.11 to Debian 9.8. After the upgrade everything seems to be working as expected except for our monitoring server seems to have one error related to MailQ for the newly upgraded server. The Icinga checks on our monitoring server ar...
- Thu Sep 28, 2017 7:40 am
- Forum: Open Source Nagios Projects
- Topic: Nagios checks for AWS S3 file ages
- Replies: 5
- Views: 2937
Re: Nagios checks for AWS S3 file ages
Where do I reference the $ARG1$ and $ARG2$. I have seen many commands with these arguments, but where do I assign the values for these arguments?
Thanks
Thanks
- Wed Sep 27, 2017 3:02 pm
- Forum: Open Source Nagios Projects
- Topic: Nagios checks for AWS S3 file ages
- Replies: 5
- Views: 2937
Re: Nagios checks for AWS S3 file ages
So the plugin does seem to run when I run it from the /nagios-plugins/ folder from the git-clone. If I move the plugin to the /usr/lib/nagios/plugins/ folder where the rest of the plugins are it fails. When I create the check_aws.cfg file in /etc/nagios-plugins/config do I just need to tell it to lo...