Issue: async 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 one below.

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.