[Chilli] CoovaChilli monitoring strategy

[Yvan BARTHÉLEMY]

Hello,

I have an installation of CoovaChilli 1.2.3 in production built using
the rpm spec available in the source package. In this configuration
the following flags are enabled:

%configure \
        --disable-static \
        --enable-shared \
        --enable-largelimits \
        --enable-miniportal \
        --enable-chilliproxy \
        --enable-chilliredir \
        --enable-chilliscript \
        --with-poll \
        --with-curl \
%if %{!?_without_ssl:1}0
        --with-openssl \
        --enable-chilliradsec \
%endif

The portal works and clients are able to connect using miniportal, but
for an unknown reason, the redirection sometimes stops working (we are
not able to reproduce this in our office so it is difficult to
troubleshot). We were able to workaround this using a shell script
that  fetches http://10.36.0.1:3990/www/coova.html every 5 minutes
using curl and that relaunches CoovaChilli when it gets no response.

We are not happy with this solution as it involves some down time
between the detection and the restarting of the service.

I believe that removing --enable-chilliredir might help to get rid of
the problem. When doing this we are not able to fetch
http://10.36.0.1:3990/www/coova.html or any coova-chilli url anymore.

Do you know a way to fetch this url or to check redirection is working
when the compile flag --enable-chilliredir is off ?

Many thanks in advance for any help or suggestion about this issue.