- About PTK
- Quick Start
- Guidance
- Preparing Configuration File
- Checking the System
- Deploy Database Cluster
- Manage Clusters
- Show Cluster List
- Show Cluster Status
- Start Database
- Stop Database
- Restart Database
- Rebuild Database
- Switchover
- Failover
- Show Plugin Information
- Install Plugins
- Upgrade Database
- Scale-out Cluster
- Scale-in Cluster
- Show Database HBA
- Set Database HBA
- Show Database Parameters
- Set Database Parameters
- Show Cluster Topology Configuration
- Show Cluster Meta Information
- Update Cluster Comment
- Update Database IP
- Role Management
- Install CM
- Uninstall CM
- Manage Cluster VIP
- Install MogHA Service
- Uninstall MogHA Service
- Rename Cluster
- Create Empty Cluster
- Throw Out A Node
- Takeover A Node
- Manage Cluster
- Uninstall Database Cluster
- Collect OS Information
- Download MogDB Installer
- Encrypt Sensitive Information
- Upgrade PTK
- PTKC
- Compatible With Higher Versions of MogDB
- Reference
- Samples of Configuration Files
- Commands
- ptk
- ptk completion
- ptk view-static-config
- ptk init-cluster
- ptk collect
- ptk rec-guc
- ptk cache
- ptk gen-ptkc
- ptk manage
- ptk demo
- ptk meta
- ptk version
- ptk self
- ptk gen-om-xml
- ptk env
- ptk gen-static-config
- ptk cluster
- ptk cluster createdb
- ptk cluster uninstall-compat-tools
- ptk cluster install-compat-tools
- ptk cluster install-mogila
- ptk cluster rename
- ptk cluster throwout
- ptk cluster takeover
- ptk cluster uninstall-cm
- ptk cluster install-cm
- ptk cluster gen-cert-files
- ptk cluster load-cm-vip
- ptk cluster del-kerberos-auth
- ptk cluster add-kerberos-auth
- ptk cluster uninstall-kerberos-server
- ptk cluster install-kerberos-server
- ptk cluster is-in-upgrade
- ptk cluster upgrade-rollback
- ptk cluster upgrade-commit
- ptk cluster upgrade
- ptk cluster demote
- ptk cluster promote
- ptk cluster refresh
- ptk cluster shell
- ptk cluster modify-comment
- ptk cluster show-config
- ptk cluster set-guc
- ptk cluster show-guc
- ptk cluster set-hba
- ptk cluster show-hba
- ptk cluster scale-out
- ptk cluster scale-in
- ptk cluster uninstall-mogha
- ptk cluster install-mogha
- ptk cluster list-plugins
- ptk cluster install-plugin
- ptk cluster inspect
- ptk cluster failover
- ptk cluster switchover
- ptk cluster build
- ptk cluster status
- ptk cluster restart
- ptk cluster stop
- ptk cluster start
- ptk uninstall
- ptk ls
- ptk install
- ptk exec
- ptk template
- ptk encrypt
- ptk checkos
- ptk download
- ptk candidate
- Troubleshooting
- FAQ
- Release Notes
- Community
- Appendix: YAML Syntax
Troubleshooting
Error Code Starting with 4xxx
PTK-4001
The user and user group configurations of the corresponding server cannot be set to root. You need to change them to common users.
PTK-4002
An unreasonable port number is used in a configuration file. PTK only accepts port numbers within the range [1024, 65534].
PTK-4003
The IP address is invalid.
PTK-4004
The directory configured for data directory (data_dir) in the configuration file cannot be a subdirectory of an application directory (app_dir). You need to modify the data directory.
PTK-4005
The directory prompted is a relative path. PTK is operated remotely, and the relative path is an unreliable path. Therefore, you need to change the relative path to an absolute path.
PTK-4006
The directory contains illegal characters. Check the corresponding fields in the configuration file.
PTK-4007
An invalid database role is specified in the configuration file. Ensure that the database role is one of primary, standby, and cascade_standby.
PTK-4008
Invalid URL
PTK-4010
The target system does not have necessary tools installed and cannot be checked. Please install the required tools on the target system.
PTK-4011
Necessary parameters are missing in the command . You can run the --help command to view the usage description.
PTK-4012
The cluster name is already used. Please use a new name.
PTK-4013
The port is unavailable. You can disable the process that occupies the port or use a new port.
PTK-4014
The release information of the operating system on different servers in the same cluster is inconsistent. PTK strongly recommends that the operating systems of all servers in the cluster be consistent when you deploy a database cluster.
PTK-4015
The CPU architecture cannot be identified.
PTK-4017
The name string contains illegal characters. Names are allowed to contain only letters, numbers, hyphens (-), underscores (_), and dots (.) when defined.
PTK-4018
The cluster name should not be empty.
PTK-4019
The cluster name is PTK's internal reserved keyword, and please change it to another name.
PTK-4020
no database server is configured in a configuration file during installation.
PTK-4021
Invalid check item number is specified when the checkos command is run.
PTK-4022
When installing a database, you specify skip checking the operating system distribution, but you do not specify the path of the installation package, and PTK cannot automatically determine which installation package should be used. In the installation command, -p or --pkg can be used to specify the installation package path.
PTK-4023
No configuration file is specified. You can use -f to specify it.
PTK-4024
In the configuration file, the upstream instance of the database instance cannot be set as itself, and the IP address of another instance must be specified.
PTK-4025
The upstream instance IP address of a database instance is set in the configuration file, but the upstream instance IP address is not found in the current set. This is usually caused by an incorrect configuration of the upstream IP address.
PTK-4026
The database instance with the primary role is not found in the configuration file.
PTK-4027
The IP address of the primary database is set in the upstream of the cascaded backup in the configuration file. The upstream of the cascaded backup must be the IP address of the standby database.
PTK-4028
There are multiple database instance configurations with the primary role in the configuration file. Ensure that only one primary database exists in a cluster configuration.
PTK-4029
The IP address of the upstream instance of the standby database in the configuration file is not configured. If the role is cascade_standby, the upstream instance field upstream_host becomes mandatory.
PTK-4030
The cluster does not exist.
PTK-4031
The database password must contain 8 to 16 characters.
PTK-4032
The two passwords entered are inconsistent.
PTK-4033
The number of database instances in the configuration file exceeds 9. Due to the database limitation, the maximum number of instances in a cluster can be 9.
PTK-4034
The xlog directory in the configuration file cannot be a subdirectory of the database directory (data_dir).
PTK-4035
The ssh_option field must be set in the configuration file for all servers (remote servers) with non-local IP addresses (also not set in global), and the error will list the servers that are not configured.
PTK-4036
The password type field in the configuration file is not encrypted with PTK encrypt, and for security reasons, the password type field is not allowed to be submitted in plain text.
PTK-4037
Plug-in installation is not supported before MogDB 2.1.0 (no plug-in has been released).
PTK-4038
The user chose to cancel the confirmation during the interactive confirmation scenario.
PTK-4039
At least two servers need to be configured during CM cluster installation.
PTK-4040
The base directory (base_dir) is used for different instances of the same server in the configuration file.
PTK-4041
The database parameter enable_dcf=on cannot be set when a two-node CM cluster is installed.
PTK-4042
The user of the server is already in use by another cluster managed by PTK, and a user of a server is not allowed to install multiple database instances.
PTK-4043
The third_party_gateway_ip parameter needs to be configured in global.cm_option.cm_server_conf in the configuration file to specify the gateway IP address.
This error occurs when installing a two-node CM cluster and -y is specified during installation. This parameter is required for two-node CM clusters.
Therefore, you can manually configure the parameter in the configuration file, or remove the -y parameter and fill in the real-time interactive form with PTK.
PTK-4044
The data node is not running. PTK cluster status can be used to confirm the instance status.
PTK-4045
The user exits the interaction when the number specified retry times is exceeded.
PTK-4046
The host field of the server in the configuration file cannot be empty.
Error Code Starting with 5xxxx
PTK-50000
Runtime error of PTK when calling the system to execute the command. The cause of the error should be determined according to the actual error information.
PTK-50001
The bash script failed to execute on the target server.
PTK-50101
Serializing the configuration file failed.
PTK-50102
The deserialization of the configuration file failed.
PTK-50103
The configuration file fails to be saved locally.
PTK-50105
The specified data directory is already in use by a running database instance.
PTK-50106
The instance with the specified IP address is not found in the current cluster.
PTK-50107
The configuration file is empty.
PTK-50108
The instance with the user ID is not found in the current cluster.
PTK-50201
The directory already exists on the server.
PTK-50202
The directory fails to be created.
PTK-50203
The file fails to be created.
PTK-50204
The local metadata file fails to be read.
PTK-50205
The file already exists.
PTK-50206
The path contains illegal characters.
PTK-50207
The directory is empty.
PTK-50208
The temporary directory fails to be created.
PTK-50209
The specified cluster is not found.
PTK-50210
The directory does not exist.
PTK-50211
The file already exists.
PTK-50301
The user already exists.
PTK-50302
The user does not exist.
PTK-50303
The user group is not matched.
PTK-50304
The file or directory prompted does not belong to the specified user, that is, the ownership limit of the file is incorrect.
PTK-50305
The user does not have sudo permissions. This error code usually occurs in scenarios that depend on the permissions of the superuser.
PTK-50601
The request for the specified URL failed.
PTK-50602
The HTTP response failed to be read.
PTK-50603
The bonding information fails to be obtained.
PTK-50604
The detection of NIC information fails.
PTK-50801
The target system did not find the prompted CPU instruction set, and the absence of some necessary instruction sets may cause the database process to fail to start.
PTK-50802
The command is not found.
PTK-50803
Invalid sysctl configuration.
PTK-50804
RemoveIPC must be set to no.
PTK-50805
Specified dependencies are not found. You need to install them manually.
Other Errors
PTK sets error codes for internally fixed error types, but there are also other errors reported by dependent libraries or system during running.
These errors need to be rectified by viewing the corresponding system or running parameters according to the error prompt. We will also collect some scenario errors and list them on the FAQ page, but we may not collect the all.
If you can not solve the error in use, you can ask questions through the Q&A channel of Modb, our developers will pay attention and reply promptly. (Note that the tag ptk is added to the question).