Platform services

Use Admin > Platform > Services on a self-managed installation to see the state of every service, restart and stop a service, and follow the maintenance jobs those actions start. For the other tabs, see Update DataMind OS and Read container logs; for the area itself and who can open it, see Platform.

Read the service state

1. Open Admin > Platform > Services.
2. Read the strip at the top. It counts the services that are up, shows how many one-off setup services completed when the installation has any, and flags each condition that needs attention with its count.
3. Open a group to see its services. A group that holds a service needing attention opens on its own and cannot be collapsed until nothing in it needs attention.
4. Read each row:
   • The service name, with a critical badge when the platform depends on the service and a one-shot badge on setup services that run once.
   • The condition badge: Up, Completed, Starting, In progress, Unhealthy, Flapping, Failed, Down or Unknown.
   • Under the name, the container's name, or no container when the service has none.
   • A ↻ restart count beside the badge, shown only above zero; its tooltip reads Docker restart count.
   • The container's status, or Not deployed when the service has no container here.
5. Click Refresh to reload the state at once. The page also keeps itself current, and updates faster while a job runs or a service is still settling.

Up means a service is running and Completed that a one-off setup service finished cleanly. Starting and In progress mean the container is still changing; Unhealthy, Flapping, Failed and Down need attention. A condition that cannot be read shows Unknown.

Finished one-off setup services are hidden by default. Turn on Show completed init in the strip to bring them back; while they are hidden, the group header counts how many.

Restart or stop a service

1. Open Admin > Platform > Services.
2. On the service's row, click the restart icon or the stop icon. Each carries the action and the service name, for example Restart <name>.
3. Read the confirmation before you confirm:
   • The title names the action and the service, for example Restart <name>?.
   • A restart brings the container back in place; services that depend on it keep running and reconnect on their own. A restart does not apply configuration changes.
   • A stop takes the container down, and it stays down until it is started again. The Services tab has no start button.
   • For a critical service, the confirm button reads Restart anyway or Stop anyway.
4. Confirm. A toast reads Restart started or Stop started and names the service. The job appears in Jobs, and the row usually moves to Starting straight away.

Actions are per row, one service at a time. While a maintenance job is running or the Installer is being replaced, the buttons are disabled until it finishes.

Follow the jobs

The Jobs list sits beside the service groups (below them on a narrow window) and shows the installation's maintenance jobs, newest first. Each row shows a status badge, running, completed, failed or cancelled, the job's label and its message.

A job stays in the list for an hour after it ends; when nothing has run yet, it reads No jobs yet.

While a job is running, its live output shows above the list. The view stays at the end while you read it; if the connection drops, the corner reads Reconnecting… and the page reconnects on its own. An empty output pane reads Waiting for output….

Who can restart and stop

• View Platform Services opens the tab and shows every service.
• Restart Platform Services adds the restart action, and Stop Platform Services adds the stop action.
• Platform Administrator holds all of them, and Platform Viewer is read-only. See Platform for the full matrix, and Roles and permissions for assigning permissions.

Limits and edge cases

• One maintenance job runs at a time; while it runs, or while the Installer is replaced, restart and stop wait. See Update DataMind OS.
• Stop is available only while the service is running; otherwise its button is disabled.
• A one-off service, or a service with no container, has no action buttons.
• When the platform cannot read the group definition, the strip reads Service schema unavailable - groups are approximate, and every service is shown in one group. Click Refresh to try again.
• When the platform reports the installation's deployment files as incomplete, the strip reads Deployment files incomplete on the host. The list below still shows what is running.
• The page reads Loading platform services while it opens, and the job list reads Loading jobs while it loads.
• Your collapsed groups and the Show completed init switch are remembered in this browser.
• If a restart or stop cannot start, the toast reads Could not start the restart or Could not start the stop, with the reason. If the groups cannot load, the page shows Service groups unavailable: with the reason and a Retry button. More in Administration troubleshooting.

Questions, answered

What is the difference between Restart and Stop?

A restart brings the container back in place, and services that depend on it keep running and reconnect on their own; a restart does not apply configuration changes. A stop takes the container down and it stays down until it is started again. The Services tab has no start button.

Why are the Restart or Stop buttons missing from a row?

A missing button means your role lacks the matching permission: Restart Platform Services or Stop Platform Services. A one-off service, or a service with no container, has no action buttons either.

Why are the Restart and Stop buttons greyed out?

A maintenance job is running or the Installer is being replaced, so the page blocks new actions until it finishes. Stop is also greyed out while the service is not running.

Why did a group open by itself and not collapse?

Something in the group still needs attention, so it stays open and its toggle is disabled until nothing in it does. Hovering the header shows Kept open while something in this group needs attention.

How do I see the one-off setup services that already finished?

Turn on Show completed init in the strip. Finished one-off services are hidden by default; while they are hidden, the group header counts how many.

What does the "↻ 2" on a row mean?

It is the container's restart count, shown only when it is above zero; hovering it shows Docker restart count. A count that keeps rising points to a service that keeps falling over.

What does the critical badge mean?

The platform depends on that service, so its confirmation uses stronger wording: the button reads Restart anyway or Stop anyway.

How long does a job stay in the list?

A job stays in Jobs for an hour after it ends, and the newest job is shown first.

Can I watch what a running job is doing?

Yes. While a job runs, its output streams above the jobs list and the view follows the end until you scroll up. If the stream drops, the corner reads Reconnecting… and the page reconnects on its own.

What does "Service schema unavailable - groups are approximate" mean?

The platform could not read the deployment definition that groups the services, so every service is shown in one group. The states below are still read from the running installation; click Refresh to try again.

Does the page update on its own?

Yes. It keeps itself current and updates faster while a job runs or a service is still settling. Click Refresh to reload it at once.