Telium Support Group

The error you are seeing in the Asterisk CLI is due to an app not properly handling concurrent use of the AstDB (SQLite 3 database). When synchronizing the AstDB HAAst will briefly lock the database (with a SQL lock), at which point apps should queue their commands until the lock is released.

Most properly designed apps respect concurrency by checking for the lock, then either blocking or retrying for a period of time, to acquire the lock. An overly simplistic application might not check for a lock, and simply report an error (“database is locked”) following an attempt to write. We have seen this error before with FreePBX and a couple of open source Asterisk add ons.

Although the proper solution involves asking the app developer to correct their code, we realize that some developers have no interest in doing so (or become hostile if you suggest anything is wrong with their code). So until the developer in question fixes their code, we do offer a workaround.

Create an Asterisk pre-start event handler (/usr/local/haast/events/asterisk.start.pre) in HAAst containing the following code:


#!/bin/bash
sqlite3 /var/lib/asterisk/astdb.sqlite3 “PRAGMA journal_mode=wal”;


This will enable the “WAL” feature of SQLite3 – which effectively prevents reader and writer processes from locking each other out of the database. You can also issue this command from any bash prompt and you should see the response “wal”. If you don’t see this respnose, repeat the command every 10 seconds until “wal” is returned. (The command can fail if the database is already locked).

You can download the products directly from our website (without the need for a key/link). The “Free” edition you can download directly actually turns into the “Commercial” edition once you add a license file.

You can request your license files at any time, after you have installed the product. Once the product is installed and running, you must telnet to the built-in telnet server and there you must enter the command “license request”.

Answer the questions presented on screen, and then send the resulting license request file to support@telium.io (you will see more instructions on the telnet screen). In response you will get a license file (and optionally a USB dongle depending on the activation options you chose onscreen) from the Telium support team.

For more information on activation options see

Yes you can! Like your other syncjobs, setup a new syncjob which requires the remotestate be ‘asterisk running’, localstate as ‘asterisk stopped’. Then set the syncjob to sync a single file:

/tmp/secast.state

Your tertiary PBX will always pull the latest security data from the active PBX. And if the tertiary promotes, there is no risk overwriting the local security data because of the localstate requirement.

PBXSync is designed to handle a mix of internal and external hosts. When you setup your pbxsync.conf file, you will notice that the rsync and MySQL IP address entries allow for up to 3 IP addresses. These three addresses represent:

1. Public IP – this is the IP address that PBXSync will publish to other PBXSync hosts not on your local subnet.
2. Private IP – this is the IP address that PBXSync will publish to other PBXSync hosts on your local subnet.
3. Local IP – this is the IP address that PBXSync uses when connecting to itself.

So for the Public IP use the IP address of your firewall, and for your Private IP use the internal (non-routable) IP address of an internal host. The local IP should probably be set to ‘localhostipv4’. Also be sure to set the localsubnets setting to match your internal network(s).

Next, on your firewall setup porting mapping from the public IP address to the internal private IP addresses & port. After that the external host will be able to reach the internal host as well.

In some (particularly recent) Asterisk versions quotes are considered just another character in the value of a setting. So

Quote:
secret=ABC

and

Quote:
secret=”ABC”

are different. Please remove quotes the credential setting values in your Asterisk /etc/asterisk/manager.conf file and restart the HAAst services.

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)

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.