[GH-ISSUE #1252] WebDAV Syncing stuck #832

Closed
opened 2026-02-25 22:38:14 +03:00 by kerem · 16 comments
Owner

Originally created by @lschricke on GitHub (Sep 9, 2022).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1252

Which version of floccus are you using?

4.17.1

Sync method

WebDAV

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

Firefox 104.0.2 (64-bit)

Which version of Nextcloud Bookmarks are you using? (if relevant)

No response

Which version of Nextcloud? (if relevant)

No response

What kind of WebDAV server are you using? (if relevant)

The box.com webdav server

Describe the Bug

Hello!
First of all, I find this tool very useful, so many thanks to the authors!

The bug I'm experiencing is that the Syncing for my two folders seems to be stuck. It stays in "Syncing" mode until I cancel it.

Here is the log file:

2022-09-09T08:52:04.229Z Starting sync process for account xxxxxxxxxxxx@dav.box.com
2022-09-09T08:52:04.254Z onSyncStart: begin
2022-09-09T08:52:04.254Z https://dav.box.com/dav/my-bookmarks.xbel.lock
2022-09-09T08:52:06.111Z https://dav.box.com/dav/my-bookmarks.xbel.lock
2022-09-09T08:52:08.273Z https://dav.box.com/dav/my-bookmarks.xbel.lock
2022-09-09T08:52:10.732Z https://dav.box.com/dav/my-bookmarks.xbel.lock
2022-09-09T08:52:13.414Z https://dav.box.com/dav/my-bookmarks.xbel.lock
2022-09-09T08:52:16.579Z https://dav.box.com/dav/my-bookmarks.xbel.lock
2022-09-09T08:52:20.450Z https://dav.box.com/dav/my-bookmarks.xbel.lock
2022-09-09T08:52:25.179Z https://dav.box.com/dav/my-bookmarks.xbel.lock
2022-09-09T08:52:30.768Z https://dav.box.com/dav/my-bookmarks.xbel.lock
2022-09-09T08:52:37.591Z https://dav.box.com/dav/my-bookmarks.xbel.lock
2022-09-09T08:52:45.823Z https://dav.box.com/dav/my-bookmarks.xbel.lock
2022-09-09T08:52:55.898Z https://dav.box.com/dav/my-bookmarks.xbel.lock
2022-09-09T08:53:08.369Z https://dav.box.com/dav/my-bookmarks.xbel.lock
2022-09-09T08:53:23.774Z https://dav.box.com/dav/my-bookmarks.xbel.lock
2022-09-09T08:53:43.173Z https://dav.box.com/dav/my-bookmarks.xbel.lock
2022-09-09T08:54:06.769Z https://dav.box.com/dav/my-bookmarks.xbel.lock
2022-09-09T08:54:36.106Z https://dav.box.com/dav/my-bookmarks.xbel.lock
2022-09-09T08:55:12.402Z https://dav.box.com/dav/my-bookmarks.xbel.lock
2022-09-09T08:55:57.831Z https://dav.box.com/dav/my-bookmarks.xbel.lock
2022-09-09T08:56:54.186Z https://dav.box.com/dav/my-bookmarks.xbel.lock
2022-09-09T08:58:04.604Z https://dav.box.com/dav/my-bookmarks.xbel.lock
2022-09-09T08:58:58.493Z Syncing failed with E027: Sync process was interrupted
2022-09-09T08:58:58.497Z onSyncFail

Expected Behavior

The syncing process finishes after some time.

To Reproduce

Not sure if this issue is easily reproducible. Is it related to Firefox? To webdav and box.com service? To Floccus itself? To the lock file maybe?

Any help is appreciated.

Thanks and have good day!

Debug log provided

  • I have provided a debug log file
Originally created by @lschricke on GitHub (Sep 9, 2022). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1252 ### Which version of floccus are you using? 4.17.1 ### Sync method WebDAV ### Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please. Firefox 104.0.2 (64-bit) ### Which version of Nextcloud Bookmarks are you using? (if relevant) _No response_ ### Which version of Nextcloud? (if relevant) _No response_ ### What kind of WebDAV server are you using? (if relevant) The box.com webdav server ### Describe the Bug Hello! First of all, I find this tool very useful, so many thanks to the authors! The bug I'm experiencing is that the Syncing for my two folders seems to be stuck. It stays in "Syncing" mode until I cancel it. Here is the log file: ``` 2022-09-09T08:52:04.229Z Starting sync process for account xxxxxxxxxxxx@dav.box.com 2022-09-09T08:52:04.254Z onSyncStart: begin 2022-09-09T08:52:04.254Z https://dav.box.com/dav/my-bookmarks.xbel.lock 2022-09-09T08:52:06.111Z https://dav.box.com/dav/my-bookmarks.xbel.lock 2022-09-09T08:52:08.273Z https://dav.box.com/dav/my-bookmarks.xbel.lock 2022-09-09T08:52:10.732Z https://dav.box.com/dav/my-bookmarks.xbel.lock 2022-09-09T08:52:13.414Z https://dav.box.com/dav/my-bookmarks.xbel.lock 2022-09-09T08:52:16.579Z https://dav.box.com/dav/my-bookmarks.xbel.lock 2022-09-09T08:52:20.450Z https://dav.box.com/dav/my-bookmarks.xbel.lock 2022-09-09T08:52:25.179Z https://dav.box.com/dav/my-bookmarks.xbel.lock 2022-09-09T08:52:30.768Z https://dav.box.com/dav/my-bookmarks.xbel.lock 2022-09-09T08:52:37.591Z https://dav.box.com/dav/my-bookmarks.xbel.lock 2022-09-09T08:52:45.823Z https://dav.box.com/dav/my-bookmarks.xbel.lock 2022-09-09T08:52:55.898Z https://dav.box.com/dav/my-bookmarks.xbel.lock 2022-09-09T08:53:08.369Z https://dav.box.com/dav/my-bookmarks.xbel.lock 2022-09-09T08:53:23.774Z https://dav.box.com/dav/my-bookmarks.xbel.lock 2022-09-09T08:53:43.173Z https://dav.box.com/dav/my-bookmarks.xbel.lock 2022-09-09T08:54:06.769Z https://dav.box.com/dav/my-bookmarks.xbel.lock 2022-09-09T08:54:36.106Z https://dav.box.com/dav/my-bookmarks.xbel.lock 2022-09-09T08:55:12.402Z https://dav.box.com/dav/my-bookmarks.xbel.lock 2022-09-09T08:55:57.831Z https://dav.box.com/dav/my-bookmarks.xbel.lock 2022-09-09T08:56:54.186Z https://dav.box.com/dav/my-bookmarks.xbel.lock 2022-09-09T08:58:04.604Z https://dav.box.com/dav/my-bookmarks.xbel.lock 2022-09-09T08:58:58.493Z Syncing failed with E027: Sync process was interrupted 2022-09-09T08:58:58.497Z onSyncFail ``` ### Expected Behavior The syncing process finishes after some time. ### To Reproduce Not sure if this issue is easily reproducible. Is it related to Firefox? To webdav and box.com service? To Floccus itself? To the lock file maybe? Any help is appreciated. Thanks and have good day! ### Debug log provided - [X] I have provided a debug log file
Author
Owner

@marcelklehr commented on GitHub (Sep 17, 2022):

Hello @lschricke

Sorry for the delay. I'm busy with work nowadays, but thank you for taking the time to give feedback.
It appears that a recent sync run did not finish and left a remnant lock file. You may simply delete my-bookmarks.xbel.lock in your box.com files and sync should work again. Also see the last faq: https://floccus.org/faq/

<!-- gh-comment-id:1250125106 --> @marcelklehr commented on GitHub (Sep 17, 2022): Hello @lschricke Sorry for the delay. I'm busy with work nowadays, but thank you for taking the time to give feedback. It appears that a recent sync run did not finish and left a remnant lock file. You may simply delete `my-bookmarks.xbel.lock` in your box.com files and sync should work again. Also see the last faq: https://floccus.org/faq/
Author
Owner

@lschricke commented on GitHub (Sep 19, 2022):

Hello @marcelklehr, thanks for your reply 👍. I did remove the lock files. Hopefully this will work fine!
Cheers!

<!-- gh-comment-id:1250825078 --> @lschricke commented on GitHub (Sep 19, 2022): Hello @marcelklehr, thanks for your reply 👍. I did remove the lock files. Hopefully this will work fine! Cheers!
Author
Owner

@lschricke commented on GitHub (Sep 21, 2022):

Hello, it did not really work I think. In fact the lock files get re-created afterwards but are never deleted from the box.com account. Is this normal?

Thanks

<!-- gh-comment-id:1253519839 --> @lschricke commented on GitHub (Sep 21, 2022): Hello, it did not really work I think. In fact the lock files get re-created afterwards but are never deleted from the box.com account. Is this normal? Thanks
Author
Owner

@lschricke commented on GitHub (Sep 29, 2022):

Hi @marcelklehr ,
In case it helps, here is a screenshot of the problematic lock file in the box.com account:

Screenshot 2022-09-29 at 10 38 41

Do you have an idea of what might causing the issue here?

Cheers!
Lucas

<!-- gh-comment-id:1261959767 --> @lschricke commented on GitHub (Sep 29, 2022): Hi @marcelklehr , In case it helps, here is a screenshot of the problematic lock file in the box.com account: <img width="898" alt="Screenshot 2022-09-29 at 10 38 41" src="https://user-images.githubusercontent.com/3723626/192983688-fbe5824b-97ee-483f-bfbb-e58d0cacc2d9.png"> Do you have an idea of what might causing the issue here? Cheers! Lucas
Author
Owner

@marcelklehr commented on GitHub (Oct 7, 2022):

I don't seem to be able to reproduce this. In my experiments floccus continues with sync if the lock file is older than 15minutes :/

<!-- gh-comment-id:1271519080 --> @marcelklehr commented on GitHub (Oct 7, 2022): I don't seem to be able to reproduce this. In my experiments floccus continues with sync if the lock file is older than 15minutes :/
Author
Owner

@marcelklehr commented on GitHub (Oct 7, 2022):

Can you query the lock file using curl and check the headers maybe? Would be interesting to see if Last-Modified actually shows the correct value.

<!-- gh-comment-id:1271522971 --> @marcelklehr commented on GitHub (Oct 7, 2022): Can you query the lock file using curl and check the headers maybe? Would be interesting to see if Last-Modified actually shows the correct value.
Author
Owner

@jdelker commented on GitHub (Oct 19, 2022):

Hey folks,

I'm also affected by this problem, but I suspect a different cause.
My Scenario: Floccus 4.17.1 with 2 "Nextcloud-Bookmarks Sync" shares on different folders.
Despite some early adopter bugs ;), this setup has operated fine for the last months/years.

