Troubleshooting Continuous Mode Errors
For instructions on resolving conflicted files in bidirectional Sync sessions, see Resolving Bidirectional Sync File Conflicts.
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:
| Continuous Sync Direction | Supported Sync Client OS | Supported Sync Server OS |
|---|---|---|
| PUSH | Linux, Windows | All |
| PULL | All | Linux, Windows |
| BIDI | Linux, Windows | Linux, Windows |
If that is not possible, you can run Sync as a cron job that detects file system changes with the Aspera Watch Service. For more information, see Starting Aspera Watch Services and Creating Watches.
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).
How to recover: 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