Re: migrate fastcgi_split_path_info to uwsgi

Am 25.12.18 um 15:23 schrieb Grouchy Sysadmin:
> The uwsgi_params file should be in the same folder as nginx.conf. It's included as part of a typical Nginx installation. Most of the time you don't need to do anything more than include it. This explains it, https://uwsgi-docs.readthedocs.io/en/latest/Nginx.html

ok.

in the mean time I tried that setup.
"uwsgi_modifier1 14; " is something that produce errors I don't understand.

If enabled in nginx.conf, uwsgi throw this error:
	Wed Dec 26 09:55:46 2018 - -- unavailable modifier requested: 14 --

without modifier1 line, nginx+uwsgi+horde works fine.

Maybe the uwsgi config is different. Here is my uwsci statup log including the active config:

[uWSGI] getting INI configuration from /usr/share/uwsgi/conf/default.ini
[uWSGI] getting INI configuration from /run/uwsgi-horde.ini
Wed Dec 26 10:00:22 2018 - 
;uWSGI instance configuration
[uwsgi]
Wed Dec 26 10:00:22 2018 - deb-confname = 
Wed Dec 26 10:00:22 2018 - deb-confnamespace = 
Wed Dec 26 10:00:22 2018 - ini = /usr/share/uwsgi/conf/default.ini
Wed Dec 26 10:00:22 2018 - autoload = true
Wed Dec 26 10:00:22 2018 - master = true
Wed Dec 26 10:00:22 2018 - workers = 2
Wed Dec 26 10:00:22 2018 - no-orphans = true
Wed Dec 26 10:00:22 2018 - chmod-socket = 660
Wed Dec 26 10:00:22 2018 - log-date = true
Wed Dec 26 10:00:22 2018 - uid = www-data
Wed Dec 26 10:00:22 2018 - gid = www-data
Wed Dec 26 10:00:22 2018 - socket = /run/horde/horde
Wed Dec 26 10:00:22 2018 - ini = /run/uwsgi-horde.ini
Wed Dec 26 10:00:22 2018 - show-config = true
Wed Dec 26 10:00:22 2018 - plugins = 0:php
Wed Dec 26 10:00:22 2018 - ;end of configuration

Wed Dec 26 10:00:22 2018 - *** Starting uWSGI 2.0.14-debian (64bit) on [Wed Dec 26 10:00:22 2018] ***
Wed Dec 26 10:00:22 2018 - compiled with version: 6.3.0 20170516 on 17 March 2018 15:41:47
Wed Dec 26 10:00:22 2018 - os: Linux-4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27)
Wed Dec 26 10:00:22 2018 - nodename: horde
Wed Dec 26 10:00:22 2018 - machine: x86_64
Wed Dec 26 10:00:22 2018 - clock source: unix
Wed Dec 26 10:00:22 2018 - pcre jit disabled
Wed Dec 26 10:00:22 2018 - detected number of CPU cores: 4
Wed Dec 26 10:00:22 2018 - current working directory: /horde
Wed Dec 26 10:00:22 2018 - detected binary path: /usr/bin/uwsgi-core
Wed Dec 26 10:00:22 2018 - setgid() to 33
Wed Dec 26 10:00:22 2018 - setuid() to 33
Wed Dec 26 10:00:22 2018 - your memory page size is 4096 bytes
Wed Dec 26 10:00:22 2018 - detected max file descriptor number: 1048576
Wed Dec 26 10:00:22 2018 - lock engine: pthread robust mutexes
Wed Dec 26 10:00:22 2018 - thunder lock: disabled (you can enable it with --thunder-lock)
Wed Dec 26 10:00:22 2018 - uwsgi socket 0 bound to UNIX address /run/horde/horde fd 3
Wed Dec 26 10:00:22 2018 - PHP 7.0.27-0+deb9u1 initialized
Wed Dec 26 10:00:22 2018 - your server socket listen backlog is limited to 100 connections
Wed Dec 26 10:00:22 2018 - your mercy for graceful operations on workers is 60 seconds
Wed Dec 26 10:00:22 2018 - mapped 218304 bytes (213 KB) for 2 cores
Wed Dec 26 10:00:22 2018 - *** Operational MODE: preforking ***
Wed Dec 26 10:00:22 2018 - *** no app loaded. going in full dynamic mode ***
Wed Dec 26 10:00:22 2018 - *** uWSGI is running in multiple interpreter mode ***
Wed Dec 26 10:00:22 2018 - spawned uWSGI master process (pid: 1678)
Wed Dec 26 10:00:22 2018 - spawned uWSGI worker 1 (pid: 1716, cores: 1)
Wed Dec 26 10:00:22 2018 - spawned uWSGI worker 2 (pid: 1717, cores: 1)

I think, my "plugins = 0:php" is related to the modifier1 error. But I did not found any document
describing the problem solved by modifier1/2 at higher level.

Andreas

> 
-- 
Horde mailing list
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: [email protected]