<div dir="ltr">Thanks Mike, I will put these parameters to false.<div><br></div><div>Luis, they are in the same LAN.</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2014-12-17 21:19 GMT-03:00 Luis Daniel Lucio Quiroz <span dir="ltr"><<a href="mailto:luis.daniel.lucio@gmail.com" target="_blank">luis.daniel.lucio@gmail.com</a>></span>:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">are your servers in same LAN or they are in the " cloud " ?<br>
<br>
2014-12-17 17:08 GMT-05:00 Michael Jerris <<a href="mailto:mike@jerris.com">mike@jerris.com</a>>:<br>
<div class="HOEnZb"><div class="h5">> from switch.conf.xml<br>
><br>
><br>
> <!-- The system will create all the db schemas automatically, set this<br>
> to false to avoid this behaviour --><br>
> <!-- <param name="auto-create-schemas" value="true"/> --><br>
> <!-- <param name="auto-clear-sql" value="true"/> --><br>
><br>
><br>
><br>
> On Dec 16, 2014, at 3:57 PM, Federico Castro <<a href="mailto:fcastelco@gmail.com">fcastelco@gmail.com</a>> wrote:<br>
><br>
> Hi Eliot and all, I keep on working in my HA solution. I'm almost done but<br>
> there are some things I would like to improve. When I finish it I will share<br>
> my solution with the community.<br>
><br>
> I have two FS Boxes with Postgres running locally. Psql is running in<br>
> read-write mode in Master node and in read-only mode in Slave. Psql is<br>
> streaming data asynchronously through nodes.<br>
><br>
> First thing I would like to improve:<br>
><br>
> FS try to DROP some tables and delete records from sip_registrations,<br>
> channels, etc. when connecting to psql and if it fails mod_sofia stops<br>
> loading. This behaviour produces (in my scenary) that FS in Slave server<br>
> does not start properly If it connects to local database because it is in<br>
> read-only mode.<br>
> To solve this I configured FS to connect to psql through virtual IP (it is<br>
> always in Master node) then mod_sofia starts properly in Slave node. The<br>
> problem here is that FS in slave node delete records from table in Master<br>
> node when get connected.<br>
><br>
> Is there any way to start FS in a "standby mode" in slave node to avoid it<br>
> trying to write database?<br>
><br>
> Thanks!<br>
><br>
><br>
><br>
> 2014-06-16 12:05 GMT-03:00 Federico Castro <<a href="mailto:fcastelco@gmail.com">fcastelco@gmail.com</a>>:<br>
>><br>
>> Hi Eliot, thanks for your verbose response, it is really useful for me.<br>
>><br>
>> I'm working on a duplicated FS + postgreSQL schema. The two boxes will<br>
>> have same HW. Both of them will run FS and postgreSQL. One will act as<br>
>> master and the other one as stand-by waiting for the first to fail.<br>
>><br>
>> FS will not have more than a hundred simultaneous calls.<br>
>><br>
>> I will read about Pacemaker and Corosync and I will update to the list<br>
>> about the implementation.<br>
>><br>
>> Thanks again.<br>
>><br>
>><br>
>><br>
>> 2014-06-13 10:45 GMT-03:00 Eliot Gable <<a href="mailto:egable%2Bfreeswitch@gmail.com">egable+freeswitch@gmail.com</a>>:<br>
>>><br>
>>> On Tue, Jun 10, 2014 at 10:56 AM, Federico Castro <<a href="mailto:fcastelco@gmail.com">fcastelco@gmail.com</a>><br>
>>> wrote:<br>
>>>><br>
>>>> Hi all, I'm working on a Freeswitch HA solution. Now I'm deciding what<br>
>>>> method and DB I'll use to track calls.<br>
>>>><br>
>>>> I have installed PostgreSQL on both servers and I configured them to<br>
>>>> replicate DB asynchronously.<br>
>>>><br>
>>>> I would like to know if someone has experience with this kind of<br>
>>>> solution and what things do I have to contemplate to deploy a solid<br>
>>>> solution.<br>
>>>><br>
>>><br>
>>> Lots of people have experience with such a solution; it all depends on<br>
>>> what you are trying to achieve.<br>
>>><br>
>>> Personally, I recommend you setup Corosync and Pacemaker both on your<br>
>>> PostgreSQL boxes and on your FreeSWITCH systems. I also recommend you run<br>
>>> PostgreSQL on a separate set of boxes from FS. Both can use a lot of memory<br>
>>> if you are running a lot of calls and/or have a lot of clients. If you need<br>
>>> performance, I recommend using the fastest disks you can get in the<br>
>>> PostgreSQL systems. Also install as much RAM as you can afford for the<br>
>>> project in the PGSQL boxes. You will want redundant power supplies in each<br>
>>> system with each supply plugged into a different circuit. You will also want<br>
>>> redundant Ethernet connectivity to redundant switches which also have<br>
>>> redundant power supplies. You will also want redundant cross-over<br>
>>> connections between the pairs of boxes.<br>
>>><br>
>>> Once you have Corosync and Pacemaker configured to start PGSQL and FS on<br>
>>> their own boxes and you have tested manual fail-over, then you need to start<br>
>>> thinking about every possible way you can make either of those two systems<br>
>>> stop working. Think about hard drives failing, power loss, kernel panics,<br>
>>> firewall rules blocking communication, someone accidentally removing the IP<br>
>>> address from one of the systems (it happens), killing processes, Sofia<br>
>>> profiles failing to load because something else is using the port, etc. Make<br>
>>> sure you have things set up to detect and recover from any such failure. One<br>
>>> of the best ways to do this is to actually build an external testing system<br>
>>> which places real calls through the system and has them route back to itself<br>
>>> to verify they made it. If it places a call and the call does not make it<br>
>>> back to itself, then you know something failed and you can run more tests to<br>
>>> determine what failed and reset it.<br>
>>><br>
>>> Like I said, it all depends on what you are trying to accomplish. If you<br>
>>> want really good automatic HA, you have to go to some pretty great lengths<br>
>>> to get it. If you are OK with occasional manual intervention, then you can<br>
>>> make some assumptions (like nobody accidentally removing your IP from the<br>
>>> interface or telling it to stop responding to ARP or throwing up a firewall<br>
>>> rule which blocks something). That makes the setup considerably easier, but<br>
>>> it also means manual intervention when something like that happens. In other<br>
>>> words, if something like that happens, you experience an outage which the HA<br>
>>> system doesn't detect and recover from. When you get calls that service<br>
>>> stopped working, you then have someone log in and take a look and manually<br>
>>> fix the issue. This could take anywhere from 5 minutes to an hour or more to<br>
>>> do, depending on how good your support is and how good your team is.<br>
>>><br>
>>> So, probably the first task you should do is list all the things you want<br>
>>> it to automatically recover from and all the things you are willing to<br>
>>> accept causing an outage and then work on your implementation based on that<br>
>>> plan.<br>
>>><br>
>>><br>
>>><br>
>>> _________________________________________________________________________<br>
>>> Professional FreeSWITCH Consulting Services:<br>
>>> <a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>
>>> <a href="http://www.freeswitchsolutions.com" target="_blank">http://www.freeswitchsolutions.com</a><br>
>>><br>
>>> FreeSWITCH-powered IP PBX: The CudaTel Communication Server<br>
>>> <a href="http://www.cudatel.com" target="_blank">http://www.cudatel.com</a><br>
>>><br>
>>> Official FreeSWITCH Sites<br>
>>> <a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
>>> <a href="http://wiki.freeswitch.org" target="_blank">http://wiki.freeswitch.org</a><br>
>>> <a href="http://www.cluecon.com" target="_blank">http://www.cluecon.com</a><br>
>>><br>
>>> FreeSWITCH-users mailing list<br>
>>> <a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
>>> <a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
>>> UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
>>> <a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
>>><br>
>><br>
> _________________________________________________________________________<br>
> Professional FreeSWITCH Consulting Services:<br>
> <a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>
> <a href="http://www.freeswitchsolutions.com" target="_blank">http://www.freeswitchsolutions.com</a><br>
><br>
> Official FreeSWITCH Sites<br>
> <a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
> <a href="http://confluence.freeswitch.org" target="_blank">http://confluence.freeswitch.org</a><br>
> <a href="http://www.cluecon.com" target="_blank">http://www.cluecon.com</a><br>
><br>
> FreeSWITCH-users mailing list<br>
> <a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
> <a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
> UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
> <a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
><br>
><br>
><br>
> _________________________________________________________________________<br>
> Professional FreeSWITCH Consulting Services:<br>
> <a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>
> <a href="http://www.freeswitchsolutions.com" target="_blank">http://www.freeswitchsolutions.com</a><br>
><br>
> Official FreeSWITCH Sites<br>
> <a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
> <a href="http://confluence.freeswitch.org" target="_blank">http://confluence.freeswitch.org</a><br>
> <a href="http://www.cluecon.com" target="_blank">http://www.cluecon.com</a><br>
><br>
> FreeSWITCH-users mailing list<br>
> <a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
> <a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
> UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
> <a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<br>
_________________________________________________________________________<br>
Professional FreeSWITCH Consulting Services:<br>
<a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>
<a href="http://www.freeswitchsolutions.com" target="_blank">http://www.freeswitchsolutions.com</a><br>
<br>
Official FreeSWITCH Sites<br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<a href="http://confluence.freeswitch.org" target="_blank">http://confluence.freeswitch.org</a><br>
<a href="http://www.cluecon.com" target="_blank">http://www.cluecon.com</a><br>
<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</div></div></blockquote></div></div>