nvbn / everpad

Evernote client well integrated with linux desktop
1.17k stars 143 forks source link

"Last sync" indicated it was working but it wasn't #297

Open RodBarnes opened 11 years ago

RodBarnes commented 11 years ago

"Last sync" indicates a recent update but new and updated notes have not shown up in Evernote either on the web app or Android. It is now working again. Below are the steps I took to resolve the issue:

I saw that the note I had created yesterday in Everpad did not appear in the Evernote web app. I checked my Android Evernote and it wasn't there, either. I clicked on "Last sync" to force a sync. After it completed, I checked again and still nothing had appeared.

I then checked my settings in the Evernote Web app and found that there were two authorizations for Everpad - one on 2013-03-10 and one on 2013-03-14. This appeared to be significant because, checking through my notes, nothing had been updated since about 2013-03-10 or thereafter. I saved every new and updated note to a separate text file (fortunately, there were not a lot of them). I then removed both authorizations from Evernote settings and removed the authorization (Settings & Management) in Everpad.

I then went back in and reauthorized Everpad (Settings & Managment) and confirmed that Evernote web settings reflected a new authorization made today (2013-03-29). However, Everpad was still showing "Wait, first sync in progress" after 30 minutes and it has not taken that long at any other time. So, I assumed it wasn't working.

I did a "apt-get purge everpad*", restarted Ubuntu, reinstalled (apt-get install everpad). It came up with the "Please perform first sync" option so I took that and it appears to be syncing. I did several tests using an auto sync time of 5 minutes with both new notes and updated notes and I then did some tests with forcing a manual sync which were also successful.

I'll continue to monitor this situation to see if it reappears.

duizendnegen commented 11 years ago

I am having similar problems, where killing and restarting (killall everpad-provider everpad) solves my problems. I have not gotten around to reproduce it or post command-line traces, though.