.. /*  
    * This file is part of the SavaPage project <https://www.savapage.org>.
    * Copyright (c) 2026 Datraverse B.V.
    * Author: Rijk Ravestein.
    *
    * SPDX-FileCopyrightText: (c) 2020 Datraverse B.V. <info@datraverse.com>
    * SPDX-License-Identifier: CC-BY-SA-4.0
    *
    * For more information, please contact Datraverse B.V. at this
    * address: info@datraverse.com
    */

.. _app-tools-start-stop:

Stopping and Starting the Server
--------------------------------

Normally there is no need to stop or start the server. This is only
required when:

-  Performing an :ref:`off-line backup <app-tools-savapage-db-export>`.

-  Migrating to an :ref:`external database <ch-external-db-migration>`.

-  :ref:`Upgrading <app-upgrading>` the application.

The SavaPage application server may be stopped or started by executing these
``systemd`` commands:

.. callout::

   .. code-block:: bash
      :caption: commands

       sudo systemctl start savapage.service    # <1>
       sudo systemctl stop savapage.service     # <2>
       sudo systemctl restart savapage.service  # <3>
       systemctl status savapage.service        # <4>

   .. annotations::
       :1: Starts the application server.
       :2: Stops the application server.
       :3: Stops and starts the application server in one go.
       :4: Echoes the run status of the application server.

If  SavaPage is installed on a SysV system, use the appropriate
``service`` commands.

.. important::

   When you start the application server, wait approximately 10 seconds
   for the service to initialize before accessing the Web App interface.

.. note::

   When the server is stopped, any SavaPage Web App loses connection
   and will be unloaded, and a browser message like "This site can’t be
   reached" will be shown. The user must wait till the server is started
   again, and press any Reload (Try Again) button to resume.