Skip to main content
Yugabyte Help Center home page
YugabyteDB Managed Status Submit a request
Sign in
  1. Yugabyte
  2. Running YugabyteDB
  3. Administration

Administration

Administrative tasks and recommended usage patterns

  • YBController based backups failing with COMMAND FAILED and return code 1
  • Disk Usage tile shows "No Data" in YugabyteDB Anywhere's Universe page
  • Non default yugaware directory in Replicated install not reflected in YBA UI
  • Preflight check or Universe creation fails with "Sudo Access to Python:false"
  • Query Performance issue when using LZ4 compression
  • How to send logs & diagnostic data to Yugabyte Support
  • Can't advance the committed index across term boundaries until operations from the current term are replicated
  • Starting/stopping master and tserver with systemd
  • Re-Purpose an On-prem Node
  • How to control the number of connections from Spark.
  • Universe backup hangs after YugabyteDB Anywhere Upgrade to 2.16
  • "DB write/read test error" Alerts after upgrading to YBA 2.12.1 or newer.
  • Unable to perform health check causing Health Check Failure Alerts
  • Health check failure with YB-Controller server error - "Error calling ping; Error: UNAVAILABLE"
  • Enable YCQL Tracing for Long Running Queries
  • YBM Connection caps
  • Snapshot too old error when config flag ysql_enable_read_request_caching is enabled
  • Endpoint does not match, address: <IP-Address>, hostname: <IP-Address>
  • How to determine tablet count of a table in YugabyteDB Managed
  • How to manually add the Longitude and Lattitude to show the location of a universe
  • Error: The frame had a length of ###, but we only support messages up to ### bytes long.
  • Uninstall Replicated based Yugabyte Anywhere aka Yugabyte Platform from the Linux host
  • Resizing universe failed with UnauthorizedOperation DescribeInstanceTypes
  • Configuring backup S3 config failing with error "Request failed with status code 500"
  • Yugabyte Anywhere upgrade fail with "Cannot pin to release sequence" error.
  • Disabling Yedis by editing the universe_details_json in the Yugaware Postgres database
  • How to collect the YugabyteDB Anywhere (platform) logs?
  • Preventing scheduled backups from being expired unexpectedly
  • S3 Restore fails with status 77 | S3 error 403
  • How to get verbose logs for azcopy.
  • Next ›
  • Last »
Yugabyte