Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When a remote server is renamed to a new domain, that server's sites also need the db_host value in sites/example.com/drushrc.php changed. This will then update the db_host value in the vhost.
We believe this was causing a mysql connection error:
PDOException: SQLSTATE[HY000] [1129] Host 'old.name.com' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts' in lock_may_be_available() (line 167 of /var/aegir/platforms/prod/drupal-7.10-1.3/includes/lock.inc).
Comments
Comment #1
Steven Jones CreditAttribution: Steven Jones commentedGood point, maybe we should pick up that the verify task has just renamed the server, and re-verify any sites that use it as a DB server.
Comment #2
ergonlogicIs this still an issue in Aegir 3.x?
Comment #3
helmo CreditAttribution: helmo commentedNot sure what the status is, but #2072267: Change site database password? might have some usefull hints.
Comment #4
colanJust ran into this myself so it's still an issue. I was renaming the DB from
db.staging
todb.staging.example.com
, where the former no longer resolves. Here's the error for findability:To fix manually for each site (after editing and saving the DB server node):
drushrc.php
.drush @staging.example.com provision-verify
.On the DB server, you then need to run the following: