All articles

Getting Started

What is CICDoo Getting started: the onboarding wizard The Dashboard and Infrastructure Map

Concepts

Production, staging and development stages Domains, subdomains and SSL Odoo versions and editions (Community vs Enterprise) Workspaces and team collaboration

Servers

Adding a server Server domains and DNS Using a load balancer Server actions: deploy, logs and charts Deleting a server

Projects & Git

Creating a project Connecting GitHub Project GitHub settings and webhook Connecting GitLab Branches and instances Tagging and filtering projects High availability with app nodes Project environments, extensions and deletion

Instances & Console

Creating an instance Restarting, stopping and removing an instance Merging branches between stages Web IDE and remote access SSH access to instances Instance settings explained Deployments and the job queue

Agent Tasks

What agent tasks are Setting up agent tasks Running a task and reviewing the result Agent time and top-ups Agent insights and task filters

Monitoring & Backups

Monitoring your instance Backups and restore S3 storage, uploads and bulk backup actions Alert notifications (email and SMS)

Workspaces & Permissions

Inviting workspace members Member permissions and resource access A member cannot see or use a resource Audit log and server activity

Account & Security

Two-factor authentication (2FA) Profile and integrations settings Passwords and account recovery

Billing & Plans

Plans and pricing Upgrading and managing your subscription If a project subscription goes unpaid The channel partner program Onboarding a client as a partner

Support & Tickets

Opening a support ticket Getting help from the CICDoo team

Troubleshooting

Troubleshooting: cannot connect a server Troubleshooting: a deployment failed Troubleshooting: git push fails with 403 after moving a repository Troubleshooting: my instance is down or slow Troubleshooting: domain or SSL problems

Troubleshooting

Troubleshooting: a deployment failed

How to find the log of a failed deployment job, fix the most common causes, and retry with a restart.

Finding the job log

Every deployment runs as a job in the queue, and every job keeps a log. That log is almost always where the answer is.

  1. Click Queue in the main sidebar. Each job shows its server, instance, type, a status (Pending, Running, Processing, Completed or Failed), who started it and when.
  2. Click Filters to narrow the list to one project or instance if needed.
  3. On the failed job, click Logs. The Job Log dialog opens; for jobs still running it updates live.
  4. Read the last lines of the log. Errors usually appear near the end.

You can also start from the instance:

  1. Open the instance in the Console and click the Queue tab.
  2. The Recent Jobs list shows that instance's jobs. Click Refresh to update it.
  3. Click View log on a job to open the same Job Log dialog.

Fixing the common causes

Work through these checks in order.

  1. Wrong or missing branch: if the branch the instance follows was renamed or deleted in your repository, the code cannot be pulled. Check that the branch still exists.
  2. Code errors during the module upgrade: a Python error or a broken XML file in your addons aborts the upgrade. The traceback in the job log names the module and file. Fix the code, push, and retry.
  3. Server offline: no job can run on a server that cannot be reached. On the Servers page, check the server's status badge before retrying.
  4. Server needs a redeploy: if the server card shows Redeploy required, run Deploy from the server's Actions menu first, see Server actions: deploy, logs and charts.
  5. Push rejected after moving the repository: see Troubleshooting: git push fails with 403 after moving a repository.

Retrying the deployment

  1. In the instance Console, click Restart.
  2. In the Restart Instance dialog, choose Soft Restart (restarts Odoo and upgrades modules). This reruns a failed module upgrade with your corrected code.
  3. If the whole container is misbehaving, choose Hard Restart (restarts the Docker container) instead.
  4. Follow the new restart job in the Queue tab and open its log the same way.

If the Console shows a Hard restart required banner, use Restart Instance in that banner and pick Hard Restart.

When to escalate

Open a support ticket when:

  • The job log shows an error that does not come from your own code.
  • Jobs stay Pending or Running for an unusually long time with no progress in the log.
  • The same deployment keeps failing after you fixed the visible cause.
  1. Open the Tickets page and click New Ticket.
  2. Set Issue Type to Instance (or Server) and choose the resource.
  3. Paste the relevant part of the job log, especially the final lines. That log is the single most useful thing you can include.
  4. Click Create Ticket.

Related: Deployments and the job queue, Restarting, stopping and removing an instance, Opening a support ticket.

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

Previous Troubleshooting: cannot connect a server Next Troubleshooting: git push fails with 403 after moving a repository

Still stuck? Open a ticket from the app or talk to an engineer.