System
See whether the platform is working normally, whether every node runs the same Release, and which problems to report to the server administrator.
This page reads the System page to see whether the platform is working normally and which problems to report to the server administrator. The System page is view-only. Open it whenever you like. Nothing changes.
Your role needs Can edit configuration.
See the system's status
The platform has two groups: nodes (the back-end parts that run separately) and Apps (the web pages people open). The System page shows nodes only.
- Open System in the menu and wait a moment, because Configuration has to ask every node first. If a node does not answer, it can take several seconds.
- Read the bar under the box at the top.
- "All nodes are on Release 5.0.0." means all is well.
- "Nodes are on different Releases" is normal during an Upgrade. If no Upgrade is under way, tell the server administrator.
- "No node answered." Tell the server administrator at once.
- Go through the Nodes, Migrations and Preflight panels and look for a red row or the word Failed. The sections below say what to look for in each panel.
Press Refresh to ask again. While a Migration is running, the page refreshes itself every 10 seconds.
Nodes
The Nodes panel has one row per node. The State column should say Ready in every row.
| State | What to do |
|---|---|
| Starting, Preflight, Waiting for a Migration or Migrating | The node is starting. Wait. |
| Refused to start (red row) | The node found a problem and will not start. Send the message under the state to the server administrator. |
| Not answering (grey row) | The node has stopped or cannot be reached. Tell the server administrator. |
Migration progress
A Migration is a one-time change to existing data that a new Release makes during an Upgrade. The Migrations panel shows every Migration. Look at the State column.
| State | What to do |
|---|---|
| Done | Nothing to do. |
| Running | Wait. The Progress column says how far it has got. |
| Paused | The node doing this work has stopped. The Migration continues by itself when the node starts again. If it stays stuck for long, tell the server administrator. |
| Failed | Press the arrow at the left of the row, read the Error, and send it to the server administrator (Troubleshooting). |
If a row says "3 skipped", the work is finished but some entries could not be done. Press the arrow to see which ones and why.
Preflight
Preflight is the check a node makes before it starts. The Preflight panel shows the result for each node. A node with a Failed or Warning entry opens by itself. Each entry has a Fix. Send it to the server administrator (Preflight checks).
Release history
The Release history panel says which Releases this site has run and when each began, newest on top. Going back to an older Release also appears as another row.
What the Overview reports from this page
The Needs attention block on the Overview takes items from this page. Press Review to come here.
| The Overview says | What to do |
|---|---|
"Migration <id> failed in <database>." | Read the Error in that row and send it to the server administrator. |
"<node> refused to start." | Send that message to the server administrator (Troubleshooting). |
| "Nodes are on different Releases: ..." | Normal during an Upgrade. If no Upgrade is under way, ask the server administrator to run the Upgrade again (Upgrade). |
"Migration <id> is paused in <database> ..." | Ask the server administrator to restart that node. |
"<node> does not answer." | Ask the server administrator to check that node. |
"Migration <id> skipped <count> entries." | Open that row and read the entries one by one. |
"Migration <id> is running in <database> ..." | Nothing to do. It is only progress. |