Thread:Project:Support desk/1.17.0 won't unlock from read-only mode

Greetings,

I just upgraded out staging mediawiki instance from 1.16.5 to 1.17.0. The upgrade seemed to go fairly well, but it won't come out of read-only mode. The message is this:

'The database has been automatically locked while the slave database servers catch up to the master'

This seems to be from LoadBalancer.php, relating to master/slave database servers. At least, that's the only place I could find this string in the documentation.

The problem is, replication is fully up-to-date. 0 seconds behind master, no obvious failures. Other things are hosted on that database cluster, so if there was some kind of global failure I'd have expected to see it by now.

Mediawiki 1.17.0 PHP 5.2.9 MySQL 5.1.52 (master and slave)

How does LoadBalancer.php check to see if the slave is up-to-date? Is there a way I can run the script manually? If I knew how it was making this decision I might be able to fix it...

Any other ideas?

Thanks, Jake