Opened 14 years ago
Closed 14 years ago
#16102 closed defect (bug) (invalid)
"Update Network" sometimes attempts to connect to incorrect database.
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | minor | Version: | 3.1 |
| Component: | Upgrade/Install | Keywords: | |
| Focuses: | Cc: |
Description
On Wordpress 3.1RC2, after installation on a network of sites I went to "update network." We're using domain mapping, but nothing special past that.
This behaved as expected until it reached a site (say, a.com) which global DNS resolves to be elsewhere. The site is currently being developed and once development is completed then we can update global DNS; for the moment, we're DNS spoofing on our local network to access it on our server.
Since we're not DNS spoofing on the server, it tries to connect to the database on the live site (as the webserver resolves it via normal DNS), can't connect, and stops the network update.
One would not expect this behavior - instead it should connect to the same database it used for all the other sites, as specified in wp-config.php.
As a workaround, I was able to deactivate the "a.com" site, do the network upgrade, and then re-activate "a.com" - but cannot upgrade it.
This is normal behavior, as the network upgrade is fired through an HTTP request. You'll want to spoof the DNS (same way you're doing it locally), or run the network upgrade a different way.