Il 28/05/2025 23:42, Mark Sapiro ha scritto:
On 5/28/25 08:27, roughnecks via Mailman-users wrote:
It's the manage.py qcluster whatever is called. I have shut down MM for the time being, because I'm not fully motivated to have it running, so I can't be more accurate right now.
I don't know how qcluster is configured in the Debian packages (which are out of date and possibly buggy anyway). You may be using django-q <https://django-q.readthedocs.io/en/latest/> and if so, you should migrate to django-q2 <https://django-q2.readthedocs.io/en/master/>. Both typically use memcached as a backend.
I wouldn't know how to migrate and if that means doing anything not in the debian-way (haven't opened any link so far).
About qcluster configs, yes, all correct but there is no configuration for caches, so probably it's the default one you specified. I can look into this.
You can get info about what qcluster is doing with
manage.py qinfoand monitor things withmanage.py qmemoryandmanage.py qmonitor.
Thanks, helpful.