Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
All solutions
    • All solutions for Managed Service for PostgreSQL
    • Restoring a Managed Service for PostgreSQL cluster after running out of free storage space
    • You are unable to delete your Managed Service for PostgreSQL cluster in the `DEAD` status if it has deletion protection enabled
    • Managed Service for PostgreSQL cluster switches to `UNKNOWN` once created
    • Resolving issues with updating configurations of clusters with `local-ssd` disks
    • Resolving the issue of cluster storage overflow with WAL logs
    • Resolving the `psql error could not translate host name to address nodename nor servname provided, or not known` error
    • Resolving the `Unrecognized configuration parameter stats_temp_directory` error
    • Resolving the `max_connections conn_limit is too high` error
    • Resolving the `Must be superuser to create this extension` error
    • Fixing the `terminating connection due to administrator command` and `ERROR: odyssey: remote server read/write error` errors
    • Resolving the `422 UNPROCESSABLE ENTITY The specified extension <'ext_name'> is not present in shared_preload_libraries` error
    • How `Conn limit` works
    • How to set up SQL query filtering
    • How to enable SQL query logging

In this article:

  • Issue description
  • Solution
  1. Managed Service for PostgreSQL
  2. Fixing the `terminating connection due to administrator command` and `ERROR: odyssey: remote server read/write error` errors

Fixing these errors: terminating connection due to administrator command and ERROR: odyssey: remote server read/write error

Written by
Yandex Cloud
Updated at December 17, 2025
  • Issue description
  • Solution

Issue descriptionIssue description

A Managed Service for PostgreSQL cluster transaction ends with one of these errors: terminating connection due to administrator command or "ERROR: odyssey: remote server read/write error sefc96761678e: (null) SSL SYSCALL error: EOF detected".

SolutionSolution

You may get such errors when the transaction failed to complete over 12 hours. Yandex Cloud has certain limits for session timeout.

To increase it, change the Session duration timeout in the cluster settings. For more information on it, see this guide. Please note the time is specified in milliseconds.

Changing this value will not affect the cluster operation in any way.

Note

When restoring a cluster from backup, the Session duration timeout value is reset to the default value, i.e., 12 hours.

Was the article helpful?

Previous
Resolving the `Must be superuser to create this extension` error
Next
Resolving the `422 UNPROCESSABLE ENTITY The specified extension <'ext_name'> is not present in shared_preload_libraries` error
© 2025 Direct Cursus Technology L.L.C.