CHT Error 404 Not Found

Hi @binod ,

I have some problem today, after I submit some tasks and forms that I updated, this is the problem I got.
I have issue like the website will return as 404 Not Found, Nginx/1.13.6

this is the medic logs

and this is the haproxy logs

Thank you very much for helping me.

And this is the startup logs

startup.logs

[info] 2023-02-07T08:12:36.274253Z couchdb@127.0.0.1 <0.9.0> -------- Application couch_log started on node ‘couchdb@127.0.0.1’
[info] 2023-02-07T08:12:36.279586Z couchdb@127.0.0.1 <0.9.0> -------- Application folsom started on node ‘couchdb@127.0.0.1’
[info] 2023-02-07T08:12:36.326791Z couchdb@127.0.0.1 <0.9.0> -------- Application couch_stats started on node ‘couchdb@127.0.0.1’
[info] 2023-02-07T08:12:36.327090Z couchdb@127.0.0.1 <0.9.0> -------- Application khash started on node ‘couchdb@127.0.0.1’
[info] 2023-02-07T08:12:36.335882Z couchdb@127.0.0.1 <0.9.0> -------- Application couch_event started on node ‘couchdb@127.0.0.1’
[info] 2023-02-07T08:12:36.336148Z couchdb@127.0.0.1 <0.9.0> -------- Application hyper started on node ‘couchdb@127.0.0.1’
[info] 2023-02-07T08:12:36.343037Z couchdb@127.0.0.1 <0.9.0> -------- Application ibrowse started on node ‘couchdb@127.0.0.1’
[info] 2023-02-07T08:12:36.349520Z couchdb@127.0.0.1 <0.9.0> -------- Application ioq started on node ‘couchdb@127.0.0.1’
[info] 2023-02-07T08:12:36.349762Z couchdb@127.0.0.1 <0.9.0> -------- Application mochiweb started on node ‘couchdb@127.0.0.1’
[info] 2023-02-07T08:12:36.359603Z couchdb@127.0.0.1 <0.212.0> -------- Apache CouchDB 2.3.1 is starting.

[info] 2023-02-07T08:12:36.359719Z couchdb@127.0.0.1 <0.213.0> -------- Starting couch_sup
[notice] 2023-02-07T08:12:36.370799Z couchdb@127.0.0.1 <0.96.0> -------- config: [features] pluggable-storage-engines set to true for reason nil
[notice] 2023-02-07T08:12:36.408099Z couchdb@127.0.0.1 <0.96.0> -------- config: [couchdb] uuid set to 9970889ca313d06cb4195fef1680957d for reason nil
[info] 2023-02-07T08:12:36.453572Z couchdb@127.0.0.1 <0.218.0> -------- open_result error {not_found,no_db_file} for _users
[info] 2023-02-07T08:12:36.556059Z couchdb@127.0.0.1 <0.212.0> -------- Apache CouchDB has started. Time to relax.

