Hi there! I was using Joplin 1.0.16x on Manjaro (Kernel 4.19.81) for a little while and then updated to 1.0.174 after I started experiencing this issue.
Joplin has stopped syncing on Manjaro. There are no issues like this with my smartphone or my old MacBook Pro but when I open the application on Manjaro, it gets stuck on “Created remote items - 1” and syncs for an indefinite amount of time. If I try to “cancel,” it also will be stuck in a “cancel” loop for the duration of the application’s use. I’ve been looking for solutions and having issues, I’m hoping somebody here can help out.
Logs from flags.txt console:
2019-11-15 13:52:36: “Starting Clipper server on port 41184”
/usr/share/joplin/resources/app/app.js:617 Revision: b0c0a48 (master)
I use Dropbox for syncing.
This is likely part of a broader problem of sync being slow on Linux desktops, I imagine if you let Joplin sync it will finish (probably after a few days). You might be able to find more information by searching on the forum.
Solved it! I suspected that the problem was something else, as I’ve had no issue syncing multiple changes with Joplin desktop on Manjaro until sometime in the last couple of weeks. The amount of CPU Joplin begins to eat when it attempts syncing now was also something I’ve never experienced before. I looked through the logs and noticed a point in which the 5-minute autosyncs were met with notification that a sync was already in progress.
Before:
2019-10-29 12:35:42: “Running background sync on timer…”
2019-10-29 12:35:42: “Scheduling sync operation…”
2019-10-29 12:35:42: “Preparing scheduled sync”
2019-10-29 12:35:42: “Starting scheduled sync”
2019-10-29 12:35:43: “TaskQueue.stop: syncDownload: waiting for tasks to complete: 0”
2019-10-29 12:35:43: “TaskQueue.stop: syncDownload: Done, waited for 0”
2019-10-29 12:35:43: "Operations completed: "
2019-10-29 12:35:43: “fetchingTotal: -”
2019-10-29 12:35:43: “Total folders: 93”
2019-10-29 12:35:43: “Total notes: 307”
2019-10-29 12:35:43: “Total resources: 191”
After:
2019-11-02 17:21:40: “Running background sync on timer…”
2019-11-02 17:21:40: “Scheduling sync operation…”
2019-11-02 17:21:40: “Preparing scheduled sync”
2019-11-02 17:21:40: “Starting scheduled sync”
2019-11-02 17:21:40: “Synchronization is already in progress. State: in_progress”
I learned that somehow, Joplin had started uploading as a resource a 20 GB zip file that I had mentioned as part of my notes. I may have drag-and-dropped in order to easily add the filepath and not intended to add the file itself, but I don’t remember for sure:
2019-10-29 17:57:05: “Attaching [20GB].zip”
2019-10-29 17:57:22: “Scheduling sync operation…”
2019-10-29 17:57:26: “Scheduling sync operation…”
2019-10-29 17:57:32: “SearchEngine: Updating FTS table…”
2019-10-29 17:57:32: “SearchEngine: Updated FTS table in 124ms. Inserted: 1. Deleted: 0”
2019-10-29 17:57:46: “Scheduling sync operation…”
2019-10-29 17:57:50: “Scheduling sync operation…”
2019-10-29 17:57:52: “Scheduling sync operation…”
2019-10-29 17:57:56: “SearchEngine: Updating FTS table…”
2019-10-29 17:57:57: “SearchEngine: Updated FTS table in 159ms. Inserted: 1. Deleted: 0”
2019-10-29 17:58:01: “Scheduling sync operation…”
2019-10-29 17:58:11: “SearchEngine: Updating FTS table…”
2019-10-29 17:58:12: “SearchEngine: Updated FTS table in 172ms. Inserted: 1. Deleted: 0”
2019-10-29 17:58:20: “File was attached.”
2019-10-29 17:58:20: “Scheduling sync operation…”
2019-10-29 17:58:30: “SearchEngine: Updating FTS table…”
2019-10-29 17:58:30: “SearchEngine: Updated FTS table in 99ms. Inserted: 1. Deleted: 0”
2019-10-29 17:58:50: “Preparing scheduled sync”
2019-10-29 17:58:50: “Starting scheduled sync”
2019-10-29 18:01:23: “Running background sync on timer…”
2019-10-29 18:01:23: “Scheduling sync operation…”
2019-10-29 18:01:23: “Preparing scheduled sync”
2019-10-29 18:01:23: “Starting scheduled sync”
2019-10-29 18:01:23: “Synchronization is already in progress. State: in_progress”
Not sure how that happened. Some kind of warning or refusal when a file past a certain size gets linked to Joplin would be a pretty useful feature.
Do you mean you’ve accidentally attached a 20GB file? I think if such a file is about to be uploaded there should indeed be a warning in the log.
Yes, apologies, will add an edited excerpt from that into my previous comment. Is there any sort of notification one is meant to receive when an upload of this size is requested?
No, not at the moment. A first step would be to add a warning about it in the log. Eventually maybe we should have something to display these warnings in the UI as notifications.