Home › Forums › HAast (High Availability for Asterisk) › Installation & Upgrade › Errors / warnings after sync
-
AuthorPosts
-
I have setup sync of type ‘file’ but I’m getting warnings and errors in the haast log file like this:
Result code ‘0’. Error code ‘5’. Exit code ’10’. Enable debug for further details.
Result code ‘0’. Error code ‘5’. Exit code ‘5’. Enable debug for further details.
I’ve been playing with the settings and I thought I was close but am stuck on the second error message now.
The first error means that the rsync process is not running. Please ensure rsync is installed, running, enabled, and configured as per the HAAst detailed installation guide.
I suspect that you actually solved the first error, since the second error means that rsync is running! But, the second error means that the rsync.haast.secret file has the wrong permissions. Please modify the permissions of this file as follows:
Quote:
chmod 600 /etc/ rsync.haast.secret
After that your sync should work.
A summary of common exit codes and their causes:
- 255 – Likely a connection problem to the remote host. You should be able to resolve this by checking the IP address / fqdn of the remote host.
- 107 – Protocol error or unexpected response. You may have to work with Telium support to trace the cause (if this is intermittent then diagnosing can require many steps)
- 23 – Error during transfer. You should be able to resolve this by checking the file/directory being synced really exists on the source.
- 10 – RSync server unreachable. You should check the ensure the RSync service is running on the remote host, and that the remote host is reachable.
- 5 – RSync file permissions error. You should check to ensure rsync config files holding passwords are mode 600.
The HAAst installation guide provides guidance on how to enable debugging to capture more information. The specific settings, and location of log files, varies by HAAst version. If you need further help capturing and understanding debug information please contact Telium support (you will need an active maintenance agreement for the support team to assist you)
Note that Sangoma made a change to FreePBX in late-2019 (release 1904 or later) that could cause incomplete synchronization or other failure. We recommend that all customers using FreePBX with HAAst upgrade to HAAst version 2.5.9 or later to ensure critical issues are addressed. (Now even tables with invalid structures will sync)
For further details of updates and fixes please see the ‘changelog’ file included with the distribution package.
-
AuthorPosts
- You must be logged in to reply to this topic.