EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB486926: A Collaboration server connection error occurs in Google Cloud Platform (GCP) private environments


Yixin Yang

Software Engineer, Senior • MicroStrategy


This article provides a solution for resolving a Collaboration server connection error in GCP private environments by editing the setenv.sh file and restarting all Library deployments.

Symptom

On the Library Admin page, a Collaboration server connection error appears in GCP private environments.
 

ka0PW0000002upJYAQ_0EMPW000009FOGB.jpeg

Solution

  • Access the Library container, via your GCP cluster management page.
     
  • Inside the Library container, navigate to
    /data/library/tomcat/bin
    and use
    nano
    to open
    setenv.sh
    for editing.
    
    nano /data/library/tomcat/bin/setenv.sh

  • Append the following snippet to
    setenv.sh
    . This script patches the URLs in the configuration file to correct the base URL format.
    
    for webapp in /usr/local/tomcat/webapps/*; do
       echo "Patching URLs in $webapp/WEB-INF/classes/config/configOverride.properties"
       sed -ci -E "s|(services.collaboration.baseURL=https://[^:]*):443([^0-9])|\1\2|g;" "$webapp/WEB-INF/classes/config/configOverride.properties"
    done
    

  • Save and close the file.
     
  • On the CGP cluster management page, get the library deployment namespace (
    mstr-env-env-[environment ID]
    ) and name (
    env-[environment ID]-library
    ). You need this information to restart the deployment.
    
    $ kubectl get deployments -A | grep library
    mstr-env-env-[environment ID]   env-[environment ID]-library                         1/1     1            1           1h

  • Restart the deployment.
    
    $ kubectl rollout restart deployment -n mstr-env-env-[environment ID] env-[environment ID]-library

  • Once Library is up, verify there is no error on the Library Admin page.
     
ka0PW0000002upJYAQ_0EMPW000009QHb7.jpeg

Comment

0 comments

Details

Knowledge Article

Published:

August 2, 2024

Last Updated:

August 8, 2024