PostgreSQL 集群狀態損壞 (No Machine, No Image) 問題

1
  1. 應用程式名稱： ecanapidb
  2. 問題： 資料庫應用程式卡在 suspended 狀態，且無法通過 CLI 啟動 Machine。
  3. 核心問題：

    • fly machine list -a ecanapidb 顯示：No machines are available。

    • 嘗試使用 fly machine run 啟動新 Machine 時，無論使用哪個標籤 (flyio/postgres:15、flyio/postgres-flex:16.1 等)，都收到 Could not find image 的錯誤。

    • 嘗試使用 fly pg restart -a ecanapidb 收到 Error: no active leader found。

  4. 解決方案請求： 請求 Fly.io 服務端團隊 手動創建一個新的 Machine，並將現有的 Volume (pg_data) 附加到該 Machine 上。
2

It looks like your last machine (now destroyed) is created with flyio/postgres-flex:17.2, could you try recreating using that image instead? That machine being destroyed is also why your app shows up as suspended and why fly pg restart doesn’t work.

Please note that database clusters created via fly pg (postgres-flex) are unmanaged. We do offer a managed alternative, if you prefer a more managed experience.

3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.