Status is the first screen after sign-in. It shows whether DataMind OS is installed, running and up to date, and holds every action on the deployment.
| Part | What it shows |
|---|---|
| The diagram | One circle per service group, joined to a centre chip. Before the first install, the chip carries the Start button |
| Right panel | Services, by group, with each service's state. Job Logs shows every event of the current or last job |
| Bottom action bar | Update, Check for updates, Start, Stop, Terminate and Restart |
Click a service to see its Container, Health, Uptime and a live Logs stream.
The address pill and the Installer pill in the top bar are on The DataMind Installer.
| The screen shows | What is happening |
|---|---|
| Loading DataMind Installer | The screen starts. If the Installer does not answer, it reads Waiting for the DataMind Installer backend… until it does |
| The centre chip with Start | No DataMind OS image is on the host yet. Start opens the first install: see Install on a fresh host |
| Initializing DataMind OS | The install job downloads the install files and prepares the deployment. Then each service shows its Layers and Downloaded progress while the images are pulled |
| Starting DataMind OS | The services come up. The screen reads This may take a couple of minutes |
| Running | The diagram shows each group's health |
While the screen is open, it checks the registry for newer DataMind OS images and a newer Installer every 30 minutes.
| Colour | The group has |
|---|---|
| Red | At least one service that failed or keeps restarting |
| Green | No failed service, and at least one running, starting or unhealthy service |
| Grey | Nothing running, or no state reported |
A service's Health row shows its own health check. A finished one-shot service shows completed
beside its name. Health and Uptime appear only when they apply.
The action bar, Cancel and the restart buttons appear for admins.
| Action | What it does | Interrupts DataMind OS |
|---|---|---|
| Update | Downloads the current install files, pulls the current images and recreates the services that changed. Available when a check found a newer or missing image; otherwise its tooltip reads DataMind OS is already up to date | Yes, a short restart of what changed |
| Check for updates | The circular-arrow icon beside Update. Compares the images on this host with the registry, and checks for a newer Installer | No |
| Start | Starts every stopped service, and recreates any service whose saved settings changed. Greyed out with N images missing — run Update first until the images are on the host | No, unless saved settings are pending |
| Restart | Restarts the services in place, with the environment they were created with. Saved configuration needs Apply changes on Configuration | Yes, briefly |
| Restart a group or a service | The same, from the right panel. One-shot services have no restart button | Yes, briefly |
| Stop | Stops every service gracefully. DataMind OS stays offline until Start | Yes |
| Terminate | Force-stops every service with SIGKILL. For a service that ignores Stop | Yes, and in-flight writes can be lost |
| Cancel | Cancels the running job. Recreated services stay recreated: finish with Start, or stop them with Stop | Can leave it part-way |
| What you see | What it means |
|---|---|
| A download icon titled Update Available | A newer image for that service is in the registry. Update takes it |
| Service catalog is outdated | The configuration schema on the host has no service list. Grouping uses a built-in default and critical-service warnings are off. The next Update downloads a fresh schema |
| N ungrouped services | Services in the deployment's Compose file that the schema places in no group. They run normally |
| Connection to DataMind Installer lost — reconnecting… | The browser lost its event stream during a job. It reconnects on its own. Reload the page if it does not |
| Container failed to start: … | That container exited with an error. Its logs are below the message |
Next steps for each are on Troubleshooting.
You are signed in with a user account. An admin can change your role on the
Users screen.
Update, Restart, Stop and Terminate, and Start when saved settings are pending. Cancel can leave it part-way. Reading logs interrupts nothing.