[debian-mysql] mysql replication issues since security upgrade

Nicholas Bamber nicholas at periapt.co.uk
Mon Mar 26 19:09:59 UTC 2012

	Since oracle have not given details of the security issues it is pure
speculation. However it is not the place I would look given the
complexity of replictaion.

	Things I would look at are:

1.) What backup and recovery procedures are you using? Are you doing
practice runs of the backup and recovery procedure?
2.) Check your replication definitions. Perhaps you have statement level
binary logging and some of the statements are non-deterministic.

I would make sure you have checked on dev.mysql.com for this stuff.

On 26/03/12 14:51, Brent Clark wrote:
> To whom it may concern.
> We have been struggling with MySQL replication, why one node
> continuously crashes, replication has issues.
> On restore, when we make a snapshot of the master, we too get the
> following.
> Mar 26 14:43:54 xyz-web02 mysqld: 120326 14:43:54 [ERROR]
> /usr/sbin/mysqld: Table './db/comm_opens' is marked as crashed and
> should be repaired
> Mar 26 14:43:54 xyz-web02 mysqld: 120326 14:43:54 [Warning] Checking
> table:   './db/comm_opens'
> Mar 26 14:43:54 xyz-web02 mysqld: 120326 14:43:54 [ERROR] 1 client is
> using or hasn't closed the table properly
> What we have identified, is that since about the 9 March, when we
> upgrade due to the following
> http://www.debian.org/security/2012/dsa-2429
> Do you think the two could be related?
> If you can help in anyway, it would be gratefully appreciated.
> Kindest Regards
> Brent Clark
> _______________________________________________
> pkg-mysql-maint mailing list
> pkg-mysql-maint at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint

More information about the pkg-mysql-maint mailing list