Overview
1. Agents are not connected to each other
Check if agents are connected to each other - in job's details see column "Peers connected". If not, please revise network between the agents and ensure that tunnel is actually possible. See this guide for possible reasons for connectivity problem.
In agent UI error ' No connection to tracker" also signals about connectivity problem. If the agent cannot connect to tracker, it won't be able to discover other agents.
The error appears for two possible reasons:
- tracker server process is not running;
- there's no network tunnel between the agent and the configured tracker server.
2. No access to the files
Check system permissions and make sure that on this computer the agent has read-write access to the files and all parenting folders. In job's details check which folders is set up for this agent.
3. Time difference between agents is more than 600 seconds
Agents may be located in different timezones so they rely on UTC timestamps - this must be the same on all agents. Check UTC time on all agents and compare results:
- OS X/Linux in Terminal:
date -u - Windows in Command Prompt:
for /f %x in ('wmic path win32_utctime get /format:list ^| findstr "="') do set %x
Run the command with minimal time lag to get more accurate results for comparing.
4. Files are currently being in use
Close all apps that might be keeping the file and preventing other apps from accessing it.
5. This is a Read-Only share
If a non-synced agent has Read-Only permissions in the job, syncing will stop if a file gets updated on it. Since this is a read-only share, the updated file will not be uploaded. To fix this problem, make sure that in the Profile assigned to this agent's group the "Overwrite any changed files" option is set to YES.
6. This is a low-priority job
If there's a job with higher priority and its being synced, this one will be waiting for its turn. See here for more details on job priority.
If neither of the tips helps, please collect logs from agents and Management Console, and send them to support.
7. No file system notifications
It refers to file updates or newly added files. If these don't sync right after being updated or added to the job folder, most likely the Agent was not notified about them. Perhaps the file system does not support file notifications or the Agent ran out to notify watchers.
Possible solutions:
- increase system notification watchers (see the guide linked above).
- decrease folder rescan interval in the Agent profile.
- rescan the folder manually.
8. Agents are busy with some other operations on files
before transferring files over the network to other Agents, the Agent shall read the files from dis and hash them. For pre-seeded folders, the Agent shall merge folder tree. Look into the Agent's activity tab and see if it's busy reading, hashing the files, or merging folder tree. Seeing an Agent perform this or that operation help better understand what's going on under the hood and evaluate whether or not the job indeed stuck.
For example, in setup with disabled p2p and only one central server, all other Agents will be discovering files' difference between each other only though the central server, which is expected to be slow.