Hi,
Verify this for the user you specified in option mysql-check:
select plugin from mysql.user where user='monitor' \G
*** 1. row ***
plugin: sha256_password
1 row in set (0.00 sec)
If you see sha256_password, it won't work.
Since password
On 06/18/2013 09:29 AM, Jayadevan M wrote:
[...]
CREATE USER monitor@haproxy_ip IDENTIFIED WITH
'mysql_native_password';
Verify it is working by doing:
select plugin from mysql.user where user='monitor' \G
*** 1. row ***
plugin:
Did you change authentication plugin to make it work ? If this is due to auth
plugin, we definitely need to update the documentation.
I did. But that did not help. So I used latest version of HAProxy. That worked.
This is the status now -
mysql select distinct user,HOST,plugin from mysql.user
Ok so it looks like changes i made a while ago to support mysql =5.5,
must be ok since haproxy 1.4.16 :
http://git.1wt.eu/web?p=haproxy.git;a=commitdiff;h=212f778d6
Regards,
Hervé.
On 06/18/2013 12:01 PM, Jayadevan M wrote:
Did you change authentication plugin to make it work ? If this is due
Hello,
It is due to the plugin and it should be document IMHO (or even fixed,
although not much benefit from it):
haproxy[8258]: Server testback_mysql/localmysql-1 is UP, reason: Layer7
check passed, code: 0, info: 5.6.11-rc60.3, check duration: 0ms. 1
active and 0 backup servers online. 0
Hello all,
I am using HAProxy for MYSQL failover. It is a MySQL master-slave replication
environment. When master is UP, all reads and writes go to master. In case the
master is down, reads and writes will go to the slave. Once the master is down
and HAProxy redirects all reads/writes to the
Hello,
There is no nice way of doing this in HAproxy that would show you that
the server is down (in the Web GUI for example). You can only check
where the traffic is going using the socket or the Web GUI and if the
failover occured you will see traffic going to the 'backup' server.
If you are
Hi,
There was a nice tutorial at
http://www.alexwilliams.ca/blog/2009/08/10/using-haproxy-for-mysql-failover-and-redundancy/
But instead of doing such complex things, please try if galera cluster
for mysql is suitable for you.
cheers
thomas
On 06/18/13 13:51, Nenad Merdanovic wrote:
Hello,
Hi!
I moved to the latets version of HAProxy and now it is working.
Jayadevan, can you tell us what version you are running (which works)
and what release you where using before? Just double checking that
commit 212f778d6 fixed that problem ...
I did. But that did not help. So I used
Steve,
Thank you. Is this for certain or are you making an educated guess?
It is certain, HAProxy does not support udp traffic which will be used for
Multicast.
I do see that there are ways to LB multicast traffic in general but
nothing about HA Proxy being able to so I suspect this is
Hello
HAProxy 1.5-dev18 seems to log the same message twice when log global
is specified in the defaults section, and again in a frontend section.
Here are the relevant extracts from our haproxy.cfg:
global
log 127.0.0.1 local4
log
Thanks John.
I suspected as much but thanks for the clarification. I'll keep
digging/testing.
-Steve
Hello Lukas,
Yes, the plugin was introduced in 5.6.6 as seen on [1]. I have uploaded
the .cap file (tcpdump -A -r capture.cap) to
http://nimzo[dot]info/files/capture{dot}cap
I don't think it is worth the effort as sha256 is used for password auth
and HAproxy doesn't do that. Further, using
Is there a good way to handle SSL and non-ssl on the same port, with ssl
handled by HAProxy
I can do ex:
frontend maybessl
bind *:443
bind localhost:1443 ssl crt example.pem
acl client_hello req_ssl_hello_type 1
use_backend ssl if client_hello
default_backend clear
Hi,
We are seeing a fair amount of 'SSL handshake failure' errors in our log,
and we are running HAProxy 1.5-dev18.
The pattern of errors is:
Jun 17 20:00:28 localhost.localdomain haproxy[26060]: 68.xxx.xx.216:56030
[17/Jun/2013:20:00:28.002] public/2: SSL handshake failure
The following are
Hi!
I gave the new set-tos option a try, and I noticed two things:
- addr.to.ss_family is never AF_INET, addr.from.ss_family is what we are
looking for (after this change, it works for IPv4)
- the IPv6 related part is missing (TOS/DSCP has the same meaning in IPv6
than in IPv4, so if
Hi Merton!
don't forget to CC the mailing-list :)
Out of the 5 possible causes you listed, we probably can't do much
about the other ones. But we can control the above two from our end. I
suppose that most 'modern' browsers nowadays should be able to do TLS
v1.0, and SSLv3 is considered as
Hi,
Jayadevan, can you tell us what version you are running (which works) and
what release you where using before? Just double checking that commit
212f778d6 fixed that problem ...
Initial - HA-Proxy version 1.4.9 2010/10/28
Now - HA-Proxy version 1.4.24 2013/06/17
I guess you had to do both
18 matches
Mail list logo
