Issue

Can’t change the default RESTPP port (9000), or rest server will fail to start.


Affected versions:

  • 2.0.4 to 2.1.4


Solution:
If your TigerGraph version is 2.0.4, please contact TigerGraph to upgrade.
If your TigerGraph version is 2.1.4, please follow the steps below.


  1. gadmin stop -fy



  2. Patch IUM file ~/.gium/GSQL/Conf2Fabconf.py
    @@ -321,7 +321,10 @@ class FabConfig(object):
                     # now (Vis and GSQL Server doesn't need this), so for now we still generated NGINX config along with
                     # restpp
                     self.fabconf['NGINX']["services"] = {"port": self.none2int(self.iumconf['nginx.services.port'])}
    -            self.fabconf[upper_name]["port"] = self.backward_support("nginx.port",
    +            self.fabconf[upper_name]["port"] = self.backward_support("restpp.port",
    +                                                                     self.backward_support("restpp.port",
    +                                                                                           9000))
    +            self.fabconf[upper_name]["nginx"]["port"] = self.backward_support("restpp.port",
                                                                          self.backward_support("restpp.port",
                                                                                                9000))


  3. Patch IUM file ~/.gium/gsql_admin
    @@ -957,6 +957,7 @@ def run_configure_save_helper():
         config_file = Config.MODIFIED_CONFIG_FILE
         fab_config_file = GSQLGlobal.GSQL_CFG_FAB_DIR + "/configs/conf_tigergraph_fab.yaml"
         invalid_license_chars = re.compile('[^0-9a-f]')
    +    GSQLGlobal.cfg.dict['nginx.port']=GSQLGlobal.cfg.dict['restpp.port']


  4. Change IUM config to use 9006 (Here, we assume the port to be 9006)
    >> gadmin --config restpp.port
    --> to 9006
    
    >> gadmin config-apply
    
    >> gadmin restart -fy all ts3 admin
    
    


  5. If later you want to change to another port, please redo step 4.

    Note: If you are using a cluster, the patches in step 2 and 3 will be automatically applied to all the other nodes in the cluster during step 4.