http status code 404 - Nagios check_http failing with 404 on certain address -


I created 2 ngosos server this week, previously there was only a proof of concept, and tonight I created one . I followed the exact same instructions on both, and migrated my existing configuration to the new server tonight. Everything works perfect, except that some check_http checks are getting a 404 error, even if I can curl and even know. Example:

  ./check_http-I 127.0.0.1 -u http://11.210.1.18:8001/alphaweb/login.html HTTP Alert: HTTP / 1.1 404 not found - in 528 bytes 0.000 seconds response time. Time = 0.000418 S ;; 0.000000 size = 528b ;;; 0   

I can curl this address with no problem but the following are successful:

  ./check_http-I 127.0.0.1 - U http://11.210.1.16:7001 HTTP is OK: HTTP / 1.1 200 Ok - 0.001 second second reaction time 288 bytes. Time = 0.000698 S ;; 0.000000 size = 288b ;;; 0   

Both of these checks work almost entirely on the same server, any idea?

Good thing is, that you get some HTTP status codes, 404 is also a good one, Because you somehow interact with a web server. Check log files on the target web server

Assume that you have access to the target web server, I would recommend you check the log files.

Both requests, even a 404 status code, will be seen there. And here's a surprise, you think that, when your check is getting some feedback, your log file is not showing any log record about it. In this situation, I suspect some proxy or IPTable.

Double click on your call spell check

But the reason for this can be very simple - there can be a small difference in your command significant differences.

Comments

Popular posts from this blog

c - Mpirun hangs when mpi send and recieve is put in a loop -

python - Apply coupon to a customer's subscription based on non-stripe related actions on the site -

java - Unable to get JDBC connection in Spring application to MySQL -