Replies: 3 comments 1 reply
-
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS |
Beta Was this translation helpful? Give feedback.
-
docker compose psNAME IMAGE COMMAND SERVICE CREATED STATUS PORTS |
Beta Was this translation helpful? Give feedback.
-
solution: in docker-compose.yaml, the mount directory is "./volumes/db/data:/var/lib/postgresql/data", clean this directory using "rm -rf ./volumes/db/data". Reload the containers. |
Beta Was this translation helpful? Give feedback.
-
Self Checks
Content
Dify crushed with no message, i found that some container could not restart, Including the database
![Uploading 1.png…]()
The database logs are like this:
initdb: error: directory "/var/lib/postgresql/data/pgdata" exists but is not empty
initdb: hint: If you want to create a new database system, either remove or empty the directory "/var/lib/postgresql/data/pgdata" or run initdb with an argument other than "/var/lib/postgresql/data/pgdata".
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.
And i did not find the directory. Thank you for take care of this.
Beta Was this translation helpful? Give feedback.
All reactions