MaxKB在本地Docker容器运行报错

MaxKB
1

先前docker安装MaxKB运行正常，后来在部署dify之后发现MaxKB运行非常慢查看运行日志有错误，容器能正常启动也能登录进入系统
2025-04-09 16:57:13 Stop service: local_model Error
2025-04-09 16:57:14 Stop service: gunicorn Error
2025-04-09 16:57:14 celery_default is stopped.
2025-04-09 16:57:15
2025-04-09 16:57:15 PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-04-09 16:57:15
2025-04-09 16:57:15 2025-04-09 16:57:15.273 CST [8] LOG: starting PostgreSQL 15.8 (Debian 15.8-1.pgdg110+1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2025-04-09 16:57:15 2025-04-09 16:57:15.273 CST [8] LOG: listening on IPv4 address “0.0.0.0”, port 5432
2025-04-09 16:57:15 2025-04-09 16:57:15.273 CST [8] LOG: listening on IPv6 address “::”, port 5432
2025-04-09 16:57:15 2025-04-09 16:57:15.276 CST [8] LOG: listening on Unix socket “/var/run/postgresql/.s.PGSQL.5432”
2025-04-09 16:57:15 2025-04-09 16:57:15.282 CST [33] LOG: database system was interrupted; last known up at 2025-04-09 16:52:03 CST
2025-04-09 16:57:15 2025-04-09 16:57:15.854 CST [33] LOG: database system was not properly shut down; automatic recovery in progress
2025-04-09 16:57:15 2025-04-09 16:57:15.860 CST [33] LOG: redo starts at 0/B353CB0
2025-04-09 16:57:15 2025-04-09 16:57:15.861 CST [33] LOG: invalid record length at 0/B353D98: wanted 24, got 0
2025-04-09 16:57:15 2025-04-09 16:57:15.861 CST [33] LOG: redo done at 0/B353D60 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2025-04-09 16:57:15 2025-04-09 16:57:15.868 CST [31] LOG: checkpoint starting: end-of-recovery immediate wait
2025-04-09 16:57:15 2025-04-09 16:57:15.875 CST [31] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.002 s, sync=0.001 s, total=0.008 s; sync files=3, longest=0.001 s, average=0.001 s; distance=0 kB, estimate=0 kB
2025-04-09 16:57:15 2025-04-09 16:57:15.878 CST [8] LOG: database system is ready to accept connections
2025-04-09 16:57:24 127.0.0.1:5432 - accepting connections
2025-04-09 16:57:27 Building prefix dict from the default dictionary …
2025-04-09 16:57:27 DEBUG:jieba:Building prefix dict from the default dictionary …
2025-04-09 16:57:27 Loading model from cache /tmp/jieba.cache
2025-04-09 16:57:27 DEBUG:jieba:Loading model from cache /tmp/jieba.cache
2025-04-09 16:57:27 Loading model cost 0.469 seconds.
2025-04-09 16:57:27 DEBUG:jieba:Loading model cost 0.469 seconds.
2025-04-09 16:57:27 Prefix dict has been built successfully.
2025-04-09 16:57:27 DEBUG:jieba:Prefix dict has been built successfully.
2025-04-09 16:57:27 Operations to perform:
2025-04-09 16:57:27 Apply all migrations: application, contenttypes, dataset, django_apscheduler, django_celery_beat, embedding, function_lib, setting, users
2025-04-09 16:57:27 Running migrations:
2025-04-09 16:57:27 No migrations to apply.
2025-04-09 16:57:27 Your models in app(s): ‘dataset’, ‘function_lib’, ‘setting’ have changes that are not yet reflected in a migration, and so won’t be applied.
2025-04-09 16:57:27 Run ‘manage.py makemigrations’ to make new migrations, and then re-run ‘manage.py migrate’ to apply them.
2025-04-09 16:57:27
2025-04-09 16:57:27 - Start Gunicorn WSGI HTTP Server
2025-04-09 16:57:27
2025-04-09 16:57:27 - Start Gunicorn Local Model WSGI HTTP Server
2025-04-09 16:57:27
2025-04-09 16:57:27 - Start Celery as Distributed Task Queue: Celery
2025-04-09 16:57:29 2025-04-09 16:57:28 Check service status: gunicorn → running at 49
2025-04-09 16:57:30 2025-04-09 16:57:29 Check service status: local_model → running at 50
2025-04-09 16:57:31 2025-04-09 16:57:30 Check service status: celery_default → running at 51
2025-04-09 16:58:02 2025-04-09 16:58:01 Check service status: gunicorn → running at 49
2025-04-09 16:58:03 2025-04-09 16:58:02 Check service status: local_model → running at 50
2025-04-09 16:58:04 2025-04-09 16:58:03 Check service status: celery_default → running at 51

2

最后的日志是正常的，没有报错，你的服务器配置是多少？

3

已解决是docker设置问题

4

咨询一下怎么解决的