When to restart and not reload Nginx?
NginxDeploymentPassengerNginx Problem Overview
When is it necessary to restart nginx and reload will not suffice?
Does it make a difference if an extension like passenger is used?
Should the service be restarted if it consumes too much memory. Any other reasons for restarting Nginx, particularly after a configuration change either in an extension or a Nginx core config?
After making a configuration change, one can either restart or reload nginx, via the binary itself or the init.d script "/etc/init.d/nginx -h" on Ubuntu. Which method should be preferred?
Nginx Solutions
Solution 1 - Nginx
Reloading nginx is safer than restarting because before old process will be terminated, new configuration file is parsed and whole process is aborted if there are any problems with it.
On the other hand when you restart nginx you might encounter situation in which nginx will stop, and won't start back again, because of syntax error.
Reloading terminates the old process, so any memory leaks should be cleared anyway.
Solution 2 - Nginx
I've experienced a case where I needed to restart nginx to have listen directives for a new IP adress kick in.
Solution 3 - Nginx
Ztyx is right - restarting when changing a listen directive is required in some cases.
With 1.6.x, you can reload when changing the listen IP address, but you need to restart when listening from "*:80" to an IP address "x.x.x.x:80".
I have only confirmed this with IPv4, behavior for IPv6 may be similar.