GAUSS-02041 -- GAUSS-02050
GAUSS-02041: "could not fsync file '%s': %m"
SQLSTATE: XX000
Description: Files cannot be synchronized.
Solution: Resolve the problem based on concrete error codes.
GAUSS-02042: "could not read file '%s', read %d of %u: %m"
SQLSTATE: XX000
Description: Internal system error.
Solution:contact technical support
GAUSS-02043: "replication slot file '%s' has wrong magic %u instead of %u"
SQLSTATE: XX000
Description: The flag in the replication slot file does not match with the current supported version.
Solution: Check whether the replication slot file has been tampered with and whether a major version upgrade has been done for the current program version.
GAUSS-02044: "replication slot file '%s' has unsupported version %u"
SQLSTATE: XX000
Description: The version specified in the replication slot file does not match with the current supported version.
Solution: Check whether the replication slot file has been tampered with and whether a major version upgrade has been done for the current program version.
GAUSS-02045: "replication slot file '%s' has corrupted length %u"
SQLSTATE: XX000
Description: The read length in the replication slot file is different from the expected length.
Solution: Check whether the replication slot file has been tampered with and whether a major version upgrade has been done for the current program version.
GAUSS-02046: "replication slot file %s: checksum mismatch, is %u, should be %u"
SQLSTATE: XX000
Description: The CRC check of the replication slot file fails.
Solution: Check whether the replication slot file has been tampered with.
GAUSS-02047: "too many replication slots active before shutdown"
SQLSTATE: XX000
Description: Too many replication slots are activated before the last database shutdown.
Solution: Check whether the value of max_replication_slots is too small. If yes, increase the value and try again.
GAUSS-02048: "wal receiver could not connect to the primary server,the connection info :%s : %s"
SQLSTATE: XX000
Description: The WAL receiver thread fails to connect to the primary server. Determine the reason based on the error message.
Solution: If you see a connection timeout error message, check if the connection is unstable due to high load on the current server. If a connection failure error message is displayed, ensure that the primary server is started.
GAUSS-02049: "could not receive database system version and protocol version from the primary server: %s"
SQLSTATE: XX000
Description: The standby server sends a version verification message to the primary server. The primary server returns a failure message. Resolve the problem based on the "%s" error message.
Solution: If the network connection times out, adjust the current network environment. If the primary server is overloaded, adjust services. If the primary server is shut down unexpectedly, identify the cause.
GAUSS-02050: "could not get the local protocol version, make sure the PG_PROTOCOL_VERSION is defined"
SQLSTATE: XX000
Description: The local version information fails to be obtained.
Solution: Ensure that the current memory is sufficient.
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