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
I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
[FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
Please do not modify this template :) and fill in all the required fields.
1. Is this request related to a challenge you're experiencing? Tell me about your story.
After installing dify, run it, and the upper left corner keeps reporting an error:
2. Additional context or comments
I set 18GB of available memory for Docker;
The output of docker ps is as follows:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
4d771c44485f nginx:latest "sh -c 'cp /docker-e…" 22 minutes ago Up 21 minutes 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp docker-nginx-1
b9d49213ea00 langgenius/dify-api:1.0.0-beta.1 "/bin/bash /entrypoi…" 22 minutes ago Up 21 minutes 5001/tcp docker-api-1
033f4cf65e05 langgenius/dify-api:1.0.0-beta.1 "/bin/bash /entrypoi…" 22 minutes ago Up 21 minutes 5001/tcp docker-worker-1
f1e9acc9fda1 langgenius/dify-plugin-daemon:0.0.1-local "/bin/bash -c /app/e…" 22 minutes ago Up 21 minutes 0.0.0.0:5003->5003/tcp docker-plugin_daemon-1
d1b48c80bde7 postgres:15-alpine "docker-entrypoint.s…" 22 minutes ago Up 21 minutes (healthy) 0.0.0.0:5432->5432/tcp docker-db-1
0427c7e62472 langgenius/dify-sandbox:0.2.10 "/main" 22 minutes ago Up 21 minutes (healthy) docker-sandbox-1
80ef3ade151f semitechnologies/weaviate:1.19.0 "/bin/weaviate --hos…" 22 minutes ago Up 21 minutes docker-weaviate-1
12bef591752f ubuntu/squid:latest "sh -c 'cp /docker-e…" 22 minutes ago Up 21 minutes 3128/tcp docker-ssrf_proxy-1
2a77218e48b5 langgenius/dify-web:1.0.0-beta.1 "/bin/sh ./entrypoin…" 22 minutes ago Up 21 minutes 3000/tcp docker-web-1
e2410bba04d4 redis:6-alpine "docker-entrypoint.s…" 22 minutes ago Up 21 minutes (healthy) 6379/tcp docker-redis-1
It seems to be a database issue, but I haven't found anything amiss in the database logs?
run ‘docker logs docker-db-1’:
PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-02-18 07:39:32.732 UTC [1] LOG: starting PostgreSQL 15.11 on aarch64-unknown-linux-musl, compiled by gcc (Alpine 14.2.0) 14.2.0, 64-bit
2025-02-18 07:39:32.733 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2025-02-18 07:39:32.733 UTC [1] LOG: listening on IPv6 address "::", port 5432
2025-02-18 07:39:32.733 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-02-18 07:39:32.740 UTC [30] LOG: database system was shut down at 2025-02-18 07:35:44 UTC
2025-02-18 07:39:32.744 UTC [1] LOG: database system is ready to accept connections
2025-02-18 07:40:02.122 UTC [1] LOG: received fast shutdown request
2025-02-18 07:40:02.123 UTC [1] LOG: aborting any active transactions
2025-02-18 07:40:02.124 UTC [42] FATAL: terminating connection due to administrator command
2025-02-18 07:40:02.124 UTC [35] FATAL: terminating connection due to administrator command
2025-02-18 07:40:02.125 UTC [1] LOG: background worker "logical replication launcher" (PID 33) exited with exit code 1
2025-02-18 07:40:02.128 UTC [28] LOG: shutting down
2025-02-18 07:40:02.129 UTC [28] LOG: checkpoint starting: shutdown immediate
2025-02-18 07:40:02.139 UTC [28] LOG: checkpoint complete: wrote 19 buffers (0.1%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.006 s, sync=0.001 s, total=0.011 s; sync files=9, longest=0.001 s, average=0.001 s; distance=8 kB, estimate=8 kB
2025-02-18 07:40:02.146 UTC [1] LOG: database system is shut down
PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-02-18 07:40:14.746 UTC [1] LOG: starting PostgreSQL 15.11 on aarch64-unknown-linux-musl, compiled by gcc (Alpine 14.2.0) 14.2.0, 64-bit
2025-02-18 07:40:14.746 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2025-02-18 07:40:14.746 UTC [1] LOG: listening on IPv6 address "::", port 5432
2025-02-18 07:40:14.747 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-02-18 07:40:14.754 UTC [30] LOG: database system was shut down at 2025-02-18 07:40:02 UTC
2025-02-18 07:40:14.760 UTC [1] LOG: database system is ready to accept connections
2025-02-18 07:40:22.800 UTC [1] LOG: received fast shutdown request
2025-02-18 07:40:22.801 UTC [1] LOG: aborting any active transactions
2025-02-18 07:40:22.801 UTC [36] FATAL: terminating connection due to administrator command
2025-02-18 07:40:22.801 UTC [35] FATAL: terminating connection due to administrator command
2025-02-18 07:40:22.802 UTC [1] LOG: background worker "logical replication launcher" (PID 33) exited with exit code 1
2025-02-18 07:40:22.808 UTC [28] LOG: shutting down
2025-02-18 07:40:22.808 UTC [28] LOG: checkpoint starting: shutdown immediate
2025-02-18 07:40:22.812 UTC [28] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.002 s, sync=0.001 s, total=0.005 s; sync files=2, longest=0.001 s, average=0.001 s; distance=0 kB, estimate=0 kB
2025-02-18 07:40:22.817 UTC [1] LOG: database system is shut down
PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-02-18 07:40:35.198 UTC [1] LOG: starting PostgreSQL 15.11 on aarch64-unknown-linux-musl, compiled by gcc (Alpine 14.2.0) 14.2.0, 64-bit
2025-02-18 07:40:35.198 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2025-02-18 07:40:35.198 UTC [1] LOG: listening on IPv6 address "::", port 5432
2025-02-18 07:40:35.200 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-02-18 07:40:35.210 UTC [30] LOG: database system was shut down at 2025-02-18 07:40:22 UTC
2025-02-18 07:40:35.216 UTC [1] LOG: database system is ready to accept connections
2025-02-18 07:45:35.292 UTC [28] LOG: checkpoint starting: time
2025-02-18 07:45:35.613 UTC [28] LOG: checkpoint complete: wrote 6 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.311 s, sync=0.003 s, total=0.322 s; sync files=4, longest=0.001 s, average=0.001 s; distance=16 kB, estimate=16 kB
2025-02-18 07:50:35.679 UTC [28] LOG: checkpoint starting: time
2025-02-18 07:50:35.798 UTC [28] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.109 s, sync=0.002 s, total=0.119 s; sync files=2, longest=0.001 s, average=0.001 s; distance=2 kB, estimate=14 kB
2025-02-18 07:55:35.817 UTC [28] LOG: checkpoint starting: time
2025-02-18 07:55:35.933 UTC [28] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.106 s, sync=0.002 s, total=0.117 s; sync files=2, longest=0.001 s, average=0.001 s; distance=3 kB, estimate=13 kB
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Self Checks
1. Is this request related to a challenge you're experiencing? Tell me about your story.
After installing dify, run it, and the upper left corner keeps reporting an error:

2. Additional context or comments
I set 18GB of available memory for Docker;
The output of
docker ps
is as follows:CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
4d771c44485f nginx:latest "sh -c 'cp /docker-e…" 22 minutes ago Up 21 minutes 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp docker-nginx-1
b9d49213ea00 langgenius/dify-api:1.0.0-beta.1 "/bin/bash /entrypoi…" 22 minutes ago Up 21 minutes 5001/tcp docker-api-1
033f4cf65e05 langgenius/dify-api:1.0.0-beta.1 "/bin/bash /entrypoi…" 22 minutes ago Up 21 minutes 5001/tcp docker-worker-1
f1e9acc9fda1 langgenius/dify-plugin-daemon:0.0.1-local "/bin/bash -c /app/e…" 22 minutes ago Up 21 minutes 0.0.0.0:5003->5003/tcp docker-plugin_daemon-1
d1b48c80bde7 postgres:15-alpine "docker-entrypoint.s…" 22 minutes ago Up 21 minutes (healthy) 0.0.0.0:5432->5432/tcp docker-db-1
0427c7e62472 langgenius/dify-sandbox:0.2.10 "/main" 22 minutes ago Up 21 minutes (healthy) docker-sandbox-1
80ef3ade151f semitechnologies/weaviate:1.19.0 "/bin/weaviate --hos…" 22 minutes ago Up 21 minutes docker-weaviate-1
12bef591752f ubuntu/squid:latest "sh -c 'cp /docker-e…" 22 minutes ago Up 21 minutes 3128/tcp docker-ssrf_proxy-1
2a77218e48b5 langgenius/dify-web:1.0.0-beta.1 "/bin/sh ./entrypoin…" 22 minutes ago Up 21 minutes 3000/tcp docker-web-1
e2410bba04d4 redis:6-alpine "docker-entrypoint.s…" 22 minutes ago Up 21 minutes (healthy) 6379/tcp docker-redis-1
It seems to be a database issue, but I haven't found anything amiss in the database logs?
run ‘docker logs docker-db-1’:
PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-02-18 07:39:32.732 UTC [1] LOG: starting PostgreSQL 15.11 on aarch64-unknown-linux-musl, compiled by gcc (Alpine 14.2.0) 14.2.0, 64-bit
2025-02-18 07:39:32.733 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2025-02-18 07:39:32.733 UTC [1] LOG: listening on IPv6 address "::", port 5432
2025-02-18 07:39:32.733 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-02-18 07:39:32.740 UTC [30] LOG: database system was shut down at 2025-02-18 07:35:44 UTC
2025-02-18 07:39:32.744 UTC [1] LOG: database system is ready to accept connections
2025-02-18 07:40:02.122 UTC [1] LOG: received fast shutdown request
2025-02-18 07:40:02.123 UTC [1] LOG: aborting any active transactions
2025-02-18 07:40:02.124 UTC [42] FATAL: terminating connection due to administrator command
2025-02-18 07:40:02.124 UTC [35] FATAL: terminating connection due to administrator command
2025-02-18 07:40:02.125 UTC [1] LOG: background worker "logical replication launcher" (PID 33) exited with exit code 1
2025-02-18 07:40:02.128 UTC [28] LOG: shutting down
2025-02-18 07:40:02.129 UTC [28] LOG: checkpoint starting: shutdown immediate
2025-02-18 07:40:02.139 UTC [28] LOG: checkpoint complete: wrote 19 buffers (0.1%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.006 s, sync=0.001 s, total=0.011 s; sync files=9, longest=0.001 s, average=0.001 s; distance=8 kB, estimate=8 kB
2025-02-18 07:40:02.146 UTC [1] LOG: database system is shut down
PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-02-18 07:40:14.746 UTC [1] LOG: starting PostgreSQL 15.11 on aarch64-unknown-linux-musl, compiled by gcc (Alpine 14.2.0) 14.2.0, 64-bit
2025-02-18 07:40:14.746 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2025-02-18 07:40:14.746 UTC [1] LOG: listening on IPv6 address "::", port 5432
2025-02-18 07:40:14.747 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-02-18 07:40:14.754 UTC [30] LOG: database system was shut down at 2025-02-18 07:40:02 UTC
2025-02-18 07:40:14.760 UTC [1] LOG: database system is ready to accept connections
2025-02-18 07:40:22.800 UTC [1] LOG: received fast shutdown request
2025-02-18 07:40:22.801 UTC [1] LOG: aborting any active transactions
2025-02-18 07:40:22.801 UTC [36] FATAL: terminating connection due to administrator command
2025-02-18 07:40:22.801 UTC [35] FATAL: terminating connection due to administrator command
2025-02-18 07:40:22.802 UTC [1] LOG: background worker "logical replication launcher" (PID 33) exited with exit code 1
2025-02-18 07:40:22.808 UTC [28] LOG: shutting down
2025-02-18 07:40:22.808 UTC [28] LOG: checkpoint starting: shutdown immediate
2025-02-18 07:40:22.812 UTC [28] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.002 s, sync=0.001 s, total=0.005 s; sync files=2, longest=0.001 s, average=0.001 s; distance=0 kB, estimate=0 kB
2025-02-18 07:40:22.817 UTC [1] LOG: database system is shut down
PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-02-18 07:40:35.198 UTC [1] LOG: starting PostgreSQL 15.11 on aarch64-unknown-linux-musl, compiled by gcc (Alpine 14.2.0) 14.2.0, 64-bit
2025-02-18 07:40:35.198 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2025-02-18 07:40:35.198 UTC [1] LOG: listening on IPv6 address "::", port 5432
2025-02-18 07:40:35.200 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-02-18 07:40:35.210 UTC [30] LOG: database system was shut down at 2025-02-18 07:40:22 UTC
2025-02-18 07:40:35.216 UTC [1] LOG: database system is ready to accept connections
2025-02-18 07:45:35.292 UTC [28] LOG: checkpoint starting: time
2025-02-18 07:45:35.613 UTC [28] LOG: checkpoint complete: wrote 6 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.311 s, sync=0.003 s, total=0.322 s; sync files=4, longest=0.001 s, average=0.001 s; distance=16 kB, estimate=16 kB
2025-02-18 07:50:35.679 UTC [28] LOG: checkpoint starting: time
2025-02-18 07:50:35.798 UTC [28] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.109 s, sync=0.002 s, total=0.119 s; sync files=2, longest=0.001 s, average=0.001 s; distance=2 kB, estimate=14 kB
2025-02-18 07:55:35.817 UTC [28] LOG: checkpoint starting: time
2025-02-18 07:55:35.933 UTC [28] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.106 s, sync=0.002 s, total=0.117 s; sync files=2, longest=0.001 s, average=0.001 s; distance=3 kB, estimate=13 kB
Beta Was this translation helpful? Give feedback.
All reactions