Waiting for environment to be ready. It can take a few minutes

coulibaly080635 · February 5, 2021, 3:51pm

Sorry

root@kobo:/home/kobo/kobo-install# ./run.py --info
Date: Fri, 05 Feb 2021 15:50:20 GMT
Server: Apache/2.4.29 (Ubuntu)
Content-Length: 452
Content-Type: text/html; charset=iso-8859-1

╔════════════════════════════════════════════════════════════════════╗
║ ║
║ KoBoToolbox could not start! ║
║ Please try python3 run.py --logs to see the logs. ║
║ ║
╚════════════════════════════════════════════════════════════════════╝
root@kobo:/home/kobo/kobo-install#

OlivierL · February 5, 2021, 4:05pm

Is koboml.xxxx.com the domain name for KPI?
Your proxy must use the same domains you saved in kobo-install configuration.

coulibaly080635 · February 5, 2021, 4:08pm

Yes it the same.

Where do you want to install?
[/home/kobo/kobo-docker]:
Please confirm path [/home/kobo/kobo-docker]
1) Yes
2) No
[1]:
Do you want to see advanced options?
1) Yes
2) No
[2]:
What kind of installation do you need?
1) On your workstation
2) On a server
[2]:
Public domain name? [xxxxxx.com]:
KPI sub domain? [koboml]:
KoBoCat sub domain? [kc]:
Enketo Express sub domain name? [ee]:
Do you want to use HTTPS?
1) Yes
2) No
[1]:
╔════════════════════════════════════════════════════════════════════╗
║ ║
║ Please note that certificates must be installed on a reverse-proxy ║
║ or a load balancer.kobo-install can install one, if needed. ║
║ ║
╚════════════════════════════════════════════════════════════════════╝
Auto-install HTTPS certificates with Let’s Encrypt?
1) Yes
2) No - Use my own reverse-proxy/load-balancer
[2]:
Internal port used by reverse proxy is 8080.

OlivierL · February 5, 2021, 4:15pm

Can you try curl -I -H 'Host: komoml.xxxx.com' -H 'X-Forwarded-Proto: https' http://127.0.0.1/service_health/ ?

What does it say?

coulibaly080635 · February 5, 2021, 4:21pm

I had 8080 port because ans NGINX use this port

root@kobo:/home/# curl -I -H ‘Host: koboml.xxxx.com’ -H ‘X-Forwarded-Proto: https’ http://127.0.0.1:8080/service_health/
HTTP/1.1 200 OK
Server: nginx/1.19.6
Date: Fri, 05 Feb 2021 16:19:52 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 331
Connection: keep-alive
X-Frame-Options: SAMEORIGIN
Vary: Accept-Language, Cookie, Origin
Content-Language: en

coulibaly080635 · February 5, 2021, 4:55pm

