1 @title Restarting Phabricator
4 Instructions on how to restart HTTP and PHP servers to reload configuration
5 changes in Phabricator.
11 Phabricator's setup and configuration instructions sometimes require you to
12 restart your server processes, particularly after making configuration changes.
13 This document explains how to restart them properly.
15 In general, you need to restart both whatever is serving HTTP requests and
16 whatever is serving PHP requests. In some cases, these will be the same process
17 and handled with one restart command. In other cases, they will be two
18 different processes and handled with two different restart commands.
20 {icon exclamation-circle color=blue} If you have two different processes (for
21 example, nginx and PHP-FPM), you need to issue two different restart commands.
23 It's important to restart both your HTTP server and PHP server because each
24 server caches different configuration and settings. Restarting both servers
25 after making changes ensures you're running up-to-date configuration.
29 - Identify which HTTP server you are running (for example, Apache or nginx).
30 - Identify which PHP server you are running (for example, mod_php or PHP-FPM).
31 - For each server, follow the instructions below to restart it.
32 - If the instructions tell you to do so, make sure you restart **both**
39 **Apache**: If you use Apache with `mod_php`, you can just restart Apache. You
40 do not need to restart `mod_php` separately. See below for instructions on how
41 to do this if you aren't sure. This is a very common configuration.
43 **nginx**: If you use nginx with PHP-FPM, you need to restart both nginx and
44 PHP-FPM. See below for instructions on how to do this if you aren't sure. This
45 is also a very common configuration.
47 It's possible to use Apache or nginx in other configurations, or a different
48 webserver. Consult the documentation for your system or webserver if you aren't
49 sure how things are set up.
55 If you are having trouble properly restarting processes on your server, try
56 turning it off and on again. This is effective on every known system and
57 under all configurations.
63 If you are using Apache with `mod_php`, you only need to restart Apache.
65 If you are using Apache in FastCGI mode, you need to restart both Apache and
66 the FCGI server (usually PHP-FPM). This is very unusual.
68 The correct method for restarting Apache depends on what system you are
69 running. Consult your system documentation for details. You might use a command
70 like one of these on your system, or a different command:
73 $ sudo apachectl restart
74 $ sudo /etc/init.d/httpd restart
75 $ sudo service apache2 restart
82 If you're using Nginx with PHP-FPM, you need to restart both of them. This is
83 the most common Nginx configuration.
85 The correct method for restarting Nginx depends on what system you are running.
86 Consult your system documentation for details. You might use a command like
87 one of these on your system, or a different command:
90 $ sudo /etc/init.d/nginx restart
91 $ sudo service nginx restart
98 This is a builtin PHP server that runs within Apache. Restarting Apache (see
99 above) is sufficient to restart it. There is no separate restart command for
100 `mod_php`, so you don't need to do anything else.
106 If you're using FastCGI mode, PHP-FPM is the most common PHP FastCGI server.
107 You'll need to restart it if you're running it.
109 The correct method for restarting PHP-FPM depends on what system you are
110 running. Consult your system documentation for details. You might use a command
111 like one of these on your system, or a different command:
114 $ sudo /etc/init.d/php-fpm restart
115 $ sudo service php5-fpm reload