GAUSS-02011 -- GAUSS-02020
GAUSS-02011: "could not receive data from DATA stream: %s"
SQLSTATE: XX000
Description: During data replication between the primary and standby servers, the standby server detects primary-standby server connection errors. Resolve the problem based on the "%s" error message.
Solution:"1. If the network connection times out, adjust the current network environment. If the primary server is overloaded, adjust services. 2. If the primary server is shut down unexpectedly, identify the cause. "
GAUSS-02012: "data replication terminated by primary server :%s"
SQLSTATE: XX000
Description: The primary server terminates data replication to the standby server.
Solution:1. Check external causes.
GAUSS-02013: "could not send data to DATA stream: %s"
SQLSTATE: XX000
Description: During data transmission between the primary and standby servers, the standby server detects errors when sending data. Resolve the problem based on the "%s" error message.
Solution:"1. If the network connection times out, adjust the current network environment. If the primary server is overloaded, adjust services. 2. If the primary server is shut down unexpectedly, identify the cause. "
GAUSS-02014: "socket not open"
SQLSTATE: XX000
Description: Network exceptions occur during connection setup between the primary and standby server. The socket of the standby server is closed and an error is perceived.
Solution: Search the above error in logs to determine the concrete reason.
GAUSS-02015: "select() failed: %m"
SQLSTATE: XX000
Description: Select returns a failure.
Solution: Determine the root cause based on the error code. The error codes returned are standard error codes. See descriptions of related error codes by querying Help in the system.
GAUSS-02016: "replconninfo1 or replconninfo2 not configured."
SQLSTATE: XX000
Description: The configuration of replconninfo1 or replconninfo2 is empty in the postgresql.conf file.
Solution: Modify corresponding configuration options in the postgresql.conf file using the gs_guc tool.
GAUSS-02017: "terminating walreceiver process due to administrator command"
SQLSTATE: 57P01
Description: The walreceiver thread of the standby server receives the SIGTERM message. The error message is printed before the process exits.
Solution: Search logs to check whether the preceding operations are correct.
GAUSS-02018: "walreceiver still running according to shared memory state"
SQLSTATE: XX000
Description: Internal system error.
Solution: Contact technical support.
GAUSS-02019: "terminating walreceiver process due to the death of walrcvwriter"
SQLSTATE: XX000
Description: Internal system error.
Solution: Contact technical support.
GAUSS-02020: "terminating walreceiver due to timeout"
SQLSTATE: XX000
Description: The heartbeat between the primary and standby servers times out. The standby server disconnects from the primary server upon failing to detect the heartbeat.
Solution:"1. Determine the reason by checking the service load and network environment of the primary server. 2. Increase the value of wal_sender_timeout or wal_receiver_timeout or reduce service load as required. "
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot