Переменные в INI-файле блокируют запуск экземпляра UWSGI - PullRequest
0 голосов
/ 02 февраля 2020

У меня есть экземпляр uWSGI с файлом конфигурации uwsgi.ini, который отлично работает, если я не указываю значения для процессов или рабочих. Но я вскоре, как только я попытаюсь установить значения c для одного из этих двух, экземпляр не может запуститься. В следующем примере я установил работники = 2 (что принимается во внимание, как вы можете видеть):

generic_1  | *** Starting uWSGI 2.0.18 (64bit) on [Sun Feb  2 12:52:12 2020] ***
generic_1  | compiled with version: 6.3.0 20170516 on 03 March 2019 08:23:09
generic_1  | os: Linux-4.9.184-linuxkit #1 SMP Tue Jul 2 22:58:16 UTC 2019
generic_1  | nodename: bd1d9ac91974
generic_1  | machine: x86_64
generic_1  | clock source: unix
generic_1  | pcre jit disabled
generic_1  | detected number of CPU cores: 4
generic_1  | current working directory: /app
generic_1  | detected binary path: /usr/local/bin/uwsgi
generic_1  | your memory page size is 4096 bytes
generic_1  | invalid cheaper value: must be lower than processes
generic_1  | 2020-02-02 12:52:12,064 INFO exited: uwsgi (exit status 1; not expected)
generic_1  | 2020-02-02 12:52:15,075 INFO spawned: 'uwsgi' with pid 17
generic_1  | [uWSGI] getting INI configuration from /app/uwsgi.ini
generic_1  | [uWSGI] getting INI configuration from /etc/uwsgi/uwsgi.ini
generic_1  | 
generic_1  | ;uWSGI instance configuration
generic_1  | [uwsgi]
generic_1  | cheaper = 2
generic_1  | processes = 16
generic_1  | ini = /app/uwsgi.ini
generic_1  | workers = 2
generic_1  | module = api.main
generic_1  | callable = app
generic_1  | chmod-socket = 660
generic_1  | vacuum = true
generic_1  | ini = /etc/uwsgi/uwsgi.ini
generic_1  | socket = /tmp/uwsgi.sock
generic_1  | chown-socket = nginx:nginx
generic_1  | chmod-socket = 664
generic_1  | hook-master-start = unix_signal:15 gracefully_kill_them_all
generic_1  | need-app = true
generic_1  | die-on-term = true
generic_1  | show-config = true
generic_1  | master = true
generic_1  | listen = 128
generic_1  | cheaper-algo = spare
generic_1  | log-4xx = true
generic_1  | log-5xx = true
generic_1  | log-ioerror = true
generic_1  | ignore-write-errors = yes
generic_1  | ignore-sigpipe = yes
generic_1  | disable-write-exception = yes
generic_1  | cheaper-step = 4
generic_1  | ;end of configuration
generic_1  | *** Starting uWSGI 2.0.18 (64bit) on [Sun Feb  2 12:52:15 2020] ***
generic_1  | compiled with version: 6.3.0 20170516 on 03 March 2019 08:23:09
generic_1  | os: Linux-4.9.184-linuxkit #1 SMP Tue Jul 2 22:58:16 UTC 2019
generic_1  | nodename: bd1d9ac91974
generic_1  | machine: x86_64
generic_1  | clock source: unix
generic_1  | pcre jit disabled
generic_1  | detected number of CPU cores: 4
generic_1  | current working directory: /app
generic_1  | detected binary path: /usr/local/bin/uwsgi
generic_1  | your memory page size is 4096 bytes
generic_1  | invalid cheaper value: must be lower than processes
generic_1  | 2020-02-02 12:52:15,093 INFO exited: uwsgi (exit status 1; not expected)
generic_1  | 2020-02-02 12:52:16,100 INFO gave up: uwsgi entered FATAL state, too many start retries too quickly
generic_1  | 2020/02/02 12:52:37 [crit] 14#14: *1 connect() to unix:///tmp/uwsgi.sock failed (2: No such file or directory) while connecting to upstream...

Любая идея, почему / как я могу это исправить?

Спасибо!

...