Hello! I have a question concerning reselling hosting using Ubuntu 16 and Plesk. When a plesk client updates his php version, all of the server's websites go down for a few seconds and display a 503 error.
Is this a problem that can be resolved by Plesk settings, Ubuntu, or an alternative operating system?
Restarting the PHP Update Server
-
ashleymiller967
- Posts: 12
- Joined: Thu Jan 22, 2015 3:40 pm
Re: Restarting the PHP Update Server
Restart your web server to restart PHP.
1. Restart the php service on Apache. If you're using Apache as your web server, use the following command to restart PHP:
2. Restart the PHP service on Nginx. If you're using Nginx as your web server, use the following command to restart it.
3. Restart the php service on Lighttpd.
1. Restart the php service on Apache. If you're using Apache as your web server, use the following command to restart PHP:
2. Restart the PHP service on Nginx. If you're using Nginx as your web server, use the following command to restart it.
3. Restart the php service on Lighttpd.
Re: Restarting the PHP Update Server
1. In the Management Console, open Services: OK -> Start -> Run -> "services.msc"
2. Choose php-fpm from the drop-down menu.
3. Select restart from the context menu by right-clicking.
2. Choose php-fpm from the drop-down menu.
3. Select restart from the context menu by right-clicking.
-
davidryan254
- Posts: 14
- Joined: Wed Jan 21, 2015 5:05 pm
Re: Restarting the PHP Update Server
A PHP extension is the PHP agent. The PHP agent is loaded and the newrelic.ini configuration file is parsed when your web server starts up and loads PHP. Until the web server is directed to reload and parse configuration files, it uses that configuration. The web server is prompted to do so when you restart it.
You're not sure why or when you'll need to restart your web server (Apache, PHP-FPM, Nginx, or something else) after:
Installing or updating the PHP agent is the first step.
2. Bringing PHP up to date to a major release version
3. Modifying the newrelic.ini or newrelic.cfg files to change any agent configuration parameters
4. Using the daemon's external startup mode
You're not sure why or when you'll need to restart your web server (Apache, PHP-FPM, Nginx, or something else) after:
Installing or updating the PHP agent is the first step.
2. Bringing PHP up to date to a major release version
3. Modifying the newrelic.ini or newrelic.cfg files to change any agent configuration parameters
4. Using the daemon's external startup mode
