Apache HTTP Server ArchLinux - php74-fpm - Alternativer PHP-Interpreter
Der Apache HTTP Server ist ein Open Source Webserver und der seit 1996 am meisten im Internet eingesetzte Webserver weltweit. Der freie und quell offenen Webserver wird von der Apache Software Foundation zur Verfügung gestellt und weiterentwickelt.
Um den Apache HTTP Server als ServermitPHP zu betreiben, kann zur Kommunikation FPM/FastCGI zum Einsatz kommen.
PHP-FPM startet gleich mehrere PHP-Interpreter-Prozesse, die ständig im Hintergrund laufen und auf Aufträge warten. Eingehende Anfragen nimmt PHP-FPM vom Webserver Apache HTTP Server entgegen und verteilt sie an die wartenden PHP-Interpreter.
Hierbei gibt es drei Möglichkeiten, die die Kommunikation zwischen dem Apache HTTP Server und dem PHP bewerkstelligen können:
mod_php - Standard, Aufruf von PHP innerhalb des Webservers Apache HTTP Server.
mod_fcgid - Nutzung von CGI/FastCGI durch Aufruf innerhalb des Apache HTTP Server durch starten eines externen Prozess durch den Apache HTTP Server
php74-fpm - Nutzung von FPM/FastCGI durch Aufruf ausserhalb des Apache HTTP Server, über einen separat gestarteten Dienstes/Daemon.
Nachfolgend soll die Variante php74-fpm genutzt werden!
Ab hier werden root-Rechte zur Ausführung der nachfolgenden Befehle benötigt. Um root zu werden geben Sie bitte folgenden Befehl ein:
$ su -
Password:
Vorteile von PHP74-FPM
Nachfolgende Vorteile besitzt PHP74-FPM gegenüber den anderen Möglichkeiten, PHP-7 im Webserver einzubinden:
PHP-7 Prozesse müssen nicht in der gleichen Umgebung, mit dem gleichen User- und der gleichen GruppenID, wie der Webserver laufen.
Es ist möglich die PHP Prozesse neu zu starten, ohne ankommende „Requests“ zu verlieren.
In der PHP74-FPM-Konfiguration kann man verschiedene Prozess Pools definieren. Für jeden Pool kann man definieren, mit welchen Rechten die Prozesse laufen, man kann die Prozesse sogar in ein Chroot einsperren oder sie mit einer anderen php.ini starten.
Jeder Prozesspool lauscht auf einem eigenen Port oder einem Unix Domain Socket, so ist es möglich in einem Webserver zu Konfigurieren wohin die „Requests“ gestellt werden sollen.
Es können PHP-7 Prozesse neu gestartet werden, ohne „Requests“ zu verlieren. Auch können PHP-7 Prozesse nach Zeit N automatisch terminiert werden.
Ein Möglichkeit ist die Nutzung der Konfigurationsvariable request_slowlog_timeout. Braucht ein „Request“ länger als definiert, wird automatisch ein „Backtrace“ des „Requests“ in ein LOG-Datei geschrieben.
PHP-FPM ist seit der PHP Version 5.3.3 fest in PHP integriert.
Der Austausch der PHP-Version ist einfacher möglich, als dies bei der Nutzung von mod_php möglich wäre.
Bessere Performance gegenüber z.B. mod_php
Der grösste Vorteile ist, die Nutzung des Apache HTTP Server im event-Modus, anstelle im prefork-Modus !!!
Um den PHP74-FPM, welcher als Dienst/Daemon als Hintergrundprozess läuft, auch nach einem Neustart des Servers zur Verfügung zu haben, soll der Dienst/Deamon mit dem Server mit gestartet werden, was mit nachfolgendem Befehl realisiert werden kann:
# systemctl enable php74-fpm.service
HINWEIS - Sollte keine Ausgabe nach Ausführung des Befehls erfolgen, wurde dieser mit der Installation bereits eingerichtet.
Eine Überprüfung, ob beim Neustart des Server der php74-fpm-Dienst/Daemon wirklich mit gestartet wird, kann mit nachfolgendem Befehl erfolgen und sollte eine Anzeige, wie ebenfalls nachfolgend dargestellt ausgeben:
Das Ansprechen von PHP über PHP74-FPM durch Apache HTTP Serverphp-fpm7 wird in nachfolgenden Konfigurationsdateien durchgeführt:
/etc/httpd/conf/httpd.conf - Einstellungen zum Laden der Module: mod_proxy und mod_proxy_fcgi und zum hinzufügen des Handlers für die Interpretation des PHP-Code.
/ect/php74/php-fpm.d/www.conf - Konfigurationsdatei für die Interpretationseinstellungen durch den Apache HTTP Server
/ect/php74/php-fpm.conf - Konfigurationsdatei für den PHP74-FPM Dienst/Daemon.
Bevor ein erneuter Neustart des Apache HTTP Server erfolgreich durchgeführt werden kann, ist es erforderlich für die nachfolgende Installation die Konfigurationsdatei /etc/httpd/conf/httpd.conf zu verändern.
Nachfolgende die Veränderung, welche vorgenommen werden muss:
Die Einbindung des Moduls mod_proxy ist erforderlich, da dieses ein einen Proxy/Gateway für den Apache HTTP Server implementiert. Es werden eine Reihe gängiger Protokolle sowie verschiedene Lastausgleichsalgorithmen unterstützt. Module von Drittanbietern können Unterstützung für zusätzliche Protokolle und Lastausgleichsalgorithmen hinzufügen.
Die Einbindung des Moduls mod_proxy_fcgi ist erforderlich, um die Unterstützung für das FastCGI-Protokoll zu realisieren. WICHTIG - Dieses Modul benötigt den Dienst von mod_proxy.
Anschliessend sind nachfolgende Ergänzungen, hier an der Konfigurationsdatei
/etc/httpd/conf/httpd.conf
z.B. am Ende der Konfigurationsdatei durchzuführen:
Erzwingt die Verarbeitung aller passenden Dateien durch den Handler für PHP/FGCI durch einen UNIX-Socket.
## DirectoryIndex: sets the file that Apache will serve if a directory# is requested.#
<IfModule dir_module>
# Tachtler# default: DirectoryIndex index.htmlDirectoryIndex index.php index.html index.htm
</IfModule>
Erklärungen:
DirectoryIndex index.php index.html index.htm
Erweiterung des DirectoryIndex um die Angabe index.php, in der Liste der Ressourcen, nach denen zu suchen ist, wenn der Client ein Verzeichnis anfordert.
/etc/php74/php-fpm.d/www.conf
Diese Konfigurationsdatei erstellt einen Pool, welcher später für den Dienst/Daemon die einzelnen „Child-Threats“ startet, welche dann letztendlich die Anfragen vom Apache HTTP Server entgegennehmen und ausführen.
Die Änderungen an dieser Konfigurationsdatei sind davon abhängig, welches Verfahren zur Kommunikation mit
PHP74-FPM zum Einsatz kommen soll.
TCP/IP-Port
UNIX-Socket
Nachfolgende Änderungen sind an dieser Konfigurationsdatei durchzuführen:
; Start a new pool named 'www'.; the variable $pool can be used in any directive and will be replaced by the; pool name ('www' here)[www]
; Per pool prefix; It only applies on the following directives:; - 'access.log'; - 'slowlog'; - 'listen' (unixsocket); - 'chroot'; - 'chdir'; - 'php_values'; - 'php_admin_values'; When not set, the global prefix (or /usr) applies instead.; Note: This directive can also be relative to the global prefix.; Default Value: none;prefix = /path/to/pools/$pool
; Unix user/group of processes; Note: The user is mandatory. If the group is not set, the default user's group; will be used.user= httpgroup= http
; The address on which to accept FastCGI requests.; Valid syntaxes are:; 'ip.add.re.ss:port' - to listen on a TCP socket to a specific IPv4 address on; a specific port;; '[ip:6:addr:ess]:port' - to listen on a TCP socket to a specific IPv6 address on; a specific port;; 'port' - to listen on a TCP socket to all addresses; (IPv6 and IPv4-mapped) on a specific port;; '/path/to/unix/socket' - to listen on a unix socket.; Note: This value is mandatory.listen= /run/php-fpm7/php-fpm.sock
; Set listen(2) backlog.; Default Value: 511 (-1 on FreeBSD and OpenBSD);listen.backlog = 511
; Set permissions for unix socket, if one is used. In Linux, read/write; permissions must be set in order to allow connections from a web server. Many; BSD-derived systems allow connections regardless of permissions. The owner; and group can be specified either by name or by their numeric IDs.; Default Values: user and group are set as the running user; mode is set to 0660
listen.owner = http
listen.group = http;listen.mode = 0660; When POSIX Access Control Lists are supported you can set them using; these options, value is a comma separated list of user/group names.; When set, listen.owner and listen.group are ignored;listen.acl_users =;listen.acl_groups =
; List of addresses (IPv4/IPv6) of FastCGI clients which are allowed to connect.; Equivalent to the FCGI_WEB_SERVER_ADDRS environment variable in the original; PHP FCGI (5.2.2+). Makes sense only with a tcp listening socket. Each address; must be separated by a comma. If this value is left blank, connections will be; accepted from any ip address.; Default Value: any;listen.allowed_clients = 127.0.0.1
; Specify the nice(2) priority to apply to the pool processes (only if set); The value can vary from -19 (highest priority) to 20 (lower priority); Note: - It will only work if the FPM master process is launched as root; - The pool processes will inherit the master process priority; unless it specified otherwise; Default Value: no set; process.priority = -19
; Set the process dumpable flag (PR_SET_DUMPABLE prctl) even if the process user; or group is different than the master process user. It allows to create process; core dump and ptrace the process for the pool user.; Default Value: no; process.dumpable = yes
; Choose how the process manager will control the number of child processes.; Possible Values:; static - a fixed number (pm.max_children) of child processes;; dynamic - the number of child processes are set dynamically based on the; following directives. With this process management, there will be; always at least 1 children.; pm.max_children - the maximum number of children that can; be alive at the same time.; pm.start_servers - the number of children created on startup.; pm.min_spare_servers - the minimum number of children in 'idle'; state (waiting to process). If the number; of 'idle' processes is less than this; number then some children will be created.; pm.max_spare_servers - the maximum number of children in 'idle'; state (waiting to process). If the number; of 'idle' processes is greater than this; number then some children will be killed.; pm.max_spawn_rate - the maximum number of rate to spawn child; processes at once.; ondemand - no children are created at startup. Children will be forked when; new requests will connect. The following parameter are used:; pm.max_children - the maximum number of children that; can be alive at the same time.; pm.process_idle_timeout - The number of seconds after which; an idle process will be killed.; Note: This value is mandatory.pm= dynamic
; The number of child processes to be created when pm is set to 'static' and the; maximum number of child processes when pm is set to 'dynamic' or 'ondemand'.; This value sets the limit on the number of simultaneous requests that will be; served. Equivalent to the ApacheMaxClients directive with mpm_prefork.; Equivalent to the PHP_FCGI_CHILDREN environment variable in the original PHP; CGI. The below defaults are based on a server without much resources. Don't; forget to tweak pm.* to fit your needs.; Note: Used when pm is set to 'static', 'dynamic' or 'ondemand'; Note: This value is mandatory.
pm.max_children = 5
; The number of child processes created on startup.; Note: Used only when pm is set to 'dynamic'; Default Value: (min_spare_servers + max_spare_servers) / 2
pm.start_servers = 2
; The desired minimum number of idle server processes.; Note: Used only when pm is set to 'dynamic'; Note: Mandatory when pm is set to 'dynamic'
pm.min_spare_servers = 1
; The desired maximum number of idle server processes.; Note: Used only when pm is set to 'dynamic'; Note: Mandatory when pm is set to 'dynamic'
pm.max_spare_servers = 3
; The number of rate to spawn child processes at once.; Note: Used only when pm is set to 'dynamic'; Note: Mandatory when pm is set to 'dynamic'; Default Value: 32;pm.max_spawn_rate = 32
; The number of seconds after which an idle process will be killed.; Note: Used only when pm is set to 'ondemand'; Default Value: 10s;pm.process_idle_timeout = 10s;
; The number of requests each child process should execute before respawning.; This can be useful to work around memory leaks in 3rd party libraries. For; endless request processing specify '0'. Equivalent to PHP_FCGI_MAX_REQUESTS.; Default Value: 0;pm.max_requests = 500
; The URI to view the FPM status page. If this value is not set, no URI will be; recognized as a status page. It shows the following information:; pool - the name of the pool;; process manager - static, dynamic or ondemand;; start time - the date and time FPM has started;; start since - number of seconds since FPM has started;; accepted conn - the number of request accepted by the pool;; listen queue - the number of request in the queue of pending; connections (see backlog in listen(2));; max listen queue - the maximum number of requests in the queue; of pending connections since FPM has started;; listen queue len - the size of the socket queue of pending connections;; idle processes - the number of idle processes;; active processes - the number of active processes;; total processes - the number of idle + active processes;; max active processes - the maximum number of active processes since FPM; has started;; max children reached - number of times, the process limit has been reached,; when pm tries to start more children (works only for; pm 'dynamic' and 'ondemand');; Value are updated in real time.; Example output:; pool: www; process manager: static; start time: 01/Jul/2011:17:53:49 +0200; start since: 62636; accepted conn: 190460; listen queue: 0; max listen queue: 1; listen queue len: 42; idle processes: 4; active processes: 11; total processes: 15; max active processes: 12; max children reached: 0;; By default the status page output is formatted as text/plain. Passing either; 'html', 'xml' or 'json' in the query string will return the corresponding; output syntax. Example:; http://www.foo.bar/status; http://www.foo.bar/status?json; http://www.foo.bar/status?html; http://www.foo.bar/status?xml;; By default the status page only outputs short status. Passing 'full' in the; query string will also return status for each pool process.; Example:; http://www.foo.bar/status?full; http://www.foo.bar/status?json&full; http://www.foo.bar/status?html&full; http://www.foo.bar/status?xml&full; The Full status returns for each process:; pid - the PID of the process;; state - the state of the process (Idle, Running, ...);; start time - the date and time the process has started;; start since - the number of seconds since the process has started;; requests - the number of requests the process has served;; request duration - the duration in µs of the requests;; request method - the request method (GET, POST, ...);; request URI - the request URI with the query string;; content length - the content length of the request (only with POST);; user - the user (PHP_AUTH_USER) (or '-' if not set);; script - the main script called (or '-' if not set);; last request cpu - the %cpu the last request consumed; it's always 0 if the process is not in Idle state; because CPU calculation is done when the request; processing has terminated;; last request memory - the max amount of memory the last request consumed; it's always 0 if the process is not in Idle state; because memory calculation is done when the request; processing has terminated;; If the process is in Idle state, then informations are related to the; last request the process has served. Otherwise informations are related to; the current request being served.; Example output:; ************************; pid: 31330; state: Running; start time: 01/Jul/2011:17:53:49 +0200; start since: 63087; requests: 12808; request duration: 1250261; request method: GET; request URI: /test_mem.php?N=10000; content length: 0; user: -; script: /home/fat/web/docs/php/test_mem.php; last request cpu: 0.00; last request memory: 0;; Note: There is a real-time FPM status monitoring sample web page available; It's available in: /usr/share/php/fpm/status.html;; Note: The value must start with a leading slash (/). The value can be; anything, but it may not be a good idea to use the .php extension or it; may conflict with a real PHP file.; Default Value: not set; Tachtler; default: ;pm.status_path = /status
pm.status_path = /php-fpm-status
; The address on which to accept FastCGI status request. This creates a new; invisible pool that can handle requests independently. This is useful; if the main pool is busy with long running requests because it is still possible; to get the status before finishing the long running requests.;; Valid syntaxes are:; 'ip.add.re.ss:port' - to listen on a TCP socket to a specific IPv4 address on; a specific port;; '[ip:6:addr:ess]:port' - to listen on a TCP socket to a specific IPv6 address on; a specific port;; 'port' - to listen on a TCP socket to all addresses; (IPv6 and IPv4-mapped) on a specific port;; '/path/to/unix/socket' - to listen on a unix socket.; Default Value: value of the listen option; Tachtler; default: ;pm.status_listen = 127.0.0.1:9001
pm.status_listen = /run/php-fpm/php-fpm-status.sock
; The ping URI to call the monitoring page of FPM. If this value is not set, no; URI will be recognized as a ping page. This could be used to test from outside; that FPM is alive and responding, or to; - create a graph of FPM availability (rrd or such);; - remove a server from a group if it is not responding (load balancing);; - trigger alerts for the operating team (24/7).; Note: The value must start with a leading slash (/). The value can be; anything, but it may not be a good idea to use the .php extension or it; may conflict with a real PHP file.; Default Value: not set;ping.path = /ping
; This directive may be used to customize the response of a ping request. The; response is formatted as text/plain with a 200 response code.; Default Value: pong;ping.response = pong
; The access log file; Default: not set;access.log = log/$pool.access.log
; The access log format.; The following syntax is allowed; %%: the '%' character; %C: %CPU used by the request; it can accept the following format:; - %{user}C for user CPU only; - %{system}C for system CPU only; - %{total}C for user + system CPU (default); %d: time taken to serve the request; it can accept the following format:; - %{seconds}d (default); - %{milliseconds}d; - %{milli}d; - %{microseconds}d; - %{micro}d; %e: an environment variable (same as $_ENV or $_SERVER); it must be associated with embraces to specify the name of the env; variable. Some examples:; - server specifics like: %{REQUEST_METHOD}e or %{SERVER_PROTOCOL}e; - HTTP headers like: %{HTTP_HOST}e or %{HTTP_USER_AGENT}e; %f: script filename; %l: content-length of the request (for POST request only); %m: request method; %M: peak of memory allocated by PHP; it can accept the following format:; - %{bytes}M (default); - %{kilobytes}M; - %{kilo}M; - %{megabytes}M; - %{mega}M; %n: pool name; %o: output header; it must be associated with embraces to specify the name of the header:; - %{Content-Type}o; - %{X-Powered-By}o; - %{Transfert-Encoding}o; - ....; %p: PID of the child that serviced the request; %P: PID of the parent of the child that serviced the request; %q: the query string; %Q: the '?' character if query string exists; %r: the request URI (without the query string, see %q and %Q); %R: remote IP address; %s: status (response code); %t: server time the request was received; it can accept a strftime(3) format:; %d/%b/%Y:%H:%M:%S %z (default); The strftime(3) format must be encapsulated in a %{<strftime_format>}t tag; e.g. for a ISO8601 formatted timestring, use: %{%Y-%m-%dT%H:%M:%S%z}t; %T: time the log has been written (the request has finished); it can accept a strftime(3) format:; %d/%b/%Y:%H:%M:%S %z (default); The strftime(3) format must be encapsulated in a %{<strftime_format>}t tag; e.g. for a ISO8601 formatted timestring, use: %{%Y-%m-%dT%H:%M:%S%z}t; %u: remote user;; Default: "%R - %u %t \"%m %r\" %s";access.format = "%R - %u %t \"%m %r%Q%q\" %s %f %{milli}d %{kilo}M %C%%"
; The log file for slow requests; Default Value: not set; Note: slowlog is mandatory if request_slowlog_timeout is set;slowlog = log/$pool.log.slow
; The timeout for serving a single request after which a PHP backtrace will be; dumped to the 'slowlog' file. A value of '0s' means 'off'.; Available units: s(econds)(default), m(inutes), h(ours), or d(ays); Default Value: 0;request_slowlog_timeout = 0
; Depth of slow log stack trace.; Default Value: 20;request_slowlog_trace_depth = 20
; The timeout for serving a single request after which the worker process will; be killed. This option should be used when the 'max_execution_time' ini option; does not stop script execution for some reason. A value of '0' means 'off'.; Available units: s(econds)(default), m(inutes), h(ours), or d(ays); Default Value: 0;request_terminate_timeout = 0
; The timeout set by 'request_terminate_timeout' ini option is not engaged after; application calls 'fastcgi_finish_request' or when application has finished and; shutdown functions are being called (registered via register_shutdown_function).; This option will enable timeout limit to be applied unconditionally; even in such cases.; Default Value: no;request_terminate_timeout_track_finished = no
; Set open file descriptor rlimit.; Default Value: system defined value;rlimit_files = 1024
; Set max core size rlimit.; Possible Values: 'unlimited' or an integer greater or equal to 0; Default Value: system defined value;rlimit_core = 0
; Chroot to this directory at the start. This value must be defined as an; absolute path. When this value is not set, chroot is not used.; Note: you can prefix with '$prefix' to chroot to the pool prefix or one; of its subdirectories. If the pool prefix is not set, the global prefix; will be used instead.; Note: chrooting is a great security feature and should be used whenever; possible. However, all PHP paths will be relative to the chroot; (error_log, sessions.save_path, ...).; Default Value: not set;chroot =
; Chdir to this directory at the start.; Note: relative path can be used.; Default Value: current directory or / when chroot;chdir = /srv/http
; Redirect worker stdout and stderr into main error log. If not set, stdout and; stderr will be redirected to /dev/null according to FastCGI specs.; Note: on highloaded environment, this can cause some delay in the page; process time (several ms).; Default Value: no;catch_workers_output = yes
; Decorate worker output with prefix and suffix containing information about; the child that writes to the log and if stdout or stderr is used as well as; log level and time. This options is used only if catch_workers_output is yes.; Settings to "no" will output data as written to the stdout or stderr.; Default value: yes;decorate_workers_output = no
; Clear environment in FPM workers; Prevents arbitrary environment variables from reaching FPM worker processes; by clearing the environment in workers before env vars specified in this; pool configuration are added.; Setting to "no" will make all environment variables available to PHP code; via getenv(), $_ENV and $_SERVER.; Default Value: yes;clear_env = no
; Limits the extensions of the main script FPM will allow to parse. This can; prevent configuration mistakes on the web server side. You should only limit; FPM to .php extensions to prevent malicious users to use other extensions to; execute php code.; Note: set an empty value to allow all extensions.; Default Value: .php;security.limit_extensions = .php .php3 .php4 .php5 .php7
; Pass environment variables like LD_LIBRARY_PATH. All $VARIABLEs are taken from; the current environment.; Default Value: clean env;env[HOSTNAME] = $HOSTNAME;env[PATH] = /usr/local/bin:/usr/bin:/bin;env[TMP] = /tmp;env[TMPDIR] = /tmp;env[TEMP] = /tmp
; Additional php.ini defines, specific to this pool of workers. These settings; overwrite the values previously defined in the php.ini. The directives are the; same as the PHP SAPI:; php_value/php_flag - you can set classic ini defines which can; be overwritten from PHP call 'ini_set'.; php_admin_value/php_admin_flag - these directives won't be overwritten by; PHP call 'ini_set'; For php_*flag, valid values are on, off, 1, 0, true, false, yes or no.
; Defining 'extension' will load the corresponding shared extension from; extension_dir. Defining 'disable_functions' or 'disable_classes' will not; overwrite previously defined php.ini values, but will append the new value; instead.
; Note: path INI options can be relative and will be expanded with the prefix; (pool, global or /usr)
; Default Value: nothing is defined by default except the values in php.ini and; specified at startup with the -d argument;php_admin_value[sendmail_path] = /usr/sbin/sendmail -t -i -f www@my.domain.com;php_flag[display_errors] = off;php_admin_value[error_log] = /var/log/fpm-php.www.log;php_admin_flag[log_errors] = on;php_admin_value[memory_limit] = 32M
Erläuterungen zu den Änderungen
pm.status_path = /php-fpm-status
Aktivieren der Statusseite durch setzen des Pfades für den Aufruf!
;;;;;;;;;;;;;;;;;;;;;; FPM Configuration ;;;;;;;;;;;;;;;;;;;;;;
; All relative paths in this configuration file are relative to PHP's install; prefix (/usr). This prefix can be dynamically changed by using the; '-p' argument from the command line.
;;;;;;;;;;;;;;;;;;; Global Options ;;;;;;;;;;;;;;;;;;;[global]; Pid file; Note: the default prefix is /var; Default Value: none;pid = /run/php-fpm7/php-fpm.pid
; Error log file; If it's set to "syslog", log is sent to syslogd instead of being written; into a local file.; Note: the default prefix is /var; Default Value: log/php-fpm.logerror_log= syslog
; syslog_facility is used to specify what type of program is logging the; message. This lets syslogd specify that messages from different facilities; will be handled differently.; See syslog(3) for possible values (ex daemon equiv LOG_DAEMON); Default Value: daemon;syslog.facility = daemon
; syslog_ident is prepended to every message. If you have multiple FPM; instances running on the same server, you can change the default value; which must suit common needs.; Default Value: php-fpm;syslog.ident = php-fpm
; Log level; Possible Values: alert, error, warning, notice, debug; Default Value: notice;log_level = notice
; Log limit on number of characters in the single line (log entry). If the; line is over the limit, it is wrapped on multiple lines. The limit is for; all logged characters including message prefix and suffix if present. However; the new line character does not count into it as it is present only when; logging to a file descriptor. It means the new line character is not present; when logging to syslog.; Default Value: 1024;log_limit = 4096
; Log buffering specifies if the log line is buffered which means that the; line is written in a single write operation. If the value is false, then the; data is written directly into the file descriptor. It is an experimental; option that can potentially improve logging performance and memory usage; for some heavy logging scenarios. This option is ignored if logging to syslog; as it has to be always buffered.; Default value: yes;log_buffering = no
; If this number of child processes exit with SIGSEGV or SIGBUS within the time; interval set by emergency_restart_interval then FPM will restart. A value; of '0' means 'Off'.; Default Value: 0;emergency_restart_threshold = 0
; Interval of time used by emergency_restart_interval to determine when; a graceful restart will be initiated. This can be useful to work around; accidental corruptions in an accelerator's shared memory.; Available Units: s(econds), m(inutes), h(ours), or d(ays); Default Unit: seconds; Default Value: 0;emergency_restart_interval = 0
; Time limit for child processes to wait for a reaction on signals from master.; Available units: s(econds), m(inutes), h(ours), or d(ays); Default Unit: seconds; Default Value: 0;process_control_timeout = 0
; The maximum number of processes FPM will fork. This has been designed to control; the global number of processes when using dynamic PM within a lot of pools.; Use it with caution.; Note: A value of 0 indicates no limit; Default Value: 0; process.max = 128
; Specify the nice(2) priority to apply to the master process (only if set); The value can vary from -19 (highest priority) to 20 (lowest priority); Note: - It will only work if the FPM master process is launched as root; - The pool process will inherit the master process priority; unless specified otherwise; Default Value: no set; process.priority = -19
; Send FPM to background. Set to 'no' to keep FPM in foreground for debugging.; Default Value: yes;daemonize = yes
; Set open file descriptor rlimit for the master process.; Default Value: system defined value;rlimit_files = 1024
; Set max core size rlimit for the master process.; Possible Values: 'unlimited' or an integer greater or equal to 0; Default Value: system defined value;rlimit_core = 0
; Specify the event mechanism FPM will use. The following is available:; - select (any POSIX os); - poll (any POSIX os); - epoll (linux >= 2.5.44); - kqueue (FreeBSD >= 4.1, OpenBSD >= 2.9, NetBSD >= 2.0); - /dev/poll (Solaris >= 7); - port (Solaris >= 10); Default Value: not set (auto detection);events.mechanism = epoll
; When FPM is built with systemd integration, specify the interval,; in seconds, between health report notification to systemd.; Set to 0 to disable.; Available Units: s(econds), m(inutes), h(ours); Default Unit: seconds; Default value: 10;systemd_interval = 10
;;;;;;;;;;;;;;;;;;;;; Pool Definitions ;;;;;;;;;;;;;;;;;;;;;
; Multiple pools of child processes may be started with different listening; ports and different management options. The name of the pool will be; used in logs and stats. There is no limitation on the number of pools which; FPM can handle. Your system will tell you anyway :)
; Include one or more files. If glob(3) exists, it is used to include a bunch of; files from a glob(3) pattern. This directive can be used everywhere in the; file.; Relative path can also be used. They will be prefixed by:; - the global prefix if it's been set (-p argument); - /usr otherwiseinclude=/etc/php7/php-fpm.d/*.conf
/ect/php7/php.ini
Die Hauptkonfigurationsdatei von PHP - php.net sollte mindestens nachfolgende Änderungen erfahren:
HINWEIS - Welche php.ini geladen wird, kann mit nachfolgendem Befehl ermittelt werden:
Beinhaltet Einstellungen zu Statusmeldungen und Informationen des Servers, abrufbar unter speziellen URL-Ergänzungen /server-status, /server-info und neuldap-status
## Get information about the requests being processed by the server# and the configuration of the server.## Required modules: mod_authz_core, mod_authz_host,# mod_info (for the server-info handler),# mod_status (for the server-status handler)## Allow server status reports generated by mod_status,# with the URL of http://servername/server-status# Change the ".example.com" to match your domain to enable.
<Location /server-status>
SetHandler server-status
# Tachtler # default: Require host .example.com# default: Require ip 127Requireall granted
</Location>
## ExtendedStatus controls whether Apache will generate "full" status# information (ExtendedStatus On) or just basic information (ExtendedStatus# Off) when the "server-status" handler is called. The default is Off.## Tachtler# default: #ExtendedStatus OnExtendedStatusOn# Tachtler - NEW -SeeRequestTailOn## Allow remote server configuration reports, with the URL of# http://servername/server-info (requires that mod_info.c be loaded).# Change the ".example.com" to match your domain to enable.#
<Location /server-info>
SetHandler server-info
# Tachtler # default: Require host .example.com# default: Require ip 127Requireall granted
</Location>
## Allow LDAP-Cache status reports generated by mod_ldap,# with the URL of http://servername/ldap-status# Change the ".example.com" to match your domain to enable.
<Location /ldap-status>
SetHandler ldap-status
Requireall granted
</Location>
## Allow PHP-FPM status reports generated by php-fpm,# with the URL of http://servername/php-fpm-status# Change the ".example.com" to match your domain to enable.
<Location /php-fpm-status>
SetHandler"proxy:unix:/run/php74-fpm/php-fpm-status.sock|fcgi://localhost/php-fpm4-status"Requireall granted
</Location>
Erklärungen:
<Location /php-fpm-status>
Wendet die enthaltenen Direktiven nur auf die entsprechenden URL an.
Schliesst die Anwendung auf die enthaltenen Direktiven nur auf die entsprechenden URL ab.
info-Konfiguration: Erster Start - php-fpm7
Falls vorstehende Änderungen (natürlich an die jeweiligen Bedürfnisse angepasst) durchgeführt wurden, sollte ein erster Start von PHP74-FPM nichts mehr im Wege stehen.
Danach kann der php74-fpm-Server mit nachfolgendem Befehle gestartet werden:
# systemctl start php74-fpm.service
Mit nachfolgendem Befehl kann der Status des abgefragt werden:
# systemctl status php74-fpm.service
● php-fpm7.service - The PHP FastCGI Process Manager
Loaded: loaded (/usr/lib/systemd/system/php74-fpm.service; enabled; preset: disabled)
Active: active (running) since Tue 2022-12-27 07:51:48 CET; 5s ago
Main PID: 1142 (php74-fpm)
Status: "Ready to handle connections"
Tasks: 3 (limit: 2316)
Memory: 5.6M
CPU: 49ms
CGroup: /system.slice/php74-fpm.service
├─1142 "php-fpm: master process (/etc/php74/php-fpm.conf)"
├─1143 "php-fpm: pool www"
└─1144 "php-fpm: pool www"
Dec 27 07:51:48 vmtest systemd[1]: Starting The PHP FastCGI Process Manager...
Dec 27 07:51:48 vmtest php74-fpm[1142]: [NOTICE] fpm is running, pid 1142
Dec 27 07:51:48 vmtest php74-fpm[1142]: [NOTICE] ready to handle connections
Dec 27 07:51:48 vmtest php74-fpm[1142]: [NOTICE] systemd monitor interval set to 10000ms
Dec 27 07:51:48 vmtest systemd[1]: Started The PHP FastCGI Process Manager.
Nachfolgender Befehl kann ebenfalls zur Überprüfung der Lauffähigkeit des php74-fpm-Servers genutzt werden und zeigt die laufenden Prozesse und deren genutzte „Pool“'s, hier (pool www):
Nach den vorangegangenen Konfigurationsschritten, sollte einem Neustart nichts im Wege stehen:
# systemctl restart httpd.service
HINWEIS - Es erfolgen keine weiteren Ausgaben, wenn der Start erfolgreich war !
info-Konfiguration: Tests
Wenn ein erneuter Neustart des Apache HTTP Server erfolgreich durchgeführt wurde, können nachfolgende Abfragen mittels eines Browsers erfolgen, wie in nachfolgenden Bildern dargestellt durchgeführt werden:
Durch anhängen nachfolgenden Zusatzes an die URL: /php-fpm7-status
kommt eine Ansicht in etwa wie nachfolgende zur Ansicht:
Mit nachfolgendem Befehl, kann eine einfache Datei mit PHP Inhalt erzeugt werden, welcher dann die bekannte PHP74-Statusseite zur Anzeige bringen sollte. Hier nachfolgendes Beispiel:
# echo'<?php phpinfo(); ?>'>/srv/http/phpinfo.php
Anschliessend kann diese Datei dann wie folgt über z.B. einen Browser aufgerufen werden, falls dieser entsprechend konfiguriert ist. Eine Ausgabe, wie nachfolgende, sollte erscheinen:
Diese Website verwendet Cookies. Durch die Nutzung der Website stimmen Sie dem Speichern von Cookies auf Ihrem Computer zu. Außerdem bestätigen Sie, dass Sie unsere Datenschutzbestimmungen gelesen und verstanden haben. Wenn Sie nicht einverstanden sind, verlassen Sie die Website.Weitere Information
tachtler/apache_http_server_archlinux_-_php74-fpm_-_alternativer_php-interpreter.txt · Zuletzt geändert: 2023/01/23 08:30 von klaus