Error Troubleshooting

Error returned when you attempt a continuous sync

If you attempt to run a continuous Sync from a client that does not support continuous mode, you receive the following error:

Failed. File system change notification not supported by platform (code=45112)

If you attempt to run a continuous Sync to a server that does not support continuous mode, you receive the following error:

Failed. [PEER} File system change notification not supported by platform (code=45112)

Solution: You must run your Sync session to or from a machine with an operating system that supports continuous mode. See the table below.

Continuous Sync Direction	Supported Sync Client OS	Supported Sync Server OS
PUSH	Linux, Windows	All
PULL	All	Linux, Windows
BIDI	Linux, Windows	Linux, Windows

Error returned when you attempt to monitor a Linux directory in continuous mode

If you attempt to monitor a directory on a Linux system (i.e., you are running async in continuous mode), you might receive the following error:

Failed to set up directory change notification - reached the per-user limit on number of inotify watch descriptors.

Cause: You have exceeded the per-user limit imposed by the OS on the number of directories that may be monitored (i.e., the number of inotify watch descriptors).

Solution: You must modify the kernel parameters on the Linux machine to increase the maximum number of user watches. The following procedure may differ between Linux versions; consult your operating system Administrator's guide for more information.

On the Linux machine, open /etc/sysctl.conf in a text editor and increase the maximum number of user watches. Enter a value that exceeds the maximum number of directories ever expected to exist in the docroot that is monitored by async. For example,

fs.inotify.max_user_watches=1000000

Save your changes and run the following command to load the configuration changes: 

# sysctl -p 

To confirm that the changes have been applied, run the following command:

# sysctl -a | grep max_user_watches  
fs.inotify.max_user_watches=1000000

The Sync client displays failure to start sync error

When the async binary on the remote computer cannot initialize, the async client gets a generic error similar to the following:

Failed to start sync session

Cause: There are several possible causes.

• async binary doesn't exist (or is not in the path and sshd cannot find/execute it).
• async binary cannot be run.
• async binary cannot initialize properly (e.g., if the system is out of memory or socket resources).
• async binary cannot create its log files, if specified with -R (bad path, bad permissions).

Solution: Check your system for the possible causes above.

Error returned when you attempt sync from Linux to Windows.

When you attempt to perform a sync from Linux to Windows, you receive the following error:

Failed. Peer error: Symlink policy copy not supported on Windows peer.

Solution: You must specify -n skip or --symbolic-links=skip when performing the sync.