Skip to Content

Instance Troubleshooting

Troubleshooting OdooBot 40 views
Advanced troubleshooting guide for Odoo instance issues - startup problems, crashes, and recovery.

Instance Troubleshooting

Advanced troubleshooting guide for resolving Odoo instance issues.

Instance Won't Start

Symptoms

  • Instance shows "Stopped" and won't change to "Running"
  • Start button doesn't work or times out
  • Instance stuck in "Provisioning" state

Troubleshooting Steps

  1. Wait 2-3 minutes: Starting can take time, especially after updates
  2. Check your subscription: Ensure it's active and not suspended
  3. Try restarting instead of start (if available)
  4. Check resource limits: You may have hit plan limits
  5. Contact support if stuck for more than 10 minutes
Subscription Issue? If your subscription is past due, instances may not start. Check My Subscriptions for payment status.

Instance Crashes or Restarts Unexpectedly

Common Causes

CauseSignsSolution
Out of Memory (OOM) RAM usage near 100% before crash Upgrade plan or optimize memory usage
Runaway Process CPU spikes to 100% Identify and fix problematic code/cron
Bad Scheduled Action Crashes at same time daily Disable or fix the scheduled action
Database Issues Errors mentioning PostgreSQL Contact support for database repair

How to Identify the Cause

  1. Check Resource History: Look for spikes before crash
  2. Review Timing: Does it happen at specific times?
  3. Recent Changes: Did you install new modules or make changes?
  4. Check Scheduled Actions: In Odoo, go to Settings > Technical > Scheduled Actions

Database Connection Errors

Error Messages

  • "Database connection failed"
  • "FATAL: too many connections"
  • "Server closed the connection unexpectedly"

Solutions

  1. Restart Instance: Clears stale connections
  2. Wait and Retry: Temporary network issues resolve themselves
  3. Check Concurrent Users: You may have exceeded user limits
  4. Reduce Long-Running Reports: Heavy reports hold connections

Recovery from Errors

Instance in Error State

  1. Note any error messages displayed
  2. Try Restart from your portal
  3. If restart fails, try Stop then Start
  4. Check recent backups are available
  5. Contact support with error details

Restoring from Backup

If your instance is corrupted or has bad data:

  1. Go to My Instances > [Instance] > Backups
  2. Select a backup from before the issue
  3. Click Restore
  4. Confirm the restore action
Warning: Restoring a backup will overwrite all current data. Make sure to create a new backup first if you want to preserve current state.

Performance Optimization Tips

Reduce Memory Usage

  • Limit list view records (Settings > Users > Preferences)
  • Disable unused modules
  • Archive old records instead of deleting
  • Optimize scheduled actions frequency

Reduce CPU Usage

  • Avoid running heavy reports during business hours
  • Optimize custom code and queries
  • Spread scheduled actions throughout the day
  • Use asynchronous processing for bulk operations

Reduce Storage Usage

  • Compress images before uploading
  • Clean up old attachments and logs
  • Archive old accounting entries
  • Delete test databases if any

When to Contact Support

Create a support ticket if:

  • Instance won't start after 10+ minutes
  • You see database corruption errors
  • Repeated crashes with no clear cause
  • You need help interpreting error logs
  • Backup restoration fails

Create Support Ticket

Was this article helpful?
Search Articles
Still need help?

Our support team is ready to assist you.

Create Ticket
Skip to main content