1) could you please be more specific as to why do you think that
loading wsrep provider makes it ignore all accounts except local root?
2) note that the joining node must have the same user privileges as the
first one, and these privileges should allow:
- root connection from any potential node of the cluster to any
other potential node (that is, in your case, first->second and
second->first)
- root connection from localhost to localhost
and all these accounts should have the same password.
This should be verified before you're even try to join a cluster. Just
start two standalone servers and test root access back and forth.
3) if the above does not work, try setting skip_name_resolve=ON and use
IP addresses
4) use 'rsync' SST, but that requires setting wsrep_provider and
wsrep_cluster_address on startup.
Regards,
Alex
--
Alexey Yurchenko,
Codership Oy, www.codership.com
Skype: alexey.yurchenko, Phone: +358-400-516-011
I can't reproduce that.
--no-defaults turns off reading any configuration files, not just
wsrep_provider variable.
How about
a) comment out only wsrep_provider option in your config files ant try
again.
b) try mysqld --no-defaults
--wsrep_provider=/usr/lib/galera/libgalera_smm.so
> 2) I have made accounts in both nodes that have all the privileges
> and
> same user/pass for any host.
>
> 3) I will try that and get to you.
>
> 4) I had set rsync at some point and the server refused to even open
> a
> mysql socket for some reason.
Understandably rsync must happen before storage engines initialization,
so, if it fails, server quits uninitialized, without even creating a pid
file. So you can login to server only AFTER it has successfully
connected and transferred state. And that's why you have to set
wsrep_cluster_address in my.cnf or on command line. It is too late to
set it up from client.
Need to check error log as to why it failed.
--
So,
1) you have a problem in your configs and you must figure it out before
you continue. I'd suspect wrong datadir setting which points to a
database directory with wrong privileges.
2) 'Unknown command' is expected: you specified provider, but have not
connected to any service/cluster (wsrep_cluster_address unset). So most
SQL commands are turned off until you do so.
--
agent_smith <awar...@gmail.com> wrote:
>--
>You received this message because you are subscribed to the Google Groups "codership" group.
>To post to this group, send email to codersh...@googlegroups.com.
>To unsubscribe from this group, send email to codership-tea...@googlegroups.com.
>For more options, visit this group at http://groups.google.com/group/codership-team?hl=en.
>
Glad to hear that.
> Do you have a deb of mysql 5.5 patched ?
Nope :( . There are some unresolved issues still (e.g. there are still
no official client/shared DEBs). But I believe you should be able to use
a binary tarball on Debian-based ssytems.
> Also are there any plans for percona-server patches ?
That's a question to Percona:
http://www.mysqlperformanceblog.com/2011/10/03/percona-server-5-5-15-galera-21-1-beta2/
But I'd wait for a more fresh release. Beta2 was still buggy.
Regards,
Alex
--