Now, for quite some time, I also experience this "lock" on multiple devices (all Firefox).
From my recent observations I encounter this situation regularly (if not always?), when the particular Windows or Mac host is woke from hibernation, I notice that Floccus shows a current sync operation, but without anything happening.
In fact, it stays in that state basically permanently. How long this state persisted can be seen on the others share "Last synchronized" message, which not seldom shows "x days ago" - with a configured sync interval of 1h!

Since this situation does not recover automatically as I would conclude from your FAQ message about stale locks and the 30min lock override, I assume that this is not related to a lock file present on the server.

<!-- gh-comment-id:1283740820 --> @jdelker commented on GitHub (Oct 19, 2022): Hey folks, I'm also affected by this problem, but I suspect a different cause. My Scenario: Floccus 4.17.1 with 2 "Nextcloud-Bookmarks Sync" shares on different folders. Despite some early adopter bugs ;), this setup has operated fine for the last months/years. Now, for quite some time, I also experience this "lock" on multiple devices (all Firefox). From my recent observations I encounter this situation regularly (if not always?), when the particular Windows or Mac host is woke from hibernation, I notice that Floccus shows a current sync operation, but without anything happening. In fact, it stays in that state basically **permanently**. How long this state persisted can be seen on the others share "Last synchronized" message, which not seldom shows "x days ago" - with a configured sync interval of 1h! Since this situation does not recover automatically as I would conclude from your FAQ message about stale locks and the 30min lock override, I assume that this is not related to a lock file present on the server.
Author
Owner

