Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data loss on non-phone node when switching wifi<->celluar with phone #50

Closed
firecat53 opened this issue Jun 30, 2014 · 1 comment
Closed

Comments

@firecat53
Copy link

I don't have logs for you yet...please let me know what/how to collect from the phone and computer.

Setup

1 linux server running Syncthing 0.8.17, 1 Verizon Razr MAXX stock Android 4.4, latest version 0.4 (also happened with previous version). Server is on wired ethernet through a consumer router with Comcast cable connection. 1 shared repository with about 2100 files and 1.45 GB, mostly wallpaper images.

I also have another node on a Linux laptop with the same repository but only connected to the server, not the phone. It works fine syncing with the server no matter what combination of VPN and wifi changes I subject it to. It doesn't appear to be relevant to the problem (problem happens even with the laptop disconnected)

Problem

The phone, mostly when switching back to wifi after being on celluar data for some time, will apparently communicate somehow with the server node, leaving the server node with the impression that it needs to delete a whole bunch of files. The repo on the phone stays correct, and the server will start re-syncing it's repo from the phone after a time. There doesn't seem to be any pattern as to which or how many files get deleted before it stops. It appears that the global repository for the server somehow becomes incorrect and causes the file deletions. It sometimes happens while just sitting there with no change in network status, and sometimes I can switch from 4G to Wifi and back again on the phone with no problems at all.

Troubleshooting

  1. Took the laptop node out of the picture. No effect
  2. Tried increasing the sync time on the phone from 60 to 120 seconds. No effect
  3. Tried changing ownership of the files on the server (there was a mix of two different UIDs). No effect
  4. Upgraded to 0.4 from the 0.3.8 version on the phone. No effect
  5. Ran just the server and laptop nodes without the phone node for over 24 hours, with numerous wifi/VPN changes on the laptop and files added/deleted for testing. Worked great.

Like I said at the top, I'd love to help debug this, but I really don't know what logs you need and how to acquire them (from the phone, at least). Also let me know any other info I can provide.

Thanks,
Scott

@Nutomic
Copy link
Contributor

Nutomic commented Jun 30, 2014

Thanks for the report!

This issue affects the upstream project, could you please post it there?

For logging, see here, or download one of the various adb apps (calmh will have to tell you what exact logs he needs).

@Nutomic Nutomic closed this as completed Jun 30, 2014
@syncthing syncthing locked and limited conversation to collaborators Nov 9, 2018
acolomb pushed a commit to acolomb/syncthing-android that referenced this issue Nov 12, 2023
…thing#52)

Fix unignoring devices and folders
Improve performance of RestApi#getDevices
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants