启动命令为：docker run -d --name=maxkb --restart=always --privileged=true -p 9517:9517 -v ~/.maxkb:/var/lib/postgresql/data -v ~/.python-packages:/opt/maxkb/app/sandbox/python-packages registry.fit2cloud.com/maxkb/maxkb
docker logs maxkb为：
docker logs maxkb
PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-02-21 09:34:44.837 CST [8] LOG: starting PostgreSQL 15.8 (Debian 15.8-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2025-02-21 09:34:44.838 CST [8] LOG: listening on IPv4 address “0.0.0.0”, port 5432
2025-02-21 09:34:44.838 CST [8] LOG: listening on IPv6 address “::”, port 5432
2025-02-21 09:34:44.840 CST [8] LOG: listening on Unix socket “/var/run/postgresql/.s.PGSQL.5432”
2025-02-21 09:34:44.843 CST [32] LOG: database system was interrupted; last known up at 2025-02-21 09:13:04 CST
2025-02-21 09:34:44.852 CST [32] LOG: database system was not properly shut down; automatic recovery in progress
2025-02-21 09:34:44.854 CST [32] LOG: redo starts at 0/21CABD8
2025-02-21 09:34:44.854 CST [32] LOG: invalid record length at 0/21CACC0: wanted 24, got 0
2025-02-21 09:34:44.854 CST [32] LOG: redo done at 0/21CAC88 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2025-02-21 09:34:44.858 CST [30] LOG: checkpoint starting: end-of-recovery immediate wait
2025-02-21 09:34:44.863 CST [30] 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.007 s; sync files=2, longest=0.001 s, average=0.001 s; distance=0 kB, estimate=0 kB
2025-02-21 09:34:44.865 CST [8] LOG: database system is ready to accept connections
127.0.0.1:5432 - accepting connections
Building prefix dict from the default dictionary …
DEBUG:jieba:Building prefix dict from the default dictionary …
Dumping model to file cache /tmp/jieba.cache
DEBUG:jieba:Dumping model to file cache /tmp/jieba.cache
Loading model cost 0.695 seconds.
DEBUG:jieba:Loading model cost 0.695 seconds.
Prefix dict has been built successfully.
DEBUG:jieba:Prefix dict has been built successfully.
Operations to perform:
Apply all migrations: application, contenttypes, dataset, django_apscheduler, django_celery_beat, embedding, function_lib, setting, users
Running migrations:
No migrations to apply.
Your models in app(s): ‘dataset’, ‘function_lib’ have changes that are not yet reflected in a migration, and so won’t be applied.
Run ‘manage.py makemigrations’ to make new migrations, and then re-run ‘manage.py migrate’ to apply them.
-
Start Gunicorn Local Model WSGI HTTP Server
-
Start Gunicorn WSGI HTTP Server
-
Start Celery as Distributed Task Queue: Celery
2025-02-21 09:35:01 Check service status: local_model → running at 72
2025-02-21 09:35:02 Check service status: gunicorn → running at 73
2025-02-21 09:35:03 Check service status: celery_default → running at 74
2025-02-21 09:35:34 Check service status: local_model → running at 72
2025-02-21 09:35:35 Check service status: gunicorn → running at 73
2025-02-21 09:35:36 Check service status: celery_default → running at 74
2025-02-21 09:36:07 Check service status: local_model → running at 72
2025-02-21 09:36:08 Check service status: gunicorn → running at 73
2025-02-21 09:36:09 Check service status: celery_default → running at 74
2025-02-21 09:36:40 Check service status: local_model → running at 72
2025-02-21 09:36:41 Check service status: gunicorn → running at 73
2025-02-21 09:36:42 Check service status: celery_default → running at 74
2025-02-21 09:37:13 Check service status: local_model → running at 72
2025-02-21 09:37:14 Check service status: gunicorn → running at 73
2025-02-21 09:37:15 Check service status: celery_default → running at 74
2025-02-21 09:37:46 Check service status: local_model → running at 72
2025-02-21 09:37:47 Check service status: gunicorn → running at 73
2025-02-21 09:37:48 Check service status: celery_default → running at 74
2025-02-21 09:38:19 Check service status: local_model → running at 72
2025-02-21 09:38:20 Check service status: gunicorn → running at 73
2025-02-21 09:38:21 Check service status: celery_default → running at 74
2025-02-21 09:38:52 Check service status: local_model → running at 72
2025-02-21 09:38:53 Check service status: gunicorn → running at 73
2025-02-21 09:38:54 Check service status: celery_default → running at 74
2025-02-21 09:39:25 Check service status: local_model → running at 72
2025-02-21 09:39:26 Check service status: gunicorn → running at 73
2025-02-21 09:39:27 Check service status: celery_default → running at 74
2025-02-21 09:39:44.932 CST [30] LOG: checkpoint starting: time
2025-02-21 09:39:45.239 CST [30] LOG: checkpoint complete: wrote 4 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.302 s, sync=0.001 s, total=0.307 s; sync files=4, longest=0.001 s, average=0.001 s; distance=22 kB, estimate=22 kB
2025-02-21 09:39:58 Check service status: local_model → running at 72
2025-02-21 09:39:59 Check service status: gunicorn → running at 73
2025-02-21 09:40:00 Check service status: celery_default → running at 74
2025-02-21 09:40:31 Check service status: local_model → running at 72
2025-02-21 09:40:32 Check service status: gunicorn → running at 73
2025-02-21 09:40:33 Check service status: celery_default → running at 74
2025-02-21 09:41:04 Check service status: local_model → running at 72
2025-02-21 09:41:05 Check service status: gunicorn → running at 73
2025-02-21 09:41:06 Check service status: celery_default → running at 74
2025-02-21 09:41:37 Check service status: local_model → running at 72
2025-02-21 09:41:38 Check service status: gunicorn → running at 73