read-only not being set

[Brad B]

When running mmm_control set_online, writer and reader roles seem to
move correctly, but the read-only variable never gets updated on
either server. So, the reader role still allows writes. I have checked
my grants; and the general query log shows no record of an attempt to
set the read-only variable. Any ideas on why this would happen?

[Brad B]

Here's my config...

# Cluster interface
cluster_interface eth0

# Debug mode
debug io

# Paths
bin_path /usr/local/mmm/bin

# Logging setup
log mydebug
file /usr/local/mmm/var/mmm-debug.log
level debug

log mytraps
file /usr/local/mmm/var/mmm-traps.log
level trap
email ro...@localhost.com

# Email notification settings
email notify
from_address mmm_c...@example.com
from_name MMM Control

# Define roles
active_master_role writer

# MMMD command socket tcp-port
agent_port 9989
monitor_ip 10.10.5.33


# Cluster hosts addresses and access params
host db-node-1
ip 10.10.5.31 0
port 3306
user repmonitor
password repmonitor
mode master
peer db-node-2

host db-node-2
ip 10.10.5.32
port 3306
user repmonitor
password repmonitor
mode master
peer db-node-1

# Define roles that are assigned to the above hosts
# Mysql Reader role
role reader
mode balanced
servers db-node-1, db-node-2
ip 10.10.5.35, 10.10.5.36

# Mysql Writer role
role writer
mode exclusive
servers db-node-1, db-node-2
ip 10.10.5.37

# Replication credentials used by slaves to connect to the master
replication_user repl
replication_password repl

# Checks parameters

# Ping checker
check ping
check_period 1
trap_period 5
timeout 2

# Mysql checker
# (restarts after 10000 checks to prevent memory leaks)
check mysql
check_period 1
trap_period 2
timeout 2
restart_after 10000

# Mysql replication backlog checker
# (restarts after 10000 checks to prevent memory leaks)
check rep_backlog
check_period 5
trap_period 10
max_backlog 60
timeout 2
restart_after 10000
# Mysql replication threads checker
# (restarts after 10000 checks to prevent memory leaks)
check rep_threads
check_period 1
trap_period 5
timeout 2
restart_after 10000

[Tim Soderstrom]

Is 'read_only=1' set in your /etc/my.cnf?

> --
>
> You received this message because you are subscribed to the Google Groups "MySQL Multi Master Manager Development" group.
> To post to this group, send email to mmm-...@googlegroups.com.
> To unsubscribe from this group, send email to mmm-devel+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/mmm-devel?hl=en.
>
>

[Brad B]

It is. A restart of mysql places both nodes in read-only mode.

On Nov 29, 5:22 pm, Tim Soderstrom <t...@moocowproductions.org> wrote:
> Is 'read_only=1' set in your /etc/my.cnf?
>
> On Nov 29, 2009, at 3:20 PM, Brad B wrote:
>
>
>
> > Here's my config...
>
> > # Cluster interface
> > cluster_interface eth0
>
> > # Debug mode
> > debug io
>
> > # Paths
> > bin_path /usr/local/mmm/bin
>
> > # Logging setup
> > log mydebug
> >    file /usr/local/mmm/var/mmm-debug.log
> >    level debug
>
> > log mytraps
> >    file /usr/local/mmm/var/mmm-traps.log
> >    level trap

> >    email r...@localhost.com

>
> > # Email notification settings
> > email notify

> >    from_address mmm_cont...@example.com

[István Pödör]

Hi,

Did you tried show variables like 'read_only' ?

If your mysql server is in read_only mode, super users can still permitted write :)

Are you sure mmm is not setting it to read_only ?

Istvan

[Brad B]

I'm certain.
I'll do a bit more debugging and post my results.
Admittedly, it's quite possible that I've done something wrong...
somewhere.

> > mmm-devel+...@googlegroups.com<mmm-devel%2Bunsubscribe@googlegroups .com>
> > .

> > > > For more options, visit this group athttp://
> > groups.google.com/group/mmm-devel?hl=en.
>

> > --
>
> > You received this message because you are subscribed to the Google Groups
> > "MySQL Multi Master Manager Development" group.
> > To post to this group, send email to mmm-...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > mmm-devel+...@googlegroups.com<mmm-devel%2Bunsubscribe@googlegroups .com>
> > .