@jdelker commented on GitHub (Oct 19, 2022):

I figured, that disabling/enabling the floccus extension does recover the problem!
Sync starts directly after that and completes successfully after roughly 1min.

<!-- gh-comment-id:1283744289 --> @jdelker commented on GitHub (Oct 19, 2022): I figured, that disabling/enabling the floccus extension does recover the problem! Sync starts directly after that and completes successfully after roughly 1min.
Author
Owner

@jdelker commented on GitHub (Nov 3, 2022):

@marcelklehr: I see this is still tagged as "waiting for more information". Is there anything I can provide for this to continue?
If you believe, that I described a totally different scenario - for the same problem observation - let me know, and I open a new issue for that.

<!-- gh-comment-id:1302229771 --> @jdelker commented on GitHub (Nov 3, 2022): @marcelklehr: I see this is still tagged as "waiting for more information". Is there anything I can provide for this to continue? If you believe, that I described a totally different scenario - for the same problem observation - let me know, and I open a new issue for that.
Author
Owner

@jdelker commented on GitHub (Nov 3, 2022):

Just an idea:
May it be possible that Floccus is just trapped within a WebDAV request, that - for what ever reason - did not receive a response and is now basically waiting forever due to a missing timeout?
What logs or stack-dumps could I gather, to find out what Floccus is waiting for?

