[Q] ERROR no such table: django_q_schedule

[amo13]

Since I updated from 1.4.1 to 1.4.4, every 30 seconds [Q] ERROR no such table: django_q_schedule is logged by the scheduler.

Could this be a dependency issue? If so, any idea which one it could be? (I have the current django-q 1.3.6)

[TheFehr]

Missing tables normally suggests the database migrations not having worked properly. How do you have it installed?

If with docker-compose, try this command:
docker-compose exec webserver python3 manage.py showmigrations
This should give you a list of all migrationsland show if they were successfully run.

[amo13]

Thank you for your reply.
I don't think I am mixing up versions since I only have one installed. I use the system packages (from distro repo) and have no virtual environment set up. Before the update, I was on Q 1.3.5 with paperless 1.4.1.
Maybe the message can be ignored, though it is flooding the logs

[amo13]

On another machine, I have paperless 1.4.4 (set up the same way) with Q 1.3.5 and I don't get the message about the missing table.

[jonaswinkler]

Scratch that about the table. The migration in django q 1.3.6 only added a field to the schedule table.

[amo13]

This is odd... I did a new installation of 1.4.3 in a VM, uploaded one document, updated to 1.4.5, and now I get the following message logged every 30s

[Q] ERROR no such column: django_q_schedule.cluster

On my productive instance, I still get [Q] ERROR no such table: django_q_schedule every 30s.
But it looks like somehow my database got messed up, because I also have the BadSignature error and the missing documents_document error...
I'd really like to know what went wrong, so I can prevent it in the future, but it looks like it won't be easy to find out.

If I need to reinstall, is there a clean way to keep or reimport the database? I put quite some effort in setting up everything, tagging etc.

[amo13]

Ok, so the error does not show up if I rename ./paperless.conf to ./paperless.conf.bak. The update pulls the paperless.conf template in the paperless directory.

What I did not expect is that this template ./paperless.conf takes precedence before /etc/paperless.conf. So I got this bug because my paperless instance was using the template config instead of mine.

So I must ask: shouldn't either the template paperless.conf file be renamed to paperless.conf.template or the precedence be changed to first /etc/paperless.conf and only second ./paperless.conf?