I had ```
ProxyPreserveHost on

After this have:

root@kobo:/home/scoulibaly# curl -I https://koboml.orangemali.com/
HTTP/1.1 302 Found
Date: Fri, 05 Feb 2021 16:48:32 GMT
Server: nginx/1.19.6
Content-Type: text/html; charset=utf-8
Location: /accounts/login/?next=/
X-Frame-Options: SAMEORIGIN
Vary: Accept-Language,Cookie,Origin
Content-Language: en
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache

OlivierL · February 5, 2021, 4:57pm

It seems that everything works as expected…

If you try in your browser: https://koboml.xxxx.com/service_health/

Can you also try the curl command without -I?

curl -H ‘Host: [koboml.xxxx.com](http://koboml.xxxx.com/)’ -H ‘X-Forwarded-Proto: https’ http://127.0.0.1:8080/service_health/

coulibaly080635 · February 5, 2021, 5:00pm

OK KPI

Mongo: OK in 0.0204 seconds
Postgres: OK in 0.0126 seconds
Enketo [http://ee.orangemali.internal]: OK in 0.989 seconds
KoBoCAT [http://kc.orangemali.internal]: OK in 0.0246 seconds

----BEGIN KOBOCAT RESPONSE----
OK

Mongo: OK in 0.00214 seconds
Postgres: OK in 0.00547 seconds

---- END KOBOCAT RESPONSE ----

OlivierL · February 5, 2021, 5:04pm

So everything works as expected now.

coulibaly080635 · February 5, 2021, 5:06pm

Yes,
Thank you very much.
But if I try to open it doesn’t work

SantiTamariz · February 23, 2022, 10:07pm

Hello, I’m trying to install using kobo-install but it always get crashed when starting the kobotoolbox. I’m using normal installation with workstation and advanced options for dev mode. I’m trying to make some changes in the kpi but I can’t even install in the normal way.

When I try using workstation without advanced options it remains every time in wait another 600 seconds and the mongo container keeps restarting but not working.

Thank you

OlivierL · February 24, 2022, 2:38pm

Hello @SantiTamariz ,

Can you provide more details please? The logs, the version of docker and compose, the OS where you’ve installed kobo-install and obviously, the version of kobo-install

SantiTamariz · February 28, 2022, 3:01pm

Hello @OlivierL ,

Could this problem be due to the new MacOs software update.
I’m using the last kobo-install code from the GitHub

Thank you,

SantiTamariz · February 28, 2022, 3:07pm

This is what I get when I try to use the advanced options with developer mode for the workstation installation.

[+] Running 1/0
⠿ kobomaintenance Warning: No resource found to remove 0.0s
[+] Running 5/5
⠿ Container kobofe-kobocat-1 Removed 2.9ss
⠿ Container kobofe-nginx-1 Removed 0.3ss
⠿ Container kobofe-kpi-1 Removed 2.5ss
⠿ Container kobofe-enketo_express-1 Removed 10.4ss
⠿ Network kobofe_kobo-fe-network Removed 0.2ss
[+] Running 5/5
⠿ Container kobobe-redis_cache-1 Removed 1.0ss
⠿ Container kobobe-mongo-1 Removed 0.2ss
⠿ Container kobobe-postgres-1 Removed 1.6ss
⠿ Container kobobe-redis_main-1 Removed 1.5ss
⠿ Network kobobe_kobo-be-network Removed 0.1ss
Launching environment
[+] Running 5/5
⠿ Network kobobe_kobo-be-network Created 0.1ss
⠿ Container kobobe-redis_cache-1 Started 3.2ss
⠿ Container kobobe-postgres-1 Started 3.3ss
⠿ Container kobobe-mongo-1 Started 3.2ss
⠿ Container kobobe-redis_main-1 Started 1.8ss
Waiting for PostgreSQL database to be up & running…
WARN[0000] network kobo-be-network: network.external.name is deprecated in favor of network.name
[+] Running 1/1
⠿ Network kobofe_kobo-fe-network Created 0.1ss
[+] Running 0/1
⠿ kpi Error 3.6s5s

OlivierL · February 28, 2022, 3:16pm

Hello @SantiTamariz,

In Docker Desktop, be sure to uncheck “Use Docker compose v2” as kobo-install is not yet compatible with it.

I’m using latest version of macOS (Monterey) and a latest version of Docker Desktop (4.5) and it’s working.

Are you using an Intel chip or an Apple M1 chip?

SantiTamariz · February 28, 2022, 3:18pm

I have just uncheck it, I will say something to you after restarting it
And I’m using intel chip on mi Mac

Rejeesh · October 1, 2024, 5:19am

Hi @OlivierL @stephenoduor @Kal_Lam

We were using an older version of KoboToolbox from 2019. I upgraded the database step by step using the documentation provided by the KoboToolbox team. After upgrading the code by checking out the latest version, I encountered build errors during the process. DNS uses HTTPS as its protocol.

I attempted to build the latest version of KoboToolbox on my local machine. Before proceeding with the upgrade, I took a dump of the old database and restored it into a new version of the KoboToolbox environment. After the database was restored, I adjusted the environment file as needed.

The task was successfully completed. However, when I ran the run.py file, I encountered a delay of 600 seconds. I have attached a screenshot showing this issue.

If there are any known issues with running KoboToolbox locally without HTTPS, I would greatly appreciate your valuable guidance on resolving this.

OlivierL · October 1, 2024, 9:15pm

Hello @Rejeesh,

You should look at kpi logs first. Maybe you will see errors there.

Rejeesh · October 4, 2024, 12:31pm

HI @OlivierL

This is log/nginx/kpi.error.log

2024/10/04 10:13:28 [error] 44#44: *316 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.161, server: kf.kobo.local, request: “GET /service_health/ HTTP/1.1”, upstream: “uwsgi://192.168.160.7:8000”, host: “kf.kobo.local”

This is log/nginx/kobocat.error.log
2024/10/03 06:37:19 [error] 43#43: *36 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.64.3, server: kc.kobo.local, request: “GET /legacy/service_health/ HTTP/1.1”, upstream: “uwsgi://192.168.64.7:8000”, host: “kc.docker.internal”

This is log/kpi/celery_kpi_worker.log

[2024-10-04 08:52:09,751: INFO/MainProcess] mingle: searching for neighbors
[2024-10-04 08:52:10,770: INFO/MainProcess] mingle: all alone
[2024-10-04 08:52:10,788: INFO/MainProcess] kpi_worker@kpi ready.
[2024-10-04 10:03:32,465: WARNING/MainProcess] /opt/venv/lib/python3.10/site-packages/celery/worker/consumer/consumer.py:507: CPendingDeprecationWarning: The broker_connection_retry configuration setting will no longer determine
whether broker connection retries are made during startup in Celery 6.0 and above.
If you wish to retain the existing behavior for retrying connections on startup,
you should set broker_connection_retry_on_startup to True.
warnings.warn(

[2024-10-04 10:03:32,490: INFO/MainProcess] Connected to redis://:**@redis-main.kobo.private:6379/1
[2024-10-04 10:03:32,491: WARNING/MainProcess] /opt/venv/lib/python3.10/site-packages/celery/worker/consumer/consumer.py:507: CPendingDeprecationWarning: The broker_connection_retry configuration setting will no longer determine
whether broker connection retries are made during startup in Celery 6.0 and above.
If you wish to retain the existing behavior for retrying connections on startup,
you should set broker_connection_retry_on_startup to True.
warnings.warn(

[2024-10-04 10:03:32,493: INFO/MainProcess] mingle: searching for neighbors
[2024-10-04 10:03:33,503: INFO/MainProcess] mingle: all alone
[2024-10-04 10:03:33,524: INFO/MainProcess] kpi_worker@kpi ready.

This is log/kpi/uwsgi.log

{address space usage: 889958400 bytes/848MB} {rss usage: 40185856 bytes/38MB} [pid: 155|app: 0|req: 25/49] 192.168.1.161 () {50 vars in 1467 bytes} [Fri Oct 4 04:22:44 2024] GET /api/v2/assets/?q=(asset_type%3Aquestion%20OR%20asset_type%3Ablock%20OR%20asset_type%3Atemplate%20OR%20asset_type%3Acollection)%20AND%20parent%3Anull&limit=100&offset=0&ordering=-date_modified&metadata=on&collections_first=true => generated 127 bytes in 29821 msecs (HTTP/1.1 200) 10 headers in 326 bytes (1 switches on core 0)
[busyness] 30s average busyness is at 52%, will spawn 1 new worker(s)
spawned uWSGI worker 4 (pid: 164, cores: 1)
[busyness] 30s average busyness is at 0%, cheap one of 4 running workers
worker 1 killed successfully (pid: 155)
uWSGI worker 1 cheaped.
[busyness] 30s average busyness is at 0%, cheap one of 3 running workers
worker 2 killed successfully (pid: 156)
uWSGI worker 2 cheaped.

This is our error log and log reports. Is there anything suspicious you found related to the issue? I would greatly appreciate your valuable guidance on resolving this.

OlivierL · October 5, 2024, 6:20pm

Unfortunately, I don’t. Everything seems to be fine.

With your browser are you able to access http://kf.<domain.tld>/service_health/?

It really depends on the settings you use.

waiting for environment to be ready could also be because from your host your domain name is not reachable. Share your .run.conf (redacted credentials), maybe I can see something.