Page MenuHomePhabricator

Documentation references to "restart your webserver" do not explicitly tell you to restart both HTTP and PHP server processes
Closed, ResolvedPublic

Description

While using nginx and trying to follow the instructions to fix post_max_size PHP parameter (which should be < 32M in order for this issue to appear), the instructions will say that only restarting the webserver is enough, but actually after editing the file, the issue is still not gone because, while using NGINX, you need to do (in debian) service php5-fpm reload.

It would be nice to include that command in the instructions so people don't get confused as only restarting the web server won't fix the issue.

Event Timeline

renannp updated the task description. (Show Details)
renannp added a subscriber: renannp.

Which instructions were you looking at which you found confusing? Can you point me at the document? (Or was it the setup warning itself?)

The command to restart php-fpm varies from system to system, but we try to remind users to restart php-fpm too in the text, at least.

I changed my configuration to be able to see the message again, so here is the screen shot:

pasted_file (412×764 px, 69 KB)

Actually it's not being advised about the php-fpm that needs to be reloaded, it only tells about the webserver restart.

epriestley triaged this task as Low priority.
epriestley renamed this task from Need better instructions to fix the issue related to post_max_size to Documentation references to "restart your webserver" do not explicitly tell you to restart both HTTP and PHP server processes.Dec 2 2015, 5:11 PM