Are you using the docker-compose-prod.yml file? That is the only file I see
that mentions allura-vm2.apache.org which is a specific hostname used for our
own site at forge-allura.apache.org If so, please follow the instructions at
the top of docker-compose-prod.yml about changing those settings to match your
own domain name. Or use docker-compose.yml or a customized version of either to
suit your needs if you don't need https yet, etc.
On 6/9/20 6:26 AM, Tony Hung wrote:
> upstream allura-vm2.apache.org {
> ## Can be connected with "allura_default"
> network
> # allura_git-http_1
> server 192.168.48.6:80;
> }
>
> When I access docker container Nginx, I found this config
>
> upstream allura-vm2.apache.org {
> ## Can be connected with "allura_default"
> network
> # allura_git-http_1
> server 192.168.48.6:80;
> }
>
> The server IP "192.168.48.6" is the part of Allura web. Maybe this is why
> showing 503 error
>
> On 2020/06/07 10:40:41, Aurélien Terrestris <aterrest...@gmail.com> wrote:
>> Hello,
>>
>> here are the outputs . Is one VM with 1cpu 1GB of RAM able to run this
>> allura version (it was working well with the same hardware since 2012)
>> ?
>>
>>
>> # docker-compose logs web
>> Attaching to allura_web_1
>> web_1 | [2020-06-03 15:10:32 +0000] [1] [INFO] Starting gunicorn 19.4.5
>> web_1 | [2020-06-03 15:10:32 +0000] [1] [INFO] Listening at:
>> http://0.0.0.0:8080 (1)
>> web_1 | [2020-06-03 15:10:32 +0000] [1] [INFO] Using worker: sync
>> web_1 | [2020-06-03 15:10:32 +0000] [11] [INFO] Booting worker with
>> pid: 11
>> web_1 | 15:10:43,415 ERROR [tg.configuration.app_config] Failed
>> to initialize mako template engine, removing it...
>> web_1 | [2020-06-03 15:24:46 +0000] [1] [INFO] Handling signal: term
>> web_1 | [2020-06-03 15:24:46 +0000] [11] [INFO] Worker exiting (pid: 11)
>> web_1 | [2020-06-03 15:24:48 +0000] [1] [INFO] Shutting down: Master
>> web_1 | [2020-06-03 15:27:00 +0000] [1] [INFO] Starting gunicorn 19.4.5
>> web_1 | [2020-06-03 15:27:00 +0000] [1] [INFO] Listening at:
>> http://0.0.0.0:8080 (1)
>> web_1 | [2020-06-03 15:27:00 +0000] [1] [INFO] Using worker: sync
>> web_1 | [2020-06-03 15:27:00 +0000] [11] [INFO] Booting worker with
>> pid: 11
>> web_1 | 15:27:12,220 ERROR [tg.configuration.app_config] Failed
>> to initialize mako template engine, removing it...
>>
>> # docker-compose logs http
>> Attaching to
>>
>> Le jeu. 4 juin 2020 à 05:26, Dave Brondsema <d...@brondsema.net> a écrit :
>>>
>>> What does `docker-compose logs` say? Or more specifically `docker-compose
>>> logs
>>> web` and `docker-compose logs http`
>>>
>>> See also
>>> https://forge-allura.apache.org/docs/getting_started/installation.html#useful-commands
>>>
>>> On 6/3/20 11:35 AM, Aurélien Terrestris wrote:
>>>> Hello,
>>>>
>>>> I just installed Allura with the docker method, on an Ubuntu 20.04 and
>>>> once done (without errors apparently), I just get 503 errors when
>>>> browsing my website. I suppose something isn't running, where to check
>>>> first ?
>>>>
>>>>
>>>> 503 Service Temporarily Unavailable
>>>> nginx/1.17.6
>>>>
>>>> best regards
>>>> A.T.
>>>>
>>>
>>>
>>> --
>>> Dave Brondsema : d...@brondsema.net
>>> http://www.brondsema.net : personal
>>> http://www.splike.com : programming
>>> <><
>>
>
--
Dave Brondsema : d...@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
