Hi,
are you sure the mysql server on 10.14.11.2 is configured to listen on a
network interface (and not only on local host) ? check on the
10.14.11.2 with netstat -tlnp | grep mysqld and see if mysql is
listed as TCP listener.
Regards,
Bogdan
agung nugroho wrote:
Krunal Patel
Bogdan-Andrei Iancu bog...@... writes:
Hi,
are you sure the mysql server on 10.14.11.2 is configured to listen on a
network interface (and not only on local host) ? check on the
10.14.11.2 with netstat -tlnp | grep mysqld and see if mysql is
listed as TCP listener.
Regards,
agung nugroho wrote:
Bogdan-Andrei Iancu bog...@... writes:
Hi,
are you sure the mysql server on 10.14.11.2 is configured to listen on a
network interface (and not only on local host) ? check on the
10.14.11.2 with netstat -tlnp | grep mysqld and see if mysql is
listed as TCP
Krunal Patel krunal.li...@... writes:
HiThanks for your help.I have installed mysql-proxy.I have tested it for
failover.It seems working.Thanks again..Krunal Patel
Hi krunal Patel,
I was read your post about failover of mysql. I still dont understand it.
Actually my need is to connect
Hi
Thanks for your help.
I have installed mysql-proxy.
I have tested it for failover.
It seems working.
Thanks again..
Krunal Patel
On Thu, Nov 27, 2008 at 1:33 PM, Uwe Kastens [EMAIL PROTECTED] wrote:
Hi,
As far as I know this problem is fixed in MySQL5 - but I am not sure
about ...
Before doing this, I'd seriously consider the problems associated with
master-master replication.
um, I don't know what they are.. but I know they are real problems. Such as
collisions in auto-incrementing data.
-Brett
On Wed, Nov 26, 2008 at 3:06 PM, Uwe Kastens [EMAIL PROTECTED] wrote:
Hi
Try use this settings:
On master
auto_increment_increment = 2
auto_increment_offset= 0
On slave
auto_increment_increment = 2
auto_increment_offset= 1
This makes sure that auto-increments do not colide between master and
slave so you can achieve switchover without conflicts because
-Users] Help!! How to do failover of mysql connection
That will not work. Try DNS SRV. Take a look at this link
http://www.zytrax.com/books/dns/ch8/srv.html
Hope it helps.
Pablo
On Tue, Nov 25, 2008 at 2:51 AM, Krunal Patel [EMAIL PROTECTED]
wrote:
Hi,
is it fine if I use DSN resolver?
Let me
:
[EMAIL PROTECTED] *On Behalf Of *Pablo Hernan Saro
*Sent:* Tuesday, November 25, 2008 8:04 AM
*To:* Krunal Patel
*Cc:* users@lists.opensips.org
*Subject:* Re: [OpenSIPS-Users] Help!! How to do failover of mysql
connection
That will not work. Try DNS SRV. Take a look at this link
http
This problem has been solved many times. The absolute most bomb-proof
MySQL failover solution involves a combination of DRBD and Linux HA
(Heart Beat). The replication model has too many issues IMO.
On Sun, Nov 23, 2008 at 9:10 AM, Uwe Kastens [EMAIL PROTECTED] wrote:
Hi Krunal,
* I
Hi,
is it fine if I use DSN resolver?
Let me explain in detail:
I setup a DSN resolver add A record for mysql servers.
mysql A 192.168.1.5
mysql A 192.168.1.6
where 192.168.1.5 192.168.1.6 are mysql cluster nodes.
So mysql.somedomain.com will point to both
Hi Krunal,
* I am having 2 MySql servers. Lets say 192.168.1.5
http://192.168.1.5 192.168.1.6 http://192.168.1.6
* Opensips is at 192.168.1.4 http://192.168.1.4.
* I would like to use 192.168.1.6 http://192.168.1.6 mysql server
for failover.
* I mean to say if
Hi Krunal,
As far as I know, the db_mysql module does not support fail-over. But you
can do it out OpenSIPS.
Search for MySQL proxy (it is what you need, but it stills alpha). Other
possibility is to consider a MySQL cluster and a local replication in the
same machine where OpenSIPS runs -with a
13 matches
Mail list logo
