You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 29, 2024. It is now read-only.
I will sometimes get an error when Blockscout's Postgres is starting up related to data already existing. This blocks Blockscout from starting.
| The database cluster will be initialized with locale "en_US.utf8". │
│ The default database encoding has accordingly been set to "UTF8". │
│ The default text search configuration will be set to "english". │
│ │
│ Data page checksums are disabled. │
│ │
│ initdb: error: directory "/var/lib/postgresql/data" exists but is not empty │
│ If you want to create a new database system, either remove or empty │
│ the directory "/var/lib/postgresql/data" or run initdb │
│ with an argument other than "/var/lib/postgresql/data".
The text was updated successfully, but these errors were encountered:
MacOS runs a periodic cleaner on the temp directory that deletes files that haven't been used in 3 days. It only deletes files but not directories, so postgres was seeing that the data directory existed but the check for PG_VERSION failed.
steezeburger
changed the title
Persistent volumes for Blockscout Postgres may cause crash on startup
Persistent volumes for Blockscout Postgres can cause crash on startup on Macs
Aug 22, 2023
steezeburger
changed the title
Persistent volumes for Blockscout Postgres can cause crash on startup on Macs
Persistent volume for Blockscout's Postgres can crash on startup on Macs
Aug 22, 2023
I will sometimes get an error when Blockscout's Postgres is starting up related to data already existing. This blocks Blockscout from starting.
The text was updated successfully, but these errors were encountered: