Odoo 11本地数据库恢复后登录页空白无响应问题求助

Hey there, let's get this blank screen issue sorted out. From your error logs, the root cause is clear: a database integrity constraint violation that's blocking Odoo's core processes, leading to the unresponsive blank page when selecting your restored database.

What's Going Wrong? #

The automatic vacuum task (ir_autovacuum) that cleans up transient/temporary models is failing when it tries to process the change_password_user table. Specifically, it's trying to set the wizard_id column to NULL, but that column has a not-null constraint (it can't be empty). This error is halting critical background processes, which prevents the Odoo web interface from loading properly.

Step-by-Step Fix #

Follow these steps to resolve the issue:

1. Stop the Odoo Service
   First, shut down your Odoo server to prevent the failing cron job from running repeatedly while you fix the database.

2. Fix the Corrupted Database Record
   Open PgAdmin 4, connect to your restored database, and run these SQL commands in the query tool:

   • First, identify the problematic rows:

     SELECT * FROM public.change_password_user WHERE wizard_id IS NULL;
     

   • Delete these invalid rows (since this is a transient table for password reset wizards, deleting them won't cause data loss):

     DELETE FROM public.change_password_user WHERE wizard_id IS NULL;
     

3. Optional: Verify Other Transient Tables
   If you want to be thorough, check other transient tables (usually named with _transient_ prefix) for similar null constraint issues, but the error log points directly to change_password_user, so this may be enough.

4. Restart Odoo and Test
   Fire up your Odoo server again, then try accessing the login page and selecting your database. The blank screen should be gone now.

5. If Issues Persist

   • Force a full reload of Odoo's static assets by visiting: localhost:8069/web?debug=assets
   • Clear your browser's cache and cookies, then try again.

Preventive Tips for Future Restores #

• Always ensure the source and target Odoo versions match exactly when restoring databases.
• After restoring, run the following command to update all modules and fix any schema mismatches:

  odoo.py -d your_database_name --update all
  

内容的提问来源于stack exchange，提问作者Btashi