servd

Documentation

Documentation > Troubleshooting >

Restart Instances

Every now and again, things don't go to plan. Rogue PHP processes and SQL queries might start misbehaving and cause your project to become unresponsive. When this happens, it can help to turn everything off and on again.

Warnings #

Before proceeding, here are some of the things to be aware of that will impact all of your project's environments:

  • Any currently-running Servd tasks (e.g. "Syncing updates", "Cloning environment") may error prematurely and leave your project in a broken state. We strongly recommend avoiding restarting your project's instances if any tasks are running, unless you believe the tasks themselves are responsible for issues that you're encountering.
  • Restarting redis will empty Craft's cached data, sessions and Servd's static page caches. This will log all users out and will likely cause a surge in uncached responses and a brief deterioration in performance.
  • Restarting the database will cause long-running database SQL queries to terminate early.
  • Restarting the dedicated queuer runners will cause queue jobs currently being performed to error out and require re-running.
  • Restarting the PHP instances will interrupt unfulfilled web requests and cause them to receive a 5XX response.

Steps #

To restart your's projects instance, perform the following steps:

  1. Go to your project's Troubleshooting page.

  2. Under the "Restart Instances" section, click the "Restart Instances" button.

  3. Wait for the "Restarting all instances" task in the task bar to complete.

  4. Once completed, your project instances should have all finished restarting.