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

OK, thanks for update. The HEAD method is preferred by monit, as it saves bandwidth, but it's true that some servers may reject it. We can implement an option for method selection in the http protocol test to allow to override the default HEAD method. > On 19 Sep 2016, at 19:04, Moshe Cohen

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

Thanks. Now the riddle is solved : line 244 in http.c determines whether a HEAD or GET requests is sent, by whether there is a regex to check. That turned out to be the critical issue. The server I am checking, apparently does not support HEAD. I verified this by also getting a 404 when accessing

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

You can either catch the communication using for example wireshark (but you'll need the server certificate do decrypt HTTPS), or it's possible to modify monit source code (src/protocols/http.c) to print every message send/received from the server + recompile monit. > On 19 Sep 2016, at 17:24,

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

No, sorry. That is not possible due to permission issues. I have compiled Monit myself. Could you point me to the code that sends the request so I could log the requests details and maybe see what is different between the cases? On Mon, Sep 19, 2016 at 6:10 PM, Martin Pala wrote: > Is it possib

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

Is it possible to get test access (via HTTPS) to that URL? > On 19 Sep 2016, at 14:35, Moshe Cohen wrote: > > I am on 5.19.0 (the latest) > > > > On Mon, Sep 19, 2016 at 3:03 PM, Martin Pala > wrote: > Which monit version it is? (monit -V) > > If you test H

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

I am on 5.19.0 (the latest) On Mon, Sep 19, 2016 at 3:03 PM, Martin Pala wrote: > Which monit version it is? (monit -V) > > If you test HTTPS, the ServerNameIndication (SNI) TLS extension may be > required, so monit can talk to name based virtual SSL server. Support for > SNI was added on mon

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

Which monit version it is? (monit -V) If you test HTTPS, the ServerNameIndication (SNI) TLS extension may be required, so monit can talk to name based virtual SSL server. Support for SNI was added on monit 5.13. Best regards, Martin > On 17 Sep 2016, at 22:20, Moshe Cohen wrote: > > I have

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

Another weird piece of info: when I added a content = 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 acces

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

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 Hend

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

Could be that monit is sending a different Host header and/or request line when compared to what curl is sending. Do you have any access to view logs or configs on the HTTP server? On Sep 18, 2016 11:16 AM, "Tino Hendricks" wrote: > I can’t be of any more help because I’m not even able to ping yo

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

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 htt

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

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 wrote: > Did you try > > If failed url https://arogacentertest.norbltd2.com/checkalive... > > ? > > Tino > > Am 17.09.2016 um 22:20 schrieb Moshe Cohen : > > I

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

Did you try If failed url https://arogacentertest.norbltd2.com/checkalive... ? Tino > Am 17.09.2016 um 22:20 schrieb Moshe Cohen : > > I have the following url, that when called with https, return 200 as shown > here: > > > curl -i https://arogacentertest.norbltd2.com:443/checkalive > HTTP/

Checking on a url does not work (from newbie)

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