[GeoNode-devel] Help with celery and geonode.security.tasks.synch_guardian
Toni Schönbuchner
toni.schoenbuchner at csgis.de
Thu Feb 14 01:10:40 PST 2019
Just for the record,
I´ve recorgnized that dirty_resources always counts 0.
Lesson learned be sure to use correct settings ...
export DJANGO_SETTINGS_MODULE=geonode.local_settings; celery worker --app=geonode.celery_app:app -Q default,geonode,cleanup,update -f /tmp/celery/celery.log -B -l debug
Now celery is cooking :)
> Message: 1
> Date: Wed, 13 Feb 2019 13:30:39 +0100
> From: Toni Schönbuchner <toni.schoenbuchner at csgis.de>
> To: geonode-devel <geonode-devel at lists.osgeo.org>
> Subject: [GeoNode-devel] Help with celery and
> geonode.security.tasks.synch_guardian
> Message-ID: <2A1E849C-2683-475B-835F-637D9B6CA86F at csgis.de>
> Content-Type: text/plain; charset=utf-8
>
> Hi there,
>
> Maybe somebody can shed some light into celery on latest master.
>
> In settings I´ve set
> DELAYED_SECURITY_SIGNALS = True
> further started celery workers with
> celery worker --app=geonode.celery_app:app -Q default,geonode,cleanup,update -f /tmp/celery/celery.log -l debug
> and beat with
> celery beat --app=geonode.celery_app:app --pidfile="/tmp/celerybeat.pid" -l debug
>
> I would expect that `geonode.security.tasks.synch_guardian` should update resoure permissions
> in background, unfortuantely this is not happening and newly uploaded layers show a warning:
> SECURITY NOT YET SYNCHRONIZED
>
> Do I missunderstand the taks queue – or have overseen something?
>
> Thanks,
>
> Toni
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-devel/attachments/20190214/144edd1e/attachment.html>
More information about the geonode-devel
mailing list