Nagios Support Forum

Hi Team,

We have one LAMP server added in Nagios monitoring on that server we are getting error related to Nagios check_http. from last few days we have observed that in "/opt/applications/apache/logs/error_log" file of apache getting below:

[Sat May 03 02:12:52 2014] [error] check_http/v2053 (nagios-plugins 1.4.13)
-----------------------------------------------------------
PFB logs for your ref:
[Sat May 03 02:12:52 2014] [error] /xxx/xxx/xxx/xxx/xxx/xxx/tzinfo.py:5: DeprecationWarning: the sets module is deprecated
[Sat May 03 02:12:52 2014] [error] from sets import Set
[Sat May 03 02:12:52 2014] [error] /usr/local/lib/python2.6/site-packages/django/views/generic/simple.py:8: DeprecationWarning: Function-based generic views have been deprecated; use class-based views instead.
[Sat May 03 02:12:52 2014] [error] DeprecationWarning
[Sat May 03 02:12:52 2014] [error] check_http/v2053 (nagios-plugins 1.4.13)
------------------------------------------------------------
All the services configured on this Server are working fine. But we are getting this "check_http" error in log file. I am not sure what error this exactly means maybe its due to Nagios OR Apache.
Can you please check from logs and let me know what could be the issue.

Thanks & Regards,
Dushyant

Looks like you have a Django environment, and it doesn't like the "sets" module in Python. The check_http/v2053 line is just the user-agent string that our plugin uses. Are you running an older version of Django? This post seems to suggest this is a possibility:

http://stackoverflow.com/questions/2040 ... ed-warning

Hi Donald,
We have Django with version Django-1.4.8. & Python version is Python 2.6.8
We are observingg this error in only on one server.We have two servers with same configuration.On other server we are not observing this nagios related error.
Can you please let us know why this nagios related error is reflecting only on one server.
Please let me know if you require any logs.

Regards,
Dushyant

Are you sure the servers are configured exactly the same, and being checked with the same command from Nagios? Those errors are not *caused* by Nagios, rather when check_http goes to check the page there is a function in Django that is being called which throws that error. This is due to the Django version being older than the Python version, so some functions got deprecated. As I said before the check_http is just the user-agent of the program that prompted the warning.