HENGSHI SENSE Installation FAQs
Installation Related Issues
Can the server hostname be modified after installation?
The server hostname cannot be changed after installation. If modification is required, please contact technical support for migration operations.
Specifically, for machines deploying Doris, the internal network IP cannot be changed either.
Insufficient Disk Space
[2023-05-06.11:19:13.150][hs_install:68][ ERROR ]: /opt/hengshi capacity is less than 10G, abort installation! Please check the disk or use larger disk
The issue is caused by insufficient disk space. After clearing up disk space or increasing disk capacity, proceed with the installation or upgrade process.
Can the middleware services used by HENGSHI be replaced?
The built-in modules of HENGSHI, including metadb, engine, minio, and redis, all support replacement with customers' own services to meet personalized needs:
- Replace metadb (Key point: configure
HS_PG_IF_EXTERNAL=true
and connection settings) - Replace engine (Key point: configure
HS_ENGINE_IF_EXTERNAL=true
and connection settings) - Replace minio (Key point: configure
HS_MINIO_IF_EXTERNAL=true
and connection settings) - Replace redis (Key point: configure
HS_REDIS_IF_EXTERNAL=true
and connection settings)
init-os Initialization Failed, User Lacks Sudo Privileges
[2023-05-06.11:31:19.337][hengshi@cluster1][hengshi-sense-bin:599][ INFO ]: internal pg metastore 10.10.10.xxx:54320
sudo: a password is required
INIT FAIL! : [dependent packages]
Grant sudo privileges to the deployment user
# Use a user with sudo privileges or the root user
echo "hengshi ALL=(ALL) NOPASSWD: ALL" >> /etc/sudoers
init engine failed, reinitialization operation
20250704:11:54:19:044695 gpinitsystem:m88:lvliang-[INFO]:-Starting the Master in admin mode
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[INFO]:-Commencing parallel build of primary segment instances
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[INFO]:-Spawning parallel processes batch [1], please wait...
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[INFO]:------------------------------------------------
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[INFO]:-Parallel process exit status
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[INFO]:------------------------------------------------
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[INFO]:-Total processes marked as completed = 0
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[INFO]:-Total processes marked as killed = 0
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[INFO]:-Total processes marked as failed = 0
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[INFO]:------------------------------------------------
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[INFO]:-Removing back out file
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[INFO]:-No errors generated from parallel processes
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[INFO]:-Restarting the Greenplum instance in production mode
File "/home/lvliang/tt3/lib/gpdb/gpdb/bin/gpstop", line 39
except ImportError, e:
^^^^^^^^^^^^^^
SyntaxError: multiple exception types must be parenthesized
File "/home/lvliang/tt3/lib/gpdb/gpdb/bin/gpstart", line 36
except ImportError, e:
^^^^^^^^^^^^^^
SyntaxError: multiple exception types must be parenthesized
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[WARN]:
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[WARN]:-Failed to start Greenplum instance; review gpstart output to
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[WARN]:- determine why gpstart failed and reinitialize cluster after resolving
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[WARN]:- issues. Not all initialization tasks have completed so the cluster
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[WARN]:- should not be used.
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[WARN]:-gpinitsystem will now try to stop the cluster
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[WARN]:
File "/home/lvliang/tt3/lib/gpdb/gpdb/bin/gpstop", line 39
except ImportError, e:
^^^^^^^^^^^^^^
SyntaxError: multiple exception types must be parenthesized
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[WARN]:-Non fatal error from Greenplum instance shutdown
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[WARN]:
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[WARN]:-Failed to start Greenplum instance; review gpstart output to
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[WARN]:- determine why gpstart failed and reinitialize cluster after resolving
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[WARN]:- issues. Not all initialization tasks have completed so the cluster
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[WARN]:- should not be used.
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[WARN]:
20250704:11:54:20:044695 gpinitsystem:m88:lvliang-[FATAL]: starting new instance failed; Script Exiting!
INIT FAIL! : [engine] /opt/hengshi/engine-cluster
Generally, look upwards along the error message for the cause of the error or the location of logs containing more error information. You can provide the error message and logs with more details to technical support for analysis.
Ubuntu 18.04 init engine failed
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 not found
The default environment of Ubuntu 18.04 may not have the necessary dependencies for Python 2.7 installed. Install the required dependencies and re-execute the initialization operation:
sudo apt install -y libpython2.7