Hi list,
I have an issue with HA configuration (Mysql Backend).

When I crash master Freeswitch, I try to recover my call (2 legs) in the slave server (same behavior if I recover in the same server "master to master").

TEST 1:
Master (crash) --> Slave (recovery)

TEST 2:
Master (crash) --> restart freeswitch in master --> Master (recovery)

I can recover only one leg, but I can see two legs in recovery table's Mysql.

Before crash:

Recovery table with one call:

mysql> select runtime_uuid, technology, profile_name, hostname, uuid from recovery;
+--------------------------------------+------------+--------------+----------+--------------------------------------+
| runtime_uuid                         | technology | profile_name | hostname | uuid                                 |
+--------------------------------------+------------+--------------+----------+--------------------------------------+
| 8b5a6b6c-adbe-11e3-b273-e98376048298 | sofia      | internal     | asbc2    | 952054fe-adbe-11e3-b291-e98376048298 |
| 8b5a6b6c-adbe-11e3-b273-e98376048298 | sofia      | external     | asbc2    | 951e4b64-adbe-11e3-b276-e98376048298 |
+--------------------------------------+------------+--------------+----------+--------------------------------------+
2 rows in set (0.00 sec)


After crash:

Linux screen:
[root@asbc2 conf]# /usr/local/freeswitch/bin/fs_cli -x 'sofia recover'
Recovered 1 call(s)

fs_cli screen:
2014-03-17 11:23:56.492759 [WARNING] switch_core_sqldb.c:2715 Invalid cdr data, call not recovered


mysql> select runtime_uuid, technology, profile_name, hostname, uuid from recovery;
+--------------------------------------+------------+--------------+----------+--------------------------------------+
| runtime_uuid                         | technology | profile_name | hostname | uuid                                 |
+--------------------------------------+------------+--------------+----------+--------------------------------------+
| acba00a6-adbe-11e3-8380-19442cf25656 | sofia      | internal     | asbc2    | 952054fe-adbe-11e3-b291-e98376048298 |
+--------------------------------------+------------+--------------+----------+--------------------------------------+
1 row in set (0.00 sec)



Freeswitch's configuration:

Version:
FreeSWITCH Version 1.5.8b+git~20140214T000311Z~fe2a4d6d47~64bit (git fe2a4d6 2014-02-14 00:03:11Z 64bit)

Both Profiles:
<param name="track-calls" value="true"/>
<param name="odbc-dsn" value="freeswitch:u_freeswitch:XXXXXXXX"/>

Switch.conf.xml:
<param name="core-db-dsn" value="freeswitch:u_freeswitch:XXXXXXXXXXXX" />
<param name="core-recovery-db-dsn" value="odbc://freeswitch:u_freeswitch:XXXXXXXXXXXXX"/>


odbc.ini:
[freeswitch]
Driver          = /usr/lib64/libmyodbc5-5.1.5.so
SERVER          = localhost
PORT            = 3306
DATABASE        = freeswitch
OPTION          = 67108864
USER            = u_freeswitch
PASSWORD        = XXXXXXXXXX


odbcinst.ini:
# Driver from the mysql-connector-odbc package
# Setup from the unixODBC package
[MySQL]
Description = ODBC for MySQL
Driver      = /usr/lib/libmyodbc5.so
Setup       = /usr/lib/libodbcmyS.so
Driver64    = /usr/lib64/libmyodbc5.so
Setup64     = /usr/lib64/libodbcmyS.so
FileUsage   = 1
UsageCount  = 1
Threading = 0
Debug   = 1
MaxLongVarcharSize = 65536



Have you an idea with this issue ? Issue is due to beta version ?

Thanks in advance.


--
Cordialement

HUBERT Mickaël
Ingénieur VOIP - Hexanet