Menu: Stop

• STOP - (Option 1)

  • Overview: Stops the running Plex Media Server process if programatic control is available.

  • Availability: If DBRepair can control services on your host, selecting stop (or 1) halts Plex Media Server directly. If host control isn't available, the menu instead reads (Not available. Stop manually.), and you must stop the server yourself before running commands that require it.

  • Technical quirks & behavior: Plex Media Server must be stopped before DBRepair can operate on the database files. Stopping/starting in containers depends on the container execution control mechanism. Some images are designed with an "Always Running" philosophy and do not allow DBRepair to stop/start Plex Media Server under program control. For these images, the only mechanism, subject to the time constraints of any health check, is to type kill -15 $(pidof 'Plex Media Server') at the container command line, wait for Plex Media Server to shut down, and then invoke DBRepair. After the database tasks are completed and you've exited the container, restart it through your normal docker start mechanism. If your image supports start/stop, it is shown in the menu for you to use; if not, you'll need to disable health checks before safely running this tool.

    • DBRepair waits up to 60 seconds for Plex Media Server to stop. If it is still running after that, Stop reports failure.
    • If PMS is already stopped Stop says so and does nothing.
    • On Windows, Stop shuts down Plex Media Server, its Script Host, Tuner Service and Transcoder, and stops the Plex Update Service. Start restarts the Update Service if it was running.

  • Safety status: Safe.

---

Back