@parisa, Thanks for sharing your solution, I'll keep this in mind if I come across similar cases.
I'll be closing the thread as resolved.
Search found 3447 matches
- Tue Jun 11, 2019 11:17 am
- Forum: Nagios XI
- Topic: problem with service history
- Replies: 4
- Views: 826
- Mon Jun 10, 2019 4:44 pm
- Forum: Nagios XI
- Topic: VMware datastore monitoring
- Replies: 3
- Views: 407
Re: VMware datastore monitoring
Hello, rferebee . The problem is likely with the permissions that have been applied in the vSphere Client. For some reason assigning the permissions at the top level of “Inventory > Hosts and Clusters” is not enough. You need to also assign the permissions at the top level of “Inventory > Datastores...
- Mon Jun 10, 2019 3:50 pm
- Forum: Nagios XI
- Topic: API returns wrong status code on failure
- Replies: 5
- Views: 470
Re: API returns wrong status code on failure
@sib, No problem. Closing this thread as resolved.
- Mon Jun 10, 2019 3:48 pm
- Forum: Nagios Log Server
- Topic: NLS: Apply configuration process does not complete
- Replies: 3
- Views: 652
Re: NLS: Apply configuration process does not complete
Hello, mrABB . Let's increase the settings in your /etc/php.ini file. Double the memory_limit value, set max_execution_time to 300, max_input_time to 300 as well. Save the file and restart apache with: service httpd restart This KB article is for XI but you can use it a guide for the LS as well. htt...
- Mon Jun 10, 2019 2:51 pm
- Forum: Open Source Nagios Projects
- Topic: Newbie trying to get Nagios Core on CentOS working
- Replies: 1
- Views: 997
Re: Newbie trying to get Nagios Core on CentOS working
m0bov , Please run this command from the command line and show me the output: cat /etc/httpd/conf.d/* Then run this command: tail -f /var/log/*error* And while it's running try to access the Core interface a few times. You should now see some errors in the console. Please copy - paste them in this ...
- Mon Jun 10, 2019 2:43 pm
- Forum: Nagios XI
- Topic: API returns wrong status code on failure
- Replies: 5
- Views: 470
Re: API returns wrong status code on failure
@sib, I understand. I'm going to submit a feature request on your behalf to add this functionality.
Please keep in mind that the decision to implement the enhancement is at the discretion of our development team.
Let me know if you have any other API related concerns.
Please keep in mind that the decision to implement the enhancement is at the discretion of our development team.
Let me know if you have any other API related concerns.
- Mon Jun 10, 2019 2:33 pm
- Forum: Nagios XI
- Topic: problem with service history
- Replies: 4
- Views: 826
Re: problem with service history
Hello, parisa . Did the service history log stop catching entries for services after you upgraded XI? Can you confirm whether other(active) services are producing State History log entries during state changes? I am able to see the recovery in service status on Nagios Did the XI service status turn ...
- Mon Jun 10, 2019 1:07 pm
- Forum: Nagios XI
- Topic: Port Bandwidth showing 0Mb/s
- Replies: 7
- Views: 989
Re: Port Bandwidth showing 0Mb/s
carlosocha , Please open the /etc/cron.d/mrtg cron file and delete --user=nagios --group=nagios at the end, so the cron will look like this: */5 * * * * root LANG=C LC_ALL=C /usr/bin/mrtg /etc/mrtg/mrtg.cfg --lock-file /var/lib/mrtg/mrtg.lock --confcache-file /var/lib/mrtg/mrtg.ok --user=nagios --g...
- Mon Jun 10, 2019 12:57 pm
- Forum: Nagios XI
- Topic: Error when using check_docker.py
- Replies: 19
- Views: 3274
Re: Error when using check_docker.py
emarmonti , Have you tried acessing the Docker API interface directly using the new plugin I uploaded? /usr/local/nagios/libexec/check_docker.py -H http://dockerIP:dockerPort/ --check-type 'containers_cpu' Here's an example: [root@centos7x64 libexec]# /usr/local/nagios/libexec/check_docker.py -H ht...
- Mon Jun 10, 2019 12:33 pm
- Forum: Nagios XI
- Topic: API returns wrong status code on failure
- Replies: 5
- Views: 470
Re: API returns wrong status code on failure
Hello, sib . The HTTP 200 OK status means that the HTTP request has been processed successfully. While the error below indicates that Nagios will not be able to add the service because some required fields were missing. But this is a separate logic. From the HTTP standpoint, the request went through...