Re: [Roundup-users] V2.3.0 Docker image (amd64) : Healthcheck

[SCHLEMMER N. <Nor...@pd...>]

Hi John

Ok... seems to be an issue with this VM... will use a new one installed from scratch

Thanks
Norbert

-----Ursprüngliche Nachricht-----
Von: ro...@cs... <ro...@cs...> 
Gesendet: Mittwoch, 18. Oktober 2023 15:01
An: SCHLEMMER Norbert <Nor...@pd...>
Cc: rou...@li...
Betreff: Re: AW: AW: [Roundup-users] V2.3.0 Docker image (amd64) : Healthcheck

*EXTERNAL source*


Hi Norbert:

In message <DU2PR01MB8557A42F2C7ABA6C35D5F45BE8D5A@DU2PR01MB8557.eurprd01.prod.
exchangelabs.com>,
SCHLEMMER Norbert writes:
>See my test results below
>
>~ $    ps -ef | grep roundup-server
>    7 roundup   0:09 {roundup-server} /usr/local/bin/python /usr/local/bin/roundup-server -n 0.0.0.0 issues=tracker
>20058 roundup   0:00 grep roundup-server
>
>
>~ $ wget -q -O /dev/null --no-verbose http://localhost:8080/issues/
>wget: server returned error: HTTP/1.1 503 Service Unavailable
>~ $   echo $?
>1

While mine looks like:

 $ docker exec fleet-tracker ps -ef
 PID   USER     TIME  COMMAND
     1 roundup   0:00 /usr/bin/dumb-init ./roundup_start fleet=tracker
     7 roundup   0:20 {roundup-server} /usr/local/bin/python /usr/local/bin/roundup-server -n 0.0.0.0 fleet=tracker

 $ docker exec fleet-tracker sh -c 'wget -q -O /dev/null --no-verbose http://localhost:8080/fleet/; echo $?'
 0

I have no idea why/how you are getting a 503. In fact I can't find Roundup ever using/returning 503 or http.SERVICE_UNAVAILABLE anywhere in the Roundup code. So I claim the 503 is not coming from Roundup.

I verified that the error from wget when connecting to the wrong port is different:

   wget: can't connect to remote host (127.0.0.1): Connection refused

If it can't resolve the hostname, wget returns:

   wget: bad address 'loclhost:8080'

Is there some other web server running on the system or inside the docker container that wget inside the container could be hitting?

Can you try running docker with a -p of:

   -p 127.0.0.1:<external port>:8080

where external port is the first port number you are currently using.
The docs recommends using 127.0.0.1 so that docker doesn't play games with the external firewall rules on your host.

I tried running docker using just '-p <external port>:8080' and I can't reproduce your error. The heartbeat check works fine.

So I am stumped as to why this is is erroring.

--
                                -- rouilj John Rouillard ===========================================================================
My employers don't acknowledge my existence much less my opinions.