Re: Checking on a url does not work (from newbie)

[Moshe Cohen]

Another weird piece of info:  when I added a

content = <exp>

It started to return 200.

Now, that is supposed to be just a change in what Monit checks on the response, not a change on the request.

Is there any tool that can show me the full requests being sent on the client side, since I have no access to the server logs?

On Sun, Sep 18, 2016 at 9:11 PM, Moshe Cohen <address@hidden> wrote:

Oh, you won't be able to ping it , it is not public, not even on a public DNS.

I will try to have the people in charge of the server provide logs, but until then, is there a way to see what request Monit is sending and compare it to what curl is sending?

On Sun, Sep 18, 2016 at 6:16 PM, Tino Hendricks <address@hidden> wrote:

I can’t be of any more help because I’m not even able to ping your server:

>
> tinomba:~ tino$ ping arogacentertest.norbltd2.com
> ping: cannot resolve arogacentertest.norbltd2.com: Unknown host

On my end I’m successful with

check host tino with address XX.XX.XX.XX

    if failed url
       http://www.oratorienchor.de/index.php
       and content == 'klassische Chorkonzerte'
       then alert

> Am 18.09.2016 um 14:52 schrieb Moshe Cohen <address@hidden>:
>
> I did actually, and it fails too, reporting a 404.
> Both methods reach the same problem.
>
> On Sun, Sep 18, 2016 at 3:45 PM, Tino Hendricks <address@hidden> wrote:
> Did you try
>
> If failed url https://arogacentertest.norbltd2.com/checkalive...
>
> ?
>
> Tino
>
> Am 17.09.2016 um 22:20 schrieb Moshe Cohen <address@hidden>:
>
>> I have the following url, that when called with https, return 200 as shown here:
>>
>> > curl -i https://arogacentertest.norbltd2.com:443/checkalive
>> HTTP/1.1 200 OK
>> Cache-Control: no-cache, no-store, must-revalidate, max-age=0
>> Content-Type: application/json; charset=utf-8
>> Date: Sat, 17 Sep 2016 20:09:39 GMT
>> Content-Length: 0
>>
>>
>> The following Monit test fails :
>>
>> # Check ArogaCenter is alive
>>   check host ArogaCenter with address arogacentertest.norbltd2.com
>>     if failed
>>     port 443 protocol https
>>     request /checkalive
>>     status = 200
>>     then alert
>>
>> The log message is:
>>
>> [UTC Sep 17 20:14:05] error    : 'ArogaCenter' failed protocol test [HTTP] at [arogacentertest.norbltd2.com]:443/checkalive [TCP/IP SSL] -- HTTP error: Server returned status 404
>>
>> Since the response is a 404, it seems the server is reached but for some reason it is looking for another path that does not exist.
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> To unsubscribe:
>> https://lists.nongnu.org/mailman/listinfo/monit-general
>
> --
> To unsubscribe:
> https://lists.nongnu.org/mailman/listinfo/monit-general
>
> --
> To unsubscribe:
> https://lists.nongnu.org/mailman/listinfo/monit-general


--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general