<!-- gh-comment-id:1302254183 --> @jdelker commented on GitHub (Nov 3, 2022): Just an idea: May it be possible that Floccus is just trapped within a WebDAV request, that - for what ever reason - did not receive a response and is now basically waiting forever due to a missing timeout? What logs or stack-dumps could I gather, to find out what Floccus is waiting for?
Author
Owner

@marcelklehr commented on GitHub (Nov 3, 2022):

If you believe, that I described a totally different scenario

This would be the case, as WebDAV and Nextcloud Bookmarks have to different locking mechanisms. Sorry for the delay.

<!-- gh-comment-id:1302615920 --> @marcelklehr commented on GitHub (Nov 3, 2022): > If you believe, that I described a totally different scenario This would be the case, as WebDAV and Nextcloud Bookmarks have to different locking mechanisms. Sorry for the delay.
Author
Owner

@marcelklehr commented on GitHub (Nov 3, 2022):

ping @lschricke

<!-- gh-comment-id:1302616389 --> @marcelklehr commented on GitHub (Nov 3, 2022): ping @lschricke
Author
Owner

@jdelker commented on GitHub (Nov 18, 2022):

FYI: I've created a new issue for the Nextcloud Bookmarks sync, due to it's possible different nature.
However, I still see a strong similarity.
Despite my previous assumption, that this is more a "locked-client" thing, rather than a central lock-file issue, I have now evidence, that this is indeed related to a central locking problem on the server.

<!-- gh-comment-id:1319864433 --> @jdelker commented on GitHub (Nov 18, 2022): FYI: I've created a new issue for the Nextcloud Bookmarks sync, due to it's possible different nature. However, I still see a strong similarity. Despite my previous assumption, that this is more a "locked-client" thing, rather than a central lock-file issue, I have now evidence, that this is indeed related to a central locking problem on the server.
Author
Owner

@marcelklehr commented on GitHub (Nov 19, 2022):

When floccus appears to be hanging/stuck can you do the following to provide client-side logs while sync is running.

Firefox

  • Go to about:debugging
  • click on debug button next to floccus entry
  • trigger a sync by clicking on sync now for the account of your choice.
  • go back to the inspector window and copy the logs after waiting for the sync to finish

Chrome

  • Go to chrome://extensions
  • enable Developer mode
  • click on dist/html/background.html button in floccus' entry next to "Inspect views: "
  • trigger a sync by clicking on sync now for the account of your choice
  • go back to the inspector window and copy the logs after waiting for the sync to finish
<!-- gh-comment-id:1320887013 --> @marcelklehr commented on GitHub (Nov 19, 2022): When floccus appears to be hanging/stuck can you do the following to provide client-side logs while sync is running. #### Firefox * Go to `about:debugging` * click on `debug` button next to floccus entry * trigger a sync by clicking on `sync now` for the account of your choice. * go back to the inspector window and copy the logs after waiting for the sync to finish #### Chrome * Go to `chrome://extensions` * enable `Developer mode` * click on `dist/html/background.html` button in floccus' entry next to "Inspect views: " * trigger a sync by clicking on `sync now` for the account of your choice * go back to the inspector window and copy the logs after waiting for the sync to finish
Author
Owner

@stale[bot] commented on GitHub (Dec 3, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

<!-- gh-comment-id:1336204249 --> @stale[bot] commented on GitHub (Dec 3, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Author
Owner

@github-actions[bot] commented on GitHub (Dec 12, 2023):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

<!-- gh-comment-id:1851150096 --> @github-actions[bot] commented on GitHub (Dec 12, 2023): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/floccus#832
No description provided.