diff --git a/product/en/docs-mogdb/v2.1/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin.md b/product/en/docs-mogdb/v2.1/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin.md index 826b4c9e80ae356c1fdcbeec469ab20ffdd8a4eb..8c4d069a4a15d5306f034bbbd55b640c82e3f568 100644 --- a/product/en/docs-mogdb/v2.1/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin.md +++ b/product/en/docs-mogdb/v2.1/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin.md @@ -17,6 +17,24 @@ MogDB provides gs_install_plugin for installing plugins. Currently, the supporte The deployment of MogDB with one primary node and multiple standby nodes has been completed. +> **release patch notes**: +> +> There is a known bug in version 2.1 of this tool that causes installation failure due to unrecognized plug-in packages. +> Please do the following to fix the patch before using this tool and then proceed with the subsequent plugin installation (for 2.1.x). +> +> - When the extranet is accessible. +> +> 1. switch to the user who installed the database (e.g.: omm): `su - omm` +> 2. perform online repair: `cd $GPHOME && curl https://cdn-mogdb.enmotech.com/mogdb-media/2.1.1/om_plugin_install_v2.1.1.patch | patch -p1` +> +> - When unable to access the extranet. +> +> 1. Please download the patch file [om_plugin_install_v2.1.1.patch](https://cdn-mogdb.enmotech.com/mogdb-media/2.1.1/om_plugin_install_v2.1.1.patch) from a server with internet access first, and then copy the patch file to the server to be repaired. +> 2. Switch to the user who installed the database (e.g.: omm): `su - omm` +> 3. Execute `cd $GPHOME && patch -p1 < [replace Patch file path here]` + +  + ## Syntax ``` @@ -150,7 +168,6 @@ gs_install_plugin [-h] [-X XML] [--all] [--dblink] [--pg_trgm] [--wal2json] [--p ```bash /opt/software/mogdb/script/gs_install_plugin -X /opt/software/mogdb/clusterconfig.xml --all - # When the installation is successful, the output is as follows: SUCCESS: dblink. SUCCESS: pg_trgm. diff --git a/product/en/docs-mogdb/v2.1/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin_local.md b/product/en/docs-mogdb/v2.1/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin_local.md index b8454731b5be75b32b237250a4425cfa046779f2..cec6b7e2bd2e89f684b03ce16e72e44001c4cbb5 100644 --- a/product/en/docs-mogdb/v2.1/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin_local.md +++ b/product/en/docs-mogdb/v2.1/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin_local.md @@ -17,6 +17,24 @@ MogDB provides gs_install_plugin_local for installing plugins. Currently, the su The deployment of MogDB single node has been completed. +> **release patch notes**: +> +> There is a known bug in version 2.1 of this tool that causes installation failure due to unrecognized plug-in packages. +> Please do the following to fix the patch before using this tool and then proceed with the subsequent plugin installation (for 2.1.x). +> +> - When the extranet is accessible. +> +> 1. switch to the user who installed the database (e.g.: omm): `su - omm` +> 2. perform online repair: `cd $GPHOME && curl https://cdn-mogdb.enmotech.com/mogdb-media/2.1.1/om_plugin_install_v2.1.1.patch | patch -p1` +> +> - When unable to access the extranet. +> +> 1. Please download the patch file [om_plugin_install_v2.1.1.patch](https://cdn-mogdb.enmotech.com/mogdb-media/2.1.1/om_plugin_install_v2.1.1.patch) from a server with internet access first, and then copy the patch file to the server to be repaired. +> 2. Switch to the user who installed the database (e.g.: omm): `su - omm` +> 3. Execute `cd $GPHOME && patch -p1 < [replace Patch file path here]` + +  + ## Syntax ``` @@ -141,7 +159,6 @@ gs_install_plugin_local [-h] [-X XML] [--all] [--dblink] [--pg_trgm] [--wal2json ```bash /opt/software/mogdb/script/gs_install_plugin_local -X /opt/software/mogdb/clusterconfig.xml --all - # When the installation is successful, the output is as follows: SUCCESS: dblink. SUCCESS: pg_trgm.