[info] 2023-02-07T08:12:36.556237Z couchdb@127.0.0.1 <0.212.0> -------- Apache CouchDB has started on http://0.0.0.0:5987/
[info] 2023-02-07T08:12:36.556728Z couchdb@127.0.0.1 <0.9.0> -------- Application couch started on node ‘couchdb@127.0.0.1’
[info] 2023-02-07T08:12:36.557125Z couchdb@127.0.0.1 <0.9.0> -------- Application ets_lru started on node ‘couchdb@127.0.0.1’
[notice] 2023-02-07T08:12:36.631425Z couchdb@127.0.0.1 <0.281.0> -------- rexi_server : started servers
[notice] 2023-02-07T08:12:36.636189Z couchdb@127.0.0.1 <0.286.0> -------- rexi_buffer : started servers
[info] 2023-02-07T08:12:36.636736Z couchdb@127.0.0.1 <0.9.0> -------- Application rexi started on node ‘couchdb@127.0.0.1’
[info] 2023-02-07T08:12:36.667549Z couchdb@127.0.0.1 <0.218.0> -------- open_result error {not_found,no_db_file} for _nodes
[warning] 2023-02-07T08:12:36.667622Z couchdb@127.0.0.1 <0.294.0> -------- creating missing database: _nodes
[warning] 2023-02-07T08:12:36.723207Z couchdb@127.0.0.1 <0.308.0> -------- creating missing database: _dbs
[info] 2023-02-07T08:12:36.723209Z couchdb@127.0.0.1 <0.218.0> -------- open_result error {not_found,no_db_file} for _dbs
[warning] 2023-02-07T08:12:36.723277Z couchdb@127.0.0.1 <0.309.0> -------- creating missing database: _dbs
[info] 2023-02-07T08:12:36.737907Z couchdb@127.0.0.1 <0.9.0> -------- Application mem3 started on node ‘couchdb@127.0.0.1’
[info] 2023-02-07T08:12:36.737953Z couchdb@127.0.0.1 <0.9.0> -------- Application fabric started on node ‘couchdb@127.0.0.1’
[info] 2023-02-07T08:12:36.769468Z couchdb@127.0.0.1 <0.9.0> -------- Application chttpd started on node ‘couchdb@127.0.0.1’
[notice] 2023-02-07T08:12:36.796539Z couchdb@127.0.0.1 <0.347.0> -------- chttpd_auth_cache changes listener died database_does_not_exist at mem3_shards:load_shards_from_db/6(line:395)

medic-sentinel logs

