Data export kobo-docker not working

User Support
1

using kobo-docker for a local server

not able to export data.

xls and csv

just running forever even with a project that have only 1 entry should be instant …

any idea on how to solve this ?

also have this in server logs

kpi_1 | celery beat v4.2.1 (windowlicker) is starting.
kpi_1 | ERROR: Pidfile (/tmp/celery_beat.pid) already exists.
kpi_1 | Seems we’re already running? (pid: 85)
kpi_1 | ERROR: Pidfile (/tmp/celery.pid) already exists.
kpi_1 | Seems we’re already running? (pid: 81)
kpi_1 | ERROR: Pidfile (/tmp/celery_sync_kobocat_xforms.pid) already exists.
kpi_1 | Seems we’re already running? (pid: 84)
kpi_1 | celery beat v4.2.1 (windowlicker) is starting.
kpi_1 | ERROR: Pidfile (/tmp/celery_beat.pid) already exists.
kpi_1 | Seems we’re already running? (pid: 85)
kpi_1 | ERROR: Pidfile (/tmp/celery.pid) already exists.
kpi_1 | Seems we’re already running? (pid: 81)
kpi_1 | ERROR: Pidfile (/tmp/celery_sync_kobocat_xforms.pid) already exists.
kpi_1 | Seems we’re already running? (pid: 84)
kpi_1 | celery beat v4.2.1 (windowlicker) is starting.
kpi_1 | ERROR: Pidfile (/tmp/celery_beat.pid) already exists.
kpi_1 | Seems we’re already running? (pid: 85)
kpi_1 | ERROR: Pidfile (/tmp/celery.pid) already exists.
kpi_1 | Seems we’re already running? (pid: 81)
kpi_1 | ERROR: Pidfile (/tmp/celery_sync_kobocat_xforms.pid) already exists.
kpi_1 | Seems we’re already running? (pid: 84)
kpi_1 | ERROR: Pidfile (/tmp/celery_beat.pid) already exists.
kpi_1 | Seems we’re already running? (pid: 85)
kpi_1 | celery beat v4.2.1 (windowlicker) is starting.

2

ok found the solution

had to open a shell to container with

docker exec -it kobodocker_kpi_1 /bin/bash

then go to \ using cd … multiple time

then cd tmp

then delete the 3 files here

and voila !! everything work :slight_smile:

3

ok look like a bug because every time server restart i got this error

and i have to do this workaround

( have to do it fast after boot because ths system hang rapidly)

— work ok if the server stop with docker-compose stop
but if the machine shut down without docker-compose stop

or a electricity faillure then this bug apear when i restart it