我在服务器上部署maxkb，通过内网进行访问，但是为什么服务可以启动，保存和发布应用的按钮甚至修改大模型的按钮点了都没有反应，控制台报错如图，请问这种情况怎么解决
以下内容是maxkb日志（似乎是Gunicorn没有正常启动，只是Gunicorn的问题吗）
[root@localhost ~]# docker logs maxkb
Operations to perform:
Apply all migrations: application, contenttypes, django_apscheduler, django_celery_beat, knowledge, models_provider, system_manage, tools, users
Running migrations:
Applying users.0001_initial… OK
Applying system_manage.0001_initial… OK
Applying models_provider.0001_initial… OK
Applying knowledge.0001_initial… OK
Applying application.0001_initial… OK
Applying contenttypes.0001_initial… OK
Applying contenttypes.0002_remove_content_type_name… OK
Applying django_apscheduler.0001_initial… OK
Applying django_apscheduler.0002_auto_20180412_0758… OK
Applying django_apscheduler.0003_auto_20200716_1632… OK
Applying django_apscheduler.0004_auto_20200717_1043… OK
Applying django_apscheduler.0005_migrate_name_to_id… OK
Applying django_apscheduler.0006_remove_djangojob_name… OK
Applying django_apscheduler.0007_auto_20200717_1404… OK
Applying django_apscheduler.0008_remove_djangojobexecution_started… OK
Applying django_apscheduler.0009_djangojobexecution_unique_job_executions… OK
Applying django_celery_beat.0001_initial… OK
Applying django_celery_beat.0002_auto_20161118_0346… OK
Applying django_celery_beat.0003_auto_20161209_0049… OK
Applying django_celery_beat.0004_auto_20170221_0000… OK
Applying django_celery_beat.0005_add_solarschedule_events_choices… OK
Applying django_celery_beat.0006_auto_20180322_0932… OK
Applying django_celery_beat.0007_auto_20180521_0826… OK
Applying django_celery_beat.0008_auto_20180914_1922… OK
Applying django_celery_beat.0006_auto_20180210_1226… OK
Applying django_celery_beat.0006_periodictask_priority… OK
Applying django_celery_beat.0009_periodictask_headers… OK
Applying django_celery_beat.0010_auto_20190429_0326… OK
Applying django_celery_beat.0011_auto_20190508_0153… OK
Applying django_celery_beat.0012_periodictask_expire_seconds… OK
Applying django_celery_beat.0013_auto_20200609_0727… OK
Applying django_celery_beat.0014_remove_clockedschedule_enabled… OK
Applying django_celery_beat.0015_edit_solarschedule_events_choices… OK
Applying django_celery_beat.0016_alter_crontabschedule_timezone… OK
Applying django_celery_beat.0017_alter_crontabschedule_month_of_year… OK
Applying django_celery_beat.0018_improve_crontab_helptext… OK
Applying django_celery_beat.0019_alter_periodictasks_options… OK
Applying tools.0001_initial… OK
-
Start Gunicorn WSGI HTTP Server
-
Start Gunicorn Local Model WSGI HTTP Server
-
Start Celery as Distributed Task Queue: Celery
Operations to perform:
Apply all migrations: application, contenttypes, django_apscheduler, django_celery_beat, knowledge, models_provider, system_manage, tools, users
Running migrations:
No migrations to apply.
Your models in app(s): ‘knowledge’ 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 WSGI HTTP Server
-
Start Celery as Distributed Task Queue: Celery
-
Start Gunicorn Local Model WSGI HTTP Server
Operations to perform:
Apply all migrations: application, contenttypes, django_apscheduler, django_celery_beat, knowledge, models_provider, system_manage, tools, users
Running migrations:
No migrations to apply.
Your models in app(s): ‘knowledge’ 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 WSGI HTTP Server
-
Start Gunicorn Local Model WSGI HTTP Server
-
Start Celery as Distributed Task Queue: Celery
Operations to perform:
Apply all migrations: application, contenttypes, django_apscheduler, django_celery_beat, knowledge, models_provider, system_manage, tools, users
Running migrations:
No migrations to apply.
Your models in app(s): ‘knowledge’ 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 Celery as Distributed Task Queue: Celery
-
Start Gunicorn WSGI HTTP Server
Operations to perform:
Apply all migrations: application, contenttypes, django_apscheduler, django_celery_beat, knowledge, models_provider, system_manage, tools, users
Running migrations:
No migrations to apply. -
Start Gunicorn Local Model WSGI HTTP Server
-
Start Celery as Distributed Task Queue: Celery
-
Start Gunicorn WSGI HTTP Server
