Telium Support Group

The snooze times for promote/demote for one or both peers is too short.

For each peer, time how long the peer requires to fully promote and fully demote (include pre/post scripts). Then add 5 seconds to each (or more depending on variability of the system performance) and set the promote and demote snooze times accordingly.

Restart HAAst and retry manual failover again. If dual active/standby contention continues then increase the snooze times in steps of 5 seconds and repeat.

Although unusual, this suggests that your FreePBX AstDB is corrupt or incomplete, and FreePBX is missing database entries needed by the dialplan. This can occur if you have installed a buggy FreePBX update, or FreePBX has crashed, etc.

There are four possible ways to correct the Asterisk database.

1. Restore the node from a backup
2. Request that FreePBX regenerate the Asterisk database using this BASH command (after stopping Asterisk). Note that some versions of FreePBX don’t support this command:
   
   curl https://SERVER/freepbx/admin/config.php?type=setup&display=devices&action=resetall

3. Recreate the Asterisk DB manually.
   • Stop FreePBX
   • Delete the /var/lib/asterisk/astdb.sqlite3
   • Start FreePBX
   • Edit & Submit each user
   • Click apply
4. Stop FreePBX on both peers and copy the file /var/lib/asterisk/astdb.sqlite3 from the working peer to the malfunctioning peer. (Be sure Asterisk is stopped on both systems before trying this).

Once corrected, be sure to resolve the underlying FreePBX/configuration/etc issue. As well, ensure that you have set the Asterisk database to synchronize in HAAst’s configuration file.

Error code 5 reflects a non-descript exit condition and is harmless.

In versions of HAAst prior to 2017 a warning with exit code 2 (in the case of MySQL database/table synchronization) means that differences were found between the source and destination tables but they were successfully synchronized. Other exit codes in this context are 0 (success, no differences), 1 (error condition), and 3 (combination of 1 and 2)

In version of HAAst from Jan 2017 onwards exit code 0 always means success (even if differences were found and then synced successfully).

No action is required; this is a normal exit code and indicates synchronization is working. We have notified the author of the library we use in the hope of a more appropriate exit code.

The wrong HAAst package has been installed. HAAst is looking for libraries that are more modern (recent) or old than those offered by your Linux distribution.

If you are sure you downloaded the right HAAst package then try a system wide update using your package manager (eg: “yum update”). Otherwise, return to the Telium web site and download a more suitable HAAst package.

If you don’t see a HAAst package that exactly matches your Linux distribution, try downloading the package for the oldest Linux distribution. The LTS (Long Term Support) versions of versions of Red Hat (eg: v6) and Ubuntu (eg: v12) are usually the best packages to try.

This problem can occur upon initial installation, or after an upgrades (if you deleted the contents of your /usr/local/haast/web_interface directory), and you have configured Apache to require a password when browsing the (virtual) directory. The problem is that your password file was not created (or was deleted during your upgrade). Please review section for 3.4.5 for details, but in summary you can create the
missing password file as follows:

htpasswd -c /usr/local/haast/web_interface/.htpasswd user1

which will also prompt you for a password for the newly created user account named ‘user1’.

Linux is complaining that something is missing. The most likely cause is that you are missing a prerequisite package. HAAst then tries to access a missing operating system library which crashes the program.

If you enabled the HAAst performance database option (writing to MySQL), but you skipped the installation steps involving MySQL drivers then you might see this error. The solution is to repeat/complete the steps in the Detailed Installation Guide relating to MySQL (sections 3.2 and 3.3)

If that’s not it, then recheck each prerequisite package as you likely missed one.

Telium’s engineering group is always interested to gather segfault information – so if you can provide direct SSH access we will take a look. (There is no cost to you, we just want to gather details). A segfault is rare and usually do to Linux prerequisites missing or misconfigured, but this is a top priority for our engineering team.

Enterprise users often attach the management interface of SecAst to an IP on a management VLAN, and access to the management VLAN is restricted. So with this setup administrators don’t want another level of authentication – so we leave it off by default.

However, if you would like to enforce authentication on the SecAst web GUI, you can add a username and password using the steps outlined in section 2.3.5 of the installation guide (Secure the Web Interface). I’ll repeat the Linux command here to save you from digging out the manual:

htpasswd -c /usr/local/secast/web_interface/.htpasswd user1

The above line will create username ‘user1’ and then prompt for a password to be associated with the username. After that the web GUI will require authentication to view the web page.