diff options
Diffstat (limited to 'issues')
-rw-r--r-- | issues/non-deterministic-gn3-setup-on-tux01.gmi | 23 |
1 files changed, 20 insertions, 3 deletions
diff --git a/issues/non-deterministic-gn3-setup-on-tux01.gmi b/issues/non-deterministic-gn3-setup-on-tux01.gmi index 51d773c..e7cc067 100644 --- a/issues/non-deterministic-gn3-setup-on-tux01.gmi +++ b/issues/non-deterministic-gn3-setup-on-tux01.gmi @@ -1,4 +1,4 @@ -# GN3 Setup on tux01 - Non-Deterministic Behavior +q# GN3 Setup on tux01 - Non-Deterministic Behavior ## Tags @@ -6,10 +6,11 @@ * priority: high * type: ops, guix * keywords: gn3 +* status: closed -## Description: +## Description -Last week, during a pairing session, Zach and I attempted to set up GN3 on tux01 following the provided channels file: +Zach and Munyoki attempted to set up GN3 on tux01 following the provided channels file: ``` (list (channel @@ -51,3 +52,19 @@ cd genenetwork3/ Despite our efforts, attempting a CURL on GN3 using Zach's username consistently resulted in an empty response. Even when Zach switched to my user (bonfacem) and repeated the steps with my ".guix-extra-profile", the CURL still produced an empty result. We tried various troubleshooting steps, such as running the commands in a shell with no specific environment set up and using su to switch to bonfacem from Zach's userspace, but the issue persists. + +## Resolution + +The error caused was due to missing SSL certificates. This was resolved by exporting the right SSL paths before starting the server. The simple fix was adding: + +``` +export SSL_CERT_DIR="$GUIX_PROFILE/etc/ssl/certs" +export SSL_CERT_FILE="$GUIX_PROFILE/etc/ssl/certs/ca-certificates.crt" +export GIT_SSL_CAINFO="$SSL_CERT_FILE" +``` + +Also, debugging was difficult because of poor logging. This is being tracked here: + +=> issues/add-logging-to-rdf-endpoints.gmi + +* closed |