Server actions: deploy, logs and charts

The Servers page at a glance

Each server is shown as a card with:

• Its name, hostname, a masked IP address and when it was last seen.
• A status badge. Servers are Online or Offline based on their regular check-ins with CICDoo, refreshed every 30 seconds. Servers monitored by UptimeRobot show Online, Down, Degraded, Paused or Pending instead.
• CPU, Memory and Storage usage with colored bars. Click "Ring view" above the cards to show the same figures as circular gauges, and "Bar view" to switch back. Your choice is remembered in this browser.
• Uptime bars, on monitored servers only: a strip covering the last 24 hours, green when up and red when down (hover a bar for details), with the 30-day uptime percentage and response time underneath. A new monitor shows "Collecting data..." until it has history.

Use the search box in the top bar to find a server by name, and the pagination controls at the bottom to move between pages.

The Actions menu

Click "Actions" at the bottom of a server card to open the menu:

• Deploy: queues a deployment for the server itself (nginx, Docker, certificates and the monitoring agent). For servers on your own domain, CICDoo re-reads the hostname's DNS first.
• Upgrade All Instances: queues an upgrade for every instance on the server that has auto-restart enabled.
• Restart All Instances: queues a restart for every instance on the server that has auto-restart enabled.
• Activity: opens the server's activity feed. Shown to the workspace owner and to members with the "Audit log" permission.
• Charts: opens the "Server Monitoring" window. Grayed out until the server has a stats source.
• Refresh DNS: re-reads the server's DNS, see Server domains and DNS.
• Edit Server: opens the "Edit Server" window.
• Delete Server: opens the delete window, see Deleting a server.

While a server is being deleted, the card shows a "Deleting" badge and the menu is replaced by the note "Tearing down containers. The server is removed when this finishes."

Server deploys are logged in the Queue: open the Queue page, find the server's Deploy job and click "Logs" to read its "Job Log", see Deployments and the job queue. To read an instance's Odoo logs, use the instance's Monitoring and Logs tabs, see Monitoring your instance.

Deploying a server

1. On the Servers page, click "Actions" on the server card.
2. Click "Deploy".
3. A message confirms that the deploy job has been queued. Follow its progress on the Queue page, see Deployments and the job queue.

Workspace members need the "Deploy servers" permission.

Upgrading or restarting all instances

1. On the Servers page, click "Actions" on the server card.
2. Click "Upgrade All Instances" or "Restart All Instances".
3. Confirm the prompt ("Upgrade all auto-restart instances on this server?" or "Restart all auto-restart instances on this server?").
4. A message tells you how many instances were queued.

Only instances with auto-restart enabled are included. If you are a workspace member, instances you do not have permission to restart are skipped, so the count can be lower than the number of instances on the server.

Viewing server activity

1. On the Servers page, click "Actions" on the server card.
2. Click "Activity". The "Server activity" window lists who did what on this server and on the instances it runs, newest first.
3. Click the arrow on an entry to see its details, where available.
4. Click "Load more" at the bottom for older entries, or "Refresh" at the top to reload.
5. Click "Open in audit log" to see the same entries on the full audit log page.

See Audit log and server activity for more.

Viewing CPU, memory and storage history

1. On the Servers page, click "Actions" on the server card.
2. Click "Charts" to open the "Server Monitoring" window.
3. Pick a time range at the top: 6h, 24h or 48h. Click the refresh button next to it to reload.
4. Read the summary tiles: Avg CPU, Avg Memory, Avg Storage and Avg Inodes.
5. Below them are the "CPU & Memory Usage", "Storage" and "Inodes" charts. Drag across a chart to zoom in, and double-click it or click "Reset zoom" to return to the full view.
6. Click "Close" when you are done.

If the window shows "No monitoring data", the server has not reported stats yet. Make sure the server's last deploy succeeded, wait a while and click "Retry".

Editing a server

The "Edit Server" window has the same five steps as the "Add New Server" wizard (Basics, Domain, Access, Maintenance and Review), see Adding a server. Workspace members need the "Edit server settings" permission to save.

1. On the Servers page, click "Actions" on the server card.
2. Click "Edit Server". The current settings load into the window.
3. Move between steps with Next and Back, or click a step name at the top, and change what you need.
4. Click "Save Changes". It is available on every step.

Points that differ from adding a server:

• On the Domain step the toggle is labelled "Own Domain" and the hostname field "Domain Name". When CICDoo manages the address, the assigned cicdoo.com subdomain is shown under the IP field.
• "Advanced network options" also contains User SSH Access. Turn it on to let users with a registered SSH key tunnel to this server's instances and open a shell in their containers. Your own SSH users and root keys are not touched. See SSH access to instances.
• On the Access step, leave the password blank to keep the current one, or leave the key upload empty to keep the current key.
• On the Maintenance step, "Force Nginx Reinstall (next deploy)" and "Force Generate SSL (next deploy)" run once on the next deploy and then switch themselves back off. Leave them alone unless you are recovering from a broken server.

Changing the hostname changes the address of every instance on the server.

Redeploy required

A card can show an amber icon titled "Redeploy required". It means the CICDoo deployment pipeline has been updated and this server needs a redeploy to apply the latest changes.

1. Hover over or click the amber icon on the server card.
2. Click "Redeploy now". This queues the same job as the Deploy action.

The "Redeploy now" button is shown only to people allowed to deploy servers.

This server is being refused

A card can show a red warning icon titled "This server is being refused". It means the server is calling CICDoo from an address that is not one of its known addresses, so CICDoo refuses it. Until this is fixed, monitoring, container supervision and SSL renewal do not run for the server. The panel shows the address it is calling from, how many times, and the addresses CICDoo knows.

If the address really is your machine (for example, it connects out through a different address than it listens on):

1. Hover over or click the red icon on the server card.
2. Check the address shown in the panel.
3. Click "This is my server, trust it".
4. Confirm the prompt, which names the address. Only confirm if it is genuinely your machine.
5. The page reloads and the address is now allowed to act as this server.

Workspace members need the "Edit server settings" permission. If you do not recognise the address, do not trust it; open a support ticket instead. You can also record the extra address yourself in the Connectivity IP field under "Advanced network options" in Edit Server, separated by a comma and placed after the server's real address, because the first address in that field is used for SSH.

Related: Adding a server, Server domains and DNS, Deleting a server, Monitoring your instance.

If you get stuck, open a support ticket from the Tickets page or the chat widget.