Gramps 6.0.8
Gramps Web API 3.19.0
Gramps Web Frontend 26.7.1
Gramps QL 0.4.0
Sifts 1.3.1
locale: en
multi-tree: true
task queue: true
OCR: true
chat: true Web Sync version)
Hi,
is this your own server or Grampshub?
Hi David, It is GrampsHub. And it still shows processing.
Mark
There is currently no process_transactions running. It looks like you were unlucky and the task was running at the exact moment when the task scheduler was being restarted due to an upgrade.
There is no way for the frontend to know this task will never finish, so it just shows its last known progress state. It should automatically disappear after 24 hours and there is nothing to do at this moment. You can just ignore it.
The other question is what happened to the sync transaction. You can check in the revision history whether it was actually applied - in this case the task may have been aborted while udpating the search index, so worst case you’d have to update the search index manually (one click).
If it hasn’t been applied, all is fine (database changes are applied as transactions so they do not leave the database in an inconsistent state), so you can just sync again.
It happened once before and timed out after ~ 4 hours. Thanks for the explanation. Can I do a sync now or should I wait until the in process notification clears? No problem if it didn’t apply the changes, I will resync from the GRAMPS desktop anyway.
Yes, no problem to sync now, let me know in case it doesn’t work as expected.
Previous (stalled) sync left no revisions record, so it must have aborted.
Current sync completed successfully with 100+ updates in about 3 minutes and updated the revisions record
The stale In Process Notification from previous sync persists.
Thanks for the explanation and all seems good again.
Mark.