[info] 2023-02-07T08:12:36.274253Z couchdb@127.0.0.1 <0.9.0> -------- Application couch_log started on node ‘couchdb@127.0.0.1’
[2023-02-07 08:13:36] Node Environment Options: ‘–max_old_space_size=8192’
[2023-02-07 08:13:37] Node Version: 8.11.4 in production mode
[2023-02-07 08:13:37] COUCH_URL http://medic-sentinel:ec8206d31152eeab@haproxy:5984/medic
[2023-02-07 08:13:37] COUCH_NODE_NAME couchdb@127.0.0.1
[2023-02-07 08:13:37] CouchDB Version: 2.3.1
[2023-02-07 08:13:37] 2023-02-07 08:13:37 ESC[32mINFOESC[39m: Waiting for API to be ready…
[2023-02-07 08:13:47] 2023-02-07 08:13:47 ESC[32mINFOESC[39m: Api is ready: {“ready”:true,“handler”:“medic-api”,“version”:“0.1.0”,“detail”:“All required services are running normally”}

[2023-02-07 08:13:48] 2023-02-07 08:13:48 ESC[33mWARNESC[39m: Disabled transition “update_clinics”
[2023-02-07 08:13:48] 2023-02-07 08:13:48 ESC[33mWARNESC[39m: Disabled transition “self_report”
[2023-02-07 08:13:48] 2023-02-07 08:13:48 ESC[33mWARNESC[39m: Disabled transition “registration”
[2023-02-07 08:13:48] 2023-02-07 08:13:48 ESC[33mWARNESC[39m: Disabled transition “accept_patient_reports”
[2023-02-07 08:13:48] 2023-02-07 08:13:48 ESC[33mWARNESC[39m: Disabled transition “accept_case_reports”
[2023-02-07 08:13:48] 2023-02-07 08:13:48 ESC[33mWARNESC[39m: Disabled transition “generate_shortcode_on_contacts”
[2023-02-07 08:13:48] 2023-02-07 08:13:48 ESC[32mINFOESC[39m: Loading transition “generate_patient_id_on_people”
[2023-02-07 08:13:48] 2023-02-07 08:13:48 ESC[33mWARNESC[39m: “generate_patient_id_on_people” transition is deprecated. Please use “generate_shortcode_on_contacts” transition instead.
[2023-02-07 08:13:48] 2023-02-07 08:13:48 ESC[33mWARNESC[39m: Disabled transition “default_responses”
[2023-02-07 08:13:48] 2023-02-07 08:13:48 ESC[33mWARNESC[39m: Disabled transition “update_sent_by”
[2023-02-07 08:13:48] 2023-02-07 08:13:48 ESC[33mWARNESC[39m: Disabled transition “update_sent_forms”
[2023-02-07 08:13:48] 2023-02-07 08:13:48 ESC[32mINFOESC[39m: Loading transition “death_reporting”
[2023-02-07 08:13:48] 2023-02-07 08:13:48 ESC[33mWARNESC[39m: Disabled transition “conditional_alerts”
[2023-02-07 08:13:48] 2023-02-07 08:13:48 ESC[33mWARNESC[39m: Disabled transition “multi_report_alerts”
[2023-02-07 08:13:48] 2023-02-07 08:13:48 ESC[33mWARNESC[39m: Disabled transition “update_notifications”
[2023-02-07 08:13:48] 2023-02-07 08:13:48 ESC[33mWARNESC[39m: Disabled transition “update_scheduled_reports”
[2023-02-07 08:13:48] 2023-02-07 08:13:48 ESC[33mWARNESC[39m: Disabled transition “resolve_pending”
[2023-02-07 08:13:48] 2023-02-07 08:13:48 ESC[33mWARNESC[39m: Disabled transition “muting”
[2023-02-07 08:13:48] 2023-02-07 08:13:48 ESC[33mWARNESC[39m: Disabled transition “mark_for_outbound”
[2023-02-07 08:13:48] 2023-02-07 08:13:48 ESC[32mINFOESC[39m: transitions: processing enabled
[2023-02-07 08:13:48] 2023-02-07 08:13:48 ESC[32mINFOESC[39m: startup complete.
[2023-02-07 08:13:48] 2023-02-07 08:13:48 ESC[32mINFOESC[39m: checking schedule again in 4 minutes
[2023-02-07 08:13:49] 2023-02-07 08:13:49 ESC[32mINFOESC[39m: saving tombstone for horti-upgrade
[2023-02-07 08:18:00] 2023-02-07 08:18:00 ESC[32mINFOESC[39m: checking schedule again in 5 minutes

From the startup logs you have provided, these error messages can be relevant:

nginx: [emerg] SSL_CTX_use_PrivateKey_file("/srv/settings/medic-core/nginx/private/custom.key") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/srv/settings/medic-core/nginx/private/custom.key','r') error:20074002:BIO routines:FILE_CTRL:system lib error:140B0002:SSL routines:SSL_CTX_use_PrivateKey_file:system lib)
nginx: [emerg] host not found in upstream "haproxy:5984" in /srv/software/medic-core/v2.1.1/x64/etc/nginx/nginx.conf:20

Have you looked at the certificates? Also the couchdb seems to be failing.

@yuv would you be able to look into this tomorrow?

Hi @Marcelo_De_Guzman ,
I took a look at the logs you provided and the log doesn’t appear to be recent one which makes it difficult to see what’s happening across these services. I could only see logs up to February 21 on the pastebin link you provided. Also, the log you’ve pasted is from 2023-02-07 which is more than a year old. Can you please provide the latest log. If possible from the time when you started to see the logs for the first time. If that’s way too past in the future, please provide most recent logs for these services.

Hi @yuv ,

This is the last record on medic-sentinel log.

[2024-06-30 23:19:30] 2024-06-30 23:19:30 INFO: Waiting for API to be ready…
[2024-06-30 23:19:40] 2024-06-30 23:19:40 INFO: Waiting for API to be ready…
[2024-06-30 23:19:50] 2024-06-30 23:19:50 INFO: Waiting for API to be ready…
[2024-06-30 23:20:00] 2024-06-30 23:20:00 INFO: Waiting for API to be ready…
[2024-06-30 23:20:10] 2024-06-30 23:20:10 INFO: Waiting for API to be ready…
[2024-06-30 23:20:20] 2024-06-30 23:20:20 INFO: Waiting for API to be ready…
[2024-06-30 23:20:30] 2024-06-30 23:20:30 INFO: Waiting for API to be ready…
[2024-06-30 23:20:40] 2024-06-30 23:20:40 INFO: Waiting for API to be ready…
[2024-06-30 23:20:50] 2024-06-30 23:20:50 INFO: Waiting for API to be ready…
[2024-06-30 23:21:00] 2024-06-30 23:21:00 INFO: Waiting for API to be ready…
[2024-06-30 23:21:10] 2024-06-30 23:21:10 INFO: Waiting for API to be ready…
[2024-06-30 23:21:20] 2024-06-30 23:21:20 INFO: Waiting for API to be ready…
[2024-06-30 23:21:30] 2024-06-30 23:21:30 INFO: Waiting for API to be ready…
[2024-06-30 23:21:40] 2024-06-30 23:21:40 INFO: Waiting for API to be ready…
[2024-06-30 23:21:50] 2024-06-30 23:21:50 INFO: Waiting for API to be ready…
[2024-06-30 23:22:00] 2024-06-30 23:22:00 INFO: Waiting for API to be ready…
[2024-06-30 23:22:10] 2024-06-30 23:22:10 INFO: Waiting for API to be ready…
[2024-06-30 23:22:20] 2024-06-30 23:22:20 INFO: Waiting for API to be ready…
[2024-06-30 23:22:30] 2024-06-30 23:22:30 INFO: Waiting for API to be ready…
[2024-06-30 23:22:40] 2024-06-30 23:22:40 INFO: Waiting for API to be ready…
[2024-06-30 23:22:50] 2024-06-30 23:22:50 INFO: Waiting for API to be ready…
[2024-06-30 23:23:00] 2024-06-30 23:23:00 INFO: Waiting for API to be ready…
[2024-06-30 23:23:10] 2024-06-30 23:23:10 INFO: Waiting for API to be ready…
[2024-06-30 23:23:20] 2024-06-30 23:23:20 INFO: Waiting for API to be ready…
[2024-06-30 23:23:30] 2024-06-30 23:23:30 INFO: Waiting for API to be ready…
[2024-06-30 23:23:40] 2024-06-30 23:23:40 INFO: Waiting for API to be ready…
[2024-06-30 23:23:50] 2024-06-30 23:23:50 INFO: Waiting for API to be ready…
[2024-06-30 23:24:00] 2024-06-30 23:24:00 INFO: Waiting for API to be ready…
[2024-06-30 23:24:10] 2024-06-30 23:24:10 INFO: Waiting for API to be ready…
[2024-06-30 23:24:20] 2024-06-30 23:24:20 INFO: Waiting for API to be ready…
[2024-06-30 23:24:30] 2024-06-30 23:24:30 INFO: Waiting for API to be ready…
[2024-06-30 23:24:40] 2024-06-30 23:24:40 INFO: Waiting for API to be ready…
[2024-06-30 23:24:51] 2024-06-30 23:24:51 INFO: Waiting for API to be ready…
[2024-06-30 23:25:01] 2024-06-30 23:25:01 INFO: Waiting for API to be ready…
[2024-06-30 23:25:11] 2024-06-30 23:25:11 INFO: Waiting for API to be ready…
[2024-06-30 23:25:21] 2024-06-30 23:25:21 INFO: Waiting for API to be ready…
[2024-06-30 23:25:31] 2024-06-30 23:25:31 INFO: Waiting for API to be ready…
[2024-06-30 23:25:41] 2024-06-30 23:25:41 INFO: Waiting for API to be ready…
[2024-06-30 23:25:51] 2024-06-30 23:25:51 INFO: Waiting for API to be ready…
[2024-06-30 23:26:01] 2024-06-30 23:26:01 INFO: Waiting for API to be ready…
[2024-06-30 23:26:11] 2024-06-30 23:26:11 INFO: Waiting for API to be ready…
[2024-06-30 23:26:21] 2024-06-30 23:26:21 INFO: Waiting for API to be ready…
[2024-06-30 23:26:31] 2024-06-30 23:26:31 INFO: Waiting for API to be ready…
[2024-06-30 23:26:41] 2024-06-30 23:26:41 INFO: Waiting for API to be ready…
[2024-06-30 23:26:51] 2024-06-30 23:26:51 INFO: Waiting for API to be ready…
[2024-06-30 23:27:01] 2024-06-30 23:27:01 INFO: Waiting for API to be ready…
[2024-06-30 23:27:11] 2024-06-30 23:27:11 INFO: Waiting for API to be ready…
[2024-06-30 23:27:21] 2024-06-30 23:27:21 INFO: Waiting for API to be ready…
[2024-06-30 23:27:31] 2024-06-30 23:27:31 INFO: Waiting for API to be ready…
[2024-06-30 23:27:41] 2024-06-30 23:27:41 INFO: Waiting for API to be ready…
[2024-06-30 23:27:51] 2024-06-30 23:27:51 INFO: Waiting for API to be ready…
[2024-06-30 23:28:01] 2024-06-30 23:28:01 INFO: Waiting for API to be ready…
[2024-06-30 23:28:11] 2024-06-30 23:28:11 INFO: Waiting for API to be ready…
[2024-06-30 23:28:21] 2024-06-30 23:28:21 INFO: Waiting for API to be ready…
[2024-06-30 23:28:31] 2024-06-30 23:28:31 INFO: Waiting for API to be ready…
[2024-06-30 23:28:41] 2024-06-30 23:28:41 INFO: Waiting for API to be ready…
[2024-06-30 23:28:51] 2024-06-30 23:28:51 INFO: Waiting for API to be ready…
[2024-06-30 23:29:01] 2024-06-30 23:29:01 INFO: Waiting for API to be ready…
[2024-06-30 23:29:11] 2024-06-30 23:29:11 INFO: Waiting for API to be ready…
[2024-06-30 23:29:21] 2024-06-30 23:29:21 INFO: Waiting for API to be ready…
[2024-06-30 23:29:31] 2024-06-30 23:29:31 INFO: Waiting for API to be ready…
[2024-06-30 23:29:41] 2024-06-30 23:29:41 INFO: Waiting for API to be ready…
[2024-06-30 23:29:51] 2024-06-30 23:29:51 INFO: Waiting for API to be ready…
[2024-06-30 23:30:01] 2024-06-30 23:30:01 INFO: Waiting for API to be ready…
[2024-06-30 23:30:11] 2024-06-30 23:30:11 INFO: Waiting for API to be ready…
[2024-06-30 23:30:21] 2024-06-30 23:30:21 INFO: Waiting for API to be ready…
[2024-06-30 23:30:31] 2024-06-30 23:30:31 INFO: Waiting for API to be ready…
[2024-06-30 23:30:41] 2024-06-30 23:30:41 INFO: Waiting for API to be ready…
[2024-06-30 23:30:51] 2024-06-30 23:30:51 INFO: Waiting for API to be ready…
[2024-06-30 23:31:01] 2024-06-30 23:31:01 INFO: Waiting for API to be ready…
[2024-06-30 23:31:11] 2024-06-30 23:31:11 INFO: Waiting for API to be ready…
[2024-06-30 23:31:21] 2024-06-30 23:31:21 INFO: Waiting for API to be ready…
[2024-06-30 23:31:31] 2024-06-30 23:31:31 INFO: Waiting for API to be ready…
[2024-06-30 23:31:41] 2024-06-30 23:31:41 INFO: Waiting for API to be ready…
[2024-06-30 23:31:51] 2024-06-30 23:31:51 INFO: Waiting for API to be ready…
[2024-06-30 23:32:01] 2024-06-30 23:32:01 INFO: Waiting for API to be ready…
[2024-06-30 23:32:11] 2024-06-30 23:32:11 INFO: Waiting for API to be ready…
[2024-06-30 23:32:21] 2024-06-30 23:32:21 INFO: Waiting for API to be ready…
[2024-06-30 23:32:31] 2024-06-30 23:32:31 INFO: Waiting for API to be ready…
[2024-06-30 23:32:41] 2024-06-30 23:32:41 INFO: Waiting for API to be ready…
[2024-06-30 23:32:51] 2024-06-30 23:32:51 INFO: Waiting for API to be ready…
[2024-06-30 23:33:01] 2024-06-30 23:33:01 INFO: Waiting for API to be ready…
[2024-06-30 23:33:11] 2024-06-30 23:33:11 INFO: Waiting for API to be ready…
[2024-06-30 23:33:21] 2024-06-30 23:33:21 INFO: Waiting for API to be ready…
[2024-06-30 23:33:31] 2024-06-30 23:33:31 INFO: Waiting for API to be ready…
[2024-06-30 23:33:41] 2024-06-30 23:33:41 INFO: Waiting for API to be ready…
[2024-06-30 23:33:51] 2024-06-30 23:33:51 INFO: Waiting for API to be ready…
[2024-06-30 23:34:01] 2024-06-30 23:34:01 INFO: Waiting for API to be ready…
[2024-06-30 23:34:11] 2024-06-30 23:34:11 INFO: Waiting for API to be ready…
[2024-06-30 23:34:21] 2024-06-30 23:34:21 INFO: Waiting for API to be ready…
[2024-06-30 23:34:31] 2024-06-30 23:34:31 INFO: Waiting for API to be ready…
[2024-06-30 23:34:41] 2024-06-30 23:34:41 INFO: Waiting for API to be ready…
[2024-06-30 23:34:51] 2024-06-30 23:34:51 INFO: Waiting for API to be ready…
[2024-06-30 23:35:01] 2024-06-30 23:35:01 INFO: Waiting for API to be ready…
[2024-06-30 23:35:11] 2024-06-30 23:35:11 INFO: Waiting for API to be ready…
[2024-06-30 23:35:21] 2024-06-30 23:35:21 INFO: Waiting for API to be ready…
[2024-06-30 23:35:31] 2024-06-30 23:35:31 INFO: Waiting for API to be ready…
[2024-06-30 23:35:41] 2024-06-30 23:35:41 INFO: Waiting for API to be ready…
[2024-06-30 23:35:51] 2024-06-30 23:35:51 INFO: Waiting for API to be ready…
[2024-06-30 23:36:01] 2024-06-30 23:36:01 INFO: Waiting for API to be ready…
[2024-06-30 23:36:11] 2024-06-30 23:36:11 INFO: Waiting for API to be ready…
[2024-06-30 23:36:21] 2024-06-30 23:36:21 INFO: Waiting for API to be ready…
[2024-06-30 23:36:31] 2024-06-30 23:36:31 INFO: Waiting for API to be ready…
[2024-06-30 23:36:41] 2024-06-30 23:36:41 INFO: Waiting for API to be ready…
[2024-06-30 23:36:51] 2024-06-30 23:36:51 INFO: Waiting for API to be ready…
[2024-06-30 23:37:01] 2024-06-30 23:37:01 INFO: Waiting for API to be ready…
[2024-06-30 23:37:11] 2024-06-30 23:37:11 INFO: Waiting for API to be ready…
[2024-06-30 23:37:21] 2024-06-30 23:37:21 INFO: Waiting for API to be ready…
[2024-06-30 23:37:31] 2024-06-30 23:37:31 INFO: Waiting for API to be ready…
[2024-06-30 23:37:41] 2024-06-30 23:37:41 INFO: Waiting for API to be ready…
[2024-06-30 23:37:51] 2024-06-30 23:37:51 INFO: Waiting for API to be ready…
[2024-06-30 23:38:01] 2024-06-30 23:38:01 INFO: Waiting for API to be ready…
[2024-06-30 23:38:11] 2024-06-30 23:38:11 INFO: Waiting for API to be ready…
[2024-06-30 23:38:21] 2024-06-30 23:38:21 INFO: Waiting for API to be ready…
[2024-06-30 23:38:31] 2024-06-30 23:38:31 INFO: Waiting for API to be ready…
[2024-06-30 23:38:41] 2024-06-30 23:38:41 INFO: Waiting for API to be ready…
[2024-06-30 23:38:51] 2024-06-30 23:38:51 INFO: Waiting for API to be ready…
[2024-06-30 23:39:01] 2024-06-30 23:39:01 INFO: Waiting for API to be ready…
[2024-06-30 23:39:11] 2024-06-30 23:39:11 INFO: Waiting for API to be ready…
[2024-06-30 23:39:21] 2024-06-30 23:39:21 INFO: Waiting for API to be ready…
[2024-06-30 23:39:31] 2024-06-30 23:39:31 INFO: Waiting for API to be ready…
[2024-06-30 23:39:41] 2024-06-30 23:39:41 INFO: Waiting for API to be ready…
[2024-06-30 23:39:51] 2024-06-30 23:39:51 INFO: Waiting for API to be ready…
[2024-06-30 23:40:01] 2024-06-30 23:40:01 INFO: Waiting for API to be ready…
[2024-06-30 23:40:11] 2024-06-30 23:40:11 INFO: Waiting for API to be ready…
[2024-06-30 23:40:21] 2024-06-30 23:40:21 INFO: Waiting for API to be ready…
[2024-06-30 23:40:31] 2024-06-30 23:40:31 INFO: Waiting for API to be ready…
[2024-06-30 23:40:41] 2024-06-30 23:40:41 INFO: Waiting for API to be ready…
[2024-06-30 23:40:51] 2024-06-30 23:40:51 INFO: Waiting for API to be ready…
[2024-06-30 23:41:01] 2024-06-30 23:41:01 INFO: Waiting for API to be ready…
[2024-06-30 23:41:11] 2024-06-30 23:41:11 INFO: Waiting for API to be ready…
[2024-06-30 23:41:21] 2024-06-30 23:41:21 INFO: Waiting for API to be ready…
[2024-06-30 23:41:31] 2024-06-30 23:41:31 INFO: Waiting for API to be ready…
[2024-06-30 23:41:41] 2024-06-30 23:41:41 INFO: Waiting for API to be ready…
[2024-06-30 23:41:51] 2024-06-30 23:41:52 INFO: Waiting for API to be ready…
[2024-06-30 23:42:02] 2024-06-30 23:42:02 INFO: Waiting for API to be ready…
[2024-06-30 23:42:12] 2024-06-30 23:42:12 INFO: Waiting for API to be ready…
[2024-06-30 23:42:22] 2024-06-30 23:42:22 INFO: Waiting for API to be ready…
[2024-06-30 23:42:32] 2024-06-30 23:42:32 INFO: Waiting for API to be ready…
[2024-06-30 23:42:42] 2024-06-30 23:42:42 INFO: Waiting for API to be ready…
[2024-06-30 23:42:52] 2024-06-30 23:42:52 INFO: Waiting for API to be ready…
[2024-06-30 23:43:02] 2024-06-30 23:43:02 INFO: Waiting for API to be ready…
[2024-06-30 23:43:12] 2024-06-30 23:43:12 INFO: Waiting for API to be ready…
[2024-06-30 23:43:22] 2024-06-30 23:43:22 INFO: Waiting for API to be ready…
[2024-06-30 23:43:32] 2024-06-30 23:43:32 INFO: Waiting for API to be ready…
[2024-06-30 23:43:42] 2024-06-30 23:43:42 INFO: Waiting for API to be ready…
[2024-06-30 23:43:52] 2024-06-30 23:43:52 INFO: Waiting for API to be ready…
[2024-06-30 23:44:02] 2024-06-30 23:44:02 INFO: Waiting for API to be ready…
[2024-06-30 23:44:12] 2024-06-30 23:44:12 INFO: Waiting for API to be ready…

Hi @yuv and @binod ,

I tried just to restart it and it works, What is just happened?

I used this command : sudo systemctl restart docker

Hi @Marcelo_De_Guzman , glad to know it worked after restart. In order to what had happened, we should also look at API log since it appears that Sentinel was waiting for API to be ready. If you have this issue next time, please attach latest Sentinel and API logs and we can debug from there.

Hi @yuv ,

I have another issue with this CHT Error 404 not found,

this time it has error.

[stack]: ‘Error: CouchDB security seems to be misconfigured, see: cht-core/DEVELOPMENT.md at master · medic/cht-core · GitHub at ClientRequest.net.get (/srv/software/medic-api/md5-cdTbX9bB8ZfHZmsqbv4Zw==/node_modules/@medic/server-checks/src/checks.js:63:16)\n at Object.onceWrapper (events.js:315:30)\n at emitOne (events.js:116:13)\n at ClientRequest.emit (events.js:211:7)\n at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:543:21)\n at HTTPParser.parserOnHeadersComplete (_http_common.js:112:17)\n at Socket.socketOnData (_http_client.js:440:20)\n at emitOne (events.js:116:13)\n at Socket.emit (events.js:211:7)\n at addChunk (_stream_readable.js:263:12)’,
[2024-05-21 14:56:48] [message]: ‘CouchDB security seems to be misconfigured, see: cht-core/DEVELOPMENT.md at master · medic/cht-core · GitHub’ }
[2024-05-21 14:56:51] 2024-05-21 14:56:51 INFO: Running server checks…

How to fix this one?

This one is our staging medic, we are testing the changes here first before pushing to production.

Hi @Marcelo_De_Guzman , Can you explain which CHT version are you using? Was it a fresh installation of CHT or upgrade from previous version? How did you install CHT on this environment? Using docker helper or using a standalone Couchdb setup? For me it looks like, you’ve standalone or custom couchdb instance running.

Can you try applying this setting on your couchdb installation if your couchdb was standalone installation?

it was not a fresh installation, it was just another CHT, we are using that one as staging site. We are developing forms, and then on this site (test-flourish.caremin.com), we tested it out and having approval. Once approved and the forms are working fine, we are gonna push it to production.

Sure, will that that setting. Is that the whole .ini file or line 21 to 32 only?

For now, Line 21 to 32 and restart couchdb or all services.

Hi @Marcelo_De_Guzman , checking on if this problem has been fixed after we identified that the server was low on space and we added more space to the server.

Hi @yuv,

Unfortunately after we increased the space, it was still error like 404.

I have a question. This is only a staging or test instance, Can I somehow re-install the medic here? and then push all my updates from the production?

Hi @Marcelo_De_Guzman , yes, please try installing the clean instance of CHT (same version as your production one). If your production is on 3.x, this guide can be helpful. For 4.x, you can follow from here.

Hi @yuv, @binod

Right now, I have most of the requirements on AWS that is stored.

What is the simplest process to re-do it, it is remove the medic-os and haproxy and re-install again, then push the forms that is working right now on the production? Do you think this will work? and gave me less time to install it again?

Thanks.

remove the medic-os and haproxy and re-install again

Yes, the self-hosting documentation for 3.x includes steps for cleanup as well:

@binod

I already remove the medic-os and haproxy, and follow the instruction.

And now, this is the problem

@Marcelo_De_Guzman and I connected and we installed 3.9 using this instruction. We had to run docker network prune -f as well to remove the old network.